To be a bit more specific. I now get really unusual errors like like "can't find I2C.h" when using the BOOT-option for compilation.

When I compile my app using the default output it no just crashes on the board (yesterday the same code was fine!)

It's really quite problematic when secret changes seem to happen and just break things without warning...

Hi Chris, Could you please help us reproduce the issue you're having. E.g. can you point me at a program example that doesn't compile anymore?

Hey Mihail. Sorry for the above comments sent a bit "in-anger" at the compiler.

Some specific things causing me problems at the moment: Start with a normal BLE examples, e.g. the heartrate example. Include the I2C.h library and it won't build for the nRF51-DK platform if you choose BOOT output option (this is platform I'm using right now). Using the other nRF51822 targets work OK and the nRF51-DK builds in "default" mode but the code stalled when it ran on my board... I'll double check that last point to make sure I'm not being dumb, but compiling for the BOOT option definitely doesn't work.

Another thing, see my other question on the mbed-dev repo not working anymore with the recent compiler update: https://developer.mbed.org/questions/71473/Cannot-find-deviceh-using-mbed-dev-libra/

You don't know when a newer/updated version of mbed-dev will be released do you?

Some missing detail: Include the I2C.h library in your example program, create an I2C object on some pins I2C i2c(p3,p4); And now it doesn't find the file when compiling for nRF51-DK (BOOT)