Hi,
Thanks for sharing your experience - I'm running into a very similar issue and hoping you might have found a solution since posting this.
I'm using an NVEM V5 board (RT1052 chip). I successfully flashed the firmware via pyOCD (tried multiple firmware versions: remora-rt1052-NVEM-0.2.1.bin, remora-rt1052-0.0.1.bin, remora-rt1052.bin - all flashed without errors). Ping to 10.10.10.10 works perfectly and consistently.
However, unlike your case, I'm getting a timeout on my very first config upload attempt - not after a successful first upload. I've tried:
- My own custom config file
- The unmodified official example configs (both nvem-rt1052.txt and remora-rt1052-basic/ec500-rt1052.txt)
- Uploading with the SWD/ST-Link connection both attached and disconnected during the upload
- Confirmed via tcpdump that the WRQ packet is sent correctly on port 69, but no response ever comes back from the board
- No firewall involved (iptables set to ACCEPT), direct point-to-point Ethernet connection, no router
The script always confirms "Valid JSON config file" and calculates the CRC correctly, so it gets stuck at exactly the same point you describe - after everything on the PC side looks fine.
Did you ever find out what caused the board to stop responding to TFTP? Was it possibly related to the eStop/enable state getting stuck, as you mentioned the LED stayed permanently lit? Any insight into how you (or anyone else) resolved this would be hugely appreciated - trying to avoid unnecessary re-flashing if there's a known cause.
Thanks in advance!