Skip to content

Commit 8efba1a

Browse files
authored
Merge pull request #108 from ankur325/update-docs-0.7-spec
Updated the documentation
2 parents e9cf860 + 9d05b05 commit 8efba1a

8 files changed

+331
-185
lines changed

docs/cli-help.md

+41-50
Large diffs are not rendered by default.

docs/how-to.md

+44-6
Original file line numberDiff line numberDiff line change
@@ -86,13 +86,13 @@ Here is steps for getting an account:
8686
* You can remember and securely save the mnemonic phrase shown after the key is created
8787
to be able to recover the key later.
8888
* Share generated `address` and `pubkey` with a number of `Trustee`s sufficient for account addition operation.
89-
* One of `Trustee`s proposes to add the account to the ledger: `dclcli tx auth propose-add-account --address=<account address> --pubkey=<account pubkey> --roles=<role1,role2,...> --from=<trustee name>`
89+
* One of `Trustee`s proposes to add the account to the ledger: `dclcli tx auth propose-add-account --address=<account address> --pubkey=<account pubkey> --roles=<role1,role2,...> --vid=<vendorID for vendor role> --from=<trustee name>` (p.s. A vendor role is tied to a Vendor ID, hence while proposing a Vendor Role vid is a required field.)
9090
* Sufficient number of other `Trustee`s approve the proposed account: `dclcli tx auth approve-add-account --address=<account address> --from=<trustee name>`
9191
* Check that the active account exists: `dclcli query auth account --address=<account address>`
9292

9393
Example:
9494
* `dclcli keys add steve`
95-
* `dclcli tx auth propose-add-account --address=cosmos1sug8cquqnn5jddkqt4ud6hcr290sn4wh96x5tv --pubkey=cosmospub1addwnpepqvnfd2f99vew4t7phe3mqprmceq3jgavm0rguef3gkv8z8jd6lg25egq6d5 --roles=Vendor,NodeAdmin --from jack`
95+
* `dclcli tx auth propose-add-account --address=cosmos1sug8cquqnn5jddkqt4ud6hcr290sn4wh96x5tv --pubkey=cosmospub1addwnpepqvnfd2f99vew4t7phe3mqprmceq3jgavm0rguef3gkv8z8jd6lg25egq6d5 --roles=Vendor,NodeAdmin --vid=4563 --from jack`
9696
* `dclcli tx auth approve-add-account --address=cosmos1sug8cquqnn5jddkqt4ud6hcr290sn4wh96x5tv --from alice`
9797
* `dclcli query auth account --address=cosmos1sug8cquqnn5jddkqt4ud6hcr290sn4wh96x5tv`
9898

@@ -259,12 +259,30 @@ The certificate must be signed by a chain of certificates which must be already
259259

260260
Example: `dclcli tx pki add-x509-cert --certificate="----BEGIN CERTIFICATE----- ......" --from=jack`
261261

262-
##### 2. Add a new model info with the given VID/PID
263262

264263

265-
Command: `dclcli tx model add-model --vid=<uint16> --pid=<uint16> --productName=<string> --productLabel=<string or path> --sku=<string>
266-
--softwareVersion=<uint32> --softwareVersionString=<string> --hardwareVersion=<uint32> --hardwareVersionString=<string> --cdVersionNumber=<uint16>
267-
--from=<account>`
264+
##### 2. Add Vendor Info
265+
266+
Add a new vendor contact info.
267+
268+
Role: `Vendor`
269+
270+
Command: `dclcli tx vendorinfo add-vendor --companyLegalName=<string> --companyPreferredName=<string> --vendorName=<string> --vid=<uint16> ----vendorLandingPageURL=<url> --from=<account>`
271+
272+
Flags:
273+
- companyLegalName `string (max64)` - Company Legal Name
274+
- companyPreferredName `optional string (max64)` - Company Preferred Name
275+
- vendorLandingPageURL `optional string (max256)` - Landing Page URL for the Vendor
276+
- vendorName `string (max32)` - Vendor Name
277+
- vid `uint16` - Vendor ID
278+
279+
280+
Example: `dclcli tx vendorinfo add-vendor --companyLegalName="XYZ Technology Solutions" --vid=123 --vendorName="XYZ Inc" --from="jack"`
281+
##### 3. Add a new model info with the given VID/PID
282+
283+
Role: `Vendor`
284+
285+
Command: `dclcli tx model add-model --vid=<uint16> --pid=<uint16> --productName=<string> --productLabel=<string or path> --sku=<string> --softwareVersion=<uint32> --softwareVersionString=<string> --hardwareVersion=<uint32> --hardwareVersionString=<string> --cdVersionNumber=<uint16> --from=<account>`
268286

269287
Flags:
270288
- vid: `uint16` - model vendor ID (positive non-zero)
@@ -301,7 +319,27 @@ Command: `dclcli tx model add-model --vid=<uint16> --pid=<uint16> --productName=
301319

302320
Example: `dclcli tx model add-model --vid=1 --pid=1 --productName="Device #1" --productLabel="Device Description" --sku="SKU12FS" --softwareVersion="10123" --softwareVersionString="1.0b123" --hardwareVersion="5123" --hardwareVersionString="5.1.23" --cdVersionNumber="32" --from=jack --cid=1 --custom="Some Custom information"`
303321

322+
##### 4. Add a new model version for the given VID/PID and Software Version
304323

324+
Command: `dclcli tx model add-model-version --vid=<uint16> --pid=<uint16> --softwareVersion=<uint32> --softwareVersionString=<string> --cdVersionNumber=<uint16> --from=<account>`
325+
326+
Flags:
327+
- vid: `uint16` - model vendor ID (positive non-zero)
328+
- pid: `uint16` - model product ID (positive non-zero)
329+
- softwareVersion: `uint32` - model software version
330+
- softwareVersionSting: `string` - model software version string
331+
- cdVersionNumber `uint32` - CD Version Number of the certification
332+
- firmwareDigests `string` - FirmwareDigests field included in the Device Attestation response when this Software Image boots on the device
333+
- softwareVersionValid `bool` - Flag to indicate whether the software version is valid or not (default true)
334+
- otaURL `string` - URL where to obtain the OTA image
335+
- otaFileSize `string` - OtaFileSize is the total size of the OTA software image in bytes
336+
- otaChecksum `string` - Digest of the entire contents of the associated OTA Software Update Image under the OtaUrl attribute, encoded in base64 string representation. The digest SHALL have been computed using the algorithm specified in OtaChecksumType
337+
- otaChecksumType `string` - Numeric identifier as defined in IANA Named Information Hash Algorithm Registry for the type of otaChecksum. For example, a value of 1 would match the sha-256 identifier, which maps to the SHA-256 digest algorithm
338+
- maxApplicableSoftwareVersion `uint32` - MaxApplicableSoftwareVersion should specify the highest SoftwareVersion for which this image can be applied
339+
- minApplicableSoftwareVersion `uint32` - MinApplicableSoftwareVersion should specify the lowest SoftwareVersion for which this image can be applied
340+
- releaseNotesURL `string` - URL that contains product specific web page that contains release notes for the device model.
341+
342+
Example: `dclcli tx model add-model-version --vid=1 --pid=1 --softwareVersion=20 --softwareVersionString="1.0" --cdVersionNumber=1 --minApplicableSoftwareVersion=1 --maxApplicableSoftwareVersion=10 --from="jack"`
305343
## Test House Instructions
306344
##### 1A. Publish an intermediate or leaf X509 certificate(s) to be used for signing the Certification blob
307345
This step is needed for off-ledger certification use case only, see [use_cases_device_off_ledger_certification](use_cases/use_cases_device_off_ledger_certification.png).

docs/quickStartGuide.adoc

+7-6
Original file line numberDiff line numberDiff line change
@@ -133,21 +133,21 @@ $ dclcli tx auth approve-add-account \
133133
--address=cosmos1pkxl6k9r4r5ng9k6upp3e4f2wt2putq652w693 --from=<trustee-account>
134134
135135
# After account approval, you can submit your product information
136-
$ dclcli tx model add-model --vid=12345 --pid=675463 --name="Disco Ball" \
137-
--productLabel="CHIP Discoball" --sku=A1234GH --softwareVersion="10123" --softwareVersionString="1.0b123" --hardwareVersion="5123" \
138-
--hardwareVersionString="5.1.23" --cdVersionNumber="32" \
136+
$ dclcli tx model add-model --vid=12345 --pid=675463 --deviceTypeID=1 \
137+
--productName="CHIP Discoball" --partNumber=A1234GH
139138
--from=cool-vendor
140139
141140
----
142141

143142
==== Check TestHouse Test Status
144143
[source,bash]
145144
----
146-
$ $ dclcli query compliancetest test-result --vid=2020 --pid=10
145+
$ dclcli query compliancetest test-result --vid=2020 --pid=10 --softwareVersion=20
147146
`{
148147
"result": {
149148
"vid": 2020,
150149
"pid": 10,
150+
"softwareVersion": "20",
151151
"results": [
152152
{
153153
"owner": "cosmos1w3waz79mptxt6wtcdcex74apt42x3y7j2n4v39",
@@ -164,7 +164,7 @@ $ $ dclcli query compliancetest test-result --vid=2020 --pid=10
164164
==== Check Zigbee Certification Status
165165
[source,bash]
166166
----
167-
$ dclcli query compliance certified-model --vid=2020 --pid=10 --certificationType="zb"
167+
$ dclcli query compliance certified-model --vid=2020 --pid=10 --certificationType="matter"
168168
`{
169169
"result": {
170170
"value": true
@@ -180,7 +180,8 @@ $ dclcli query compliance all-certified-models
180180
{
181181
"vid": 2020,
182182
"pid": 10,
183-
"certification_type": "zb"
183+
"softwareVersion": "20",
184+
"certification_type": "matter"
184185
}
185186
]
186187
},

0 commit comments

Comments
 (0)