Add Zephyr support for MAX32690 Boards - #11328
Brandon-Hurst wants to merge 1 commit into
Conversation
e53205c to
0ef59f5
Compare
- Board aliases in ports/zephyr-cp/boards/board_aliases.cmake - Support for MAX32690FTHR, APARD32690, and MAX32690EVKIT APARD / EVKit had storage_partition by default in board support, but the MAX32690FTHR needed an explicit partition. Optional ramdisk usage for testing without flash wear. All boards successfully built, tested on MAX32690FTHR. Signed-off-by: Brandon Hurst <brandon.hurst97@gmail.com>
0ef59f5 to
d3abe62
Compare
tannewt
left a comment
tannewt
left a comment
There was a problem hiding this comment.
Each board needs a circuitpython.toml too. That should fix the CI.
Is there BLE support in Zephyr now? I'd love to deprecate the analog port in favor of the Zephyr one.
Thanks!
|
Hey @tannewt, we are still working on open BLE support, but it's not upstreamed just yet. So if possible would like to keep the baremetal port around for the time being. But very interested in supporting as much as possible on Zephyr as well. I'll go in and add those .toml files, thanks :) |
That's great news! Totally fine to keep the bare metal port around until then. |
2 participants
Description
Add Zephyr support for MAX32690 Boards
APARD / EVKit had storage_partition by default in
board support, but the MAX32690FTHR needed an explicit partition.
Also added ramdisk usage for testing without flash wear.
Testing
All boards successfully built, tested successfully on MAX32690FTHR both with ramdisk and flash filesystem.