Re: #if directives and the MYNEWT_VAL(..) macro

We’ve tried to document the overall system configuration fundamentals: https://mynewt.apache.org/latest/os/modules/sysinitconfig/sysinitconfig/ You can always check the configuration settings for a target using: newt

Re: #if directives and the MYNEWT_VAL(..) macro

Hi Sigve, On Tue, Jun 06, 2017 at 01:01:20PM +0200, Sigve Sebastian Farstad wrote: [...] > So, there are perhaps two bugs in here. 1) why is MYNEWT_VAL_I2C_0 0 and > not '0', as it is defined in syscfg.yml? The single quotes are a YAML escaping mechanism similar to shell quoting. So, values of

Re: #if directives and the MYNEWT_VAL(..) macro

This is not a bug although some folks might want these things turned on by default. It might also be a bit confusing and hard to find in code or documentation, but the default for alot of these peripheral config variables are by default 0. You need to turn them on if you want to use a certain

Re: #if directives and the MYNEWT_VAL(..) macro

On Tue, Jun 6, 2017, at 08:01 AM, Sigve Sebastian Farstad wrote: > Hi all, > > *Short version: *I2C didn't work, and I think I've narrowed it down to > a bug with #if directives and the MYNEWT_VAL(..) macro in the core > that potentially affects many boards.> > *Long version:* > I started

#if directives and the MYNEWT_VAL(..) macro

Hi all, *Short version: *I2C didn't work, and I think I've narrowed it down to a bug with #if directives and the MYNEWT_VAL(..) macro in the core that potentially affects many boards. *Long version:* I started looking at mynewt for work, and I'm trying to use I2C with an nRF52 (both nRF52dk and