rtos

Is your enhancement proposal related to a problem? Please describe.
access_addr always seems to be of size 4; that should be #defined.
crc_init always seem to be of size 3; that should be #defined.

https://github.com/zephyrproject-rtos/zephyr/pull/31009/files#r736229677
https://github.com/zephyrproject-rtos/zephyr/pull/31009/files#r736229386

Describe the solution you'd like
A

The yew framework allows developers to create web UI in Rust. It could compile Rust code into WebAssembly bytecode that runs inside the browser to render the DOM objects for the UI.

Alternatively, it could compile Rust to native machine code, and run it on a Rust-based web server (actix-web) to generate the HTML elements for the UI ([SSR](https://yew.rs/docs/next/advanced-topic

In PROTECTED mode, the MPU is used to map regions of memory to supervisor- and/or user-accessible memory. Currently, that algorithm is very simple: The entire address range is made accessible in supervisor mode; a single MPU region is used to enable user-mode access in each user memory region.

Each MPU region must bit both of a power-of-two size and with an alignment in memory equal to the si

With aligned_alloc() in the C11 standard, free() is called to free memory, rather than an equivalent aligned_free().

We should update our library with some logic that can be used to correctly call aligned_free() if free() is used instead.