Simultan access GPIO13 from core m7 and GPIO9 from core m4

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

Simultan access GPIO13 from core m7 and GPIO9 from core m4

Jump to solution
663 Views
AndreasL
Contributor I

Dear NXP team,

CPU i.mxrt1176CVM8A.

In my application I have on core m4 motor control application and on core m7 real time application.

If I access simultaneously from core m7 GPIO13 and from core m4 GPIO9, the access to GPIO9 will be delayed more than 31µs.

In the datasheet I can found chapter 13.1 And in chapter 2.1.2 System Bus Diagram following information

When LPSRMIX master is accessing GPIO13, XB will hold WAKEUPMIX master requests to any AIPS4 peripheral until current LPSRMIX master access is completed. Because GPIO13 access is based on 32 K clock as it’s in SNVS domain to save power, these WAKEUPMIX master requests could be held for over 31µs.

I understand the delay from core m7 between AIPS4 to GPIO13(LPSRMIX-Domin) but not the delay from more than 31µs to the GPIO9(WAKEUPMIX) pin GPIO_AD_31 over the direct way from core m4 to GPIO-SOC.

Please find in the attachment the bus diagram, I have marked with green and blue communications:

Please can you help me. I have with this delay a problem with the motor control cycle!

0 Kudos
Reply
1 Solution
531 Views
Pablo_Ramos
NXP Employee
NXP Employee

Hi @AndreasL,

Thanks for the information.

During the period when GPIO13 registers are being accessed, the LPSR domain bus will be on hold.

In this case, GPIO9 is part of the LPSR domain, which means that communication from the M4 core to GPIO9 must wait until the M7 core finishes accessing the GPIO13 registers.

See Table 3: i.MX RT1170 Modules List in the i.MX RT1170 Crossover Processors Data Sheet.

If the motor control cycle implementation is being affected by this behavior, you could try using a GPIO other than GPIO13.

Best Regards,

Pablo

View solution in original post

3 Replies
609 Views
Pablo_Ramos
NXP Employee
NXP Employee

Hi @AndreasL,

I am not able to see the attachment of the bus diagram. Could you please send it again?

What are the configurations of the Cortex?

What are the speeds of both Cortex?

Best Regards,
Pablo

0 Kudos
Reply
578 Views
AndreasL
Contributor I

Hi Pablo,

Many thanks for your quick response.

The cortex m7 is the master the main clock is: 792.000.000 Hz
The main clock of the cortex m4 is: 392.727.258 Hz
Bus clock root is: 240 MHz
Bus LPSR clock root is: 160 MHz

Please find also attached the configuration files.

 BusDiagram.png

Best Regards,
Andreas

0 Kudos
Reply
532 Views
Pablo_Ramos
NXP Employee
NXP Employee

Hi @AndreasL,

Thanks for the information.

During the period when GPIO13 registers are being accessed, the LPSR domain bus will be on hold.

In this case, GPIO9 is part of the LPSR domain, which means that communication from the M4 core to GPIO9 must wait until the M7 core finishes accessing the GPIO13 registers.

See Table 3: i.MX RT1170 Modules List in the i.MX RT1170 Crossover Processors Data Sheet.

If the motor control cycle implementation is being affected by this behavior, you could try using a GPIO other than GPIO13.

Best Regards,

Pablo

%3CLINGO-SUB%20id%3D%22lingo-sub-2290123%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ESimultan%20access%20%20GPIO13%20from%20core%20m7%20and%20GPIO9%20from%20core%20m4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2290123%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EDear%20NXP%20team%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ECPU%20i.mxrt1176CVM8A.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20my%20application%20I%20have%20on%20core%20m4%20motor%20control%20application%20and%20on%20core%20m7%20real%20time%20application.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20I%20access%20simultaneously%20from%20core%20m7%20GPIO13%20and%20from%20core%20m4%20GPIO9%2C%20the%20access%20to%20GPIO9%20will%20be%20delayed%20more%20than%2031%C2%B5s.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20the%20datasheet%20I%20can%20found%20chapter%2013.1%20And%20in%20chapter%202.1.2%20System%20Bus%20Diagram%20following%20information%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20LPSRMIX%20master%20is%20accessing%20GPIO13%2C%20XB%20will%20hold%20WAKEUPMIX%20master%20requests%20to%20any%20AIPS4%20peripheral%20until%20current%20LPSRMIX%20master%20access%20is%20completed.%20Because%20GPIO13%20access%20is%20based%20on%2032%20K%20clock%20as%20it%E2%80%99s%20in%20SNVS%20domain%20to%20save%20power%2C%20these%20WAKEUPMIX%20master%20requests%20could%20be%20held%20for%20over%2031%C2%B5s.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20understand%20the%20delay%20from%20core%20m7%20between%20AIPS4%20to%20GPIO13(LPSRMIX-Domin)%20but%20not%20the%20delay%20from%20more%20than%2031%C2%B5s%20to%20the%20GPIO9(WAKEUPMIX)%20pin%20GPIO_AD_31%20over%20the%20direct%20way%20from%20core%20m4%20to%20GPIO-SOC.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EPlease%20find%20in%20the%20attachment%20the%20bus%20diagram%2C%20I%20have%20marked%20with%20green%20and%20blue%20communications%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EPlease%20can%20you%20help%20me.%20I%20have%20with%20this%20delay%20a%20problem%20with%20the%20motor%20control%20cycle!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2290657%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Simultan%20access%20%20GPIO13%20from%20core%20m7%20and%20GPIO9%20from%20core%20m4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2290657%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20Pablo%2C%3C%2FP%3E%3CP%3EMany%20thanks%20for%20your%20quick%20response.%3C%2FP%3E%3CP%3EThe%20cortex%20m7%20is%20the%20master%20the%20main%20clock%20is%3A%20792.000.000%20Hz%3CBR%20%2F%3EThe%20main%20clock%20of%20the%20cortex%20m4%20is%3A%20392.727.258%20Hz%3CBR%20%2F%3EBus%20clock%20root%20is%3A%20240%20MHz%3CBR%20%2F%3EBus%20LPSR%20clock%20root%20is%3A%20160%20MHz%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20find%20also%20attached%20the%20configuration%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22BusDiagram.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22BusDiagram.png%22%20style%3D%22width%3A%20349px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22BusDiagram.png%22%20style%3D%22width%3A%20349px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F372258iB65BDE40D00DC153%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22BusDiagram.png%22%20alt%3D%22BusDiagram.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EBest%20Regards%2C%3CBR%20%2F%3EAndreas%3C%2FP%3E%3CP%3E%E2%80%83%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2290406%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Simultan%20access%20%20GPIO13%20from%20core%20m7%20and%20GPIO9%20from%20core%20m4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2290406%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F189442%22%20target%3D%22_blank%22%3E%40AndreasL%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3EI%20am%20not%20able%20to%20see%20the%20attachment%20of%20the%20bus%20diagram.%20Could%20you%20please%20send%20it%20again%3F%3C%2FP%3E%0A%3CP%3EWhat%20are%20the%20configurations%20of%20the%20Cortex%3F%3C%2FP%3E%0A%3CP%3EWhat%20are%20the%20speeds%20of%20both%20Cortex%3F%3C%2FP%3E%0A%3CP%3EBest%20Regards%2C%3CBR%20%2F%3EPablo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2291136%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Simultan%20access%20%20GPIO13%20from%20core%20m7%20and%20GPIO9%20from%20core%20m4%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2291136%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%2F189442%22%20target%3D%22_blank%22%3E%40AndreasL%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3EThanks%20for%20the%20information.%3C%2FP%3E%0A%3CP%3EDuring%20the%20period%20when%20GPIO13%20registers%20are%20being%20accessed%2C%20the%20LPSR%20domain%20bus%20will%20be%20on%20hold.%3C%2FP%3E%0A%3CP%3EIn%20this%20case%2C%20GPIO9%20is%20part%20of%20the%20LPSR%20domain%2C%20which%20means%20that%20communication%20from%20the%20M4%20core%20to%20GPIO9%20must%20wait%20until%20the%20M7%20core%20finishes%20accessing%20the%20GPIO13%20registers.%3C%2FP%3E%0A%3CP%3ESee%20Table%203%3A%20i.MX%20RT1170%20Modules%20List%20in%20the%20i.MX%20RT1170%20Crossover%20Processors%20Data%20Sheet.%3C%2FP%3E%0A%3CP%3EIf%20the%20motor%20control%20cycle%20implementation%20is%20being%20affected%20by%20this%20behavior%2C%20you%20could%20try%20using%20a%20GPIO%20other%20than%20GPIO13.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20Regards%2C%3C%2FP%3E%0A%3CP%3EPablo%3C%2FP%3E%3C%2FLINGO-BODY%3E