-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Zephyr to v4.0.0 and use main mender-mcu #37
Conversation
Removes the incompatible pointer types warning Signed-off-by: Daniel Skinstad Drabitzius <[email protected]>
We need to rebuild the workspace image if we e.g. change the revision of any of the projects Signed-off-by: Daniel Skinstad Drabitzius <[email protected]>
930af59
to
0a64f46
Compare
* Update the Zephyr revision from `v3.7.0` to `4.0.0` * Change the `mender-mcu` revision from `v0.3-inventory` to `main` * Change `CONFIG_MBEDTLS_ZEPHYR_ENTROPY` to `CONFIG_MBEDTLS_ENTROPY_POLL_ZEPHYR` and enable `CONFIG_MBEDTLS_ENTROPY_C`. * Set `CONFIG_ZVFS_OPEN_MAX` from 4 to 5 to fix `ENFILE` (23) errors when creating sockets * Increase `CONFIG_NET_SOCKETS_CONNECT_TIMEOUT` to stop zsock_connect() from timing out too early, see: zephyrproject-rtos/zephyr@fc007ee * Disabled `ESP_SPIRAM` in esp32_ethernet_kit config due to linking errors * Update zephyr sdk from 0.16.9 to 0.17.0 Ticket: MEN-7927 Signed-off-by: Daniel Skinstad Drabitzius <[email protected]>
0a64f46
to
e3211ba
Compare
Tested on esp32-s3 and nRF52840 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me otherwise. Much better/shorter than what I would expect. 👍 ❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good! Thank you.
Feel free to totally ignore my comment below...
@@ -9,11 +9,11 @@ manifest: | |||
projects: | |||
- name: zephyr | |||
remote: zephyrproject-rtos | |||
revision: v3.7.0 | |||
revision: v4.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once you are in this area, and you have your setup fresh... could you experiment a bit with name-allowlist
in the import to only get the things that we need? 🙈
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah - yes. I tried that briefly when I started this, but abandoned it for some reason. But I can do it in a new PR - shouldn't be too hard.
The updated config options are really just based on trial and error on arm. The net socket timeout can probably be set a bit higher, same with the max open file descriptors; what do you think a reasonable value is?