Hi,

I have another startup-related problem with an at91SAM7 family CPU; hopefully you guys can help.

The demo worked fine right away on my dev board (the standard atmel S64 board), but it crashes about 2/3 of the time on my S256 board (custom made, but similar to the dev board). I'm pretty sure the hardware is ok, since I've been running other code on it for months with no trouble.

When entering xTaskCreate for the first time, one of three things will happen:

1. jump to AT91F_Default_IRQ_handler (an infinite loop)
2. jump to dabtvec (Data Abort, another infinite loop)
3. Successful completion (runs fine)

I haven't found any way to predict which one I'll get, although I only get successful completion with the JTAG connected. Without it, the board just continually resets.

Any suggestions?

Thanks,

Brian

Sorry to ask obvious question but sometimes the obvious is too obvious.

>Without it, the board just continually resets

Is the watchdog being enabled? It might be that with the jtag the macro file disables the watchdog, but without the jtag the watchdog keeps running.

>The demo worked fine right away on my dev board
> (the standard atmel S64 board),

Proving the standard code, your jtag link and compiler installation are all sound.

>but it crashes about 2/3 of the time on my S256
>board (custom made, but similar to the dev board

I presume the 256 is backward compatible with the 64? I know the 256 has more memory, but is the start of the memory in the same location as per the 64? Did you make any changes to the code to run on the 256?

Thanks for answering...I believe I found the answer. I did change a couple of files to work with the S256 board, and I think I inadvertently allowed an interrupt to fire before the scheduler was initialized. I'm still not exactly sure why it was crashing in the way it did, but I have a good lead on it now.

Thanks,

Brian