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] [August 2010 Threads] AT91SAM7SE512 heap in SDRAM and variable alloPosted by gulash on August 18, 2010 Hi, I have a following problem: I'm devoloping device based on Atmel AT91SAM7SE512 CPU. It has SDRAM connected with 16-bit wide data bus. I want to put heap in this SDRAM. I've used heap_2.c but I experienced memory leaks when using vPortFree() - it looked like this function returnred more memory that was previously allocated. Then I started using heap_3.c andehence - malloc. I use Rowley CrossWorks in current version. First I had to manually initialize heap because initializastion in provided startup file happened before SDRAM controller initialization. It seemd to be working but recently I've experienced some weird effects. When I call subroutine from a task it looks like variables in that subroutine ale allocated under one address and used by the fallowing code with different address. The difference is few words but leads to serious memory leaks. In other words variable is allocated under eg. 0x20010000 and later referenced as 0x2000FFFC. Can someone give me any suggestion wehere to look for a soulution ?
RE: AT91SAM7SE512 heap in SDRAM and variable alloPosted by Dave on August 18, 2010 I would look at your hardware configuration. Especially where the memory controller is initialized to get around your first problem. Very doubtful this is a FreeRTOS problem.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|