Data Sheet

Problems with updating the HM-1x firmware
These modules are fairly robust and can put up with a lot. If you for some reason happen to
power down the module during firmware update, after you had entered the AT+SBLUP
command, do not be alarmed. It won’t have completed the update process. Simply repower
he module, and send the firmware file again. It will complete the process.
The most common problem with this, is establishing the connection with the module using
usb_serial app on the wixel. It has been reported (though I have not seen it) that some
modules are being delivered fixed to a different baud rate from that specified by the
manufacturer as the default. You can determine what the baud rate is by setting your
terminal program to different baud rates and issuing an “AT” on each until you get “OK” in
response. Once you flash the new firmware onto the module, it should use the default 9600
baud rate, which is also used by xBridge.
BLE Name stays at HMSoft, instead of xBridgeXXYY.
If, when you scan for your xBridge in xDrip (or any BLE scanner) you see the name HMSoft,
this generally means one of two things:
1. You had a BLE connection established when you loaded the App onto the wixel.
Disconnect your BLE module (even better, turn off all Bluetooth on any nearby
phones), and re-flash the wixel code.
2. You did not verify that the HM-1x module is communicating at 9600 baud.
Either you did not update the firmware, or you simply didn’t check that this was the
case. Re-load the usb_serial app onto the wixel, and determine the current baud
rate by cycling from 115200 down. Once you determine the baud rate, reflash the
new firmware onto the HM-1x module, or at the very least send the command
“AT+BAUD0”, followed by “AT+RESET”.
How do I know if it is working?
Well, before you connect it to XDrip or any other app, the wixel will wake. If you are not
connected to it via a USB cable, with a serial terminal program, and for at least 30 seconds
initially, you will not notice anything
After 30 seconds, you should see the GREEN LED light up if you are connected to USB and
have a serial terminal program open to the port.
Because the code only turns on the Yellow LED when a BLE connection is made under
normal operation, it is sometimes difficult to know what it is up to. Here are the steps to go
through.
1. When you first load the xBridge2.wxl file onto the wixel and you are connected via
USB, the GREEN LED will light after 30 seconds, and the RED LED will also light
briefly at that point. The GREEN LED indicates it is connected to the USB port, and
the RED LED indicates that it has read it’s settings from the FLASH memory.
2. Use a BLE utility, or XDrip, to scan for a BT device. You should find a device with a
name like XBridgeXX. If you see that, the wixel has woken and correctly configured
the HM-10 module, and should be ready to go.