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

[gfmoore]

Your not going to believe this, but I just went and got my more up to date Samsung Galaxy Tab S6 and bam, there was DfuTarg as bold as you like.

So it all came down to my older Samsung Note 4 phone (I admit with a ViperOS rom). 

I can't believe it. 

But why would ble_app_blinky work fine and not this? 

[Einar Thorsrud]

Good to hear. That way at least what happens on the nRF side makes sense. I cannot say why the old Note 4 did not handle this correctly, but it is clearly an issue on that and not the nRF.

[gfmoore]

Actually that is not very supportive or helpful. If the ble_app_blinky advertisement can be seen on my phone, which still works fine and doesn't need replacing, then surely so should the ota dfu program. If my business case involves flashing to a device from my phone then it actually needs to work, so IT IS a NRF problem.

I have to say, and I doubt I'll get any further support, but your attitude is dismissive and it seems that really all you want to do is close this ticket and not help at all. Are you sure you are in the right job?

I think it is time to sell this junk on ebay and go elsewhere.

Pretty disgusted with Nordic to be honest. I think you should find a lake and go jump in it.

Regards, Gordon.

[Einar Thorsrud]

Hi Gordon,

I am more than happy to provide support on Nordic products. However, we have now established that the example works and advertises as expected, and that the problem is with your Note 4 running unoriginal software (ViperOS). I am not in a position to debug your ViperOS device.

[gfmoore]

Okay, I apologise for getting frustrated. Please don't throw yourself in any lake, unless that is your thing :sardonic smile

I am not asking you to debug my phone, BUT ble_app_blinky advertises it's name, yes and my phone can see it. No problem.

the OTA DFU advertises it's name, but my phone cannot see DfuTarg. 

I would have thought? that both apps are using similar functions in order to advertise their name?

So what is different in the two apps in the advertising phase that one is okay with my phone and the other isn't. 

I am hoping that with your extensive knowledge and expertise you might be able to explain and then maybe it can be fixed, because I can't afford a new phone and I need this functionality.

Pretty please