You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The Zephyr project is currently supporting several chips from the STM32F4 family, but not the STM32F479. Creating e.g. a simple blink project and defining a custom board using as soc "stm32f479xx" results in an unknown soc error, as expected.
Describe the solution you'd like
I'd love to have native support in Zephyr for that chip and its variants. From my understanding it requires defining or extending the soc definitions for that chip based on the F469. A (the only?) major difference seems to be in the F479 containing hardware support for cryptography.
Describe alternatives you've considered
None, beyond manually writing a soc definition by hand myself.
Additional context
I'd love to help with that process if possible, but as I am only starting to work with Zephyr my understanding of it is still rather limited.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The Zephyr project is currently supporting several chips from the STM32F4 family, but not the STM32F479. Creating e.g. a simple blink project and defining a custom board using as soc "stm32f479xx" results in an unknown soc error, as expected.
Describe the solution you'd like
I'd love to have native support in Zephyr for that chip and its variants. From my understanding it requires defining or extending the soc definitions for that chip based on the F469. A (the only?) major difference seems to be in the F479 containing hardware support for cryptography.
Describe alternatives you've considered
None, beyond manually writing a soc definition by hand myself.
Additional context
I'd love to help with that process if possible, but as I am only starting to work with Zephyr my understanding of it is still rather limited.
The text was updated successfully, but these errors were encountered: