NetBurner Community Forum

I set my ShortSocket size back to 100 and rebuilt the system files. I then copied the code above into a program, and reduced the OSTimeDly in my ConnectionsTask loop to (1) to reduce my wait time. I also added the lines for task monitor. The result is this: #include "predef.h" #include <st...

I'm getting lockups after approximately the same amount of time regardless of what the ShortSockets size is set at. I've tried 10 to 1000. When I had the size set at 10, it fills up the ShortSockets and keep going for a while before lockup, leading me to believe that you cannot actually run out of S...

I tried taking SHORT_SOCKET_SIZE to 300 and then 1000, but still saw the lockups. I then wrote a function to check the number of free sockets. This lives in my tcp.cpp: int NumberOfShortSocketsRemaining() { int counter = 0; for (int i = 0; i < SHORT_SOCKET_SIZE; i++) { if (ShortSockets[i].m_flags ==...

Ok, that would make sense. So the system can have 32 open sockets, plus (by default) 100 closed sockets that are finishing up and closing down, thus a total of 132. Is there a function to get the number of free closed sockets? Is there a way to decrease the timeout from 120 seconds to 30 seconds? Re...

I've been working on an app for a NANO54415 and started experiencing lockups. I'm using NNDK v2.6.4. All tasks will stop reporting data to the debug serial port, I lose the ability to ping it, and cannot search for it on the network any more. The link light remains lit, but I need to press the reset...

Very nice.

Are the internals of IPv6 more complicated than IPv4, or is it not as thoroughly documented because it still has that new protocol smell?

Update: This project has taken a bizarre turn, the bug has apparently vanished. Last time I saw a lockup was 3 days ago. I even rolled back to the old code, and I cannot get it throw any traps or lockup now. I'm happy that it's working normally, but I'm also perplexed about what happened.

@ dpursell: I have tested this with OSCrit as well. Same issue. The Semaphore code looks like this: OS_SEM MySemaphore; OSSemInit(&MySemaphore, 1); //This goes around code that accesses the shared variables. OSSemPend(&MySemaphore, 0); //Do stuff with shared vars OSSemPost(&MySemaphore);...

The fact that the system locks up directly after the HTTP task gets preempted seems to indicate that this is what's causing the problem. You may want to look into forcing this situation to occur more often so that you don't have to wait for hours to test any potential fixes Clever idea. I added a f...

All three tasks will sleep until there is something to do. I had Main at a priority of 50 until yesterday, moved to a higher priority to confirm that it wasn't waiting on one of the other tasks. The memory corruption issue stemmed from the QuadSerial task writing data to a string variable that is re...