-
Notifications
You must be signed in to change notification settings - Fork 963
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
[Documentation request]Using the WeAct Blackpill F411 in the Arduino IDE #1118
Comments
All information are here:
This depends on which method you want to use. HID requires you self install its BL. For the one with STM32Cube Programmer it is not needed to install third party BL.
Well, this is the default option for all boards, which can support USART, USB,... it is up to end user to use the option he wants. No particular values are requested by default as user can manually switch in the BL mode if he doesn't want USB enabled by default.
BMP has been added by the community and I never use it. JLink is not supported anyway I guess you could use it with the generated binary. You can customize the Arduino IDE with your own config using boards.local.txt or platform.local.txt and By default the STM32F4 series has a built-in bl and you can flash thanks DFU or Serial using the STL32CubeProgrammer which required to be installed manually one time then the Arduino IDE will be able to use it automatically. See https://github.com/stm32duino/wiki/wiki/Upload-methods#stm32cubeprogrammer Feel free to amend the wiki it is a community project 😉 |
I've just saw this: I doesn't have this board so doesn't know if the upload method works with this bootloader. In that case you will have to change the BL or as said add your custom upload method. There will be no specific update to manage this BL. |
I got it working. It isn't a long or painful process in itself. I has no introduction to this beforehand, which is why I was confused about what I was doing wrong, as the required documentation was spread out in 4 places: the Stm32duino wiki, Serasidis/STM32_HID_Bootloader documentation, the WeAct fork of this (WeActTC/STM32_HID_Bootloader), and the derivative HID bootloader by WeAct(WeActTC/WeAct_HID_Bootloader_F4x1/), all of which had somewhat different pieces of information. The process of messing things up and then fixing them cleared up a lot of the knowledge issues. Next up, |
As said I was not aware they developped their own BL. We are currently working on a way to automatically restart in this BL mode --> #710 For the Wiki, I guess it could be fine to create a dedicated boards section then it would be easy to feed it for each board if needed. |
I have a WeAct BlackPill F411 which i want to use. I am able to program it using a combination of Arduino IDE (to build the firmware binary) and
dfu-util
(to program it) as detailed on the stm32duino forums, which I successfully tested usingblinky
.The board is unmodified in any way (no change from the WeAct HID bootloader or hardware modding of any time).
My problem is that, I am unable to successfully program the board using the Arduino IDE directly using the
HID Bootloader
option forUpload Method
.Describe the solution you'd like
I would like to be able to use program the board using just the Arduino IDE directly, without needing to fall back to using
dfu-util
to program the board. Towards that I would love to have the documentation to make this possible.In particular, I would love the following information:
USB Support
USB Speed
Upload Method
Alternatives I considered
I have not modified the IDE's menu settings that pre-loaded on choosing the
Board variant
:Generic Stm32F4 series
andBoard Part Number
:BlackPill F411CE
other than selectingHID Bootloader 2.2
as the Upload Method.I don't have an external programmer like a
Black Magic Probe
or aSTLink
and clones. I do have a Segger J-link Edu Mini, but I could not find any information on how to use it as a programmer under Arduino IDE. In case it is possible to use the J-link Edu Mini, I would appreciate that information as well.The text was updated successfully, but these errors were encountered: