- Devel - lists.tockos.org

Threat model appendix: use case description
by Johnathan Ryan Van Why Feb. 17, 2026

Feb. 17, 2026

Hi all, I want to call attention to a threat model PR I opened last month: Threat model appendix: use case description <https://github.com/tock/book/pull/81>. It documents a few different use cases for Tock with varying security requirements and describes how Tock can be configured to satisfy each use case. To my knowledge, this is the first concrete description of how application identifiers and short IDs should be generated in practice. If you are interested or involved in Tock's application ID infrastructure (or any subsystem that may need to use application IDs), please take a look. -Johnathan

1 0

Re: Support tockloader for STM32L4
by Branden Ghena Jan. 14, 2026

Jan. 14, 2026

If you want to install applications over UART, you'll need some kind of system for receiving those bytes and writing them to memory. That's usually the tock-bootloader. Rarely, some systems have a hardware bootloader system capable of that. The tock-bootloader repo is not obsolete. It's just been quite stable for a while now, so it hasn't needed updates. Alternatively, many platforms Tock supports have USB->JTAG support. This doesn't require any software like a bootloader, but it does require hardware to support it, usually in the form of an additional chip on a board. That separate chip can be an entirely separate Microcontroller running software like DAPLink, which is how the Microbit v2 works, or some other hardware JTAG converter. JTAG support is preferred over bootloaders when available, since it doesn't require any additional software running on the actual microcontroller. Thanks, Branden Ghena Northwestern University On Tue, Jan 13, 2026 at 6:26 AM Kamil Duljas via Devel < devel(a)lists.tockos.org> wrote: > Thanks a lot! Could you please explain something to me? I think I’m > missing an important piece. > As far as I understand, tockloader allows installing apps and > communicating over UART, etc. > But to install applications, do I also need to implement a bootloader? > Is the tock-bootloader repository obsolete? If so, what is the current > recommended approach? > > best, > Kamil Duljas > > pon., 12 sty 2026, 17:27 użytkownik Tyler Potyondy <potyondyt(a)gmail.com> > napisał: > >> I recently added tockloader support for the WL5xx board family. It is >> still a work in progress and has a few hacky fixes I need to cleanup, but >> here's my branch in case it helps you for adding L4 tockloader support: >> https://github.com/tyler-potyondy/tockloader/commits/ents-board-config/ >> <https://urldefense.com/v3/__https://github.com/tyler-potyondy/tockloader/co…> >> >> -Tyler Potyondy >> >> On Mon, Jan 12, 2026 at 7:31 AM Branden Ghena via Devel < >> devel(a)lists.tockos.org> wrote: >> >>> Sure! Go ahead and make a PR to Tockloader whenever. >>> >>> And thanks for the contributions! We will get to reviewing them as soon >>> as we can. >>> >>> Thanks, >>> Branden Ghena >>> Northwestern University >>> >>> >>> On Mon, Jan 12, 2026 at 1:52 AM Kamil Duljas via Devel < >>> devel(a)lists.tockos.org> wrote: >>> >>>> Hi, >>>> My PR is waiting for review https://github.com/tock/tock/pull/4672 >>>> <https://urldefense.com/v3/__https://github.com/tock/tock/pull/4672__;!!Dq0X…> >>>> >>>> but I'm wondering if I can add support in tockloader parallelly. A code >>>> should be similar to F4 boards but it should be separated because OpenOCD >>>> defines his own cfg file for L4 boards. >>>> >>>> -- >>>> Best, >>>> Kamil Duljas >>>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)lists.tockos.org >>> To unsubscribe send an email to devel-leave(a)lists.tockos.org >>> >>

1 0

Re: Support tockloader for STM32L4
by Branden Ghena Jan. 13, 2026

Jan. 13, 2026

Sure! Go ahead and make a PR to Tockloader whenever. And thanks for the contributions! We will get to reviewing them as soon as we can. Thanks, Branden Ghena Northwestern University On Mon, Jan 12, 2026 at 1:52 AM Kamil Duljas via Devel < devel(a)lists.tockos.org> wrote: > Hi, > My PR is waiting for review https://github.com/tock/tock/pull/4672 > <https://urldefense.com/v3/__https://github.com/tock/tock/pull/4672__;!!Dq0X…> > > but I'm wondering if I can add support in tockloader parallelly. A code > should be similar to F4 boards but it should be separated because OpenOCD > defines his own cfg file for L4 boards. > > -- > Best, > Kamil Duljas >

3 2

The main direction of development STM32
by Kamil Duljas Jan. 12, 2026

Jan. 12, 2026

Hi, As a Rust enthusiast, I wanted to gain more experience by adding support for an STM32L4 board. It’s quite a popular board in Poland, with many tutorials on electronics blogs. At the same time, I’m wondering about the next steps for STM32 support in general. It’s a very popular vendor, and the wide range of boards definitely makes it easier to get started with Tock OS. Do you have any roadmap for STM32 boards or plans for supporting other platforms? Best regards, Kamil Duljas

2 1

Support tockloader for STM32L4
by Kamil Duljas Jan. 11, 2026

Jan. 11, 2026

Hi, My PR is waiting for review https://github.com/tock/tock/pull/4672 but I'm wondering if I can add support in tockloader parallelly. A code should be similar to F4 boards but it should be separated because OpenOCD defines his own cfg file for L4 boards. -- Best, Kamil Duljas

1 0

Re: Porting Tock OS to STM32 (L476 / F756)
by Branden Ghena Nov. 24, 2025

Nov. 24, 2025

HI Kamil, While you're welcome to use DMA, it's not required for an initial port of a board. Often DMA is a later addition once the proof of concept works and a more-performant system is desired. Using interrupts for the UART would be totally fine. Thanks, Branden Ghena Northwestern University On Mon, Nov 10, 2025 at 6:06 AM Kamil Duljas via Devel < devel(a)lists.tockos.org> wrote: > Hi, regarding the port to the STM32L476RG — work in progress :) > I’m wondering about UART transmission. I noticed that some boards (e.g. > Nucleo, Discovery) use interrupts, > while others use DMA as well. Should I use UART with DMA, or is DMA > optional at this stage? > > Kamil > > pon., 3 lis 2025 o 16:10 Leon Schuermann <leon(a)is.currently.online> > napisał(a): > >> I'm excited seeing the progress made on this port! >> >> Kamil Duljas via Devel <devel(a)lists.tockos.org> writes: >> > I noticed that GPIO code for F3 F4 and L4 is 80-90% the same. maybe we >> > could extract it as a common part like stm32x ? I guess it could be >> > done for many pheripherials. >> >> Yes! In general, avoiding such code duplication is desirable, and there >> should be plenty of existing examples in the `chips/` folder, like >> `nrf5x` or `stmf4xx`. >> >> However, Tock has some particular (and somewhat implicit) conventions >> when it comes to code-sharing for multiple targets. For instance, we >> generally discourage conditional compilation by means of Cargo features >> (`#[cfg(...)]`) in our code, as that makes code harder to test. >> >> For a new target, I think it could be good to first get a chip and board >> crate merged (which perhaps duplicates some code that is not completely >> identical and thus trivially sharable between chips), and then split out >> that common infrastructure in a follow-up PR. This way you won't risk >> de-railing the PR to add the board over discussions on how to organize >> that shared infrastructure. >> >> -Leon >> > > > -- > Pozdrawiam, > Kamil Duljas >

2 1

Re: Porting Tock OS to STM32 (L476 / F756)
by Kamil Duljas Nov. 10, 2025

Nov. 10, 2025

Hi, while porting stm32L476 I noticed that GPIO code for F3 F4 and L4 is 80-90% the same. maybe we could extract it as a common part like stm32x ? I guess it could be done for many pheripherials. niedz., 26 paź 2025 o 18:56 Kamil Duljas <dudo1990(a)gmail.com> napisał(a): > Thank's! I guess STM32L4 series are widely available :) It's newer than > F4. It would be a pleasure to maintain the board :). I will be back with > basic support :) > > niedz., 26 paź 2025 o 17:43 Amit Levy <amit(a)amitlevy.com> napisał(a): > >> That's great! >> >> It's unfortunately a bit buried, but there the porting guide suggests >> what a minimal upstream board should support: < >> https://book.tockos.org/development/porting#adding-a-platform-to-tock-repos… >> > >> >> >> 1. The hardware must be widely available. Generally that means the >> hardware platform can be purchased online. >> 2. The port of Tock to the platform must include at least: >> - Console support so that debug!() and printf() work. >> - Timer support. >> - GPIO support with interrupt functionality. >> 3. The contributor must be willing to maintain the platform, at least >> initially, and help test the platform for future releases. >> >> >> In other words, the blink and hello world apps should work. >> >> GPIO, RCC and UART should be sufficient for this. >> >> Having said that, there is no harm to initiating a draft pull request >> _or_ sharing an external repo with the port at whatever stage you have if >> it would be useful to get a gut check that the style and/or implementation >> details are on the right path. >> >> >> On October 26, 2025 8:46:05 AM PDT, Kamil Duljas <dudo1990(a)gmail.com> >> wrote: >> >>> Thank you for all replies. I ran Tock os on L476 :D but only minimal >>> stuff to blinking Led. I'm wondering what should be done before first >>> official pull request? Full gpio, RCC, UART? >>> >>> Greetings >>> Kamil Duljas >>> >>> pon., 20 paź 2025, 19:30 użytkownik Patrick Pannuto <ppannuto(a)ucsd.edu> >>> napisał: >>> >>>> +Tyler Potyondy <tpotyondy(a)ucsd.edu> and a few other folks are most of >>>> the way through a port to the STM32WLE5xx family, which may share some more >>>> with the STM32L than the existing STM32F upstream as well >>>> >>>> On Sat, Oct 18, 2025 at 5:51 AM Amit Levy via Devel < >>>> devel(a)lists.tockos.org> wrote: >>>> >>>>> Hi and welcome! >>>>> >>>>> I don't see any obstacles. The STM32L476 is a Cortex-M4, of which there >>>>> are many examples upstream, and the STM32F756 is a Cortex-M7 for which >>>>> there is support (albeit only one example upstream, so there is of >>>>> course a slightly higher likelihood of kinds to iron out). >>>>> >>>>> Since both are STM chips, I'd expect much of their peripherals to be >>>>> shared with or at least very similar to some of the STM32 chips for >>>>> which there are upstream ports. >>>>> >>>>> Keep posted and please feel free to ask questions or for help or if you >>>>> run into issues! >>>>> >>>>> -Amit >>>>> >>>>> Kamil Duljas via Devel <devel(a)lists.tockos.org> writes: >>>>> >>>>> > Hi, >>>>> > >>>>> > I'd like to port Tock OS to an STM32 microcontroller - either the >>>>> STM32L476 >>>>> > or STM32F756. >>>>> > >>>>> > Are there any known technical obstacles or limitations that would >>>>> make this >>>>> > difficult? >>>>> > >>>>> > Best regards, >>>>> > Pozdrawiam, >>>>> > Kamil Duljas >>>>> > _______________________________________________ >>>>> > Devel mailing list -- devel(a)lists.tockos.org >>>>> > To unsubscribe send an email to devel-leave(a)lists.tockos.org >>>>> _______________________________________________ >>>>> Devel mailing list -- devel(a)lists.tockos.org >>>>> To unsubscribe send an email to devel-leave(a)lists.tockos.org >>>>> >>>> > > -- > Pozdrawiam, > Kamil Duljas > -- Pozdrawiam, Kamil Duljas

2 2

Porting Tock OS to STM32 (L476 / F756)
by Kamil Duljas Oct. 26, 2025

Oct. 26, 2025

Hi, I'd like to port Tock OS to an STM32 microcontroller - either the STM32L476 or STM32F756. Are there any known technical obstacles or limitations that would make this difficult? Best regards, Pozdrawiam, Kamil Duljas

3 4

TockWorld will be at Microsoft after RustConf
by Amit Levy July 14, 2025

July 14, 2025

It's official! TockWorld will be hosted at Microsoft in Redmond, WA, just a stone's throw from RustConf in downtown Seattle on September 5th. The specific schedule is still TBD, but most of the speakers and their talks are listed: https://world.tockos.org/tockworld8/ Registeration will open soon, so sign up to be notified: https://world.tockos.org/tockworld8/register

1 0

Call for interest in MMU and/or paging
by Amit Levy June 20, 2025

June 20, 2025

Please respond if you are currently working on, or otherwise have an interest or stake in support for MMU-based platforms in Tock and paging support in particular. There are a couple parallel efforts underway, all of which would require careful consideration to achieve successfully alongside MPU-based protection. You can respond only to me (amit(a)amitlevy.com) but better to the list. For example, why you're interested (e.g. you have or are planning support for a platform that has an MMU, or there are specific features you'd hope to get from paging) and whether and what efforts you have underway. I will use this to ensure people are kept in the loop and included in discussions. Thanks! Amit

3 2