I'm trying to create a image to flash a MIMXRT1176.
We are using a IS25WP256 QSPI flash (32MB, size 0x02000000).
I have 3 different bins, in well-defined memory positions:
-Firmware: Starting in 0x30000000
-Audio: Starting in 0x300F0000
-Images: Starting in 0x30400000
I tried this whole project flashing the bins separately with MCUXpresso IDE, and it's working.
But I need to create a unique file for bootloader and production flashing purposes.
I did a merge with srec_cat to create a unique HEX file, with size = 0x01640c40 (<0x02000000)
When I try to use this .hex in "Flash Programmer Tool", i have this error:
Looking at the target memory, the size is wrong:
Looking at the configuration of the flash, its seems to be OK (32MB):
Created with this configuration:
Trying to build an image, I have the same problem.
What am I doing wrong?
Thank you very much
已解决! 转到解答。
Hi Daniel,
it seems we have limitation in Flash Programmer to maximal size 0x1000000 (16MB).
Have you tried the build & write with the merged image?
Have you tried Additional Images instead of merged image, what I recommended in the previous post?
Hi Daniel,
if the problem is still reproducible, can you attach the FCB binary file, so we can reproduce the issue on our side?
Just a note: instead of merging images into one binary, you can specify additional images at the build page, see button "Additional images" (this may safe some time writing the data into flash).
I send you attached the file.
I'm using this converted_fcb, created with simplified with correct memory size (0x2000000)
The test is OK with this fcb:
But I think the problem is not with the FCB, because the limitation still being present:
I also tried to do a merge with the "Merge images tool", and the same happens:
Hi Daniel,
it seems we have limitation in Flash Programmer to maximal size 0x1000000 (16MB).
Have you tried the build & write with the merged image?
Have you tried Additional Images instead of merged image, what I recommended in the previous post?
With the new version of SPT, and doing the build and write it's working now!
But I need a simple solution for manufacturing.
Can I create a unique file to write?
I saw the manufacturing tool, but I didn't find much information about it.
Thank you very much
Hi Daniel,
for manufacturing, here is the link to documentation:
Generic workflows — MCUXpresso Secure Provisioning Tool 25.03 25.03 documentation
Hi @daniJVV ,
I'd add one note - if build & write works for you, then also manufacturing will work, no need to change the workflow just because of manufacturing tool. Just follow the documentation to create a manufacturing package and then import it.
Regards,
Libor
Hi Daniel,
on the first look the memory configuration size looks good, but not the computed range in the Flash programmer.
1. Can you confirm what version of SEC tool you are using? Looks like you are using quite old version.
2. Could you try if you reproduce in the latest SEC tool 25.03?
Regards,
Libor
Hi Libor,
Thanks for your answer.
Now seems that the size of target memory is correct, but when trying to load the HEX file same error appears:
Any ideas?
Can I perform the same from different approach?
Thank you in advance