Hi Experts,
I am trying to connect a third-party JTAG Debugger(Yokogawa Digital Computer adviceLUNA) to Juno-r1 Board.
When using the firmware provided from Recovery-CD, the debugger is connected to Juno.But when using the firmware builded 15.12 LSK with DEBUG options,I can't connect in spite of same procedure and environment.
According to a error message showed by the debugger, the debugger fails to access to the Mem-AP's TAR register.
What should I confirm to connect adviceLUNA to Juno-r1 Board?
Best regards.
Hi,
Thanks for clarifying.
It's interesting that you're not even able to connect to the Juno in UEFI when using the latest deliverables. Out of interest, which target are you trying to connect to? My best guess at this point is that you're trying to connect to one of the Cortex-A53 cores, but it's powered down when using the new deliverables as they make one of the Cortex-A57 cores the primary core.
If this is the case, please can you try connecting to:
ARM Development Boards > Juno ARM Development Platform (r1) > Bare Metal Debug > Debug Cortex-A57_0
And see if that works?
Thank you for your response.
I am trying to connect to one of the Cortex-A57 cores.
I confirmed my procedures and configuration files of my debugger again,I wasn't going to connect to the Cortex-A53.
> If this is the case, please can you try connecting to:> ARM Development Boards > Juno ARM Development Platform (r1) > Bare Metal Debug > Debug Cortex-A57_0
Is this the configuration of DS-5?I'm using a third-party debugger, therefore I'm selecting similar thing.
Ah, my bad, I thought you were using a 3rd party JTAG in conjunction with DS-5. I'm afraid I'm not sure what the problem could be then. It's very strange that you're able to connect using the recovery CD, but not even able to connect during UEFI when using the latest deliverables.
Do you have access to a DS-5 installation and a DSTREAM? It would be interesting to see if the same issues are replicated using these tools instead.
Other than that, I really don't know what the issue is. The fact that it works with the recovery CD suggests it's not a hardware problem, but rather a software problem. But, we're not aware of anyone having these issues, at least when using DS-5 with a DSTREAM.
It might be worth contacting the distributor of your debugger (YDC?) to see if they're aware of any similar issues, or to see if they're able to replicate the issue using a Juno with the latest deliverables.
Also, you could try the inverse of what I suggested last time, and try to connect to Core0 of the A53 cluster?