5744P, Nexus related pad muxed to GPIO. when enter debugging mode via JATG , the GPIO seems do not controlled by SW. when dis-connect debugger, the GPIO work well in GPIO mode.
Could you please check, if entering debugging mode through JATG, Nexus even be started, and then Nexus related working on Nexus IO.
And how to disable nexus .
below is JTAG circuit please check it.
Solved! Go to Solution.
use this command to turn off the EVTI signal - it's ON by default:
Then you can use the pin as GPIO also in debug mode.
Do you need to such configuration also for Pemicro? I didn't find it, I would have to ask others. Just let me know...
customer used Lauderbach via JATG, i duplicated the issue w/ PE-Multi-link via JATG on 5744P EVB, from SSCM Status register, here i see NXEN bit is 1, means Nexus enabled.
Please confirmed that. TKS
I did quick test on my board using Lauterbach and PE Multilink Universal FX.
I used signal NEXUS_MSEO0_B (GPIO 89) which is easily accessible on Nexus P1 connector on EVB.
I'm toggling this pin in endless loop in my project.
In Lauterbach, I simply use 'sys.up', no other configuration is done. I can toggle the GPIO when debugger is connected. Then I used command Nexus.ON (it's OFF by default) and I can't toggle the pin now. Then I used Nexus.OFF and I can toggle the pin again.
When I'm using PE Multilink, I can toggle the pin too. There's no trace option, so there's no configuration I could test.
Notice that NXEN bit in SSCM is something different. It only says, if debug mode is entered or not. If a debugger is connected, it's '1'. If not, it's '0'.
From my point of view, this is expected behavior. Which pins do you use exactly?
the device always starts up in JTAG mode and the Nexus must be explicitly enabled via JTAG if needed. So, the question is what kind of debugging tools you use.
JTAG signals seems to be correct in the picture.