The DFU operation scenario.

[jsna]

HI.

nRF51 is inexperienced users.

I've downloaded using nRFgo Studio.

Preparation before the test to dfu.

1. nRF51_SDK_10.0.0

   1. Components\softdevice\s110\hex

      • s110_nrf51_8.0.0_softdevice.hex

   2. dfu\bootloader\pca10028\dual_bank_ble_s110\arm4_build

      • nrf51422_xxac.hex

   3. After building the application, it has been downloaded(using nRFgo Studio).

      • ble_app_uart_dfu.hex

   4. I have created a zip file that want to upgrade.

      • Creating an image file

   5. nRF Toolbox

      • When the button is pressed(SELECT DEVICE), The name seemed "DfuTarg". Finally, I downloaded a uart application(ble_app_uart_dfu.hex), I think there seems to be marked with the "Nordic_UART". Why does this name does not look Nordic_UART?

Thank you.

[Michael Dietz]

Short answer: Things get cached a lot with BLE. You will notice this all the time when you develop. Maybe you change the device name, advertising data, service info etc.. and it will still have old value.

Really the only way I've found to workaround this is to disable and re enable BLE (when using phone applications). With master control panel PC application this isn't a problem because you can reset your usb dongle and re discover services as you need to.

Maybe someone has a better answer.. But i see this a lot and haven't found a great way with the smart phone aps.

[Michael Dietz]

This is because of caching occurring on the smartphone application. I'm guessing you are either using android or iOS Master Control Panel. Try closing master control panel, disabling bluetooth, re enabling it and then starting master control panel again and scanning for the uart application. Now you should see the name is Nordic_UART.

If you use PC Master Control Panel you probably won't see this problem.