BMDA v2.0.0 + bmp does not start due to registry problem

[positron96]

Hello!

I recently decided to update to official stable bmda v2.0.0, on Windows 10 x64. Before that I used a custom-built version from 3576cdf (which I used for a year or two), and it worked with the same hardware and on the same system.

Unfortunately, I can't get it to work with a physical black-magic probe (on a stlink). It crashes upon starting with this error, related to USB devices registry entry:

D:\Cloud\Programming\BlackMagicProbe>blackmagic-bmda.exe                                                      
Error opening registry key SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_02\&0002\Device Parameters, got error 00000002: The system cannot find the file specified.                                                                                                                                                              
Error opening registry key SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00\&0000\Device Parameters, got error 00000002: The system cannot find the file specified.                                                                                                                                                              
Unexpected problems finding the device!                                                                                                                          

Indeed I don't have the aforementioned registry keys. What I do have is another one under this VID/PID:

This only happens when there is blackmagic probe connected.

[dragonmux]

Which build of W10 are you using? This looks like the W11 problem caused by Microsoft changing something about the registry API in a way that broke RegGetValue(..., ..., ..., RRF_RT_REG_SZ, ..., ..., ...) - unfortunately we haven't yet had the time and bandwidth to dig into this and how to fix it, however we are aware of the problem.

Thought there was an issue open for the W11 variant of this problem, but can't currently find it.

[ALTracer]

This is a known bug on Windows 11, I believe some users complained in GH issues or discussions (can't find exact text though). I get this, too, on Win11 24H2 build 10.0.26100.7462, against a bluepill running swlink v2.0.0-113-g f04ccfd; using a GH release binary of BMDA v2.0.0 on a relatively fresh/clean install machine (no dev tools on this one yet).
A crude workaround is to pass -d,--device COM3 (or \.\COM99) argument to bypass the USB interface -> COM port finder logic broken by Microsoft.
Thanks to work of maintainers WINUSB is auto associated to BOS descriptors, and winser.sys is auto associated to CDC-ACM descriptors, that headache of Win7 era is gone.

Logs

PS > .\blackmagic-bmda.exe -l
Available Probes:
     Name                 Serial #                  Manufacturer              Version
  1. Black Magic Probe (SWLINK) 76AE36E1                  Black Magic Debug         v2.0.0-113-gf04ccfdd

PS > .\blackmagic-bmda.exe -tv 5
Black Magic Debug App v2.0.0
 for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link and FTDI (MPSSE)
Using 1d50:6018 76AE36E1 Black Magic Debug
 Black Magic Probe (SWLINK) v2.0.0-113-gf04ccfdd
Error opening registry key SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_02\&0002\Device Parameters, got error 00000002: �� ������� ����� ��������� ����.

prefix:
Error opening registry key SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00\&0000\Device Parameters, got error 00000002: �� ������� ����� ��������� ����.

Unexpected problems finding the device!

compare to

PS > .\blackmagic-bmda.exe -d COM3 -tv 5
Black Magic Debug App v2.0.0
 for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link and FTDI (MPSSE)
Running in Test Mode
Target voltage: Unknown
Speed set to 6.000MHz for SWD
Switching from JTAG to dormant
Switching out of dormant state into SWD
Deprecated JTAG to SWD sequence
DP DPIDR 0x2ba01477 (v1 rev2) designer 0x43b partno 0xba
AP   0: IDR=24770011 CFG=00000000 BASE=e00ff000 CSW=e3000040 (AHB3-AP var1 rev2)
Halt via DHCSR(00030003): success after 3ms
ROM Table: BASE=0xe00ff000 SYSMEM=1, Manufacturer 020 Partno 411 (PIDR = 0x00000a0411)
0 0x0e000e000: Generic IP component - Cortex-M4 SCS (System Control Space) (PIDR = 0x04000bb00c DEVTYPE = 0x00 ARCHID = 0x0000)
-> cortexm_probe
CPUID 0x410fc241 (M4 var 0 rev 1)
cortexm_probe: Examining Part ID 0x0411, AP Part ID: 0x0411
Calling stm32f1_probe
Calling stm32f4_probe
1 0x0e0001000: Generic IP component - Cortex-M3 DWT (Data Watchpoint and Trace) (PIDR = 0x04003bb002 DEVTYPE = 0x00 ARCHID = 0x0000)
2 0x0e0002000: Generic IP component - Cortex-M3 FBP (Flash Patch and Breakpoint) (PIDR = 0x04002bb003 DEVTYPE = 0x00 ARCHID = 0x0000)
3 0x0e0000000: Generic IP component - Cortex-M3 ITM (Instrumentation Trace Module) (PIDR = 0x04003bb001 DEVTYPE = 0x00 ARCHID = 0x0000)
4 0x0e0040000: Debug component - Cortex-M4 TPIU (Trace Port Interface Unit) (PIDR = 0x04000bb9a1 DEVTYPE = 0x11 ARCHID = 0x0000)
5 0x0e0041000: Debug component - Cortex-M4 ETM (Embedded Trace) (PIDR = 0x04000bb925 DEVTYPE = 0x13 ARCHID = 0x0000)
ROM Table: END
Resuming target
***  1   STM32F411 M4
Attaching to target..
Halting target
Target halted: Halt requested
Attach success
RAM   Start: 0x20000000 length = 0x20000
Flash Start: 0x08000000 length = 0x10000 blocksize 0x4000
Flash Start: 0x08010000 length = 0x10000 blocksize 0x10000
Flash Start: 0x08020000 length = 0x60000 blocksize 0x20000
Detaching from target

I can also dump an export from my registry for MI_00 / Interface 0 the ttyBmpGdb port:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00\8&2b056550&0&0000]
"DeviceDesc"="@usbser.inf,%usbserial.devicedesc%;Устройство с последовательным интерфейсом USB"
"LocationInformation"="0016.0000.0000.006.004.000.000.000.000"
"Capabilities"=dword:00000080
"Address"=dword:00000004
"ContainerID"="{48c30c10-bce2-53a7-96dc-6e627654e92f}"
"HardwareID"=hex(7):55,00,53,00,42,00,5c,00,56,00,49,00,44,00,5f,00,31,00,44,\
  00,35,00,30,00,26,00,50,00,49,00,44,00,5f,00,36,00,30,00,31,00,38,00,26,00,\
  52,00,45,00,56,00,5f,00,30,00,32,00,30,00,30,00,26,00,4d,00,49,00,5f,00,30,\
  00,30,00,00,00,55,00,53,00,42,00,5c,00,56,00,49,00,44,00,5f,00,31,00,44,00,\
  35,00,30,00,26,00,50,00,49,00,44,00,5f,00,36,00,30,00,31,00,38,00,26,00,4d,\
  00,49,00,5f,00,30,00,30,00,00,00,00,00
"CompatibleIDs"=hex(7):55,00,53,00,42,00,5c,00,43,00,4f,00,4d,00,50,00,41,00,\
  54,00,5f,00,56,00,49,00,44,00,5f,00,31,00,64,00,35,00,30,00,26,00,43,00,6c,\
  00,61,00,73,00,73,00,5f,00,30,00,32,00,26,00,53,00,75,00,62,00,43,00,6c,00,\
  61,00,73,00,73,00,5f,00,30,00,32,00,26,00,50,00,72,00,6f,00,74,00,5f,00,30,\
  00,30,00,00,00,55,00,53,00,42,00,5c,00,43,00,4f,00,4d,00,50,00,41,00,54,00,\
  5f,00,56,00,49,00,44,00,5f,00,31,00,64,00,35,00,30,00,26,00,43,00,6c,00,61,\
  00,73,00,73,00,5f,00,30,00,32,00,26,00,53,00,75,00,62,00,43,00,6c,00,61,00,\
  73,00,73,00,5f,00,30,00,32,00,00,00,55,00,53,00,42,00,5c,00,43,00,4f,00,4d,\
  00,50,00,41,00,54,00,5f,00,56,00,49,00,44,00,5f,00,31,00,64,00,35,00,30,00,\
  26,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,32,00,00,00,55,00,53,00,42,\
  00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,32,00,26,00,53,00,75,00,\
  62,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,32,00,26,00,50,00,72,00,6f,\
  00,74,00,5f,00,30,00,30,00,00,00,55,00,53,00,42,00,5c,00,43,00,6c,00,61,00,\
  73,00,73,00,5f,00,30,00,32,00,26,00,53,00,75,00,62,00,43,00,6c,00,61,00,73,\
  00,73,00,5f,00,30,00,32,00,00,00,55,00,53,00,42,00,5c,00,43,00,6c,00,61,00,\
  73,00,73,00,5f,00,30,00,32,00,00,00,00,00
"ConfigFlags"=dword:00000000
"ClassGUID"="{4d36e978-e325-11ce-bfc1-08002be10318}"
"Driver"="{4d36e978-e325-11ce-bfc1-08002be10318}\\0001"
"Mfg"="@usbser.inf,%msft%;Корпорация Майкрософт"
"Service"="usbser"
"FriendlyName"="Устройство с последовательным интерфейсом USB (COM3)"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00\8&2b056550&0&0000\Device Parameters]
"VendorRevision"=dword:00000000
"RevisionId"=dword:00000200
"ExtPropDescSemaphore"=dword:00000001
"PortName"="COM3"
"PollingPeriod"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00\8&2b056550&0&0000\Device Parameters\e5b3b5ac-9725-4f78-963f-03dfb1d828c7]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_1D50&PID_6018&MI_00\8&2b056550&0&0000\Device Parameters\WDF]

[positron96]

Well, this is definitely happening on Win 10 22H2, mine is "Version 10.0.19045.6466".

Edition	Windows 10 Pro
Version	22H2
Installed on	‎16/‎02/‎2024
OS Build	19045.6466

Thanks for the workaround with -d switch, I'll try it soon.

What is interesting is what changed between my old build from 2024 and 2.0 and whether it's reasonable to bring old behavior back, because the old one works perfectly fine for me.

[dragonmux]

We changed how we locate the entries so it's much less of a headache and more robust - it's not a BMDA change that's the cause of this, but rather that Microsoft changed internals of the APIs we're calling in a way that broke documented and pre-existing behaviour - if you were to run W10 21H2 or possibly even 22H1 it would all just work again.

[positron96]

I am noticing something weird. I've forked v2.0.0, built it via "build and upload" Github Action (added a commit that disables other OSes and firmware), ran it and noticed that:

1. It does not have this problem
2. The binary is 2.5Mb compared to official v2.0.0 from releases page (670Kb)

This suggests that it's not the code or WinApi change, but something in the build process for release.

Here is the build: https://github.com/positron96/blackmagic/actions/runs/20669594888

Output:

D:\Cloud\Programming\BlackMagicProbe>blackmagic-bmda -tv 5                                                   
Black Magic Debug App d3cd0a98                                                                               
 for Black Magic Probe, ST-Link v2 and v3, CMSIS-DAP, J-Link and FTDI (MPSSE)                                
Using 1d50:6018 C1CE8CF8 Black Magic Debug                                                                   
 Black Magic Probe (ST-Link/v2) v1.10.2-dirty                                                                
Found AUX Serial at COM4                                                                                     
prefix: 7&241c5050&0                                                                                         
Using BMP at COM3                                                                                            
Running in Test Mode                                                                                         
Target voltage: 3.28V                                                                                        
Speed set to 6.000MHz for SWD                                                                                
Switching from JTAG to dormant                                                                               
Switching out of dormant state into SWD                                                                      
Deprecated JTAG to SWD sequence                                                                              
No usable DP found                                                                                           
No target found