Hi Rob - Went through this a few years back with FreeRTOS. The link below may be helpful. Hope that helps! Best Regards, Dave

Will see if other downstream users request such support. How long would want for the various phases? - k

As with and open source project, patches/PRs are welcome to improve and support this :) - k

Thanks for the swift response. That's a shame. I will go look at the PR at your link as shifting to the re-entrant versions just for Zephyr is going to be painful. Rob

Re-entrant support between newlib and zephyr is not currently supported. There’s an old PR on the subject https://github.com/zephyrproject-rtos/zephyr/pull/21518 - k

Should I expect C library functions (e.g. strtok()) under Zephyr to be re-entrant or must I call the re-entrant versions (i.e. in this case strtok_r())? I ask because I am building/running nRF52840

The typical way I've seen this done is: Phase 1: Create the main branch at the same commit hash as master. Repo maintainers make sure that the main branch is synced to master. Phase 2: Set the default

Jack, We are utilizing what GitHub provides and as far as I can tell once we make the change to the default branch from ‘master’ to ‘main’ the ‘master’ branch will no longer exist in the

Hi, Will there be a period of time that we have two main branches ("master" and "main") that are auto-synced to give time for people to adjust their tools? Thanks, Jack

All, We’ve identified some changes we need to make to west to make the transition of branch name cleaner. We will delay the branch name change until these changes are made to west and a version of

We will be changing the default branch on github from ‘master' to ‘main' on Friday (Mar 11, 2021). There is no action required for any open PRs, however you’ll need to update your local git

Hi there, This means that you don’t have a full zephyr environment. Please follow the Getting Started Guide from scratch and you should be able to get this working:

I created this project on windows and built it successfully. Migrated to Linux as this is our normal build environment. Checked the file out of git and upon attempting to build I get the following

Thank you very much. I understand more now and was able to find my mistake. I’ve focused too much on trying to get DT_N_S_vbatt_S_vbatt0 to be defined while the mistake was somewhere else - in my

So you are seeing correct behavior. The are several ways to get a NODE reference (DT_PATH and DT_NODELABEL) are 2 of them. They should expand to DT_N_S_vbatt_S_vbatt0. (This is meant to be

Hello, Thank you for your response. My code is very similar to https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/boards/nrf/battery/src/battery.c with the change that I’ve refactored

Oh, noticed your DT_PATH(batt, vbatt_lipo) is not correct. Try: #define VBATT_LIPO DT_PATH(batt, vbatt0) or #define VBATT_LIPO DT_NODELABEL(vbatt_lipo) - k

That looks normal. What does the code you are building look like? I think the .dts you have looks reasonable, my guess is the issue is more on the code usage side. Your define of VBATT_LIPO will

Hello, I'm writing an application for nrf52832 based board ADC + voltage divider functionalty as in the great nRF battery example

Hello, I’m a student in electronics and I’m trying to use Zephyr on the VEGABoard, but I’m facing some issues. I’ve been able to run some demos provided by openisa in the sdk, and modify some,