I tried to flash soc-rangetest-rail-dmp example project using the gecko sdk suite 1.1.1 on a module that we have built on and i am unable to find the device.
I am using EFR32BG13P632HG. The example project works on the development tools.
Flashing a project created for a WSTK radio board into custom hardware is not a good idea.
The radio board projects bring code to handle hardware dependencies like the SPI Flash which could fry your custom hardware.
To get those projects running on your hardware you should create the project for the specific OPN (not radio board) that you are using. Most likely the project will not build out of the box so it requires some adaptation to make sure it runs on your hardware.
To differentiate between a radio board and OPN please check this KBA: https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2018/12/12/bluetooth_soc-empty-wk3r
Are you trying to scan the device with smartphone App, for e.g, BlueGecko, right ? I will suggest to check your hardware design with a simpler example firstly, for e.g, the soc-empty or some peripheral example released via SiliconLabs github.
In general, if you are creating a new application for a custom board, you need to configure the setting in the hal-config-board.h accordingly. Please make sure that the setting in this file is correct for your hardware design, for e.g, DCDC present or not, serial port pin etc.
Hi, i tried using soc-btmesh-light (Bluetooth Mesh SDK 1.4.3) on the hardware that we have built on and also configured the setting in hal-config-board.h according to my hardware. I am able to scan the device with smartphone app(blue gecko). For the range test example project (soc-rangetest-rail-dmp), I also had configured the setting in hal-config-board.h. I then tried to flash the modified example on the development kit and i am able to find the device using blue gecko app. However when i flash the modified firmware into the hardware we have built, i am unable to find the device through the app.