#1 March 14, 2016 15:55:44

aflewellen-gore@filtersense.co
Registered: 2016-01-11
Posts: 5
Profile   Send e-mail  

Loading Stock Firmware Over UART

We’re at the point where we want to test BLE functionality on our prototype. We would like to load a stock firmware hex file (SaBLE-x Dev Board Firmware for ModuleLink (480-0040)) onto the module from our main processor over UART. Then we'd like to connect to the module with a smartphone to test range, board layout, and to estimate power consumption. Is this possible?

I don't care about the usual peripherals on the dev board. Almost all the I/O pins that are used on the Dev board are floating on our prototype. We only have power, ground, UART, reset, and DIO9 backdoor connected to the module.

Are there any special considerations that I should take into account?

Offline

#2 March 15, 2016 17:30:35

SupportEngineer
Registered: 2016-03-11
Posts: 85
Profile   Send e-mail  

Loading Stock Firmware Over UART


Unfortunately, the SaBLE-x 480-0040 firmware will not run properly if most of the IOs are floating since the firmware relies on I2C communication from the sensors and will cause the module to lock up.

Offline

#3 March 16, 2016 17:50:37

adamashafi
Registered: 2015-12-02
Posts: 3
Profile   Send e-mail  

Loading Stock Firmware Over UART

I assume you can, however, load the 480-0038-R1.3.hex firmware, and then enable the BLE advertising using the relevant host processor commands.

We also have most of the SaBLE-x I/Os floating (I2C etc…) and I would hope the 480-0038-R1.3.hex firmware won't lock up in this case. If you could confirm that would be appreciated.

- Adam

Offline

#4 March 16, 2016 17:55:32

rerickson
Registered: 2014-01-01
Posts: 340
Profile   Send e-mail  

Loading Stock Firmware Over UART

Hello,

You are correct. You can use the 480-0038 firmware with minimal IO connections and it will function. All you will need is power, ground, tx, rx, DIO 9 (BL_EN), reset.

Offline

#5 Nov. 28, 2016 10:19:47

arnold_w
Registered: 2015-08-19
Posts: 11
Profile   Send e-mail  

Loading Stock Firmware Over UART

I have a few questions:
A. Will the module lock up or will it not lock up, if the I2C-pins are floating?
B. How many wires (except GND) are used inside the USB-cable that was supplied with the SaBLE-x board?
C. If the answer to question B was 2, then how do you control the reset and DIO9 backdoor pins?
D. If the answer to question B was 4, then how do you control the reset and DIO9 backdoor pins from a virtual com port driver (when I plug in the USB-cable it shows up as a virtual com port in the Device Manager)?

Edited arnold_w (Nov. 28, 2016 10:20:12)

Offline

#6 Nov. 28, 2016 14:25:44

rerickson
Registered: 2014-01-01
Posts: 340
Profile   Send e-mail  

Loading Stock Firmware Over UART

If you are using the module link firmware in the dev board, it is expecting to see the sensors on the I2C bus. If it doesn't see the sensors, it will cause issues with the firmware.

We use DTR on the FTDI virtual COM port to control the modules reset and RTS to control DIO9 (Boot_EN). Please see the schematics for the dev board. They can be downloaded from the SaBLE-x documentation page.

Offline

#7 Dec. 1, 2016 16:08:03

arnold_w
Registered: 2015-08-19
Posts: 11
Profile   Send e-mail  

Loading Stock Firmware Over UART

arnold_w
A. Will the module lock up or will it not lock up, if the I2C-pins are floating?
Yes, if the pins are floating then the module will lock up. However, if you pull up both DIO_3_SCL and DIO_2_SDA to 3.3 V via 10 kOhm pull-up resistors, then it will work fine (of course, the temperature sensor, light sensor and tilt position sensor will report garbage to the Bluetooth chip).

Edited arnold_w (Dec. 1, 2016 16:11:00)

Offline

Board footer

Moderator control