Cannot have code in multiple RAMs when using MCUXpresso Secure Provisioning tool

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

Cannot have code in multiple RAMs when using MCUXpresso Secure Provisioning tool

263 Views
nxp16
Contributor III

Our project on the IMXRT1171 boots from SD card and runs from RAM.  Previously most of our code fit into ITC RAM, and MCUXpresso Secure Provisioning tool had no issue with it as long as we modified our start address to 0x3000 (and modified the size -0x3000 smaller).  However, we started running out of ITC RAM and had to move some functions (via linker templates) to OCRAM.  After doing this, MCUXpresso Secure Provisioning tool now complains that it does not support code in different memories.  I was hoping to avoid moving everything into OCRAM but it looks like that's what I'm going to have to do now.  Is there some other workaround to get the tool to work with code in two separate RAMs?

 

Thanks!

-m

0 Kudos
Reply
1 Reply

169 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hi @nxp16,

Could you please specify what error you are getting from SPT? In any case, my recommendation would be to use the FlexRAM capabilities of the i.MX RT1170 to adjust the size of the ITC RAM to your application's needs. Here is an AppNote that explains how to do so: AN12077: Using the i.MX RT FlexRAM – Application Note

BR,
Edwin.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2354295%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ECannot%20have%20code%20in%20multiple%20RAMs%20when%20using%20MCUXpresso%20Secure%20Provisioning%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2354295%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EOur%20project%20on%20the%20IMXRT1171%20boots%20from%20SD%20card%20and%20runs%20from%20RAM.%26nbsp%3B%20Previously%20most%20of%20our%20code%20fit%20into%20ITC%20RAM%2C%20and%20MCUXpresso%20Secure%20Provisioning%20tool%20had%20no%20issue%20with%20it%20as%20long%20as%20we%20modified%20our%20start%20address%20to%200x3000%20(and%20modified%20the%20size%20-0x3000%20smaller).%26nbsp%3B%20However%2C%20we%20started%20running%20out%20of%20ITC%20RAM%20and%20had%20to%20move%20some%20functions%20(via%20linker%20templates)%20to%20OCRAM.%26nbsp%3B%20After%20doing%20this%2C%26nbsp%3BMCUXpresso%20Secure%20Provisioning%20tool%20now%20complains%20that%20it%20does%20not%20support%20code%20in%20different%20memories.%26nbsp%3B%20I%20was%20hoping%20to%20avoid%20moving%20everything%20into%20OCRAM%20but%20it%20looks%20like%20that's%20what%20I'm%20going%20to%20have%20to%20do%20now.%26nbsp%3B%20Is%20there%20some%20other%20workaround%20to%20get%20the%20tool%20to%20work%20with%20code%20in%20two%20separate%20RAMs%3F%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3E-m%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2355463%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Cannot%20have%20code%20in%20multiple%20RAMs%20when%20using%20MCUXpresso%20Secure%20Provisioning%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2355463%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%2F70127%22%20target%3D%22_blank%22%3E%40nxp16%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3ECould%20you%20please%20specify%20what%20error%20you%20are%20getting%20from%20SPT%3F%20In%20any%20case%2C%20my%20recommendation%20would%20be%20to%20use%20the%20FlexRAM%20capabilities%20of%20the%20i.MX%20RT1170%20to%20adjust%20the%20size%20of%20the%20ITC%20RAM%20to%20your%20application's%20needs.%20Here%20is%20an%20AppNote%20that%20explains%20how%20to%20do%20so%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Fapplication-note%2FAN12077.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EAN12077%3A%20Using%20the%20i.MX%20RT%20FlexRAM%20%E2%80%93%20Application%20Note%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EBR%2C%3CBR%20%2F%3EEdwin.%3C%2FP%3E%3C%2FLINGO-BODY%3E