• AVR Freaks

Hot!Effect on hex file of enabling NVM driver in Harmony

Author
lot080420
New Member
  • Total Posts : 21
  • Reward points : 0
  • Joined: 2020/08/04 14:02:03
  • Location: 0
  • Status: offline
2020/08/20 15:42:57 (permalink)
0

Effect on hex file of enabling NVM driver in Harmony

If I configure NVM via harmony configurator to be 256K at 0x9D100000, hex file changes to have the following extra allocations
[1] In NVM memory space (0x1d100000 - 0x1d13ffff) all 0's … any way to prevent that? I really need this space to be all 0xff's
:020000041d10cd
:1000000000000000000000000000000000000000f0
:1000100000000000000000000000000000000000e0
etc
[2] Right after end of configured NVM, random values in hex file from 0x1d14000 .. 0x1d1a 0438  … anyone know why and how I can prevent this?
If I do not enable NVM then no entries in hex file for 0x1d100000 - 0x1d1fffff as expected
:020000041d14c9
:10000000e0ffbd271c00bfaf1800beaf21f0a0036a
:100010002000c4af2400c5af1000c0af2400c28fc1
#1

1 Reply Related Threads

    NKurzman
    A Guy on the Net
    • Total Posts : 19034
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: Effect on hex file of enabling NVM driver in Harmony 2020/08/20 22:44:21 (permalink)
    0
    0x1d100000 and 0x9D100000
     
    Which Chip? a PIC32? which one?
    did you look at the Section on Memory Spaces?
    Physical (0x1D) vs Cached (0x9D) vs Non-Cached (0xBD)?  They overlap.  I think those two addresses refer to the same memory (Assuming a PIC32).  the Hex file will contain the Physical Address.
    #2
    Jump to:
    © 2020 APG vNext Commercial Version 4.5