soc: adi: max32: Enable primary core to configure/start secondary core #84539
Conversation
Refactors the max32 soc family configuration to allow socs with cores other than arm cortex-m4. This will make it possible to add support for the secondary risc-v core that exists on some max32 variants. Signed-off-by: Maureen Helm <[email protected]>
Adds support for the primary m4 core to configure the boot address and start the clock for the secondary risc-v core. Unlike the msdk which defers this function to applications and requires users to copy/paste code from an msdk example application into their own application, in zephyr it is implemented in the common soc init routine of the primary core. It can be enabled/disabled and configured with Kconfig symbols and a devicetree chosen node, allowing applications to override board-level defaults if desired using overlays instead of modifying zephyr code. Signed-off-by: Maureen Helm <[email protected]>
The max32 risc-v support I've done so far doesn't support interrupts or the kernel timer, so it's not useful for general purpose yet and I'm a little concerned someone would think they could start running zephyr applications on it. It's currently only useful if someone wants to pick up where I left off and finish the port. If someone is interested, I have zephyr booting the hello world sample to ram console. I'm upstreaming a subset of that work here to enable a zephyr app on the arm core to start some app (not necessarily a zephyr app) on the risc-v core. |
|
@ttmut @microbuilder can you take a look? |
Adds support for the primary m4 core to configure the boot address and
start the clock for the secondary risc-v core. Unlike the msdk which
defers this function to applications and requires users to copy/paste
code from an msdk example application into their own application, in
zephyr it is implemented in the common soc init routine of the primary
core. It can be enabled/disabled and configured with Kconfig symbols and
a devicetree chosen node, allowing applications to override board-level
defaults if desired using overlays instead of modifying zephyr code.
Signed-off-by: Maureen Helm [email protected]