Just a reminder to everyone that you should sign up to get security notifications. This will ensure that you have all the latest information about the latest security vulnerabilities and whether Silicon Labs products are affected or not. We have a video on the following page that shows you how  https://www.silabs.com/security

Hi All,

   Silicon Labs will issue an official advisory about this as soon as it's ready. In the meantime, my suggestion is that you use the security features in our stack to avoid the problems described in that report. The main threat is that a device forms a bond and encrypts/authenticates the connection but on subsequent connections encryption/authentication is not used which allows some attacking device to claim it is a device that was previously bonded. You can avoid this problem by making sure that your GATT characteristics have the authenticated read/write properties. Making those characteristics authenticated will cause the stack to raise the security level of the connection. You could also use the 'only allow bonded connections' flag in the security manager configuration once you have bonded with any client that you need to.

 

Steve

ncp-host is a template project to create a host on an EFR32. The functionality is limited, similar to that of soc-empty.

Hi,

   I just tried the NCP throughput tester on an MG13 and it works just fine for me. I suggest that you check your COM port settings.

To reiterate, I really don't think that this is the best way for you to implement what you asked for at the beginning of this thread. If you want to do a serial communication channel, we have the SPP over BLE article for that.

Steve

Hi,

   no, you do not have to call that API. If you don't have any specific timing/duty cycle requirements you can just let the stack use the defaults 10ms window/interval.

https://docs.silabs.com/bluetooth/latest/le-gap#cmd_le_gap_set_discovery_timing

Steve

Peng,

   You can go into the project settings and remove the binapploader.o file as shown in the attached.

 

Steve

You can use the following API to change the behavior

https://docs.silabs.com/bluetooth/latest/system#cmd_system_linklayer_configure

 

Steve

Hi,

   The 2.7.6 version is preferred because of some fixes. When the install button is greyed out it usually means that you need to install the updates on the product updates tab first.

 

Steve

Hi,

   resetting the NCP should go very quickly, much less than 30 seconds. Typical reasons for the NCP to fail to start up are a missing bootloader or mistmatched USART settings. I suggest that you try connecting to the NCP with bgtool (compatible tools in the launcher) If you don't get an answer, try reflashing the bootloader.

 

Steve

It's difficult to say what happened with the second tablet unless we have a packet trace. There could be an interference problem, the tablet could be at fault or the problem could be with our stack.