Port nRF51-ble-bcast-mesh-master to RedBear Lab BLE Nano

[Max]

I use Keil uVision 4.74.0.22 to compile nRF51-ble-bcast-mesh-master with nrf51_sdk_v6_1_0_b2ec2e6 and get the rbc_mesh_BLE_Gateway.hex. However, I drag and drop the hex file to MBED drive and it's not working. I heard that uVision trial version only support 32KB firmware size. Would that be the problem?

[Hung Bui]

@Max: have you also drag and drop softdevice to the mbed driver ? When compiling normal project with KEIL, the softdevice is not included.

You can follow this link: https://devzone.nordicsemi.com/blogs/11/using-nrf51-sdk-with-the-nrf51822-mbed-kit/

[Max]

Thanks for the tip. I got rbc_mesh_BLE_Gateway working by merging it with s110_nrf51822_7.3.0_softdevice (didn't know merge is required). However, rbc_mesh_led_example is not working and I found that its main.c doesn't include nrf_adv_conn_init(). Would that be the problem?

[Hung Bui]

@Max: How did you test the LED example ?

Note that the BLE_Gateway allow a phone to connect and join the network, that's why we have nrf_adv_conn_init() so that BLE central device can connect and control the other nodes.

In the LED example, they only do broadcast mesh, won't allow connection. The control is either from button press, or from a phone connected to the BLE Gateway.

[Max]

I see. Previously, I was expecting to see advertising packets from LED example. Now I can turn LED on/off on LED example by writing LED1 value characteristic on Gateway example.

Because I still can't see any rebroadcasting packets, I am wondering how the change of LED1 value on Gateway example got to propagate to other nodes?

[Hung Bui]

@Max: Currently the packet between LED-Mesh is not BLE compatible. We have the option RBC_MESH_PACKET_FORMAT_ADV_COMPATIBLE for the init_params.packet_format but it's under development not ready yet.