You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To use my hs-probe as CMSIS-DAP (SWDv2) for RP2040, I built binary image from the latest.
I tried both "cargo build --release ..." and "cargo build --release features turbo" but neither worked. Windows does NOT respond to re-pluging my hs-prove hardware.
I've been using ST's "CubeProg" utility for STM32 MCUs rather than "dfu-util" on Windows10 for DFU. I checked and verifyed the newly built image is correctly DFUed with proper partameter setting such as offset 0x08000000.
So, I guess something is wrong in my "cargo build " process or environments...
To make my "hs-probe" work as CMSIS-DAP again, would some of you put the binary image to the respository for buiding result verification ?
The text was updated successfully, but these errors were encountered:
Dear staffs,
To use my hs-probe as CMSIS-DAP (SWDv2) for RP2040, I built binary image from the latest.
I tried both "cargo build --release ..." and "cargo build --release features turbo" but neither worked. Windows does NOT respond to re-pluging my hs-prove hardware.
I've been using ST's "CubeProg" utility for STM32 MCUs rather than "dfu-util" on Windows10 for DFU. I checked and verifyed the newly built image is correctly DFUed with proper partameter setting such as offset 0x08000000.
So, I guess something is wrong in my "cargo build " process or environments...
To make my "hs-probe" work as CMSIS-DAP again, would some of you put the binary image to the respository for buiding result verification ?
The text was updated successfully, but these errors were encountered: