The app attribute is aware of owned-singleton crate and its Singleton attribute. When this attribute is applied to one of the resources the runtime will perform the unsafe initialization of the singleton for you, ensuring that only a single instance of the singleton is ever created.

Note that when using the Singleton attribute you'll need to have the owned_singleton in your dependencies.

Below is an example that uses the Singleton attribute on a chunk of memory and then uses the singleton instance as a fixed-size memory pool using one of the alloc-singleton abstractions.

fn main() {
//! examples/


extern crate panic_semihosting;

use alloc_singleton::stable::pool::{Box, Pool};
use cortex_m_semihosting::{debug, hprintln};
use lm3s6965::Interrupt;
use rtfm::app;

#[app(device = lm3s6965)]
const APP: () = {
    static mut M: [u32; 2] = [0; 2];

    static mut P: Pool<M> = ();

    #[init(resources = [M])]
    fn init() -> init::LateResources {

        init::LateResources {
            P: Pool::new(resources.M),

        priority = 2,
        resources = [P],
        spawn = [foo, bar],
    fn I2C0() {;;

    #[task(resources = [P])]
    fn foo(x: Box<M>) {
        hprintln!("foo({})", x).unwrap();

        resources.P.lock(|p| p.dealloc(x));


    #[task(priority = 2, resources = [P])]
    fn bar(x: Box<M>) {
        hprintln!("bar({})", x).unwrap();


    extern "C" {
        fn UART0();
        fn UART1();
$ cargo run --example singleton