parsing - Can addresses in Intel Hex be overlapped? -


I'm trying to write a simple Intel hex parser myself.

And even after reading the wiki I have some questions.

1. Can the address be overlapped? I mean this check is always right?

  if (hexal [k] -> gtk + hexal [k] -> count> gt; hexale [k] of [1] - & gt; address) HEX_DEBUG is sorted ("[%" PRIx16 "] address and [%" PRIx16 "]" "overlapping", hexcel [k] -> address, hexal [of + 1] - & gt; address); Return HEX_EOVERLAP; }  

2. Could there be a difference between the address hex file used to load some EPOS? I mean, I should use

  (if 1 of hexal [k] -> address + hexal [k] - gt; count & gt; hexale [of + 1] - & Gt; Address) {} / / & gt; Compare or if (hexal [k] -> address + hexal [k] -> gt; count = hexcel [k-1] - & gt; address) //! = Comparison  

probe. I could not find some restrictions on this.

  1. I have never been overlapping in my practice, so I'm also interested in knowing this But, more broadly, while considering this matter, when any record can be overlapping, not only thinks the next case as wrong.
  2. It is very specific to target memory, but it is very common to take place. I am developing firmware for microcontrollers and as a result there are several memory areas in hex file. Each area starts with the "extended linear address" record.

Comments

Popular posts from this blog

ios - How do I use CFArrayRef in Swift? -

eclipse plugin - Run java code error: Workspace is closed -

c - Error on building source code in VC 6 -