Burn CC25xx/HM10 firmware using a NodeMCU or Wemos D1 mini.
On ESP8266/NodeMCU-style boards (e.g. Wemos D1 Mini), the DTR/RTS auto-reset circuit that resets the chip when the serial port opens doesn't always reliably boot it back into normal run mode after a full USB unplug/replug — it can leave the chip stuck in its ROM bootloader, where it will never respond to CCLoader no matter how long you wait. This is a hardware/driver quirk, not a CCLoader bug, and a plain reset button press doesn't fix it either. The fix is to let esptool perform its own (more robust) reset handling once before running CCLoader: run esptool --port /dev/ttyXXX chip_id (a quick, read-only command) after any reconnect, then run CCLoader normally. This is only needed after a physical reconnect/power-cycle — it's not required right after flashing, since the upload process already leaves the board in a working state.
Use the files provided in folder Bin. The BIN files are already converted and ready to flash with CCLoader
Detailed Zigbee flashing information. Thx @blakadder
- Wire the pins:
| Pin Name | Pin# | NodeMCU/Wemos Pin | GPIO# |
|---|---|---|---|
| P2_1 (DEBUG_DATA) | Pin #8 | D5 | GPIO14 |
| P2_2 (DEBUG_CLOCK) | Pin #7 | D2 | GPIO4 |
| RSTB (RESET_N) | Pin #11 | D1 | GPIO5 |
| 3.3V | Pin #12 | 3.3V | |
| GND | Pin #13 | GND |
-
Use CCLoader.exe to load the CC2541hm10v707.bin firmware via the NodeMCU to the HM-10 with command:
CCLoader_x86_64.exe [Number of the COM port] CC2541hm10v707.bin 0
-
You should see a result similar to
If you're not sure the flash succeeded connect to HM-10 module over serial and issue AT+VERR commands which should show v707.
If you cannot communicate with the HM-10 module even after a successful firmware flash change you serial terminal baudrate to 9600, then issue AT+RENEW command which should reset the module to firmware factory settings and the proper 115200 baudrate.
You can Up- and Downgrade to other firmwares using the Manufacturer upgrade tool.