The BLE stack requires HFXO running at exactly 38.4MHz. This is from UG136:

Note: The Bluetooth stack only supports 38.4 MHz HFXO frequency; no other HFXO frequencies are supported.

Hi, I tried to use HFRCO instead of the HXFO crystal.  Here's the configuration I used.

CMU_OscillatorEnable(cmuOsc_HFRCO, true, true);
/* Change to 38MHz HFRCO. Use calibration data from DI page. */
while(!!(CMU->SYNCBUSY & CMU_SYNCBUSY_HFRCOBSY)) {
    /* Busy wait */
}
CMU->HFRCOCTRL = *(uint32_t *)(&DEVINFO->HFRCOCAL12);
SystemHfrcoFreq = 38000000;                                                                                                                                                                                                                                                                                            
/* Set WSHFLE to allow access to LE peripherals when running at frequencies above 32 MHz. */
CMU->CTRL |= CMU_CTRL_WSHFLE;

I get an assertion while trying to initialize the BLE stack:

gdb) bt                           
#0  Default_Handler ()
#1  <signal handler called>
#2  0x00023922 in RAILInt_SetChannel ()
#3  0x00023ae4 in RAILCore_ConfigChannels ()
#4  0x00025170 in RFHAL_ConfigBle1MbpsViterbi ()
#5  0x0002517e in RFHAL_BleInit ()
#6  0x00023cac in RAILCore_BLE_Init ()
#7  0x00023cc8 in RAIL_BLE_Init ()
#8  0x0001ae24 in ll_radioInit ()
#9  0x00019590 in BTLE_LL_Init ()
#10 0x0001812c in bg_radio_init ()
#11 0x00013f3a in gecko_stack_init ()
#12 0x0000d852 in gecko_init (config=0x2e384 <config>)

Is HXFO an absolute requirement to use the BLE stack? If no, what's the recommended configuration to use HFRCO instead?

thanks!

Dave

hey hey! that worked!

Interesting that specifying the full path in Linux is not needed.

thanks a bunch!

I'm getting the following error when I run this on the Mac OS X command line.

$> /Applications/Simplicity\ Studio.app/Contents/MacOS/studio -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild --launcher.suppressErrors -no-indexer -data /tmp/ss_workspace -import . -build ncp/GNU\ ARM\ v4.9.3\ -\ EVK\ Default -D EVK
Project: file:/Applications/Simplicity%20Studio.app/Contents/MacOS can't be found!
Studio:
Java was started but returned exit code=1
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Xmx640m
-Declipse.p2.unsignedPolicy=allow
-Djava.net.preferIPv4Stack=true
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Djava.class.path=/Applications/Simplicity Studio.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
-os macosx
-ws cocoa
-arch x86_64
-launcher /Applications/Simplicity Studio.app/Contents/MacOS/studio
-name Studio
--launcher.library /Applications/Simplicity Studio.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.300.v20150602-1417/eclipse_1611.so
-startup /Applications/Simplicity Studio.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.overrideVmargs
-application org.eclipse.cdt.managedbuilder.core.headlessbuild
-no-indexer
-data /tmp/ss_workspace
-import .
-build ncp/GNU ARM v4.9.3 - EVK Default
-D EVK
-vm /Applications/Simplicity Studio.app/Contents/Eclipse/jre/Contents/Home/lib/jli/libjli.dylib
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Xmx640m
-Declipse.p2.unsignedPolicy=allow
-Djava.net.preferIPv4Stack=true
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Djava.class.path=/Applications/Simplicity Studio.app/Contents/MacOS//../Eclipse/plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar

The key message, I think, is: 

Project: file:/Applications/Simplicity%20Studio.app/Contents/MacOS can't be found!

A few notes:

• This headless build works just fine in the Linux version of Simplicity Studio.
• I tried creating a symlink (ln -s) called "/Applications/Simplicity%20Studio" with no luck
• I can't find any xml file that may be the culprit
• I'm running the latest version as of this morning June 26, 2017
• Attached you'll find all the gory details of my config

Anyone else run into this issue? Is this known?

Hi, I used the hardware configurator tool in Simplicity Studio v3 to set up USART1 to use pins PD0 (TX) and PD1(RX). This is on the EFM32WG-STK3800 eval board.

I noticed my uart console was spitting out garbage.

After reading the RM and studying the uartdrv.c code, UARTs require HFPER clock enabled to set the baud rate.

However, the hardware configurator does not do this.  More explicitly, 

CMU_ClockEnable(cmuClock_HFPER, true);

is not being called anywhere in InitDevice.c (source file created from the configurator).

Is this a bug in the configurator tool in simplicity studio v3?

thanks!

I installed Simplicity Studio v3 on my Windows VM.  Through that OS, I updated the onboard ST-LinkV2 firmware to 0v11p2b71 by following this guide

After that, I'm able to see the device on my Mac OS X.

Still nothing in the linux version, though... but that's for another thread.

I'm having the same problem with Giant Gecko Starter Kit.  I've tried 2 boards with no luck.

I do not see this issue under the Known Issue in the Release Notes either.

Here's what I'm running.

• EFM32GG-STK3700 eval board
• Simplicity Studio v3
• Mac OS X El Capitan 10.11.3

Is this a real issue? 

.. because .isc file contains much more then just gatt.xml...

I suppose I could manually re-generate the files on every SimplicityStudio update, and revision control all files outputted from appbuilder.. but that just feels clunky to me.  I'd much rather automate the whole thing for every build.  It's a maintenance issue, really.

In any case, I understand the overall flow better now. Thanks for the support!

So is it safe to say the following?

.isc -> gatt.xml -> gatt_db.{c,h} ?

if so, it would be nice to have a command line version of appbuilder with the .isc file as input so we would only need to work with and control the .isc file.

this thread, though, made me discouraged.  Anyone know if there are plans to have an appbuilder command line option?

Hi,

I noticed when hitting the generate button....

... , it produces a BgBuild_Log.txt file that looks like this (ignore the warnings):

// Copyright 2017 Silicon Laboratories, Inc.
//
//

Executing: bgbuild
Output:
ALL OK

Error:
Unknown option 'n'.
WARNING: 2a00 length attribute is 8 but actual value length is 11. 8 will be used.
WARNING: 2a29 length attribute is 20 but actual value length is 4. 20 will be used.
WARNING: 2a24 length attribute is 10 but actual value length is 3. 10 will be used.
WARNING: 2a25 length attribute is 20 but actual value length is 8. 20 will be used.
WARNING: 2a27 length attribute is 10 but actual value length is 3. 10 will be used.

Does appbuilder call the bgbuild executable to create the *gatt_db.{c,h}* files?  If so, what does the bgbuild command line look like? How does it work without a .bgproj file?

thanks!

Dave