Paul Russell / Mbed 2 deprecated FOTA4

This is a modified "BLE_Default_App". It doesn't use retargetStdout() which allows it to work with online Libs available on 20150123 (nRF51822, BLE_API)

Dependencies:   BLE_API mbed nRF51822

You are viewing an older revision! See the latest version

FOTA Notes

Just a gathering of notes from my first FOTA test on an nRF51822-mkit, then an nRF51822-EK, and also nRFBeacon (using JLink Lite, or wire to nRF51822-EK)

FYI: Miscellaneous Notes

  1. When using the BLE UART in a FOTA App it 'may be necessary' to ensure all transmissions from mbed FOTA are terminated with "/n" to push the transmission over BLE. It is possible that unsent BLE UART may confuse the FOTA DFU process. This is unconfirmed, but I did notice FOTA DFU connection issues that may have been caused by this.

A: Prep Platform for FOTA

  1. Download the FOTA initial hex file from "Default Bootloader" section of:
  2. Copy the hex file to the *normal* virtual USB drive of your FOTA platform
    • Connect Platform to computer, a virtual drive should appear with file "mbed.htm" (If anything else you are in the wrong mode)
    • When powering up the platform by connecting USB don't press reset or any other buttons
    • drag the hex file to the virtual USB drive
    • wait till the file is fully processed (drive disconnects, then reappears and file is gone
  3. disconnect the USB to powerdown the platform, then reconnect to powerup with FOTA
    • LED1 blinks with default app installed
    • Debug available on USB Serial "ping..." (TeraTerm 9600,8N1)
    • You may need to Press reset and/or restart TeraTerm depending on what else you do
  4. Use Android App "nRF UART 2.0"
    • Connect to [DefaultApp]
    • Confirm regular "ping" messages
  5. Check FOTA:
    • Start Android App "nRF Master Control Panel" (MCP)
    • Connect to device [DefaultApp]
    • There should be 5 services, including Device Firmware update service
      • If not then disconnect and reconnect to refresh the services list (May be caches from your previous tests)
  6. To restore non-FOTA operation and mbed virtual drive see "Firmware Update" section in

B. Compile sample project for FOTA Platform

  1. Get to your compiler: https://developer.mbed.org/users/yihui/code/BLE_Default_APP/
    • I had no issues with this today for mkit 2015Jan11
  2. Ensure FOTA Platform selected
    • i.e. for the mkit select "Nordic nRF51822 FOTA" (not "Nordic nRF51822 mkit")
  3. Modify the main.cpp so you are sure it is your file that is loaded
    • change line: DEBUG("ping\r\n");
    • to custom message : DEBUG("It Worked!\r\n");
  4. Compile, save hex file
    • FOTA Hex file should be about 55KB (Application only, no bootloader or softdevice)
    • (Normal mkit non-FOTA hex file should be >250KB)

C. Loading sample project using MCP

  1. copy hex file to Android device (Maybe to the folder "Download")
    • Options: Shared folder, copy over USB cable, email to phone, etc.
  2. Start MCP
  3. Connect to [DefaultApp]
  4. Click [DFU] Button, Follow prompts to select Application hex file
    • At this time use "No" for "Init Packet" (Future Feature?)
  5. Allow bootloader to process file
    • New project should run automatically after completed

D. Check loaded sample project

  1. Use Android App "nRF UART 2.0"
    • Connect to [DefaultApp] (Or whatever you modified it to)
    • Confirm that your modified message is received
  2. Use MCP to connect
    • In MCP it may be necessary to disconnect/reconnect to refresh the services for new Project on mkit

. ======================================================================================

E. FOTA on an nRF51822-EK (Not an mbed platform, but can run mbed using FOTA)

  1. Start nRFgo Studio on PC
  2. Select the nRF51822-EK
  3. Do [Erase All]
  4. Select Tab [Program Application]
  5. Select the FOTA Initial hex file for the Platform
  6. Program the application (Option: verify)
  7. Disconnect the USB from the nRF51822-EK
  8. Powerup the nRF51822-EK with Battery or USB
  9. Continue with steps A5 through B,C,D
    • Serial Debug over BLE works using App nRF UART 2.0
    • LEDs and Buttons may need IO redefinitions

. ======================================================================================

F. FOTA on an nRF51822-Beacon PCA20006 (Not an mbed platform, but can run mbed using FOTA)

  1. Check that the Beacon still works, and record the LED Behaviour when insert battery (Needed for check in later step)
  2. Remove battery from nRFBeacon, disconnect USB from JLink Lite or EK
  3. Wire P2 on the nRFBeacon to the SWD on the Jlink-Lite from the nRF51822-DK kit, or the nRF51822-EK (PCA10001)
    • use P2 instead of testpoints as less likely to damage circuit if burn these pads. Its tiny work so get help if uncertain of your soldering skills
    • It may be useful to wire in a connector so can disconnect/reconnect the 4 signals later.
    • Signals Required(4): V+ Target, Gnd, SWDIO(=T_TMS), SWDCLK(=T_CLK)
      • The serial signals aren't required for programming (They are only for USB Serial Debug)
    • For the nRF51822-EK turn off SW4, and wire the signals to the mbed IC side of the isolation buffers (Between U4 and R15/R16).
  4. Check before Powering:
    • Check your wiring for incorrect wiring and shorts.
    • Insert Battery in Beacon, Ensure LED still blinks same as before wiring
    • Test that the beacon still transmits properly to a smartphone (nRF MCP App)
  5. Start nRFgo Studio on PC
  6. Select "nRF51 Programming"
  7. Do [Erase All]
  8. Select Tab [Program Application]
  9. Select the FOTA Initial hex file for the Platform
  10. Program the application (Option: verify)
  11. Disconnect:
    • Unplug USB
    • Remove battery
    • Disconnect the nRFBeacon from the programming wiring (or leave if you expect to re-use)
  12. Insert Battery
  13. Continue with steps A5 through B,C,D
    • Serial Debug over BLE works using App nRF UART 2.0
    • LEDs and Buttons may need IO redefinitions

. ======================================================================================

All wikipages