Re: How to sync a dos file system externally

2018-10-02 Thread Ian Caddy
On 3/10/2018 7:32 AM, Chris Johns wrote: On 03/10/2018 04:56, Cliff Geschke wrote: I have implemented a dos file system (msdos_*) on a flash device. Is the flash device a chip you have direct access too? The reason I ask is if possible using JFFS2 (a journaling file system) or even YAFFS

Re: How to sync a dos file system externally

2018-10-02 Thread Chris Johns
On 03/10/2018 04:56, Cliff Geschke wrote: > I have implemented a dos file system (msdos_*) on a flash device. Is the flash device a chip you have direct access too? The reason I ask is if possible using JFFS2 (a journaling file system) or even YAFFS (commercial license maybe needed) is a better

How to sync a dos file system externally

2018-10-02 Thread Cliff Geschke
I have implemented a dos file system (msdos_*) on a flash device. Because it is possible for the user to power down the system unexpectedly, I want to sync the file system to the flash device after a 3 second idle time. How do I externally force a sync on msdos from another thread? A

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-02 Thread Catalin Demergian
Hi, I continued debugging. It turned out _Thread_Unblock is not called because in _Event_Surrender (called directly by rtems_event_send) boolean var unblock is false. to be more exact, in if ( _Event_Is_blocking_on_event( the_thread, wait_class ) && _Event_Is_satisfied( the_thread,

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-02 Thread Sebastian Huber
On 02/10/2018 08:48, Catalin Demergian wrote: Hi, This assert may not be directly related to my issue because I reproduced it a few times (with RTEMS_DEBUG enabled in the build) without seeing the assert being hit. What I discovered is that after a while _Scheduler_priotity_Unblock is not

Re: rtems_message_queue_receive / rtems_event_receive issues

2018-10-02 Thread Catalin Demergian
Hi, This assert may not be directly related to my issue because I reproduced it a few times (with RTEMS_DEBUG enabled in the build) without seeing the assert being hit. What I discovered is that after a while _Scheduler_priotity_Unblock is not called for my task anymore. And since