@@ -18,8 +18,9 @@ messaging is supported in CHIP.
18
18
The CHIP demo application is intended to work on two categories of ESP32
19
19
devices: the
20
20
[ ESP32-DevKitC] ( https://www.espressif.com/en/products/hardware/esp32-devkitc/overview ) ,
21
- and the [ M5Stack] ( http://m5stack.com ) . Support for the
22
- [ M5Stack] ( http://m5stack.com ) is still a Work in Progress.
21
+ and the [ M5Stack] ( http://m5stack.com ) . On the [ M5Stack] ( http://m5stack.com ) this
22
+ example displays a CHIP QRCode with the device's Soft-AP SSID encoded in the TLV
23
+ section.
23
24
24
25
## Building the Example Application
25
26
@@ -45,13 +46,25 @@ step. To install these components manually, follow these steps:
45
46
Currently building in VSCode _ and_ deploying from native is not supported, so
46
47
make sure the IDF_PATH has been exported(See the manual setup steps above).
47
48
48
- - In the root of the example directory, source ` idf.sh ` and use the
49
- ` defconfig ` make target to configure the application with defaults .
49
+ - In the root of the example directory, sync the dependencies and source
50
+ ` idf.sh ` . Note: This does not have to be repeated for incremental builds .
50
51
52
+ $ make -C third_party/connectedhomeip -f Makefile-bootstrap repos
51
53
$ source idf.sh
54
+
55
+ - Next, if you want to use the M5Stack with its display and show a QRCode run
56
+ ` menuconfig ` .
57
+
58
+ $ idf make menuconfig
59
+
60
+ While in the configurator, navigate to ` WiFi Echo Demo ` ->` Device Type ` and
61
+ select ` M5Stack ` .
62
+
63
+ Otherwise, run the default config.
64
+
52
65
$ idf make defconfig
53
66
54
- - Run make to build the demo application
67
+ - Run make to build the demo application.
55
68
56
69
$ idf make
57
70
@@ -105,6 +118,10 @@ There are two ways to use the Echo Server running on the device.
105
118
I (5524) chip[DL]: SYSTEM_EVENT_STA_GOT_IP
106
119
I (5524) chip[DL]: IPv4 address changed on WiFi station interface: <IP_ADDRESS>...
107
120
121
+ Note: If you are using the M5Stack, the screen will display the server's IP
122
+ Address and Port if it successfully conencts to the configured 2.4GHz
123
+ Network.
124
+
108
125
5 . Then running the following command will ping the ESP32 and cause it to echo.
109
126
If necessary replace the ` <IP_ADDRESS> ` with the address printed by the
110
127
device in the monitor.
@@ -120,9 +137,10 @@ your network configuration. To erase it, simply run.
120
137
121
138
Alternatively, you can connect to the ESP32's Soft-AP directly.
122
139
123
- 1 . After the application has been flashed, connect the ESP32's Soft-AP. It's
124
- usually something like ` CHIP_DEMO-XXXX ` where the last 4 digits are from the
125
- device's MAC address.
140
+ 1 . After the application has been flashed, connect the ESP32's Soft-AP. If you
141
+ use the M5Stack, the Soft-AP's SSID is encoded in the TLV section of the
142
+ QRCode on screen. It's usually something like ` CHIP_DEMO-XXXX ` where the
143
+ last 4 digits are from the device's MAC address.
126
144
127
145
2 . Once you're connected, the server's IP can be found at the gateway address
128
146
and at the listed port number(Default: ` 8000 ` ).
0 commit comments