Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training




Loading

another startup problem on SAM7

Posted by Nobody/Anonymous on November 17, 2005
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

RE: another startup problem on SAM7

Posted by Nobody/Anonymous on November 18, 2005
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?


RE: another startup problem on SAM7

Posted by Nobody/Anonymous on November 18, 2005
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


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.


Free TCP/IP and file system demos for the RTOS


Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists