It appears that using the Secure Provisioning Tool to program a pre-built image into an RT1050 the image is placed at 0x60001000 instead of 0x60000000. This results in an image that does not boot. Using the SDP and BLHOST utilities from the command line and placing the same image at 0x60000000 the result is an image that boots correctly.
1. Why does the tool place the image offset by 0x1000?
2. Is there a way to change this offset?
Here is a snippet from the log file of the tool when it writes the image into FLASH.
/Applications/MCUX_Provi_v1/MCUXpresso Secure Provisioning Tools v1.app/Contents/MacOS/tools/blhost/mac/blhost -u 0x15A2,0x0073 -j -- write-memory 0x60001000 /Users/andrewm/MUN4_NXP_provisioning_tool/u-boot.bin 9
Thanks for the information, that's helpful in understanding how the tool works. Is there any way to change the settings of the tool in order to accommodate a bootable image that includes the FCB already?
currently such image is not supported. However you can specify custom FCB content using:
toolbar - Boot Device - flex-spi-nor/user FCB file
write expects the bootable image without FCB configuration (_nopadding.bin). Typical workflow for images located in flash:
You can find detailed description in the documentation, chapter Workflow.