STLINK/V2-1 and STLINK/V2 SN incompatibility on NUCLEO-F401RE board

[xor-gate]

• Programmer/board type: NUCLEO-F401RE
• Programmer firmware version: n/a
• Operating system: Mac OS X
• Stlink tools version and/or git commit hash: 0f6dcbd (> v1.2.0)
• Stlink commandline tool name: st-util
• Target chip (and optional board): e.g STM32F401RE (NUCLEO-F401RE)

Output:

$ system_profiler SPUSBDataType
        STM32 STLink:

          Product ID: 0x374b
          Vendor ID: 0x0483  (STMicroelectronics)
          Version: 1.00
          Serial Number: 0672FF494951785087023310
          Speed: Up to 12 Mb/sec
          Manufacturer: STMicroelectronics
$ ./st-info --probe
Found 1 stlink programmers
 serial: 303637324646343934393531373835
openocd: "\x30\x36\x37\x32\x46\x46\x34\x39\x34\x39\x35\x31\x37\x38\x35"
  flash: 524288 (pagesize: 16384)
   sram: 98304
 chipid: 0x0433
  descr: F4 device (Dynamic Efficency)

The current stlink tools/library is unable to detect a binary or hexstring serial number. The best fix is to detect if the serial is already hex encoded or encode it into a hex string. We need to have a generic hexstr_from_bin, hexstr_to_bin and hexstr_is_valid.

[slyshykO]

If convert openocd: "\x30\x36\x37\x32\x46\x46\x34\x39\x34\x39\x35\x31\x37\x38\x35" to "normal" ASCII we can see this string
"0672FF494951785". Looks similarly to 0672FF494951785087023310, at least first 15 signs.

[tarek-bochkati]

please check http://openocd.zylin.com/#/c/5396/, it could be linked to this

[Nightwalker-87]

@tarek-bochkati: Could you open a PR for this, as you were involved in this topic anyway?

[tarek-bochkati]

PR #1106
@Nightwalker-87 , here is it.
I have omitted the hla serial aka openocd serial
Only one valid serial is displayed that matches the serial as displayed in STM32CubeProgrammer.
Tested on ubuntu focal fossa