Hi,

You can't. Bluetooth Mesh is built on top of Bluetooth 4.0 specification where 2M and LE Coded PHY didn't exist.

The only PHY you can use for BT Mesh is 1M.

Regards,

Tiago

You just need to call start_discovery command, assuming that you don't want to change the scanning parameters.

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

You can also refer to this:

• MCU Peripheral Examples on GitHub (also includes EFR32)

Here you can find a snippet to read from flash.

https://www.silabs.com/community/wireless/bluetooth/forum.topic.html/reading_user_data-lihH

Also, why are you testing flash endurance exactly? The figure of 10k cycles is just indicative, you could easily go way beyond that on some parts.

What kind of information are you expecting to get from and how does this affect your application development?

Hi,

You can't use PS keys to test this, the index of the key doesn't map directly a to a flash address. When you write the same key multiple times it will go to the same flash page, once that page is full then it will defragment and erase the page so you need to write the same key X times before a flash page gets erased.

If you really want to test the flash endurance then you should use the em_msc functions directly, and loop between writing to a flash location and erasing the page.

Regards,

Tiago

Hi,

Why are you using your phone as a slave device? The most common setup is exactly the other way around, phone is the master and TB Sense is the slave.

Smartphones are not advertising as LE devices, you need an app for that. If you try with lighBlue it can emulate peripherals and will start advertising so you can try with that.

What is you use case exactly, why are you using the phone as a slave instead of master?

Regards,

Tiago

1. Can you tell me what I need to do to get Simplicity to stop complaining about the modified board? 

It seems you forgot to attach I guess the error you are getting is some incompatible part number warning and asking if you want to proceed with debugging? You can't do anything about that, studio associates kits to their known OPNs so there is no way to get rid of the error.

1. Can you suggest a high-level list of steps toward getting a sample app running in the modified board? 

Create a soc-empty project for the OPN that you soldered into the TB Sense 2 and take it from there. More details on the soc-empty can be found here:

• KBA_BT_0901: Bluetooth SoC-Empty example