ChibiOS Free Embedded RTOS

It would probably be simpler to keep the transmit and receive on the same thread, since you can only do one at a time. (In all RS-485 systems I've come across, the default mode is receive, at least as far as the hardware is concerned, with transmit being selected only if you've got something to send...

Are you using 2-wire RS-485? If so, you will also receive the data you sent unless specifically blocked in hardware (preferred) or software

I added that assertion after your reports steved, now I have to understand under which conditions that erroneous time window can occur. Giovanni Nearly eight hours of operation without a crash once I removed that assertion in line 480. I'll leave it on overnight. Would it be more helpful to restore...

ulikoehler has given you a good summary of the merits of the various types of storage. It does depend very much on the amount of storage you need, and how often it might change. If change is relatively infrequent, you can have a background task writing to EEPROM, in which case the delays are less of...

Just to add that I'm currently seeing a similar problem, as mentioned in another thread. I'm trying to debug it, and have reduced the code to a single serial port active, with DELTA=5. I'm also consistently seeing that assert in line 480 triggered when the system halts. I'll comment it out now and s...

Main issue with EEPROM is that you have to wait after each write - typically a few msec. You can usually write up to one complete page of data (16-32 bytes, IIRC) in one write period, and that data has to be aligned on a page boundary. If hardware cost isn't a big problem have a look at FRAM - you c...

Going backwards from my perspective, I'm afraid. The code I started running on 14th March is still running - 10 days continuous operation (unless we had a power cut, which I would probably have noticed). This is using a delta of 2. It had some improvements over the code which originally triggered my...

I ported genosensor's routines to V3.0; they're linked to earlier in this thread. And they're working well on a 32F407.

What I haven't ported are his test programs.

Giovanni wrote:This increases my idea that a Cortex-specific debug plugin would make a lot of sense, all of this is not strictly related to ChibiOS but to the CPU architecture.
Giovanni

+1
Much easier than trying to follow a trail through several processor-specific files etc

Are assertions/checks/statechecker enabled on the board failing after few minutes? Giovanni Yes indeed; never got near enough finished on code to even consider disabling them. #define CH_DBG_STATISTICS FALSE #define CH_DBG_SYSTEM_STATE_CHECK TRUE #define CH_DBG_ENABLE_CHECKS TRUE #define CH_DBG_ENA...