IMXRT595-EVK DSP and CM33 Peripheral Access Isolation

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMXRT595-EVK DSP and CM33 Peripheral Access Isolation

Jump to solution
1,346 Views
wx1
Contributor I

Hi NXP community, I'm working with the MIMXRT595-EVK​ board (Cortex-M33 + Fusion F1 DSP dual-core system) and have a question about peripheral access between the two cores.
I'm developing a dual-core application where the CM33 acts as the main processor and the DSP handles real-time signal processing. After processing data, I'd like the DSP to directly control some peripherals (like GPIO/LEDs) to indicate status without involving the CM33 for every operation.

    

 

Labels (1)
0 Kudos
Reply
1 Solution
1,241 Views
mayliu1
NXP Employee
NXP Employee

Hi @wx1 ,

Thanks for your updated information.

A1: Yes, it is right that  the peripheral access address of both cores is the same. Please refer to RT500RM chapter2 Memory Maps

A2: I do not think  it is  your code version issue,  Currently, Zephyr's support for the MIMXRT595 is mainly focused on the Cortex-M33 core.

please create a new case for future issues. we will do our best to support you.

Best Regards

MayLiu

View solution in original post

0 Kudos
Reply
3 Replies
1,273 Views
mayliu1
NXP Employee
NXP Employee

Hi @wx1 ,

Thank you so much for your interest in our products and for using our community.

Regarding your question, please refer to IMXRT500RM, chapter 2.6 AHB Peripherals.

https://www.nxp.com/webapp/Download?colCode=IMXRT500RM

mayliu1_0-1765173907742.png

Wish it helps you.
If you still have question about it, please kindly let me know. 

Best Regards
MayLiu

0 Kudos
Reply
1,271 Views
wx1
Contributor I
Thank you, the peripheral access address of both cores is the same, right?
I'm using zephyr and rt595, but I find that there is no device tree for peripherals in DSP, Is it my code version issue?
0 Kudos
Reply
1,242 Views
mayliu1
NXP Employee
NXP Employee

Hi @wx1 ,

Thanks for your updated information.

A1: Yes, it is right that  the peripheral access address of both cores is the same. Please refer to RT500RM chapter2 Memory Maps

A2: I do not think  it is  your code version issue,  Currently, Zephyr's support for the MIMXRT595 is mainly focused on the Cortex-M33 core.

please create a new case for future issues. we will do our best to support you.

Best Regards

MayLiu

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2256110%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIMXRT595-EVK%20DSP%20and%20CM33%20Peripheral%20Access%20Isolation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256110%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20NXP%20community%2C%20I'm%20working%20with%20the%20MIMXRT595-EVK%E2%80%8B%20board%20(Cortex-M33%20%2B%20Fusion%20F1%20DSP%20dual-core%20system)%20and%20have%20a%20question%20about%20peripheral%20access%20between%20the%20two%20cores.%3CBR%20%2F%3EI'm%20developing%20a%20dual-core%20application%20where%20the%20CM33%20acts%20as%20the%20main%20processor%20and%20the%20DSP%20handles%20real-time%20signal%20processing.%20After%20processing%20data%2C%20I'd%20like%20the%20DSP%20to%20directly%20control%20some%20peripherals%20(like%20GPIO%2FLEDs)%20to%20indicate%20status%20without%20involving%20the%20CM33%20for%20every%20operation.%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2256110%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EDSP(PowerQUAD%20%7C%20Coolflux)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2256680%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20IMXRT595-EVK%20DSP%20and%20CM33%20Peripheral%20Access%20Isolation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256680%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257485%22%20target%3D%22_blank%22%3E%40wx1%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3EThank%20you%20so%20much%20for%20your%20interest%20in%20our%20products%20and%20for%20using%20our%20community.%3C%2FP%3E%0A%3CP%3ERegarding%20your%20question%2C%20please%20refer%20to%20IMXRT500RM%2C%20chapter%26nbsp%3B2.6%20AHB%20Peripherals.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.nxp.com%2Fwebapp%2FDownload%3FcolCode%3DIMXRT500RM%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.nxp.com%2Fwebapp%2FDownload%3FcolCode%3DIMXRT500RM%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22mayliu1_0-1765173907742.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22mayliu1_0-1765173907742.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22mayliu1_0-1765173907742.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22mayliu1_0-1765173907742.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F368876i7CD5DE7F38C3177E%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22mayliu1_0-1765173907742.png%22%20alt%3D%22mayliu1_0-1765173907742.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EWish%20it%20helps%20you.%3CBR%20%2F%3EIf%20you%20still%20have%20question%20about%20it%2C%20please%20kindly%20let%20me%20know.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20Regards%3CBR%20%2F%3EMayLiu%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2256705%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20IMXRT595-EVK%20DSP%20and%20CM33%20Peripheral%20Access%20Isolation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2256705%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EThank%20you%2C%20the%20peripheral%20access%20address%20of%20both%20cores%20is%20the%20same%2C%20right%3F%3CBR%20%2F%3EI'm%20using%20zephyr%20and%20rt595%2C%20but%20I%20find%20that%20there%20is%20no%20device%20tree%20for%20peripherals%20in%20DSP%2C%20Is%20it%20my%20code%20version%20issue%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2257731%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20IMXRT595-EVK%20DSP%20and%20CM33%20Peripheral%20Access%20Isolation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2257731%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257485%22%20target%3D%22_blank%22%3E%40wx1%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20updated%20information.%3C%2FP%3E%0A%3CP%3EA1%3A%20Yes%2C%20it%20is%20right%20that%26nbsp%3B%26nbsp%3Bthe%20peripheral%20access%20address%20of%20both%20cores%20is%20the%20same.%20Please%20refer%20to%20RT500RM%20chapter2%26nbsp%3BMemory%20Maps%3C%2FP%3E%0A%3CP%3EA2%3A%20I%20do%20not%20think%26nbsp%3B%20it%20is%26nbsp%3B%20your%20code%20version%20issue%2C%26nbsp%3B%20Currently%2C%20Zephyr's%20support%20for%20the%20MIMXRT595%20is%20mainly%20focused%20on%20the%20Cortex-M33%20core.%3C%2FP%3E%0A%3CP%3Eplease%20create%20a%20new%20case%20for%20future%20issues.%20we%20will%20do%20our%20best%20to%20support%20you.%3C%2FP%3E%0A%3CP%3EBest%20Regards%3C%2FP%3E%0A%3CP%3EMayLiu%3C%2FP%3E%3C%2FLINGO-BODY%3E