hi Syed,

Please select the GNU ARM v7.2.1 as the default active toolchain.

hi,

I don't think so that the stack will set wrong length parameter for the specified advertising set. Please upload the C source file here and I'd like to review it.

Thanks

Hello:

I am trying to capture current consumption using energy profiler, and the data you record goes into an isd file?

Where is this file? Is there a dialog where I specify where the file should be?

I also get a"no launch history" message. How do you launch history?

Thanks in advance,

Marcelo

Did you check if the device was locked, and try to unlock the debug access by using the Simplicity Commander. Please make sure that the RESETn is connected between the debugger and target device.

hi Leandre,

Are you using the default soc-btmesh-light demo for the test?
I also try to replicate the symptom but failed. When put the iOS device away from the light node, the "gecko_evt_le_connection_closed_id" event will be triggered on the mesh node side with error code 0x208 (connection_timeout).

Thanks

Looks like it's a timing issue, have you even tried the flow similar as below.

void appMain(gecko_configuration_t *pconfig)
{
	// ......
	while(1)
	{
		if(notifications_enabled && jpgLen > 0)
		{
			evt = gecko_peek_event();
			if(evt == NULL)
			{
				SendImg();
				continue;
			}
		}
		else
		{		
			evt = gecko_wait_event();
		}

	    /* Handle events */
	    switch (BGLIB_MSG_ID(evt->header)) {
	       ……
	    ｝	
	}
}

hi Yong,

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. 

Thanks

hi Aaron,

Please also add " #include "em_cmu.h" " to app.c

Thanks

hi Vneehu,

Is the external debugger a 3rd debugger or our WSTK ?
Please make sure that the BGM121 on custom board is powered correctly. If you are using the WSTK in debug out mode to debug the custom board, please make sure that you have connected the VTARGET of the WSTK to VDD.

Thanks