The official Mbed 2 C/C++ SDK provides the software platform and libraries to build your applications.

Dependents:   hello SerialTestv11 SerialTestv12 Sierpinski ... more

Issue: Update from rev. 97 to rev 98 breaks code for RedBearLab BLE Nano and nRF51822-mKIT

Hi, when I copy the mbed_blinky example (mbed lib rev. 98) as .hex file to the MBED filesystem, the disk immediately disconnects and reconnects. Afterwards a file "fail.txt" tells me on the BLE Nano "SWD ERROR". On the nRF51822-mKIT the same problem occurs with the message "OUT OF MEMORY". If I switch back to rev. 97 everything works.

Even when I try to copy a larger project (50 kB hex file,) which usually (with older library version) takes some seconds to transfer, the MBED disk disconnects directly.

Solution is so far not to upgrade and use rev. 97.

Regards

Daniel

Example program

7 comments:

01 May 2015

Hello,

it was working for me, and I retest again, mkit with firmware 218 . Blinky does blink, no failure. both revisions 97 and 98

I was having some problems this week with my board, it was failing to flash. Therefore I updated firmware to 218 . What firmware do your boards have? Can you try to update to the latest if it fixes the problem?

01 May 2015

Hi Martin,

also FW 218 from Feb 19 2015 on my mkit. I tried so far to update the firmware on the mkit again, just to be sure, still the same issue.

I also tried the mbed-src instead of the precompiled library. If rev. 530 to rev. 517 were used, the compiled hex file (blinky led example) always has 4 kB and results in an error after flashing. With rev. 516 and earlier (also with mbed-lib rev. 97) the hex file is larger than 200 kB and no error occurs.

The BLE Nano has version 0203, build Sep 12 2014. The newest as avaliable from the platform website.

01 May 2015

I suspect the problem might be in the online IDE and its modes. ARe you using beta or not?

I tried beta and normal mode, binaries for blinky have over 200k, in both cases and are valid..

01 May 2015

with revision 516 of the mbed-src, we pulled in the change for v8 of the Nordic SDK (together with an updated v8.0 of the S110 softdevice).

targets.py was updated to look for v8.0 of the softdevice, and the linker scripts were updated to link applications to begin at the offset meant for v8.

If your applications .hex files aren't sized around 200k, most likely the softdevice isn't getting discovered/merged by the toolchain. Could you please confirm that a file called s110_nrf51822_8.0.0_softdevice.hex is present under mbed-src/libraries/mbed/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/..., and could you please also confirm that no other similar softdevice .hex file is present under that location in your build tree?

01 May 2015

Hi,

I use the normal mode for the IDE.

If I update the mbed-src there is a folder with one "s130" file within: mbed-src/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib/s130_nrf51822_1.0.0/s130_nrf51_1.0.0_softdevice.hex (also in the online repo http://developer.mbed.org/users/mbed_official/code/mbed-src/file/47d2b67c511f/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib )

In the old working revision 516 there was a s110 device (http://developer.mbed.org/users/mbed_official/code/mbed-src/file/b3fb5c6901a6/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/Lib)

03 May 2015

Please don't use the latest from mbed-src for your online builds. Mbed-src is like a development branch. The binary mbed SDK is the official release; and the online toolchain follows this official release. Every time we update the Nordic softdevice on github and mbed-src, the online toolchain goes out of sync until the next release of the binary mbed-SDK. The next binary release is expected to happen next week.

04 May 2015

Hi,

thanks for your advice. Usually I don't use the src. Just because the binary didn't compile, I wanted to see if the problem also affects the src.

After the server problems over the weekend the rev. 98 is now working as it should :)