I am using ULinkPro Debugger to program and debug software on NXP LPC4088FBD144 MCU.
While downloading program in debug mode, I am getting following error message "Cannot access memory" and "Cannot enter Debug Mode". Downloading program on MCU is not possible.
I tried changing Max Clock frequency (all values of frequency) in Target Driver Setup - Debug - Settings to solve the problem. Problem not solved.
Please suggest a suitable solution to the problem.
>>Please suggest a suitable solution to the problem.
Have you contacted technical support? Try that
Does your system otherwise function? Who designed the board, and who validated the connectivity of the trace connector? Do any of the pins on the trace side have dual use? ie are they connected to high order address bits on an external memory bus, etc. Can that conflict with normal/trace operation? Have you configured the board for trace? Have you tested the trace pod on any known working board/hardware? Do you have a high quality USB cable connecting the pod, it is very fussy.
Thank you for your reply to my post.
I am using custom designed board. However, after experimenting with uVision Keil v5.14, I have observed said errors disappear.
After setting, Options for Target 1 -> Debug -> Settings -> Debug (Cortex-M Target Driver Setup) -> Connect and Reset Options -> With Pre-Reset said problems disappear.
Please suggest reason for disappearance of error under above mentioned setting.
Figure out what your board does wrong. Compare with a working board.
I saw the same error on a Cortex-M0 target last night, after the FW was updated in my Segger J-Link Plus. I will try your fix; if it works there is something recently wrong with their update. (I used it without issue on 9/21/16 last). Thank you.
Please update me about your observations and obtained results. I want to understand root-cause of the problem, so that finding solution to the problem becomes systematic and deterministic.
Sunil, it turns out it was a mistake on my end. I didn't have a proper power supply to the DUT and the current demands on reflash operations was browning out the CPU. I don't know if that will help you or not but at least it is something to check off your investigation list.
Best, Dan