Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DFUed built firmware binary image is not recognized by Windows10 #43

Open
shoichi-kojima opened this issue Aug 18, 2023 · 1 comment
Open

Comments

@shoichi-kojima
Copy link

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 ?

@ithinuel
Copy link

I had issues where dfu-ing after building master would fail, Windows 11 & linux (didn't test on macos).
#41 fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants