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

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

  • Hi.

    Unfortunately I cannot help you with this question since this is a 3rd party module and I do not know what is in the factory pre-flashed firmware. I suggest that you contact ublox on their support forum.

    Best regards,

    Andreas

  • Hi Andreas.

    Thanks for your comment. I did contact with u-blox support forum but since is the first time I do and while waiting for an answer, I just wanted to make sure that Nordic's awesome support (really ¡) couldn't provide the answer in this case. 

    Best regards

    Juan

  • Hi Andreas.

    Let me ask you. If you buy a stand-alone module integrating an nRF52840 SoC, and you read in the datasheet that this module supports Secure Boot and FOTA features, both enabled by hardware, what would you expect?

    And more precisely,

    1.- Would you expect the module advertising its device name on boot up?

    2.- Would you expect the de module supporting a DFU Service on boot up?

    3.- After scanning and connecting with this module using your Connect Tool, would you expect a DFU sign showing on top of its services listing window, enabling you to initiate a secure data firmware process to update the SoC firmware images? 

    Thanks in advance for your comments.

    Regards,

    p143/ Juan

  • 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

  • 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

Related