BLE end device manufacturer vendor based on Nordic BLE 4.2 or BLE 5.0

[Hardik V Patel]

Hi,

Our system is based on the  nrf52832 with SDK  BLE_2.0.1 for the mesh.I have few queries as per below,

1)It would be great if you could suggest any vendor who is working on Nordic BLE 4.2 or BLE 5.0 for manufacturing end devices like Bulb or light, door and motion sensor. We required this three type of devices to work with our product for communication between gateway with the end device.

2)I need DFU (Bootloader)UART for our application to upgrade nrf52832 firmware by the host controller but unfortunately, it is not available in current BLE mesh SDK, We have one host arm cortex-4 based 32-bit controller and from it, we want to do the firmware upgrade over the UART for thenrf52832. so we have decided to implement our own UART DFU support. We have got an answer from nordic that it is possible but not easy and not sure so Can you please give us contract detail of any technical person who is sure about it?

3)How we can proceed for development of DFU UART ? and what are the things required to accomplished it, We have found less information in the infocenter Nordic to start development of DFU UART, so please give us proper guidance and tell us a roadmap to complete it,

4)Let us know if any permission or resources required for the key or anything required from the Nordic company when we want to develop DFU UART?

[Hung Bui]

Hi Hardik, 

 

1. Please let us know your location so we can direct you to our sale representative for your request. 

2. Do you also plan to do Mesh DFU or only serial DFU ? If you only plan to have serial DFU I don't see any problem using our serial DFU from our nRF5 SDK for your purpose. 

3. The documentation on UART/serial DFU is here. An example is here.

4. No, you are free to use any resource provided by Nordic, as long as you keep the license header in the files. 

[Hardik V Patel]

Hi Hung Bui,

Nice to meet you! Please find my answer as per below,

1)City:- Ahmedabad, Country:- India

2)Yes, We want to use Mesh SDK BLE_2.0.1 and in that, there is no support of DFU UART, in the detail for more clarification, For the DFU UART, we also want to develop our own custom HOST utility by our own. Don't want to use Nordic traditional ones like NRFutil or other. We want to do the firmware upgrade over the UART using the 32-bit microcontroller and it is RTOS don't have any OS, So please guide us how we can do this?

So Basically, We need two things to develop one is for the host(Ex:-32-bit microcontroller like STM32, LPC1788) and one is for the target(nrf52832 DFU UART). we need to develop code in the nrf52832 DFU UART and in the HOST controller(32-bit microcontroller) Serial firmware Update code over the UART.

[Hung Bui]

Hi Hardik, 

1) I will send you via PM the contact to our RSM in India. 

2) Please clarify, you only want to update firmware on single nRF52 without updating other nodes in the mesh network ?

The Mesh DFU provided in the SDK is to be used to update the whole mesh. It works in the way that the first node when receiving new firmware will propagate the firmware during the DFU process. I don't know why you say no support of DFU UART ? Step 10 in this guide is when the new firmware is transmitted to the node. 

 

If you want to update just one node from the the master MCU, you can use our nRF5 SDK's UART DFU bootloader instead of the Mesh DFU as in the links in my last answer. 

[Hardik V Patel]

2) Yes, I only want to update the  nRF52 without updating other nodes in the mesh network. I asked in the same Nordic forum earlier and they told that mesh SDK has not support of DFU UART in the SDK and I have also not found source code example in the SDK. Please find this link(NRF Link), If you have any idea then please share my sample example code and DFU UART code for both host(32-bit controller ) and target (NRF52)

[David Edwin]

The simplest way would be to have an "app_id" for the serial node separate from the rest of the Mesh nodes. This would still propagate the DFU over the radio but since there is no other node with the same "app_id" as the serial node it will only update the serial node. This is currently available with the Mesh DFU.