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] [March 2005 Threads] Debug LPC22xx FreeRTOS with ULINK Posted by Nobody/Anonymous on March 22, 2005 Hello,
I have problems to get the FreeRTOS to run on a LPC2229 with external RAM for debug purpose with the ULINK debugger. Code download is OK, but debug cause problem.
RE: Debug LPC22xx FreeRTOS with ULINK Posted by Nobody/Anonymous on March 23, 2005 Can you provide more information?
Which compiler are you using? What is the problem exactly? What have you changed to get external RAM working?
???
RE: Debug LPC22xx FreeRTOS with ULINK Posted by Nobody/Anonymous on March 23, 2005 oh sorry, yes..
The uVision3 IDE + ULINK and using the Keil ARM tools (DKARM V1.5) I've modified the settings for debuging from external RAM e.g CODE org ..and size, also for RAM. I'm use a initialization file (XRAM.ini) with some settings for the debug session. Also a modified startup.s. this normaly works with other projects. If I start the debug session with FreeRTOS port, the code is downloaded normaly to RAM via the ULINK. program runs until main and wait. stepping through the code (TaskCreate) makes nonsense and caused a total crash.
any idea ?? maybe a right startup.s ??
Thank's
RE: Debug LPC22xx FreeRTOS with ULINK Posted by Nobody/Anonymous on March 24, 2005 Problem solve,
PABCAKE = problem exist between chair and keyboard !
the size of code and data space should never exeed the physical size of the used RAM for debug !
thank's
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|