We have released the new Core Module 2. Everything is the same, only the flash process is now easier and faster.
With Core R2 you can use the BigClown Playground GUI tool to program nodes, manage radio network and create rules in Node-RED.
Technical and visual differences
The most significant change is that R2 has only single button. This is the
B button. It has moved and you can use it for your program. The
R reset button is not necessary anymore because communication and firmware flashing is now done automatically over FTDI chip.
|Model||Core R1||Core R2|
The new Core Module 2 is not using DFU mode anymore. We have added new flashing over FTDI chip and virtual serial port over USB. This means that the flashing procedure is now the same as with the Radio Dongle. Please, use the --device <PORT> (e.g. COM4 or /dev/ttyUSB0) parameters instead of the former --dfu or --device dfu parameter.
- No need to press any button to start firmware update.
- Faster firmware uploads over FTDI chip
- Smaller firmwares because USB stack is now handled by FTDI chip.
- Simple debugging over serial port. The UART2 is connected to the FTDI so you can use bc_log_* functions.
- No issues with DFU drivers on Windows.
Flashing Core Module R1
- Connect the Micro USB cable to the Core Module and your computer.
- You have to switch to Core Module to the DFU mode.
Upload firmware with following command
bcf flash --device dfu [firmware]:[version]
Example which flashing wireless-motion-detector firmware from Wireless Motion Detector project:
bcf flash --device dfu bigclownlabs/bcf-radio-motion-detector:latest
Flashing Core Module R2
With Core R2 you can also use the BigClown Playground GUI tool to program nodes, manage radio network and create rules in Node-RED.
Flash firmware with following command
bcf flash [firmware]:[version]
Example which flashing wireless-motion-detector firmware from Radio Motion Detector project:
bcf flash bigclownlabs/bcf-radio-motion-detector:latest
Print bc_log debug messages over UART2 serial to your computer with
Flash firmware and immediatelly start logging after upload
bcf flash [firmware]:[version] --log
List of connected devices
You can also add the
--device parameter to the
bcf so you don't have to choose the serial port every time.
Run following command to see connected devices
You should see as output something as following. On Windows instead of
/dev/ttyS4will be for example
COM13. Following device list is same on macOS and Linux.
Connect the Micro USB cable to the Core Module and your computer
bcf devicescommand and you should see one added.
Newly connected module is the
Now you can force to use that serial port during flashing:
bcf flash --device /dev/ttyUSB0 bigclownlabs/bcf-radio-motion-detector:latest