Is it planned to support the new STM32G series in the near future?
I'm particularly interested in the G4 series, as I want to use the STM32G431 for a new product development.
On ST website they state that the Nucleo G431RB is already mbed compliant, but can't find it under targets.
[X] Question
[ ] Enhancement
[ ] Bug
@ARMmbed/team-st-mcd
@ARMmbed/team-st-mcd Yes or no? :-) We can close this question then...
Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.
Mhh, not very nice to just close without any answer even though this issue was raised before the policy changed.
By the way, the same question was raised in the forum already for STM32G0 without any answer since August 30.
Mhh, not very nice to just close without any answer even though this issue was raised before the policy changed.
You still can get an answer. As we don't have an answer to all questions, some might be without an answer unfortunately, and now closed.
True, the policy has an affect now for older issues prior the policy. Those relevant can be opened on the forum, we can still look at some closed here. I'll try to find an answer for this question.
@ARMmbed/team-st-mcd Would you be able to provide an answer for this question?
By the way, the same question was raised in the forum already for STM32G0 without any answer since August 30.
@NadyaARM
sorry for not answering. We're looking at all requests and trying to prioritize targets roadmap.
We'll let you know when a plan is confirmed for G0 and/or G4.
We also welcome users contributions to add new boards support:
https://os.mbed.com/teams/ST/wiki/steps-to-create-a-new-STM32-platform
@desmond-blue , can you please update Forum's question with an answer from @LMESTM ?
Awesome. Thanks. I have already started porting parts of my firmware to Zephyr, but would appreciate to be able to stay with mbed for now.
Didn't know that specific link for new STM32 platforms. Unfortunately, I failed to get a not supported STM32L452 Nucleo board running with mbed some time ago (probably because of some linker file issues), so I'd rather not try to port an entirely new family of MCUs.
Hi all
For your information, STM32G0 family has been introduced in #12093
Regards,
Hi
For STM32G4, I can share the results of "automatic" script results in
https://github.com/jeromecoutant/mbed/tree/DEV_STM32G4
This branch can't compile, but I think it is a good starting point.
Regards,
Jerome
Hi Jerome, thanks a lot for your effort.
I decided to migrate my firmware to Zephyr RTOS. But I'm sure the STM32G4 support will be helpful for others as well.
@jeromecoutant
I took your branch and have basic support for the NUCLEO_G747RE target (gpio and system initialization, enough to compile blinky while ignoring a lot of features that require UART).
You can see my branch here: https://github.com/AGlass0fMilk/mbed-os/tree/add-nucleo-g474re
I am hoping we can collaborate a bit to add the rest of the features since you are obviously more familiar with the STM platform than I am.
Maybe you could convince your project managers to give you some time to assist me since there is another developer working on this now :)?
@AGlass0fMilk
Please push a pull request for official review with all interested people.
No problem to enable feature 1 by 1, as long as you check tests results.
See #12482
Most helpful comment
sorry for not answering. We're looking at all requests and trying to prioritize targets roadmap.
We'll let you know when a plan is confirmed for G0 and/or G4.
We also welcome users contributions to add new boards support:
https://os.mbed.com/teams/ST/wiki/steps-to-create-a-new-STM32-platform