[doc] Known good example output for command 'st-info --probe'

[stappersg]

• Programmer/board type: Stlink/v3mini
• Programmer firmware version: dont know, might be the problem
• Operating system: Linux, Debian bullseye
• Stlink tools version: 1.6.1+ds-2, 2020-06-21
• Stlink commandline tool name: st-info
• Target chip (and optional board): STM32L072, PX-HERO, https://www.crowdsupply.com/piconomix/px-her0-board/

Commandline-Output:

$ ./st-info --probe
Found 1 stlink programmers
 serial:     303033413030323233343338353130323334333133393339
 hla-serial: "\x30\x30\x33\x41\x30\x30\x32\x32\x33\x34\x33\x38\x35\x31\x30\x32\x33\x34\
\x33\x31\x33\x39\x33\x39"
 flash:      0 (pagesize: 0)
 sram:       0
 chipid:     0x0000
 descr:      unknown device

Description:

Issue #716 was closed without a this is how it is supposed to look, without clearly stating target must be present.

Expected:

Have documented how a known good looks, wether or not the target device must be present.

In other words: Have #716 amended.

[stappersg]

Additional information from the issue reporter:

• With or without the target board, I get the same output from st-info --probe.
• When target board connected to stlink V3mini does a st-info --probe reset the board.
• My plan of getting a [doc] Known good example output for command 'st-info --probe' #1007 mentions this issue in st-info --probe finds programmer and doesn't display its details #716 failed ... :-/

[stappersg]

My research show that updating the firmware of my STLINK is an option.
It is also what #716 (comment) says.

Time will tell who was here first on reporting a known good of st-info --probe ... 😃

[Nightwalker-87]

@stappersg: Does it work now, after updating the firmware?
There is no (one) "known good" really, as the displayed information is MCU dependent.
You can expect that the connected chip is properly detected if the empty fields as well as the chipid field are all filled out.
Please also refer to doc/devices_boards.md to verify a correct chip detection and compare the read memory sizes with the known specifications-

* My plan of getting a _#1007 mentions this issue_ in #716 failed  ... `:-/`

This is because editing resolved old tickets is locked to prevent recycling of old issues.

[stappersg]

Does it work now, after updating the firmware?

ST-LINK V3MINI updated with en.stsw-link007_V2-37-26.zip from https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/stsw-link007.html

I see no improvement. Thing I didn't noticed before that the LED at USB connector of the STLINKV3MINI goes from red to green after the st-info --probe.

This all new to me was reason for buying several sets. I can send a set to developer. Those who are interested can email me at stappers at stappers dot it

[Nightwalker-87]

This could be related to incomplete support of the STLink-v3 programmer series by this toolset as well...

[stappersg]

With stlink-gui

• Chip: unknown device
• Core: 0xbc11477
• Flash size: 0 kB
• RAM size: 0 kB

Clicking on connect gets LED near USB connector from red to green.
Doing a read seems succesfull, but I get an empty file.

Other thing I did at my side is ordering another STLINK V3MINI, this time with adaptor to 2.54mm header plus Dupont cables. When it arrives is the plan to test it an known good STM32 device.

[Nightwalker-87]

STLINK V3MINI is not officially or fully supported by this toolset (#820).
Please consider this.

[stappersg]

Reporting now it works ...

$ st-info --probe
Found 1 stlink programmers
 serial:     303033413030323233343338353130323334333133393339
 hla-serial: "\x30\x30\x33\x41\x30\x30\x32\x32\x33\x34\x33\x38\x35\x31\x30\x32\x33\x34\x33\x31\x33\x39\x33\x39"
 flash:      131072 (pagesize: 128)
 sram:       20480
 chipid:     0x0447
 descr:      L0xx Category 5

I can't tell what did the trick.
Might be related to doing cargo flash. ( Yes, cargo is the Rust package manager.)

[Nightwalker-87]

@stappersg Did you use a STLINK-V3 as well?

[stappersg]

On Tue, Oct 06, 2020 at 11:48:40AM -0700, nightwalker-87 wrote: @stappersg Did you use a STLINK-V3 as well?

Yes. (It is the only ST-LINK I have.) Getting the STLINK-V3 in the right state is most likely be down by `cargo flash`. `cargo flash` is based upon https://probe.rs My plan is to update the stlink documention with a known good example. (To be continued)

[Nightwalker-87]

I see. However it would be helpful to understand the change an executed cargo flash introduces in reference to this stlink toolset.

[stappersg]

My plan is to update the stlink documention with a known good example. (To be continued)

There is now merge request #1049