FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [April 2006 Threads] AT91SAM7A2 portPosted by Nobody/Anonymous on April 3, 2006 Hello,
I am planning on using this device, because I need external flash/ram for my application. Has anybody considered or started a port to this chip?
Or could anybody advice me on a good starting point and/or toolchain for performing this port?
I am new to the FreeRTOS system and community, but a friend of mine has only good to tell about it.
Thanking you in advance. Henrik
RE: AT91SAM7A2 portPosted by Richard on April 3, 2006 There are very few differences between the AT91SAM7S and AT91SAM7X ports, so although I don't know of anybody using FreeRTOS on the A2 I suspect it will be a simple task to do so.
It might even come down to just changing the header files that are included to get the correct peripheral register locations.
The best way of creating a new port is to start with the SAM7S or SAM7X project and just select a different target in the IDE. I think this can be done from both the IAR and CrossWorks IDE's.
You may also need to add a bit of code to the startup assembler file to initialise the external memory interface as this is not present on either the S or X ports. The thing to watch out for is that the startup code creates the stacks for IRQ and Supervisor modes, and starts the processor in Supervisor mode.
Its best not to use the Atmel startup code as this places software between an interrupt being generated and the application ISR being called. This confuses the kernel code, which expects to be called directly.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|