gt;>
>> 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
>>> t
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
if you ask me.
Will
> On Jun 6, 2017, at 4:59 AM, Fabio Utzig <ut...@linux.com> wrote:
>
> 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
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
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
