Simon Goldschmidt wrote
> That can't work: input processing is not called from your while(1) loop
> and tcp_write/tcp_output thus still racing with input processing (e.g.
> TCP ACKs).
I'm not sure I understand this. Isn't input processing ballback-based?
Simon Goldschmidt wrote
>> just to ke
I see. The problem is that for time reasons the port that I've set up is done
very poorly. It uses the raw api. It is nothing but a single thread that
initializes the stack and then lowers its priority to minimum and loops
endlessly just to keep the pcb variable valid. I know this is very bad but I
Hello,
I have a problem with tcp communication. I'm resending data from an
automotive network over tcp and I'm using tcp_write followed by tcp_output
to send the data immediately. I'm also using freeRTOS. I have a global TX
buffer. The access to this buffer is protected by a mutex so that differen
