Can not load a *.bin

[yota news]

Posted on May 24, 2018 at 14:21

I already loaded some *.bin files, perfectly compiled with a perfectly functional tool chain.

But today it doesn't work anymore...

If I check with STLinkUpgrade 3.2.10, it tells me that the firmware is at version V2J30M21, which is also the last one.

When I try to flash the *.bin file with a simple drag & drop or copy-paste, the transfer seems to fail with the following error in the fail.txt file : The interface firmware FAILED to initialize the target MCU

What does it means ? how can I solve this ?

[Tilen MAJERLE]

Posted on May 24, 2018 at 14:47

Hello

news.yota

‌,

do you use any low-power features of the target MCU?

Best regards,

Tilen

[Tesla DeLorean]

Posted on May 24, 2018 at 14:49

Perhaps your firmware muddles with the PA13/PA14 debug pins, or goes into a low power or sleep mode?

Try using the ST-LINK Utilites to erase the firmware on the target.

Try pulling BOOT0 High so your code on the chip stops running.

[Artur IWANICKI]

Posted on May 24, 2018 at 14:55

Hello,

In case you have modified your debug pins / configure not used IO lines as analog in STM32CubeMX / have used low power modes (without wakeup) / overclocked your MCU, you can still erase/reprogram MCU configuring the debugger connection to 'connect under reset'. In this case once you try to erase/write into FLASH memory using debugger, it will first reset the MCU (blocking its code execution) and then perform the operation you want. This option is available in most of the toolchains. In STM32 STLink Utility you can find it Target->Settings->Mode

Best Regards,

Artur

[yota news]

Posted on May 24, 2018 at 15:11

Thanks all for your amazing feedback !

I didn't used low power features.

I'll test the BOOT pin tricks, but I mainly suspect an issue on the firmware update indeed... I don't use cubeMX (I'm on linux) but the STLinkUpgrade tool in java... and the revision V2J30M21 it offers doesn't seems to be the good one, for a reason I can't explain...

Next step may be to reboot under windows with the ST tool chain and try to understand what happened.

[Artur IWANICKI]

Posted on May 24, 2018 at 15:36

In the meantime I have checked and STLink v2.1 (tested on F401RE-Nucleo board) is connecting with 'connect under reset' option to the MCU.

Best Regards,

Artur

[Tesla DeLorean]

Posted on May 24, 2018 at 14:59

Is there a way of specifying 'connect under reset' when using the mbed drag-n-drop MSC ?

[Tesla DeLorean]

Posted on May 24, 2018 at 15:33

Older versions of the ST-LINK Utilities and stand-alone update utility will let you go backward in firmware versions.

Check also CubeMX settings for turning off or disabling debug, or ones to enable SWD/SWV

[AOnat]

On a Nucleo, it could also mean that you simply forgot JP6 in the 'E5V' configuration and the processor is not powering up correctly!