samples: boards: infineon: board specific samples #90834
Conversation
sreeramIfx
commented
May 29, 2025
sreeramIfx
commented
- Sample required to enable CM7 cores on XMC7200
sreeramIfx
force-pushed
the
xmc7200_cm0_app
branch
from
9837c7a to
b95bb6b
Compare
- Sample required to enable CM7 cores on XMC7200 Signed-off-by: Sreeram Tatapudi <[email protected]>
sreeramIfx
force-pushed
the
xmc7200_cm0_app
branch
from
b95bb6b to
2818db3
Compare
|
There was a problem hiding this comment.
I don't see how this sample is demonstrating anything Zephyr related. It's just a demonstration of Cypress HAL.
There was a problem hiding this comment.
Yes, But this application is required to be able to run zephyr apps on the cm7 cores
There was a problem hiding this comment.
Then you can put this code in soc_m7.c file in soc/infineon/... , similar to https://github.com/zephyrproject-rtos/zephyr/blob/cf6170cbe605c3876ea73451b589fa59855ba12a/soc/st/stm32/stm32h7x/soc_m7.c
There was a problem hiding this comment.
Basically what @JarmouniA said :) Please consider closing this PR if this sounds like an acceptable solution
There was a problem hiding this comment.
@kartben @JarmouniA Please note that this application is expected to run on the M0 core to enable the M7 cores. Doing the M7 enabling from the soc_m0p.c would mean that the M7 core would be enabled before or during the driver initializations on the M0 core. It does not give the M0 applications the control/flexibility to enable M7 at a later point in time (for additional configuration or application logic related reasons). Providing a standalone application would provide that flexibility. Please let me know your thoughts.
There was a problem hiding this comment.
@kartben @JarmouniA Any thoughts on this?
There was a problem hiding this comment.
@kartben @JarmouniA Please note that this application is expected to run on the M0 core to enable the M7 cores.
That sounds exactly like a SoC Hook to me.
Doing the M7 enabling from the soc_m0p.c would mean that the M7 core would be enabled before or during the driver initializations on the M0 core.
You can choose when you want the hook to run
see include/zephyr/platform/hooks.h
It does not give the M0 applications the control/flexibility to enable M7 at a later point in time (for additional configuration or application logic related reasons).
Zephyr does not aim to cover all the usecases of a given platform, it only gives a stable base to build on. The rest is up to the user depending on how far they want to go.
Providing a standalone application would provide that flexibility.
What is implemented here is not a Zephyr app logic, it is not using any Zephyr API or features.
