mcu

Describe the feature request

Since LVGL is more and more used as an desktop app too, I think it's necessary to have a clean application exit event too.
Right now, all example have a while(1) { } in their main function so when you close the app (by clicking the X icon, or Alt+F4 or ...), you're actually leaking all the application objects.

For most of them, it's not important, but som

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 set_mode_X() HIL functions need to support returning an error if hardware does not support that mode or if the implementation cannot put the hardware in to that mode at that time. See for an example where panic is used instead of returning an error https://github.com/tock/tock/pull/2629/files.

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

• #114
• #113
• #121
• #123
• #125
• #126
• #127
• #128
• #129
• #130
• #131
• #132
• #133
• #134
• #135
• #136
• #137
• #138
• #139
• #140
• #141
• #142
• #143
• #144
• #145
• #146
• #147
• #148
• #149
• #150
• #151
• #152
• #153

Library/API/IoT binding

ESP32

Visual Studio version

VS2022 (17.1.1)

.NET nanoFramework extension version

2022.2.0.13

Target name(s)

ESP32_REV0

Firmware version

1.8.0.279

Device capabilities

** .NET nanoFramework extension v2022.2.0.13 loaded **
GitHub repo: https://github.com/nanoframework/Home
Report issues: https://github.com/nanoframework/Home/issues
Browse