Closed stephendpmurphy closed 3 years ago
I should add that executing an erase command on the part ALWAYS works, regardless of the current ability to flash the part.
So I have some more info to report back. I am also debugging and building the same source for the LPC55S28 which is the micro used when purchasing an LPC55xx dev kit.. I am able to flash and erase the dev kit no problem using my same DAPLink probe with PyOCD.
So after some digging I noticed that the LPC55S28 is shipped with PyOCD and the target_lpc55s28.py
includes the target_lpc5500.py
file which had a comment that seems very suspicious and likely my problem.
Is the suggested fix for getting LPC5526 support in PyOCD to add the target as a buit-in then?
Just finished adding a built-in target for the LPC5526 and this appears to have cleared up my issues. I can now flash, erase and debug no problem :+1:
Hi all,
I am getting a repeated issue when attempting to flash a blank LPC5526 using pyocd. It always results in a Memory Transfer Fault. This issue persists when using a custom DAP-Link programmer as well as a JLink Plus.
The only way to get the device usable is to use the JLinkExe utility with my JLink Plus to program the part. Once the part is programmed, I can then use PyOCD and any of my probes to flash and debug the part. The issue comes back as soon as I erase the part again.
@flit I know when working with you recently on the LPC55S69 and DAP-Link there were noted issues with programming the part in which I was ALSO able to get around by using the full Segger suite. Is this related/still a known issue?
Error output: