CubeProgrammer 2.11.0 Bootloader revision reading bug

[Kraal]

Hello,

I have updated CubeProgrammer to its latest revision (2.11.0) and it finally displays the bootloader version in the target information box (with a Nucleo-G070RB).

However it keeps reading the bootloader revision every 1 second, as shown by the log below:

  10:41:44:080 : ST-LINK SN  : 0671FF505048878667122244
  10:41:44:081 : ST-LINK FW  : V2J39M27
  10:41:44:082 : Board       : NUCLEO-G070RB
  10:41:44:083 : Voltage     : 3.22V
  10:41:44:089 : SWD freq    : 4000 KHz
  10:41:44:090 : Connect mode: Under Reset
  10:41:44:090 : Reset mode  : Hardware reset
  10:41:44:097 : Device ID   : 0x460
  10:41:44:098 : Revision ID : Rev B
  10:41:44:105 : Reading data...
  10:41:44:111 : r ap 0 @0x1FFF77DD 0x00000004 bytes Data 0xFFFFFFFF
  10:41:44:111 : Database: Config 0 is active.
  10:41:44:111 : flash loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/FlashLoader/0x460.stldr is loaded
  10:41:44:111 : halt ap 0 
  10:41:44:112 : r ap 0 @0x4002103C 0x00000004 bytes Data 0x00000000
  10:41:44:112 : w ap 0 @0x4002103C 0x00000004 bytes Data 0x08000000
  10:41:44:112 : Debug in Low Power mode enabled.
  10:41:44:113 : r ap 0 @0x40015808 0x00000004 bytes Data 0x00001800
  10:41:44:113 : w ap 0 @0x40015808 0x00000004 bytes Data 0x00001800
  10:41:44:113 : r ap 0 @0x40015804 0x00000004 bytes Data 0x00000006
  10:41:44:114 : w ap 0 @0x40015804 0x00000004 bytes Data 0x00000007
  10:41:44:114 : Reading data...
  10:41:44:116 : r ap 0 @0x1FFF75E0 0x00000004 bytes Data 0xFFFF0080
  10:41:44:118 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:44:199 : UPLOADING OPTION BYTES DATA ...
  10:41:44:199 :   Bank          : 0x00
  10:41:44:199 :   Address       : 0x40022020
  10:41:44:199 :   Size          : 112 Bytes
  10:41:44:199 : Reading data...
  10:41:44:199 : r ap 0 @0x40022020 0x00000070 bytes Data 0xDFFFE1AA
  10:41:44:200 : UPLOADING OPTION BYTES DATA ...
  10:41:44:200 :   Bank          : 0x00
  10:41:44:201 :   Address       : 0x40022020
  10:41:44:202 :   Size          : 112 Bytes
  10:41:44:202 : Reading data...
  10:41:44:226 : r ap 0 @0x40022020 0x00000070 bytes Data 0xDFFFE1AA
  10:41:44:227 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:44:227 : UPLOADING ...
  10:41:44:228 :   Size          : 1024 Bytes
  10:41:44:228 :   Address       : 0x8000000
  10:41:44:228 : Read progress:
  10:41:44:228 : Reading data...
  10:41:44:229 : r ap 0 @0x08000000 0x00000400 bytes Data 0x20000890
  10:41:44:230 : Data read successfully
  10:41:44:230 : Time elapsed during the read operation is: 00:00:00.007
  10:41:44:232 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:45:199 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:46:210 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:47:217 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:48:226 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:49:236 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:50:247 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:51:256 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:52:267 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:53:277 : r ap 0 @0x1FFF6FFE 0x00000004 bytes Data 0xFFFF00B2
  10:41:53:884 : Disconnected
  10:41:53:884 : Disconnected from device.

Is it on purpose ?

Also the bootloader revision does not appear with a Nucleo-L053R8. Both boards ST-link have been updated to the latest revision V2J39M27.

Why can't we have the bootloader displayed for all devices ?

[Kraal]

Update on this matter:

I tried with a Nucleo-G0B1RE, also with its latest ST-link update.

The bootloader version is not displayed either, despite being a new board release (MB1360-G0B1RE-C02).

I hope this will improve in the next release...

[Tesla DeLorean]

The constant probing is also annoying. Especially when testing/logging work on external loaders.

Surely presence detection would be better done, more transparently, on the ST-LINK side of things, ie in the driver, or in it's firmware. Perhaps sensing if SWDIO, SWCLK, or NRST tri-state at a basic level so it's less intrusive?

[Houda GHABRI · Accepted solution]

Hi @Kraal​ ,

You are right , no need to read BL version continually when connecting using STLink.

I submit an internal ticket to fix this behavior.

Also, for L0 family reading BL is not yet supported by CubeProgrammer, ticket inserted to add it in future release.

Internal ticket number: 133017  (PS: This is an internal tracking number and is not accessible or usable by customers). 

Houda

[Kraal]

Hi @Houda GHABRI​ ,

Thank you for the follow-up.

Regarding the L0 ticket, be aware that for L010K4 and L011K4 the address of BL revision in system memory does not match AN2606.

Reading 1 byte at 0x1FF00FFE return 0xC0 for L053 (as expected), but returns 0x00 for L011. If the address is changed to 0x1FF00FFF, then it returns 0xC2 for L011 (better, but I was expecting C3 according to AN2606).

Interestingly enough, reading 0x1FF00FFD return 0x31 (as in USART V3.1) and reading 0x1FF00FFB returns 0x11 (as in SPI V1.1) on the L011K4.

Best regards,

Kraal

- Edited for readability -

[Houda GHABRI]

Hi @Kraal​ ,

Thanks for all your interesting feedbacks, I will raise it to BootLoader team.

Houda