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

uBlox NINA-B302 doesn't advertise its DEVICE_NAME

p143

Hi All. 

I am familiarised with NINA-B312 module and I am used to seeing its local name being advertised after switch-on, but while testing a  NINA-B302 I've just bought I can't see any DEVICE_NAME being advertised. Is that normal? Is this due to the factory pre-flashed firmware? The supply voltage is 3,6 volt and the consumption (2,x mV) seems fair enough.  


Thanks in advance

Parents
  • 0

    Hi Juan.

    1) I can unfortunately not now it, I would guess perhaps the name of the device is the advertising name. It is up to the manufacturer to choose, and perhaps it is stated in the datasheet.

    2) They could support Nordics DFU service, or their own custom DFU service, it would be up to them to choose. We have no control over their options.

    3) Same as above, this depends on what the 3rd party module have implemented, and it is entirely up to the manufacturer of that module.

    Most of our customers are product manufacturers, and the end user should contact the manufacturers for questions related to their product, not the chip manufacturer, since we do not have control over what our customers do with our chips.

     Best regards,

    Andreas

  • 0 in reply to AndreasF

    Hi Andreas.

    Practising the Secure DFU procedure over a nRF52840 SoC, I've noticed that after you flash the Softdevice and the Secure DFU Bootloader images into the target device, as soon as you flash the app image, if you scan and connect back to the same device, the DFU sign does not show up anymore in the top right of its Service List window, so it looks like you can't make more dfu flashing on it.

    If this is the way it should be, is there a way to keep the DFU functionality forever so you could customize your device through BLE as many times as you decide to along its life cycle? 

    Thanks for your time.

    Best regards,

     

    p143/ Juan

  • 0 in reply to AndreasF

    Hi, Andreas.

    Thanks. I think I finally got the idea.

    One last (hopefully) question:

    According to your comment above (... If you want to "keep the DFU functionality", then you have to include a method in your code where you can enter the bootloader.), to include this method in the new app to be uploaded, would it be enough to copy-paste the code you find here, first in the sdk_config.h file (regarding settings with bonds o without bonds) and then the rest (DFU event handler, Power Manager module, and Buttonless Secure DFU Service Initialization) in the main.c file, and in both cases just at the beginning of the existing app code?

    Best regards

  • 0 in reply to p143

    Hi.

    I'm not sure what you are linking to, that link is broken.

    However, the should not be any issues in including the DFU Service to your applications existing code, you should only have to follow the guide in DocLib.

    Best regards,

    Andreas

  • 0 in reply to AndreasF

    Hi.

    The broken link you mention was pointing to the same document you refer to in your "guide" link. That's why I ask you:

    ... would it be enough to copy-paste the code you find in the "Buttonless Secure DFU Service" document, that is, copy-pasting (at the top of the sdk_config.h file) the code regarding the settings with bonds o without bonds, and then (at the top of the main.c file), the code regarding the DFU event handler, the Power Manager module and Buttonless Secure DFU Service Initialization? 

    I know it may seem a silly question for you, but I would very much appreciate your answer (you could call it help) since I am not yet experienced enough in "C" language.

    Thanks so much.

    Best Regards,

    Juan

  • 0 in reply to p143

    Hi.

    p143 said:
    ... would it be enough to copy-paste the code you find in the "Buttonless Secure DFU Service" document, that is, copy-pasting (at the top of the sdk_config.h file) the code regarding the settings with bonds o without bonds, and then (at the top of the main.c file), the code regarding the DFU event handler, the Power Manager module and Buttonless Secure DFU Service Initialization? 

     Yes, as I said in my previous reply, you should only have to follow the guide on DocLib, which shows you how to add the Buttonless Secure DFU Service to a BLE application (DFU event handler, Power Manager,  Buttonless Secure DFU Service Initialization)

    Best regards,

    Andreas

  • 0 in reply to AndreasF

    Hi.

    Following the guide you were suggesting, I get errors while trying to compile. In order to ascertain were is the problem, I am adding the five scripts being mention in this guide (SDK configuration header files, DFU event handler, enable auto shutdown retry, implement the power management and Initialize de Buttonless Secure DFU Services) one at a time, and running a Build immediately after each script has been pasted.   

    As soon as I reach the "DFU event handler" script, I get the following error:

    Would you mind telling me what is wrong?

    Thanks

Reply
  • 0 in reply to AndreasF

    Hi.

    Following the guide you were suggesting, I get errors while trying to compile. In order to ascertain were is the problem, I am adding the five scripts being mention in this guide (SDK configuration header files, DFU event handler, enable auto shutdown retry, implement the power management and Initialize de Buttonless Secure DFU Services) one at a time, and running a Build immediately after each script has been pasted.   

    As soon as I reach the "DFU event handler" script, I get the following error:

    Would you mind telling me what is wrong?

    Thanks

Children
Related
Terms of service