This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ATE flash doesn't appear to be committing AUTO PATCH data (NRF52)

Hi there,
  I'm new to using an ATE and a NRF52 and I'm trying to use an ATE array with telnet commands to program firmware on 10 devices.  After the firmware is applied, our goal is to program a couple of memory addresses with serialized data. Our product uses a NRF52 chip.  I'm trying to isolate just the application of the memory addresses as follows:
1) reboot a device that has been successfully reprogrammed with the ATE
2) telnet to the ATE device
3) verify #status of the ATE
4) #auto patch 1 1,10001080,4:55555555
5) Receive immediate #ACK
6) wait for receive #RESULT:1:OK: (Total 17.312s, Erase 11.251s, Prog 5.730s, Verify 0.316s)
7) Receive #DONE
8) Power cycle device
9) attempt to read memory location with #read 1 10001080,4
10) receive back #DONE1:OK:FFFFFFFF
Am I missing something here?   would love any guidance you can offer
Parents
  • Providing an answer to my own problem here, the issue with my usage of the #AUTO PATCH on the ATE is that the ATE requires a memory address to be present in the original HEX file as a flag in order to be patched.  If the hex file never comes across 0x10001080 in the source hex file, it'll never get around to PATCHING that location.  Adding dummy data at that location as a target for programming allowed the AUTO PATCH process to burn our data.

Reply
  • Providing an answer to my own problem here, the issue with my usage of the #AUTO PATCH on the ATE is that the ATE requires a memory address to be present in the original HEX file as a flag in order to be patched.  If the hex file never comes across 0x10001080 in the source hex file, it'll never get around to PATCHING that location.  Adding dummy data at that location as a target for programming allowed the AUTO PATCH process to burn our data.

Children
No Data
Related