is the repo alive?

[divi255]

Good day,

I'm looking for a lightweight thread or async solution for our plc rtos project, your seems to work pretty fine.

It misses a couple of things, e.g. support of more CPUs. It would be also nice to let it have own mutex / rwlock with specified cycle delays between locking attempts. And of course, docs + cargo crate.

If you're going to support it, I'll send pull requests. Or it's better to just do a fork?

[n-k]

Hello @divi255! I haven't been keeping up with this much, but I'm not planning to abandon this repo. $WORK has me looking into computer vision type stuff lately so I've been away from embedded code.

About the points you mention, I think mutex/rwlock implementation should be done first so that this becomes easier to use on the architectures which are supported currently, and then support for FP registers and more archs can come. Of course, if you have patches already, then they are welcome in any order :)

I should have done better docs and maybe published it on crates.io before, let me try to do that over the coming weekend.

[divi255]

thanks for the fast reply.

Yes, it would be nice to create cargo crate.

The only thing I would like to ask you is to make functions __CORTEXM_THREADS_cpsid and __CORTEXM_THREADS_cpsie as public (and probably rename them to something like "disable_threads/enable_threads". This will allow threads to enter "exclusive" mode, e.g. to work with resources without any kind of lock protection.

I see similar functions to disable/enable interupts exist in cortex_m::interrupt, but I consist it's better to have own as the functionality may be extended.

About mutexes. I'm testing everything on stm32f103. I found spin::RwLock works fine, even without any code modification, but spin::Mutex freezes the board for some reason (even if no threads are used). So it seems this problem is out of your library context.

[n-k]

This crate is now on crates.io here: https://crates.io/crates/cortexm-threads
Documentation can be seen here: https://docs.rs/cortexm-threads/0.1.0/cortexm_threads/

@divi255 , I'm planning to open smaller issues to address your points. I should be able to get to them next week.