-
Notifications
You must be signed in to change notification settings - Fork 1k
Maple upload broken #2436
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
Comments
And wtf is this doing Lines 2526 to 2528 in b24801b
It spells |
Oh lookie lookie there, when I change Arduino_Core_STM32/platform.txt Lines 113 to 114 in b24801b
to be
I do get a successfull upload |
So obviously, when Tools -> Upload Method --> Maple DFU Bootloader 2.0 is selected, it should use 1EAF:0003 as the VID:PID for DFU-Util. This is probably even irregardless of the selected chip (doesn't matter whether "Generic STM32F103C8" or "Bluepill C8", since the Maple DFU bootloader will always show up as that VID:PID. I'm not sure what this core here is doing using that other 0x0483:0xdf11, because that is the generic "STM Device in DFU Mode" VID/PID, not the one for Maple. I'm a bit baffled that the most popular Bluepill board with the most popular USB bootloader can't be used in this core out of the box- |
Hi @maxgerhardt
A typo mistake, sorry for this. I've made a lot of changes to feat new Arduino specification. I've tested the Blue Pill but when rebased and squashed several branches I've made a mistake. I'm only human so please be comprehensive....
Same here, this kind of comment is really not constructive and only your opinion. It is a community project and all contributions are welcome (PR, review, discussions,...). Doing my best (alone) ... Fixed by #2440. |
Describe the bug
When selecting a Bluepill STM32F103C8 and the Mapple Bootloader 2.0 from here, the STM32Duino core fails to use the correct USB PID/VID of 0x1EAF:0x003 and instead uses 0x0483:0xdf11. Upload subsequently fails to find the correct device.
To Reproduce
No source code relevant. Blinky sketch for PC13.
Steps to reproduce the behavior:
Get hit with failure
(no wonder if you select teh wrong VID/PID)
Expected behavior
Uploading with the Maple bootloader actually uses the right PID/VID
Screenshots
None
Desktop (please complete the following information):
Board (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: