Bootloader advertising changed from DfuTarg to Dfu

RE: Bootloader advertising changed from DfuTarg to Dfu

Hung Bui — Wed, 15 Jun 2016 14:07:13 GMT

Hi makouda,

You need to count the length is also 1 byte, and the type is another one byte.

So what you have is:

3 + 18 + 5 = 26, meaning you have 5 byte left. With that 5 byte, 1 byte is for length, 1 for type and then you have 3 left for the actual device name.

(your manufacturing data = 1 byte length + 1 byte type + 2 byte company ID + 1 byte data = 5 bytes)

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Wed, 15 Jun 2016 12:32:09 GMT

hye Hung I didnt really get it. first : even if there is only 5 bytes left for the device name, then why didn't advertise DfuTa instead of Dfu. second I didn't understated when you say manufacturing data (including 2 bytes company ID , next 5 bytes) I only put one byte for manufacturing data !!! aslo by summing 3 + 18 + 2 + 5 + 5 = 33. do you mean only 3 bytes left for the name?????

RE: Bootloader advertising changed from DfuTarg to Dfu

Hung Bui — Wed, 15 Jun 2016 11:44:35 GMT

Hi Makouda,

Isn't it already 31 bytes in the RAW data you showed in the above image ?

Note that there are flags (first 3 bytes), UUID ( next 18) manufacturing data (including 2 bytes company ID , next 5 bytes) so there is only 5 bytes left for the device name. And the adv module has a "smart" feature to use BLE_ADVDATA_SHORT_NAME instead of the FULLNAME if the space is not enough.

Note that the lengths are also occupy one byte for each of them. If you want to add extra data, you can think of using scan response packet.

Also please declare uint8_t adv_manuf_data_data[1]; as public/static variable otherwise it will be cleared after the function finishes.

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Mon, 13 Jun 2016 15:12:30 GMT

now strangely even on Iphone it advertised Dfu !!!!! this way I should configure on my application to connect to Dfu in order to load the new app, but then I'm afraid that the name would change again randomly and I can no longer update once the product hit the market. any help please, can you please try using android phone to check if it advertise Dfu or DfuTarg. I'm already updated the project above

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Wed, 08 Jun 2016 15:01:52 GMT

no I tested that, I disabled iphone bluetooth and enabled, even turned off the phone, so I guess the cache is deleted

RE: Bootloader advertising changed from DfuTarg to Dfu

MartinBL — Wed, 08 Jun 2016 14:59:55 GMT

I used MCP on my PC. So the same device is showing up as DfuTarg on iPhone and just Dfu on android? Could it be that the phone has cached information about the device?

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Wed, 08 Jun 2016 08:15:29 GMT

I tried using an Iphone and the advertising is DfuTarg, but with all my android phones it advertise only Dfu. which which phone did you try Martin ???

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Mon, 06 Jun 2016 14:38:04 GMT

yes I tried again on many nrf51822 peripherals, I erased everything, flashed SD8 and the bootloader and it advertise only Dfu. when I delete the manufacturer data then it advertize DfuTarg

RE: Bootloader advertising changed from DfuTarg to Dfu

MartinBL — Mon, 06 Jun 2016 14:28:53 GMT

Yes, I use nRF51 rev 3, SDK 10.0.0, and SD 110 V8.0.0. I tried erasing everything and then re-flashed the SD and your code and now I can't get it to work anymore either. Very strange indeed. But it is working for you now?

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Mon, 06 Jun 2016 14:03:35 GMT

that's really strange, I erased all, I flash only the softdevice and the bootloader and I got Dfu on advertising. how can the bootloader behave differently !! did you try using nrf51, sdk10, SD8 :)

RE: Bootloader advertising changed from DfuTarg to Dfu

MartinBL — Mon, 06 Jun 2016 13:54:25 GMT

I have compiled your project with the advertising_init() routine in your original post and it seems to work fine. Initially the application would not run though, as the "Reset and Run" option in the debug settings was not enabled. I don't know if this happens just on my system or if it could be related to your issue though.

RE: Bootloader advertising changed from DfuTarg to Dfu

makouda — Mon, 06 Jun 2016 12:23:50 GMT

Hi Martin, I added the bootloader project. it's based on the bootloader example of SDK10

RE: Bootloader advertising changed from DfuTarg to Dfu

MartinBL — Mon, 06 Jun 2016 11:50:36 GMT

Hi. That sounds strange. From your table it looks like you should be just within the limits of 31 bytes in your advertising packet.

Do you get an error returned from ble_advdata_set()?

Are you basing this on an example? Which one?

Can you upload your main.c file?