-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
bluepill_f103c8 wont work with dfu upload and STM32duino-bootloader #87
Comments
here is the pio output from bluepill_f103c8:
here is the output from genericSTM32F103C8:
noticed that bluepill seems to have an extra linking step during upload?
|
ok the "extra" linking step seems to happen again during upload step whenever i change environments (boards), even after I did a compile step prior to upload step. Not sure why, or that it has any effect...
|
the prog size does look significantly larger with generic than bluepill:
vs
I wonder why this would be. The code did not change.. only change was environment targeted (i.e. the board type) |
hmm looks like if board name contains "generic" and upload type is "dfu" then there is some different linking happening... I wonder if "bluepill_f103c8" is not what I'm thinking it is? |
Fixed in 5da2246 Please re-test |
looks possibly similar to #53
using a generic bluepill board, with this bootloader
https://github.com/rogerclarkmelbourne/STM32duino-bootloader/blob/master/binaries/generic_boot20_pc13.bin
not able to get functional code with this:
but i do get functional code from this:
The text was updated successfully, but these errors were encountered: