Hi,
i am a proud user of the j-link edu. I try to use the debugger with the Atmel SAM3X8E on a Arduino DUE board trough the SWD interface.
I don't use any special init script. I have the strange problem that after flashing and running sometimes (8 of 10 cases) the mcu gets stuck in the reset handler. I use the standard init code of the Atmel ASF.
If i run the board without connected debugger (no running gdb-server or j-link commander, but wired j-link) the processor runs without issue. After some random iteration of disconnecting and reconnecting the debugger, mcu board and restarting gdb-server it starts to working, and as long as i don't disconnect power at the mcu i have no problems. But as soon as i disconnect and reconnect power to the mcu it will get stuck in the reset handler if the debugger is connected.
If the mcu is stuck i can debug it and get a halt in the following loop of the init code.
Display All
the variables are as follow:
this seems all reasonable. But
This can not happen with this code. Interrupts are turned off at this point. And it only happens if the debugger is connected. So my guess is that the debugger somehow messes with the variable?
This is my first project with ARM mcus and external debuggers so any hint what is going on would be nice
i am a proud user of the j-link edu. I try to use the debugger with the Atmel SAM3X8E on a Arduino DUE board trough the SWD interface.
I don't use any special init script. I have the strange problem that after flashing and running sometimes (8 of 10 cases) the mcu gets stuck in the reset handler. I use the standard init code of the Atmel ASF.
If i run the board without connected debugger (no running gdb-server or j-link commander, but wired j-link) the processor runs without issue. After some random iteration of disconnecting and reconnecting the debugger, mcu board and restarting gdb-server it starts to working, and as long as i don't disconnect power at the mcu i have no problems. But as soon as i disconnect and reconnect power to the mcu it will get stuck in the reset handler if the debugger is connected.
If the mcu is stuck i can debug it and get a halt in the following loop of the init code.
Source Code
the variables are as follow:
this seems all reasonable. But
This can not happen with this code. Interrupts are turned off at this point. And it only happens if the debugger is connected. So my guess is that the debugger somehow messes with the variable?
This is my first project with ARM mcus and external debuggers so any hint what is going on would be nice