Hi, I want to implement a parallel debug on two quasi-identical programs on two different atsamda1j16b cores. I am using an atmel-ice programmer.
The reason I want to implement this is to allow for "hardware in the loop" of my system on both devices. I don't want to transmit data back to my system using UART as it would change the application specification.
For further information on my project I am building two hex files from one project with slight differences through #ifdef statements. I am generating two different .elf files and then I use the atprogram utility to program my devices. This works. But this utility doesn't afford the debugging of the device.
Currently I am using the atbackend utility to generate a local gdb server. Then using atmel studio utility arm/arm-gnu-toolchain/bin/arm-none-eabi-gdb.exe to connect to this remote serial host.
I am missing some details in getting this utility to work, but this might not be the best solution for what I want.
What I want is trace functionality and real-time data acquisition of my variables through the ICE debugger.
Could you direct me further?
Any documentation I am missing?
Suggestions to other technologies such as OpenOCD or an easier to use interface will be accepted. However I wish to not use two different atmel studio processes running in parallel. Perhaps some guide to hardware in the loop or some python library I am unaware of?
Thanks in advance,
Tim
