zephyrproject-rtos / zephyr

Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
https://docs.zephyrproject.org
Apache License 2.0
10.18k stars 6.24k forks source link

TI-AM62x: Add Zephyr Support for M4 and R5 cores #49413

Closed DhruvaG2000 closed 1 year ago

DhruvaG2000 commented 1 year ago

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe. The R5 and M4 cores are MCU cores in the TI Sitara processor AM62x and it would greatly benefit having support for Zephyr on these cores. One could perhaps build the binaries on the main A53 core running linux and then flash them to the MCU cores using Remote Proc.

Describe why you are asking for this support? I am asking since I am not 100% sure on how to go about this effort, whether the port procedure would be different than other MCU's or not and also how and whether the code/OS running on the A53 core affects these other cores. Will we have to add support for things like RProc RPmesg, interrupts, etc. or this is taken care of completely by the linux side?

If this is a new board or SoC, please state whether you are willing to maintain the Zephyr support for it if it is included in the main tree This can be called as a new board, because the headers are the same as that of a Raspberry pi.

Additional context The image of the AM62x-SK EVM is: image

The official website: https://www.ti.com/tool/SK-AM62 The user guide: https://www.ti.com/lit/ug/spruj40/spruj40.pdf The TRM of the AM62x : https://www.ti.com/lit/ug/spruiv7/spruiv7.pdf

DhruvaG2000 commented 1 year ago

Another thought- This could perhaps be extended to the entire TI's KeyStone 3-ARCH ?

github-actions[bot] commented 1 year ago

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.