How to unbrick a bricked SensorTile

[JBrad.4]

I tried to flash the FP-SNS-ALLMEMS1 firmware (https://www.st.com/content/st_com/en/products/embedded-software/mcu-mpu-embedded-software/stm32-embedded-software/stm32-ode-function-pack-sw/fp-sns-allmems1.html) to a brand new SensorTile over bluetooth. The process completed according to the BLE app on my Android device and said to restart the board for the update to complete.

Now the board doesn't light up when powered as it did before. Is there a way that I can unbrick the device or force fresh firmware onto the board over USB for example?

[Eleon BORLINI]

Hi @JBrad.4​ ,

did you upload the file with the ST BLE app, as described in the User Manual p.47?

(Note: The binary file must only contain the application firmware; it is not possible to upgrade the boot loader as well).

You can check this thread if the issue is similar to yours, especially for the part where the recovery procedure is suggested.

-Eleon

[JBrad.4]

This is useful Eleon thank you. I uploaded the firmware as described in the manual.

I downloaded the firmware from the link in the original post. I then unzipped the file which contained a folder titled STM32CubeFunctionPack_ALLMEMS1_v4.1.0.

Inside that folder structure I uploaded Projects/STM32L476RG-SensorTile/Applications/ALLMEMS1/Binary a binary called STM32L476RG-SensorTile_ALLMEMS1_v4.1.0.bin. There were two files with the same name so I just selected the first one. Is there a chance that I did something wrong here?

---

RE: the thread you linked, do I need any other hardware except what comes with the SensorTile development kit here: https://www.st.com/en/evaluation-tools/steval-stlkt01v1.html .

[Eleon BORLINI]

Hi @JBrad.4​ ,

The ALLMEMS1 project is the correct one, but ok, there are two files, a .bin file with the bootloader (ALLMEMS1_ST_BL.bin) and the other one without the bootloader (ALLMEMS1_ST.bin).

The first one, the one with the bootloader, has to be used when you upgrade the firmware via STLINK, while for FOTA firmware upgrade, i.e. via Bluetooth, you have to use the ALLMEMS1_ST.bin one.

Which one did you use?

Ps: for exploiting the full capability of the debug of the Sensortile, and in general for the STM32 MCUs programming, I'm afraid that suggested hardware is needed...

-Eleon

[JBrad.4]

Hi Eleon,

I now have the STLINK V3. What I can't figure out is how to connect it to my SensorTile. Is there an explanation somewhere as I'm struggling to see which pins for anything feasibly connect to each other.

Thanks,

James

[Eleon BORLINI]

Hi @JBrad.4​ ,

you have to connect the CN6 connector of the ST LINK V3 shown in the picture below

 

to the 5-pin SWD connector for programming debugging on the Sensortile cradle expansion (STLCX01V1), p.9 of the user manual UM2101, through a flat cable.

Please assure that the SWD pin on the first connector is linked to the SWD on the second connector.

You can also use the SWD connector on the cradle device STLCR01V1.

-Eleon

[Eleon BORLINI]

Hi @JBrad.4​ ,

I have an update... you have to use the level shifter on the B-STLINK-VOLT board extension to program the Sensortile at 1.8V, since this is the running voltage of the Sensortile STM32L4 uC. But being the connector of this board a STDC14 connector, you should adapt this to the a standard pitch SWD connector of the Sensortile cradle.

Otherwise, you have to use the STLINK V2 or any X-NUCLEO board, that are provided of an embedded STLINK.

-Eleon