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] [January 2007 Threads] Performance FreeRTOS with lwIPPosted by Joe on January 14, 2007 Hi @all,
I have adapted the FreeRTOS to an LPC2290 from NXP and 75MHz 8MB-Flash/4MB SRam with the lwIP-Stack. It works fine, but I think it is strange slow. When I call the vTaskList-function it needs about 3 seconds to fill the buffer with the actual task-functions and to print it out via printf.
Is there anybody who has an idea what the kind of problem it could be or does anybody have an idea how to accelerate the system ?
kind regards
Joe
RE: Performance FreeRTOS with lwIPPosted by Joe on January 15, 2007 anybody = anyone :-)
RE: Performance FreeRTOS with lwIPPosted by Richard on January 15, 2007 A couple of tips:
1) The function that prints out the tasks is good as a debugging aid, but it keeps interrupts disabled for the entire time that it is creating the table so is not good to use in anger. It needs to do this to capture the system in a consistent state. Creating the table requires multiple list searches and many printf calls so is somewhat lengthy. I suspect that creating this table is causing MAC interrupts to be missed, resulting in timeouts, etc. on the TCP/IP comms.
2) The lwip options in the FreeRTOS.org download are not optimised for any particular system. There have been some good threads on the lwip mailing list recently on how lwip options (buffer sizes, window sizes, etc.) can be optimised.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|