Problems with image size on MIMXRT1176

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

Problems with image size on MIMXRT1176

Jump to solution
1,573 Views
daniJVV
Contributor III

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:

 

daniJVV_0-1747210479586.png

 

Looking at the target memory, the size is wrong:

daniJVV_1-1747210522358.png

Looking at the configuration of the flash, its seems to be OK (32MB):

daniJVV_2-1747210574578.png

Created with this configuration:

daniJVV_3-1747210622909.png

 

Trying to build an image, I have the same problem.

 

daniJVV_4-1747210714977.png

 

 

What am I doing wrong?

Thank you very much

 

Tags (2)
0 Kudos
Reply
1 Solution
1,515 Views
marek-trmac
NXP Employee
NXP Employee

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?

Regards,
Marek


NOTE: If you find the answer useful, kindly click on "ACCEPT AS SOLUTION" button

View solution in original post

0 Kudos
Reply
9 Replies
1,555 Views
marek-trmac
NXP Employee
NXP Employee

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).

Regards,
Marek


NOTE: If you find the answer useful, kindly click on "ACCEPT AS SOLUTION" button
0 Kudos
Reply
1,528 Views
daniJVV
Contributor III

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:

daniJVV_0-1747215102829.png

 

But I think the problem is not with the FCB, because the limitation still being present:

daniJVV_1-1747215182493.png

 

I also tried to do a merge with the "Merge images tool", and the same happens:

daniJVV_2-1747215294193.png

 

 

0 Kudos
Reply
1,516 Views
marek-trmac
NXP Employee
NXP Employee

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?

Regards,
Marek


NOTE: If you find the answer useful, kindly click on "ACCEPT AS SOLUTION" button
0 Kudos
Reply
1,494 Views
daniJVV
Contributor III

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

0 Kudos
Reply
1,485 Views
marek-trmac
NXP Employee
NXP Employee

Hi Daniel,

for manufacturing, here is the link to documentation:

Generic workflows — MCUXpresso Secure Provisioning Tool 25.03 25.03 documentation

Regards,
Marek


NOTE: If you find the answer useful, kindly click on "ACCEPT AS SOLUTION" button
1,482 Views
liborukropec
NXP Employee
NXP Employee

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

1,477 Views
daniJVV
Contributor III

Thank both for your support! 

0 Kudos
Reply
1,563 Views
liborukropec
NXP Employee
NXP Employee

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

1,559 Views
daniJVV
Contributor III

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:

 

daniJVV_0-1747213959936.png

 

Any ideas?
Can I perform the same from different approach?

Thank you in advance

0 Kudos
Reply