Understanding data in cypress hex file

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
ansh_2022771
Level 2
Level 2
First like received First like given

Hi,

I was parsing generated hex file of my boot-loadable project. I am using 256K flash which is from 0x00000000 to 0x0004000.

Something didn't make sense in the end of the hex file

Intel hex file format : GENERAL: INTEL HEX FILE FORMAT

04 - extended linear address record, and you can see addresses as 90300000, 90400000 and so on. I am attaching the data as well.

:0200000490303A

:020000000FAF40

:0200000490402A

:4000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C0

:400040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000080

:0200000490501A

:0C00000000020E34119E00010EB0214DD4

:0200000490600A

:0100000001FE

:00000001FF

Can anyone tell me anything about this memory location and what are we saving here  ?

0 Likes
1 Solution
MeenakshiR_71
Employee
Employee
100 likes received 50 likes received 25 likes received

Anish,

Please refer to PSoC 6 Programming Specifications | Cypress Semiconductor section 3.1 (Organization of the hex file) for details.

In addition to the data that goes into flash, the hex files saves additional content like checksum, metadata and eFuse data as part of the hex file. Since these data do not map to any physical memory address, the 0x90xxxxxx address space is reserved for this purpose in the hex file.

Let me know if this helps.

Regards,

Meenakshi Sundaram R

View solution in original post

0 Likes
1 Reply
MeenakshiR_71
Employee
Employee
100 likes received 50 likes received 25 likes received

Anish,

Please refer to PSoC 6 Programming Specifications | Cypress Semiconductor section 3.1 (Organization of the hex file) for details.

In addition to the data that goes into flash, the hex files saves additional content like checksum, metadata and eFuse data as part of the hex file. Since these data do not map to any physical memory address, the 0x90xxxxxx address space is reserved for this purpose in the hex file.

Let me know if this helps.

Regards,

Meenakshi Sundaram R

0 Likes