Search Results

Search results 1-3 of 3.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Thank you I will reach out if needed. This thread can be marked as resolved.

  • Hi Alex. Thanks for the response I have removed the setup target function. Here is a logfile that was produced when running it again. One thing that might be useful to note. The output above where it can identify the El1-3 and debug architecture only appears when the core is halted before hand and our board is not running properly. When we have restarted the machine and everything is running well we get this output where we are having issues with the CPU-TAP. One thing this might be from is that…

  • Hello! I am currently configuring support for debugging an Cortex-A53 core through Ozone. Here is some quick info about my enviornment. I am using the JLink Plus Compact. Firmware is V10. Hardware is V10.10 Ozone 3.26h The issue I am running into currently is that Ozone doesn't halt the CPU so the debugger can attach. When I attempt to run my configuration. A Popup window pops up that says this. --------------------------- J-Link V7.66f Error --------------------------- CPU_HW_Halt(): Function p…