04:12 <re_irc> <James Munns> Small announcement, I just released v0.1.0 of "MnemOS", my tiny general purpose operating system. It currently (only) supports the nRF52840 (specifically the adafruit nRF52840 feather express), though I plan to support other MCUs, and potentially some day MCUs as well.

04:12 <re_irc> It operates in a similar space as Neotron - for folks attempting to build their own hobby PC.

04:12 <re_irc> The docs are here: https://mnemos.jamesmunns.com/, including a full "getting started" guide for both users and developers, and the source code is all here: https://github.com/jamesmunns/pellegrino.

04:12 <re_irc> It doesn't do a _lot_ yet, but it has the ability to load and launch user programs from a QSPI Flash acting as a Block Storage Device, as well as multiplexed Virtual Serial Ports over the USB-UART connection (think TCP/UDP ports, but over a serial port).

04:12 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/bfe07d1188727046b728d188db4aa018d6549c92550664c5720b85baed02ac7a (6 lines)

04:12 <re_irc> <James Munns> I chat about it more actively on #anachro:matrix.org (https://matrix.to/#/#anachro:matrix.org), so feel free to head over there if you'd like to chat about it :)

04:16 <re_irc> <James Munns> It would likely be relatively easy to port to any nRF52840-based development (if the board has some kind of external SPI/QSPI flash), and challenging but possible to port it to another MCU with a reasonably deluxe amount of RAM/Flash. The 840 has 256K of RAM and 1MiB of flash, but it could fit in a lot less flash, and a bit less RAM.

04:16 <re_irc> <James Munns> Small announcement, I just released v0.1.0 of "MnemOS", my tiny general purpose operating system. It currently (only) supports the nRF52840 (specifically the adafruit nRF52840 feather express), though I plan to support other MCUs, and potentially some day MPUs (like Cortex-A devices) as well.

04:16 <re_irc> It operates in a similar space as Neotron - for folks attempting to build their own hobby PC.

04:16 <re_irc> The docs are here: https://mnemos.jamesmunns.com/, including a full "getting started" guide for both users and developers, and the source code is all here: https://github.com/jamesmunns/pellegrino.

04:16 <re_irc> It doesn't do a _lot_ yet, but it has the ability to load and launch user programs from a QSPI Flash acting as a Block Storage Device, as well as multiplexed Virtual Serial Ports over the USB-UART connection (think TCP/UDP ports, but over a serial port).

04:16 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/704d2ebfd1e18f19c810393907b41e2769e052aa4a5fe122b9f940f635deb9e7 (6 lines)

04:17 <re_irc> <James Munns> I'm gunna go to bed now, but feel free to AMA or open any issues, happy to chat about it. It would be great to get a couple more folks involved.

04:22 <re_irc> <James Munns> (in particular, I'd love to mentor someone to port it to the nRF52840-DK, as I know a lot more folks have that hardware sitting around these days! It's mostly down to tweaking the QSPI driver, and changing some pin mapping - feel free to open an issue if you're interested, or me in the anachro room and I'll check back in a couple of hours :) )

04:26 <re_irc> <James Munns> It would likely be relatively easy to port to any nRF52840-based development board (if the board has some kind of external SPI/QSPI flash), and challenging but possible to port it to another MCU with a reasonably deluxe amount of RAM/Flash. The 840 has 256K of RAM and 1MiB of flash, but it could fit in a lot less flash, and a bit less RAM.

12:19 <Lumpio-> Just out of interest does it require XIP or some other means to run stuff directly from external flash or does it load stuff to RAM first?

12:22 <re_irc> <James Munns> Loads into RAM

12:22 <Lumpio-> ah, neat

12:23 <re_irc> <James Munns> I'm unsure if this is a permanent design decision, but that's what it does now :)

12:24 <Lumpio-> Can add support for both later :D

12:53 <re_irc> <James Munns> Right now, each App has a max of 128KiB of space, which needs to cover the code and RAM usage. The linker script defines the max stack size (defaults to 16KiB).

12:54 <re_irc> <James Munns> (this is because I split the 840's RAM in half, half for the OS, half for the app. Honestly the OS doesn't currently need that much, but it might later once it does more)

12:55 <re_irc> <James Munns> Though stack overflows would be hard to catch now, since your stack grows towards your executable code 😅

12:58 <re_irc> <James Munns> Ill probably use the Flip-Link trick (easier for me, because stack size is declared), and set up the MPU at some point. The user app is already running in unpriv mode with it's how stack pointer.

13:08 <re_irc> <James Munns> * its own

14:02 <re_irc> <yruama_lairba> hi, i'm looking how some stm32 peripheral HAL crates are done. some use a "pac" module internally. From where comes the used SVD files ? Is there some include directive in SVD files so a SVD description is effectively shared accross a MCU family ?

14:02 <re_irc> <yruama_lairba> https://docs.rs/crate/stm32-usbd/0.6.0/source/

14:03 <re_irc> <yruama_lairba> https://docs.rs/stm32_i2s_v12x/0.2.0/stm32_i2s_v12x/

14:16 <re_irc> <dirbaio> yruama_lairba: typically these just grab a PAC for one particular chip and copy the relevant .rs files out

14:16 <re_irc> <dirbaio> and rely on the fact the registers are the same between many chips

14:17 <re_irc> <dirbaio> and no, there's no sharing or "includes" in svd

14:18 <re_irc> <yruama_lairba> ok, so everything need to be done manually :/

14:20 <re_irc> <dirbaio> with the stm32-rs pacs, yes

14:24 <re_irc> <dirbaio> that's one of the reasons stm32-metapac exists. it does share (https://github.com/embassy-rs/stm32-data/tree/main/data/registers) registers across different families, and it can tell you which version it has so you can do stuff like "#[cfg(spi_v2)]" to write drivers that work in all stm32 chips (https://github.com/embassy-rs/embassy/blob/master/embassy-stm32/src/spi/mod.rs)

14:29 <re_irc> <yruama_lairba> the published crate is empty https://crates.io/crates/stm32-metapac

14:31 <re_irc> <yruama_lairba> i'm not even sur this package exist for general usage purpose since the repo is focused on async/await

14:31 <re_irc> <yruama_lairba> * sure

14:32 <re_irc> <dirbaio> you have to use it from the git repo for now

14:32 <re_irc> <dirbaio> "stm32-metapac" is just a PAC, there's nothing specific about async/await

14:32 <re_irc> <dirbaio> +to it

14:36 <re_irc> <yruama_lairba> i can't use it if i want my work to be published on crates.io

14:40 <re_irc> <yruama_lairba> anyway, i'm talking about rework a particular crate since 2 week, and I still haven't done anything yet

19:07 <re_irc> <riskable> Anyone with an RP2040 board want to try my TicKV implementation for that platform? It's a wear-leveling, ACID transaction, persistent key/value store that will survive reboots/power cycling... https://github.com/riskable/rp2040-tickv (need feedback).

21:56 <re_irc> <James Munns> Oh wow, that's perfectly timed!

21:58 <re_irc> <James Munns> I didn't realize tock os had a tickv port

22:01 <re_irc> <James Munns> Ohhh it's different from the redox os fs

22:02 <re_irc> <James Munns> I think their fs is called TFS, but I could have sworn it unsed to be called tickifs

22:37 <re_irc> <9names (@9names:matrix.org)> naming it "ticki FS" has that classic "can't think of a good name, i'll just name it after myself since it will _definitely_ be replaced/renamed later" vibe

23:33 <re_irc> <firefrommoonlight> In the spirit of practical examples, I just posted one demonstrating SPI, DMA, and filtering using CMSIS-DSP - https://github.com/David-OConnor/stm32-hal/blob/main/examples/spi_imu_filtered.rs

23:34 <re_irc> <firefrommoonlight> It's condensed to a single ~500 line file, with the intent of showing how to structure a program with RTIC, digital filters, reading multiple registers with DMA etc

23:43 <re_irc> <9names (@9names:matrix.org)> this is really good. i love how you've broken it up into mod blocks, so it's easy to see where there would be separate files. also the comments on how to regenerate the lookup tables are :chefskiss:

23:43 <re_irc> <firefrommoonlight> has some simple-looking code that helps with some subtle things, like how to pad the read/write buffers, how to make the filters compatible with RTIC resources etc

23:43 <re_irc> <firefrommoonlight> Thx!

23:44 <re_irc> <firefrommoonlight> IIR coeffs are weird due to the diff formats! CMSIS-DSP uses a particular one that's diff from the python native output, hence the manipulation