Hi,
I'm trying to create a bootable image (from QSPI) that executes code from ITCM. I'm currently able to create a bootable image that executes code from flash but I have a timing issues: the code seems not to be executing at the same speed in comparission when executing from ITCM (debugging).
I referred to the following link to create the bootable images: https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/Generating-a-Bootable-Image-for-the-RT1050/ta-p/...
It works fine when creating the image executing from flash, but when I tried to create an image that executes from ITCM (using the file imx-itcm-unsigned-dcd.bd ofcourse) the first command that creates the .bin fails letting the bin as 0Bytes (nopadding bin file isn't created either). So I don't know what it is probably happening. My project is configured like this:
So I'm putting the code in ITCM when linking the code to RAM and all the data heap and stack is being placed at DTCM (I'm using FreeRTOS whit the Newlib-semihost configuration).
In the guide they say that we have to change the ivtOffset to 0x1000 but the example is for running in DTCM, I don't know if this applies also for running in ITCM. Also the bd file for ITCM has a note telling:
# Note: This is an example address, it can be any non-zero address in ITCM region
My ITCM memory starts at 0 so I tried so many addresses for this files (even the 0) but the result is always the same, the bin file is always created with 0Bytes.
Is there something I'm missing or is there an extra configuration I need for running from ITCM?
Thank you so much!!
@kerryzhou Thank you so much for your answer. I imported the blink led example from the SDK, modified the memory map to link the code to ITCM and put the start location at 0x2000 as you recommended but unfortunately the problem is the same. When I used the file imx-itcm-unsigned.bd with the elftosb.exe -f imx -V -c command, the bin generated is 0KBs. I tried to do it for the DTCM and the result is the same. The project's configuration is this:
Maybe there is something missing I have to configure, other than the memory regions. This process works fine when I use the imx-flexspinor-normal-unsigned.bd when the code is in flash. But in RAM isn't working
Hi MissaelMaciel,
Thanks for your updated information.
If it is your customer board, I think we need to make sure it works at first.
Do you fanout the debug pins? SWD interface.
If yes, I highly recommend you use the debugger to check, whether your board can download code, check the external QSPI flash, and boot at first.
Just make sure the hardware works OK, then you can use the MFGTool to download the code.
Because, if your hardware have issues, and you use the MFGtool download, you may just see it can't boot, it is not easy to find the root issues.
Now, please run this sdk code in your internal RAM at first:
SDK_2.9.1_EVKB-IMXRT1050\boards\evkbimxrt1050\driver_examples\flexspi\nor
Please run it at first, when you can finish all the qspi flash read, erase, write successfully?
If it can write successfully, then you can download a simple project with debugger, eg, led_blinky, exit the debugger, and run it, whether your gpio can toggle or not?
Please check it at first, any updated information, please kindly let em know.
Best Regards,
Kerry
Hi @kerryzhou thanks for your quick answer.
I think I had not explained myself well. The issue is not booting.
When I posted this issue for help I explained that I'm able to create a bootable image, boot from QSPI and run de code from flash. The board works fine and it seems not to have issues.
Since our product is critical, we cannot take the risk of executing code from flash using cache due to memory overruns, that's why whe want to execute code from ITCM.
The main issue is that when using the elftosb tool, I cannot create the "xx_nopadding.bin" because it is always created as 0KB size when I execute this command: elftosb.exe -f imx -V -c ../../bd_file/imx10xx/imx-itcm-unsigned.bd -o evkbimxrt1050_hello_world_itcm.bin evkbimxrt1050_hello_world_itcm.s19
So the issue is with the tools and no with the HW. I configured the helloworld SDK example to link code to ITCM, I generated the S19 but the elftosb tool fails in the 1st step.
I can debug this project, I can create the bootable image and boot from QSPI with this project when code executes in flash but not when I want to create the image to execute code from ICTM.
Please revisit the very very first post in the thread (when I open de issue) for this details. The issue is with the tools.
Thank you so much,
Missael Maciel
Hi MissaelMaciel,
Your issue can't generate the ivt_evkbimxrt1050_iled_blinky_0xa000_nopadding.bin, should still related to your image.
Please follow me and try again, I already make it works on MIMXRT1050-EVKB board with QSPI flash.
1. your code, take mcuxpresso project as an example, led_blinky.
Then build the project and generate the .s19 file:
You will get the evkbimxrt1050_iled_blinky_0xa000.s19.
Check the .s19 image:
From 0xa000, it's correct!
2. imx-itcm-unsigned.bd
options {
flags = 0x00;
# Note: This is an example address, it can be any non-zero address in ITCM region
startAddress = 0x8000;
ivtOffset = 0x1000;
initialLoadSize = 0x2000;
# Note: This is required if the default entrypoint is not the Reset_Handler
# Please set the entryPointAddress to Reset_Handler address
entryPointAddress =0x0000a305;
}
sources {
elfFile = extern(0);
}
section (0)
{
}
entryPointAddress =0x0000a305; is the app entry point, check 0xa000+4 address data in the app image.
4. generate the related files
cmd:
./elftosb.exe -f imx -V -c imx-itcm-unsigned.bd -o ivt_evkbimxrt1050_iled_blinky_0xa000.bin evkbimxrt1050_iled_blinky_0xa000.s19
./elftosb.exe -f kinetis -V -c program_flexspinor_image_qspinor.bd -o boot_image.sb ivt_evkbimxrt1050_iled_blinky_0xa000_nopadding.bin
You can find my related file is OK, and get the .sb file
5. use MFGTool to download the code
So, totally works OK with ITCM.
Please check my attached project and files.
If you still have issues, please use my attached files.
Wish it helps you!
Best Regards,
Kerry
Hi carlosflr,
Read this application note at first:
https://www.nxp.com/docs/en/application-note/AN12077.pdf
Internal ITCM to RT1050 is 128KB in default, not 256KB.
If you want to use 256K, you need to reconfigure the flexRAM:
I mean, because the start address can't be 0 in the bd, so maybe you need from 0X3000 instead of 0X2000.
But you can try 0X2000 on your side, whether it work OK or not.
Because I find the MCUBootUtility can use the app from 0X2000, so it should works you can try 0X2000 app on your side.
You also can use this tool instead of the MFGtool, it is more easy to use:
https://github.com/JayHeng/NXP-MCUBootUtility/releases/tag/v3.1.1
the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility
Wish it helps you!
Best Regards,
Kerry
Best Regards,
Kerry
Hi,
I'm posting this for anyone that get into a similar issue with the i.MXRT family. The issue behind following the AN12077 is that the way to change FlexRAM sizes on Runtime (section 2.1.1.2) can only be achieved if the image to be load into any of FlexRAM sections (ITC in this case) can fit into the default section size (set by the eFuses). For example, in this specific scenario, we created a >128kb bootable intended to be executed in ITC, in that image program we were trying to reconfigure the ITC size to 256kb, so the image could fit on it. The problem behind this rationale is that the code to reconfigure FlexRAM (normally placed in ResetHandler) won't be executed until bootROM copies all the image from FLASH to ITC, and since ITC default value is set to 128kB, then bootROM fails to copy the image.
One solution for this issue is to add the configuration of the FlexRAM in the DCD file. This DCD file will be executed by the BootROM before copying the image from FLASH to ITC. These are the steps to perform this solution:
1. Using MCUXresso Config Tools, open Device Configuration Data (DCD)
2. Choose Output Format: Binary (So we can provide the .bin to elftosb tool, or MCUBootUtility)
2. Add the commands needed to configure FlexRAM. The commmands for a 256kB ITC, 128kB DTC and 128kB OCRAM are shown below:
3. Update the Code so MCUXpresso generates the binary.
Now, we just need to add the dcd.bin file to our boot descriptor (.bd) file by adding the following statement:
DCDFilePath = "/dcd/file/path/dcd.bin";
Then, generate the bootable image with the imx and kinetis commands from elftosb and flash it to the devide using mfgtools (or MCUBootUtility).
Now the bootROM will execute the commands from the dcd file and therefore enlarging ITC to 256kb, then it will copy the image to ITC.
Hi MissaelMaciel,
You mentioned, you are using:imx-itcm-unsigned-dcd.bd
Do you also use the SDRAM? If not, you don't need to use the dcd.
About the app, I suggest you use the simple project to try your ITCM, eg, the SDK helloworld, led_blinky code. Generate the related ITCM app code, and use the imx-itcm-unsigned.bd, try it again.
imx-itcm-unsigned.bd can be found from the SDK:
SDK_2.9.1_EVKB-IMXRT1050\middleware\mcu-boot\bin\Tools\bd_file\imxrt105x
BTW, normally, you need to leave some ITCM space for the ITCM, so you can relocate your app from 0Xa000, or 0x2000. You can't just relocate to ITCM 0.
Your following picture:
location ITCM from 0X2000/0XA000, SIZE: 0X40000-0X2000/0X40000-0XA000
In your imx-itcm-unsigned.bd:
options {
flags = 0x00;
# Note: This is an example address, it can be any non-zero address in ITCM region
startAddress = 0xa000;
ivtOffset = 0x400;
initialLoadSize = 0x2000;
# Note: This is required if the default entrypoint is not the Reset_Handler
# Please set the entryPointAddress to Reset_Handler address
// entryPointAddress = 0x60002411;
}
Please try it again.
If you still have questions about it, please kindly let me know.
Best Regards,
Kerry
