Hi!
I got the Ethernet connection working to my bootloader. FM successfully erases selected flash blocks and FM can read the flash memory of my LPC2366 on my own PCB board.
But... When it comes to writing the new .hex file to the flash something goes wrong.
The message Operation Failed. (programming - failed to send data to the device) pops up and the procedure stops. (Allthough FM reports Finished at the status field at the bottom of the program).
The erased flash blocks are the ones used by the new .hex file. Block 5 - 10.
I managed to run the UART debug to see what happends during flash write. This is what happends:
LPC Rx: U 23130
LPC Tx: 0
LPC Rx: W 1073742336 512.
LPC Tx: 0
LPC Rx: ...Data...
...
LPC Rx: ...Data...
LPC Rx: 44524
LPC Tx: OK
LPC Rx: W 1073742848 512
Here it stops...
In the Rowley debugger, it seems as the code runs into a dabort_handler.
Any ideas?
Please see the debug file attached.
Regards
I got the Ethernet connection working to my bootloader. FM successfully erases selected flash blocks and FM can read the flash memory of my LPC2366 on my own PCB board.
But... When it comes to writing the new .hex file to the flash something goes wrong.
The message Operation Failed. (programming - failed to send data to the device) pops up and the procedure stops. (Allthough FM reports Finished at the status field at the bottom of the program).
The erased flash blocks are the ones used by the new .hex file. Block 5 - 10.
I managed to run the UART debug to see what happends during flash write. This is what happends:
LPC Rx: U 23130
LPC Tx: 0
LPC Rx: W 1073742336 512.
LPC Tx: 0
LPC Rx: ...Data...
...
LPC Rx: ...Data...
LPC Rx: 44524
LPC Tx: OK
LPC Rx: W 1073742848 512
Here it stops...
In the Rowley debugger, it seems as the code runs into a dabort_handler.
Any ideas?
Please see the debug file attached.
Regards