upstream changes

Hello Mike, 

The nRF Connect SDK tag v1.4.1 is two years old, is there a reason for why you are using this? Current official tag is v1.9.1, with v2.0.0 right around the corner, we would recommend updating to a newer version of NCS as this might fix your issue.

One solution would be to cherry pick the PR you are referring to, however, this might introduce more issues given that you using an older version.

Kind regards,
Øyvind

I would very much like to update to newer SDK, but I am branching off an existing project based on 1.4.1. I did try to update but ran into issues where it didn't build/work and I was spending too much time trying to find the magic combination of settings in the prj.conf and device tree overlay that I gave up and added a workaround in my code. The fixes in zephyr are in the 3.1 release so I won't get them yet regardless.

The cherry pick may be a good solution for the next time.

Thanks,

Mike

Sorry for the inconvenience. Is there any way to test the scenario with the latest releases to confirm whether or not it has been fixed. 

Kind regards,
Øyvind

There are a number of Kconfig settings that changed, making it an effort to build on newer NCS. I reviewed the relevant zephyr source code and verified it is not present in v2.7.

The answer to my real question appears that there is no good way to handle this scenario and if I need the changes, either cherry pick the commits or wait. In my case, I was able to add a workaround in my code.

There are a number of Kconfig settings that changed, making it an effort to build on newer NCS. I reviewed the relevant zephyr source code and verified it is not present in v2.7.

The answer to my real question appears that there is no good way to handle this scenario and if I need the changes, either cherry pick the commits or wait. In my case, I was able to add a workaround in my code.