-
Notifications
You must be signed in to change notification settings - Fork 18
gd32: add gd32f4xx #6
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
Conversation
|
GD32F405/407, GDF450 use the same gd32f4xx firmware library. |
60cbedd to
fdc9571
Compare
gmarull
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Please, squash into a single commit
- Provide the origin download URL for the HAL in the commit message
|
Hi @cameled , Thank you for helping us. I few minors to make sure everything is in the right place:
|
70c03e0 to
0cf1247
Compare
I have update the GD32F4XX.
|
|
Hi @nandojve |
If you detected any problem, please, suggest at zephyrproject-rtos/zephyr#38661. |
|
Hi @cameled , To get this in, we need a PR at Zephyr that build this library with a board. Are you open a PR for F405? |
I have a GD32F450I-EVAL board, and gd32f4xx library will work with it.
Thast's great! |
|
FYI I'll open a PR for GD32F450I-EVAL board in the next couple of days, I just need to improve the organization of Kconfig options as current model doesn't fit F4XX (SoC name != HAL name as in F403). |
Hi @gmarull |
gmarull
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Download URL is http://www.gd32mcu.com/download/down/document_id/247/path_type/1 (0cf1247 message needs to be adjusted)
GD32F4xx firmware library support GF32F405, GD32F407 and GF32F450. Origin: http://www.gd32mcu.com/en/download Filename: GD32F4xx Firmware Library Signed-off-by: HaiLong Yang <[email protected]>
I prefer the GD32F4 download site, people can easily to know where the gd32f4xx firmware library come from. |
gmarull
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, review my comments on conflicting names. Also, please create a section in the HAL README file/s to document which names have conflict and their new names.
gmarull
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the efforts, LGTM!
|
@nandojve could you please review? |
Hi @carlescufi , yes, I can start in the weekend. It has been an unprecedented week and I had not have proper time to check Zephyr PRs since last week. |
nandojve
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM in overall. However, first we should define what will be the standard that we will follow. Otherwise we can fall into the trap of opinions and create unnecessary conflicts.
In my view, this can be in following what we already have in tree or only after #8 with proper adjusts.
|
@cameled can you use |
GD32 timer_init function name conflict with Zephyr. Rename it to gd32_timer_init to temporarily solve the conflict. Signed-off-by: HaiLong Yang <[email protected]>
GD32 CAN have some name conflict with Zephyr. Add prefix 'GD32_' to these GD32 CAN macro name. Signed-off-by: HaiLong Yang <[email protected]>
Zephyr have BIT macro defined in sys/util_macro.h, add a redefine check for gd32 BIT MACRO. Signed-off-by: HaiLong Yang <[email protected]>
Done. |
nandojve
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Add GD32F4xx firmware library V2.1.3.