Hi,
Yes, I use configUSE_PREEMPTION 1
There is no vTaskDelay() in my Idle task, but the __wfi instruction. Schould
wait for the next tick interrupt
Thomas
From: lwip-users-bounces+tjo=agramkow@nongnu.org
[mailto:lwip-users-bounces+tjo=agramkow@nongnu.org] On Behalf Of Nikolas
Karakot
I noticed that someone is using the LPC1788 with LwIP.
Can you point me to the driver for this part? I want to use it in my
next project.
I looked in the contribs and ports and it does not seem to be there.
Thanks for your help.
Chris.
___
lwi
> There is no vTaskDelay() in my Idle task, but the __wfi instruction. Schould
> wait for the next tick interrupt
Good - the idle task must *never* block. Which task would run if the
idle task was blocked?
Later versions of FreeRTOS include a tickless idle mode that stops the
tick interrupt and
>> To protect the TX function I use a critical section so one task can complete
>> the transmit before a new one can do it.
>Does the Tx function use FreeRTOS API calls? If so then you can't use a a
>critical section. Use a mutex instead.
The TX function does not use any API calls.
The crit
>> Is this still the case with lwip 1.4.1? Can't sockets be used
>> without system?
>
>No. It's in the nature of BSD-alike socket APIs that they run "sequential".
>lwIP needs a dedicated thread to handle incoming packets and timers.
I thought this would also be done from the polling thread.
>>
Fabian Cenedese wrote:
> >No. It's in the nature of BSD-alike socket APIs that they run
> "sequential". lwIP needs a dedicated thread to handle incoming packets and
> timers.
>
> I thought this would also be done from the polling thread.
>From which polling thread? I don't think I understand th
