Firmware and bootloader binary file issues

[pyi285]

If you do firmware and check the internal flash, the picture below appears. However, if you build it as a binary file, you get the same result as the picture on the right.
Is there a reason for this or is there any way I can fix it?

1. The difference between the two pictures is that the FF part is displayed as 00. Please explain the reason.
2. Please explain if there is any other way to solve the binary file problem.
3. Finally, looking at the address 00000, what exactly does the first line of the 015A000 part do?
#mpc5674f #bootloader # Binary

[pyi285]

In the first question, do you know why the values stored in the board's flex memory and changed to binary files are different when building as a binary file in CodeWarrior?
ex)
Flex status saved on board after firmware
015A0000 00010110 FFFFFFFF FFFFFFFF
When you open a binary file after building it as a binary file
015A0000 00010110 00000000 00000000
Is there any way to solve the result where FFFFFFFF FFFFFFFF should come out as 00000000 00000000?

[davidtosenovjan · Accepted solution]

Are you using .elf/.srec file what usual practice, then only used address ranges are included in the file. Check whether mentioned area is defined in the linker command file.

[pyi285]

If so, is there any way to float it with an F other than 0?

[davidtosenovjan]

I have find a document dealing with this topic:

https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/cw-mcu/13290/1/ANxxxx_Fill_Pattern_featu...

[pyi285]

#pragma fill_alignment_data_with_FF on

Can you tell me where to put this?
I would be very grateful if you could attach a picture

[davidtosenovjan]

I am not sure what you are trying to compare as you are loking for different addresses 0x0001_0000 vs 0x0000_0000.

Anyway these are two booting address options from following sets:
0x0000_0000
0x0000_4000
0x0001_0000
0x0001_C000
0x0002_0000
0x0003_0000

and pattern on that address in Reset Configuration Half Word