Currently I have a script that flashes the SD Card as follows:
dd if=u.bin of=/dev/mmcblk0 bs=512 seek=8 && sync
dd if=fsl_fman_ucode_t2080_r1.1_108_4_5.bin of=/dev/mmcblk0 bs=512 seek=1500 && sync
dd if=iram_Type_A_LS1021a_r1.0.bin of=/dev/mmcblk0 bs=512 seek=1580 && sync
I was having problems when the SPL was loading that part of the data was being corrupted.
Well, I had a thought. What if the U-Boot was extending beyond the 1500 sector where I write
Well, if I changed these lines to:
dd if=fsl_fman_ucode_t2080_r1.1_108_4_5.bin of=/dev/mmcblk0 bs=512 seek=1800 && sync
dd if=iram_Type_A_LS1021a_r1.0.bin of=/dev/mmcblk0 bs=512 seek=1880 && sync
U-Boot data wasn't being corrupted.
Obviously, I need to modify these locations in software!
I do understand that - I am asking for some guidance if our u-boot is larger than the allocated area.
As indicated from the original post, we were given by NXP a script that wrote these 3 sections:
But, when writing u-boot (dd if=u.bin of=/dev/mmcblk0 bs=512 seek=8 && sync) indicates:
"1621+1 records out"
Are you saying that the script we have is wrong?
Thanks in advance.