ChibiOS Free Embedded RTOS

I've found the same condition while working with CDC on F103. Despite the heavy bidirectional traffic, the problem may not manifest itself for several days. With this fix, it keeps working flawlessly for more than a week now.

Sorry for the false alarm. This was a pilot error due to supplying an invalid target for GDB which loaded corrupted image into device. Now everything works just fine.

Both chSemSignal and chSemWait are normal functions and must be NOT called within chSysLock and chSysUnlock.

Correct, but I mean that it is chSemWait acquires and not releases lock before switching to the HIGHPRIO thread. Eg., dbg_lock_cnt is zero before chSemSignal() invocation and is 1 right ...

Hi, I'm trying to workout debug panic in the following scenario:

High priority thread T1 created and then sleeps on chSemWait() function;
then main thread signals to it with chSemSignal();
being the high priority, T1 immediately rescheduled, but inherits chSysLock() from chSemSignal(). As a result ...

meanwhile you may use the lwip_bindings from the repository version.

That's what I'm doing now. And while we're at it, the small patch suggested to make lwip location configurable:


Index: lwip.mk
===================================================================
--- lwip.mk ...

May be I've missed something, but why 2.4.x branch doesn't have lwip_bindings in the os/various? It doesn't exist either in release files, neither in the svn repo.