I am working on thunderboard EFR32bg22 in this I am able to use different GATT profiles now I want to implement the bLE profile on my custom board with the component same as in thunderboard . in the custom board, I am able to run bare metal LED blinking but I am not able to use BLE stack. any program with a GATT profile is not working what could be the possible reason for that?
Thanks and Regards
Rakesh
Bluetooth Low Energy
Discussion Forums
EFR32BG22 Series 2 Modules
Unanswered
Hello!
Do you get any error message when you call the gecko_init function?
Can you debug the Bluetooth application?
What crystals are you using exactly?
0
I guess this is same question as the one raised in another thread.
No, I am not able to debug the BLE application. crystal used in the custom board is the same as in Thunderboard EFR32BG22 (32.768 kHz(LFXO) and 38 MHz(HFXO)).
We are using the EFR32BGC224F512GM32 MCU in our design. Here are our observations so far
1. Our Firmware works on Thunderboard from Silabs
2. An example project that does not use the HFXO and LFXO e.g. the Blink project work on our custom board
3. Any project such as the iBeacon that requires the use of the BLE stack (and hence the XTals) does not seem to work.
We request support in order to understand the source of this issue. There are no Loading Xtals or other components on the XTAL pins and hence they can be ruled out (This is as per reference design).
We also used the XTals on the thunderboard in order to ensure that the correct Xtals are being used, however, we are still unable to get the FW to work
1. When we try to debug the FW using the Simplicity Studio, the code does not jump to the main function
2. On clicking the pause button on the debugger the code is found to be jumping between addresses in the range from 0x328 to 0x384.
Please see attached the excerpt of the Map file from the compilation output. The project used for this code is the Simplicity Studio Standard iBeacon Project.
The issue is that you don't have a bootloader on your device and that is a requirement for running the application. You need to create a bootloader suitable for your application (depending on how you wish to update the firmware on the field) and flash that into your module, then the application should run fine.
0
thanks for the quick reply.
can you help me to understand how I can implement this, is there any quick start guide which I can refer to understand how can create the bootloader for the device.
how to use BLE stack on the custom board?
hello,
I am working on thunderboard EFR32bg22 in this I am able to use different GATT profiles now I want to implement the bLE profile on my custom board with the component same as in thunderboard . in the custom board, I am able to run bare metal LED blinking but I am not able to use BLE stack. any program with a GATT profile is not working what could be the possible reason for that?
Thanks and Regards
Rakesh
Hello!
Do you get any error message when you call the gecko_init function?
Can you debug the Bluetooth application?
What crystals are you using exactly?
I guess this is same question as the one raised in another thread.
https://www.silabs.com/community/wireless/bluetooth/forum.topic.html/_how_i_can_checkiftheexternalclockofthecust-ejKp
No, I am not able to debug the BLE application. crystal used in the custom board is the same as in Thunderboard EFR32BG22 (32.768 kHz(LFXO) and 38 MHz(HFXO)).
We are using the EFR32BGC224F512GM32 MCU in our design. Here are our observations so far
1. Our Firmware works on Thunderboard from Silabs
2. An example project that does not use the HFXO and LFXO e.g. the Blink project work on our custom board
3. Any project such as the iBeacon that requires the use of the BLE stack (and hence the XTals) does not seem to work.
We request support in order to understand the source of this issue. There are no Loading Xtals or other components on the XTAL pins and hence they can be ruled out (This is as per reference design).
We also used the XTals on the thunderboard in order to ensure that the correct Xtals are being used, however, we are still unable to get the FW to work
1. When we try to debug the FW using the Simplicity Studio, the code does not jump to the main function
2. On clicking the pause button on the debugger the code is found to be jumping between addresses in the range from 0x328 to 0x384.
Please see attached the excerpt of the Map file from the compilation output. The project used for this code is the Simplicity Studio Standard iBeacon Project.
Attached for reference.
.ARM.attributes
0x00000352 0x3c ./gecko_sdk_3.0.0/platform/common/toolchain/src/sl_memory.o
.ARM.attributes
0x0000038e 0x3c ./gecko_sdk_3.0.0/platform/emdrv/nvm3/src/nvm3_default_common_linker.o
.ARM.attributes
0x000003ca 0x3c ./gecko_sdk_3.0.0/platform/emdrv/nvm3/src/nvm3_hal_flash.o
.ARM.attributes
0x00000406 0x3c ./gecko_sdk_3.0.0/platform/emdrv/nvm3/src/nvm3_lock.o
.ARM.attributes
0x00000442 0x3c ./gecko_sdk_3.0.0/platform/emlib/src/em_cmu.o
.ARM.attributes
0x0000047e 0x3c ./gecko_sdk_3.0.0/platform/emlib/src/em_core.o
.ARM.attributes
0x000004ba 0x3c ./gecko_sdk_3.0.0/platform/emlib/src/em_emu.o
Thanks and Regards
thanks for the quick reply.
can you help me to understand how I can implement this, is there any quick start guide which I can refer to understand how can create the bootloader for the device.
Thanks and Regards