• State Not Answered
  • Replies 26 replies
  • Subscribers 64 subscribers
  • Views 3253 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 271760
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF5_SDK_17.0.2_d674dde\examples\dfu\secure_bootloader\pca10056_s140_ble_debug\ses won't advertise DfuTarg name

gfmoore

So I now have nRF 52840 dk and I'm working through the secure bootloader example. I am using SES. (Windows).

So I built and flashed the the app and it looks fine, it has Leds 1 and 2 lit and the software layout looks fine (in nRF Connect)

In trying to use the Connect J-Link, I see the output (in part)

<debug> nrf_dfu_ble: Enabling the BLE stack.
<debug> nrf_dfu_ble: No advertising name found
<debug> nrf_dfu_ble: Using default advertising name
<debug> nrf_dfu_ble: Advertising...

As far as I know the advertising name is defined in the sdk_config.h?

// <s> NRF_DFU_BLE_ADV_NAME - Default advertising name.
#ifndef NRF_DFU_BLE_ADV_NAME
#define NRF_DFU_BLE_ADV_NAME "DfuTarg"
#endif

I've tried following the code and stepping into, but it's a rabbit warren and I got lost.

Can you help please.

Gordon

Parents
  • 0

    Okay then.

    So what could I be doing wrong, or what should I be doing to see DfuTarg on my phone. It worked fine when I followed through on the ble_blinky example. Saw the advertisment fine.

    I have rebooted my phone, turned off bluetooth, left it a few minutes, turned it on again. (To clear any cache?)

    I don't understand why, if I'm using the pure code I can't see DfuTarg? Is it something to do with the public key?

  • 0 in reply to gfmoore
    gfmoore said:
    I have rebooted my phone, turned off bluetooth, left it a few minutes, turned it on again. (To clear any cache?)

    It is a problem that phones cache device names etc, but I would expect it should have been cleared by turning it off and on again like you did. Do you by any chance have an addition DK or dongle so that you can test with nRF Connect for Desktop and the Bluetooth app? With that there is no caching issue, and you get full control.

    gfmoore said:
    I don't understand why, if I'm using the pure code I can't see DfuTarg? Is it something to do with the public key?

    It is not used at this point in the bootloader so I do not see how an issue with the signature could make it fail. Does it help to revert back to the example signature (it obviously will not work with firmware you sign, but it would be interesting to double check if that is related to the issue you see here or not just to rule it out.)

Reply
  • 0 in reply to gfmoore
    gfmoore said:
    I have rebooted my phone, turned off bluetooth, left it a few minutes, turned it on again. (To clear any cache?)

    It is a problem that phones cache device names etc, but I would expect it should have been cleared by turning it off and on again like you did. Do you by any chance have an addition DK or dongle so that you can test with nRF Connect for Desktop and the Bluetooth app? With that there is no caching issue, and you get full control.

    gfmoore said:
    I don't understand why, if I'm using the pure code I can't see DfuTarg? Is it something to do with the public key?

    It is not used at this point in the bootloader so I do not see how an issue with the signature could make it fail. Does it help to revert back to the example signature (it obviously will not work with firmware you sign, but it would be interesting to double check if that is related to the issue you see here or not just to rule it out.)

Children
Related