@@ -10,6 +10,9 @@ control.
10
10
- [ Building the Example Application] ( #building-the-example-application )
11
11
- [ Commissioning and cluster control] ( #commissioning-and-cluster-control )
12
12
- [ Commissioning] ( #commissioning )
13
+ - [ Bypass mode] ( #bypass-mode )
14
+ - [ BLE mode] ( #ble-mode )
15
+ - [ IP mode] ( #ip-mode )
13
16
- [ Cluster control] ( #cluster-control )
14
17
15
18
---
@@ -40,36 +43,99 @@ The CHIP demo application is supported on
40
43
The output image files are stored in
41
44
` out/ameba-amebad-all-clusters/asdk/image ` folder.
42
45
46
+ The bootloader image files are stored in
47
+ ` out/ameba-amebad-all-clusters/asdk/bootloader ` folder.
48
+
43
49
- After building the application, ** Ameba Image Tool** is used to flash it to
44
50
Ameba board.
45
51
46
- 1 . Connect your device via USB and open Ameba Image Tool.
47
- 2 . Select correct serial port and set baudrate as ** 115200** .
48
- 3 . Browse and add the corresponding image files in the Flash Download list to
49
- the correct locations
50
- 4 . Click ** Download** button.
52
+ 1 . Connect your device via USB and open Ameba Image Tool.
53
+ 2 . Select correct serial port and set baudrate as ** 115200** .
54
+ 3 . Browse and add the corresponding image files in the Flash Download list to
55
+ the correct locations
56
+ 4 . Click ** Download** button.
51
57
52
58
## Commissioning and Cluster Control
53
59
54
- ### Commissioning
60
+ ## Commissioning
61
+
62
+ There are three commissioning modes supported by Ameba platform:
63
+
64
+ ### Bypass mode
65
+
66
+ 1 . In "connectedhomeip/config/ameba/args.gni"
67
+
68
+ - set ` chip_bypass_rendezvous = true `
69
+ - Set ` chip_ip_commissioning = false `
70
+ - Set ` chip_use_clusters_for_ip_commissioning = false `
71
+ - Set ` chip_config_network_layer_ble = false `
72
+
73
+ 2 . In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"
74
+
75
+ - Set ` #define CHIP_DEVICE_CONFIG_ENABLE_CHIPOBLE 0 `
76
+
77
+ 3 . Build and Flash
78
+ 4 . Use ATS\$ command to run all-cluster example.
79
+ 5 . Connect to AP using ` ATW0, ATW1, ATWC ` commands
80
+ 6 . Test with
81
+ [ Chip-Tool] ( https://github.com/project-chip/connectedhomeip/tree/master/examples/chip-tool )
82
+ or
83
+ [ Python Controller] ( https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/python_chip_controller_building.md ) .
84
+
85
+ ### BLE mode
86
+
87
+ 1 . In "connectedhomeip/config/ameba/args.gni"
55
88
56
- The commissioning is carried out via WiFi.
89
+ - set ` chip_bypass_rendezvous = false `
90
+ - Set ` chip_ip_commissioning = false `
91
+ - Set ` chip_use_clusters_for_ip_commissioning = false `
92
+ - Set ` chip_config_network_layer_ble = true `
57
93
58
- 1 . After download all-cluster example to Ameba board, boot up the board by
59
- pressing the reset button.
60
- 2 . Use ATW commands to setup network.
61
- 3 . Use ATS\$ command to run all-cluster example.
62
- 4 . Use
63
- [ standalone chip-tool] ( https://github.com/project-chip/connectedhomeip/tree/master/examples/chip-tool )
64
- to communicate with the device.
94
+ 2 . In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"
65
95
66
- $ ./chip-tool pairing bypass ${NODE_ID_TO_ASSIGN} 192.168.xx.xxx 5540
96
+ - Set ` #define CHIP_DEVICE_CONFIG_ENABLE_CHIPOBLE 1 `
67
97
68
- ### Cluster Control
98
+ 3 . Build and Flash
99
+ 4 . Use ATS\$ command to run all-cluster example.
100
+ 5 . Test with
101
+ [ Chip-Tool] ( https://github.com/project-chip/connectedhomeip/tree/master/examples/chip-tool )
102
+ or
103
+ [ Python Controller] ( https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/python_chip_controller_building.md ) .
69
104
70
- - After successful commissioning, use the OnOff cluster command to control the
71
- OnOff attribute. This allows you to toggle a parameter implemented by the
72
- device to be On or Off.
105
+ ### IP mode
106
+
107
+ 1 . In "connectedhomeip/config/ameba/args.gni"
108
+
109
+ - set ` chip_bypass_rendezvous = false `
110
+ - Set ` chip_ip_commissioning = true `
111
+ - Set ` chip_use_clusters_for_ip_commissioning = true `
112
+ - Set ` chip_config_network_layer_ble = false `
113
+
114
+ 2 . In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"
115
+
116
+ - Set ` #define CHIP_DEVICE_CONFIG_ENABLE_CHIPOBLE 0 `
117
+
118
+ 3 . Build and Flash
119
+ 4 . Use ATS\$ command to run all-cluster example.
120
+ 5 . Connect to AP using ` ATW0, ATW1, ATWC ` commands
121
+ 6 . Test with
122
+ [ Chip-Tool] ( https://github.com/project-chip/connectedhomeip/tree/master/examples/chip-tool )
123
+ or
124
+ [ Python Controller] ( https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/python_chip_controller_building.md ) .
125
+
126
+ ## Cluster Control
127
+
128
+ After successful commissioning, use the OnOff cluster command to control the
129
+ OnOff attribute. This allows you to toggle a parameter implemented by the device
130
+ to be On or Off.
131
+
132
+ - Via
133
+ [ Chip-Tool] ( https://github.com/project-chip/connectedhomeip/tree/master/examples/chip-tool#using-the-client-to-send-matter-commands )
73
134
74
135
$ ./chip-tool onoff on 1
75
136
$ ./chip-tool onoff off 1
137
+
138
+ - Via
139
+ [ Python Controller] ( https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/python_chip_controller_building.md#step-8-control-application-zcl-clusters )
140
+
141
+ $ chip-device-ctrl > zcl OnOff Toggle 1234 1 0
0 commit comments