10 years ago.

How to flash nrf51822 with mbed hex on mac

I'm trying to flash my kit with the blinky sample code hex received from the mbed compiler. I'm using a mac 10.9.2. I tried dragging the hex file to the mbed drive and it created a fail.txt file with "SWD Error" written inside. How do I get the hex on the board?

Question relating to:

The nRF51822-mKIT is a low cost ARM mbed enabled development board for Bluetooth® Smart designs with the nRF51822 SoC. The kit gives access to all GPIO pins via pin headers …

I am seeing somehow related problem, so I thought I will add to this thread.

I am using nrf51822-mbed + Safari on Mac 10.9.3. When I drag the hex file (size = 218KB) to the mbed drive, the following message is displayed:

The item “mbed_blinky_NRF51822_.hex” can’t be copied because there isn’t enough free space.

At the same time, the mbed drive is ejected and the mbed LED starts to flash faster (not the user LED which blinky code is designed to flash).

The setting of the Target switch (SW3) doesn't seem to make a difference. Actually, nothing seems to make a difference and now I am wondering if the hardware I received is just not happy.

posted by Dani Dakhil 21 Jun 2014

This issue is resolved. It is an operator error. I am new to this download mechanism and didn't realize that the reset button should not be pushed while plugging in the USB cable (this procedure is for the firmware update).

posted by Dani Dakhil 22 Jun 2014

1 Answer

10 years ago.

That's pretty odd... The same procedure works for me on the same version of OSX!

Accepted Answer

Did u have to install any drivers or other software?

posted by Anthony DiPasquale 16 Apr 2014

No, nothing... It just showed up as a mass storage device and when I dragged the .hex file to it it programmed the board and then reset.

posted by Janek Mann 16 Apr 2014

Ah, the Target power switch was "off". Turn that on and then it programmed fine. Hit the reset button and the LED started blinking. Thanks!

posted by Anthony DiPasquale 16 Apr 2014

I had the same issue on my Mac (10.8) and the only thing that helped me was to restart the Mac.

posted by Wayne Keenan 22 May 2014