TMS320F28388D: Uniflash message: File Loader: Verification failed: Values at address 0x200000@Program do not match Please verify target and memory map

Hi Sebastian,

1) Did you program any DCSM security settings in the OTP on this device previously?  Please check your linker command file/map file to see if anything is mapped to the DCSM USER OTP.

2) If not standalone verify, does full erase and program load work fine without verify errors?

Thanks and regards,
Vamsi

More details below:

 - Arm project is set to: rom with = 16, memory width = 16.

 - Contents of the image flashed by uniflash is not equal to .hex file

hex file:                            F000 BAD6 4770 0000
uniflash view:                   D6BA 00F0 0000 7047
memory map view:           00F0 D6BA 7047 0000 

It seems like the uniflash is changing the bytes order.

fsbl_cpu3.zip
he order of bytes.

Hi Sebestian,

Hex-file is showing 16-bit data.  Uniflash view is showing 32-bit data.  Hence, both are same.

What do you mean by memory map view?  

Thanks and regards,
Vamsi

Hi, 

In my opinion there is a conversion :Big Endian <-> Little Endian and additionaly Mid Big Endian <-> Mid Little Endian.

1a_out16.jpg and 1b_out16.jpg shows .out file which was used to flash memory.

As you can see .hex file is the same as in Memory Browser (ccs side) - F000 BAD6 4770 0000  the same order of bytes. 

2a_out16.jpg and 2b_out16.jpg shows .hex file which was used to flash memory.

As you can see .hex file is not the same as in Memory Browser (ccs side) - F000 BAD6 4770 0000 vs 00F0 D6BA 7047 0000

Conclusion:

- When I flash the memory using UniFlash with .out file then program after flashing and restarting  starts properly.

- When I flash the memory using UniFlash with .hex file then program after flashing and restarting  doesn't start properly, because the order of bytes in the flashed memory is not the same as in .hex file: F000 BAD6 4770 0000 vs 00F0 D6BA 7047

Hi Sebastian,

How did you generate the hex file?  

Thanks and regards,
Vamsi

Hi Vamsi,

hex file is generated using tektronix format.

Hi,

This is the command.

Ki said:

Carefully check your screenshot. You have the C28xx CPU1 selected. You are flashing to C28xx and NOT the M4.

To clarify:

Hi Sebastian,

Did you check Ki's suggestion on selecting the correct core to program the image?

Thanks and regards,

Vamsi

Hi,

It seems that problem was in generating .hex file in the tektronix format. Uniflash works properly, bytes are not swapped. Thank you for your support.

Hi Sebastian,

Thank you for the update. I am closing this post.  

Regards,

Vamsi