[En-Nut-Discussion] ethernut3 debugging with openocd

[Dave Warren]

Hi Joerg,

I have had something simular. I was using Nut 4.2.1 on the AT91SAM7X256. 
When I broke in with JTAG I found the crash was a data abort (bad address 
for data read). I never did understand it but increasing the size of the 
stack in my threads made it go away. I don't understand why. Also I 
discovered that you need a standard out device even if this is only the null 
device.

good luck

Dave Warren


----- Original Message ----- 
From: "imsjoerg" <imsjoerg at googlemail.com>
To: <en-nut-discussion at egnite.de>
Sent: Wednesday, July 18, 2007 1:40 PM
Subject: [En-Nut-Discussion] ethernut3 debugging with openocd


> Hi,
>
> we are using the Ethernut3 board as a base for developing our application.
> Recently I got Eclipse Europa with Yagarto toolchain running for
> compiling and basic debugging.
> I can load my application into RAM with gdb and it halts
> at main(). I can step one line and set a breakpoint in main so it stops 
> there.
> Once the program runs I can halt it, but the program has crashed.
> This is where I need help.
> Something with interrupts, stack, vectors???
>
> The program is a multitasking application based on Nut/OS.
> I use OOCD  R141 on WinXP with ARM-USB-OCD.
>
> Any advice welcome!
>
> Joerg
>
> (I put this question on the openocd forum too)
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>