Is this possible?
Yesterday I observed that, I can , using Segger GDBServer , connect & start debugging on one core , while, it seems ( as I'm not convinced ..) , I could also _same_ time, fire up JLinkExe and connect using same JLink to the other core, and do things like Halt & Go that other core, while still being able to debug through the GDBServer connected to the main core .(=one I'm busy with).
This seems what I would expect & is awesome, but . .
When I tried do this with Ozone (because it interacts faster with target .. .. ), I cannot do the same : I cannot , after starting Ozone's session, fire up JLink commander to the other core. And vice versa (if JLinkExe connected, cannot connect with Ozone).
So where is the wrong behavior ? Ozone locking access to JLink or I did something causing spurious behavior with GDBServer/JlinkExe in the first case ?
Yesterday I observed that, I can , using Segger GDBServer , connect & start debugging on one core , while, it seems ( as I'm not convinced ..) , I could also _same_ time, fire up JLinkExe and connect using same JLink to the other core, and do things like Halt & Go that other core, while still being able to debug through the GDBServer connected to the main core .(=one I'm busy with).
This seems what I would expect & is awesome, but . .
When I tried do this with Ozone (because it interacts faster with target .. .. ), I cannot do the same : I cannot , after starting Ozone's session, fire up JLink commander to the other core. And vice versa (if JLinkExe connected, cannot connect with Ozone).
So where is the wrong behavior ? Ozone locking access to JLink or I did something causing spurious behavior with GDBServer/JlinkExe in the first case ?