Hey delu,

Again thank you all for the help! Turns out there is an issue with autogen: LFXO remains selected instead of HFCLKLE even at higher LEUART baud rates. Changing that to HFCLKLE fixes the problem.

Will do, thanks again for your help. However at this point I don't think VCOM_ENABLE is the cause, because I was able to get VCOM to work in other project configurations before, and I had not set any GPIOs. In addition to that, since there are no traces populated for PA5 on my custom board, I don't think the default PA5 GPIO set in autogen (if any) would have any effect, and I did not specify other GPIOs to set VCOM_ENABLE.

I was able to get LEUART to work using Empty C Project as base, but the same setup won't work if the base is Bluetooth SOC Empty. I was wondering if there is something in Bluetooth SOC Empty that is causing the issue.

All that said, I will look into the schematic and give it a shot. Thanks!

Hey delu,

For my application, the custom board is interfacing with the WSTK via the Mini-Simplicity connector, and I noticed that on its pin diagram VCOM_ENABLE is not specified. Does that mean I will have to solder a wire from my custom board PA5 to the WSTK?

I thought if I set the WSTK debug mode to OUT, I should be able to just use VCOM without having to set the enable pin? Please correct me if I am wrong.

Thanks again.

Hey delu,

Thanks again for the quick response. This is helpful. I have one more question for you: if PA5 needs to be set to enable VCOM, then why would IOStream USART work? Is it just a strange undefined behavior, and I should set PA5 in either configurations?

Hey delu,

I am still having issues on my side (custom board using BGM111A256V2). Using the same TX and RX pins (PF4 and PF5), IO Stream USART works but IO Stream LEUART does not for some reason.

A couple of follow-up questions:

1. What is PA5 used for?
2. Have you tried using 115200 baud instead of 9600 baud? Or is it not doable because brd4303a does not have the high frequency clock needed?

Thanks again!

Hi Jui Yen Chua,

Perhaps other customers have used the Unity Test harness and can offer suggestions on using it with Simplicity Studio.

I have glanced at the provided github link and it appears that Unity adds a few files to the project, so it sounds like you are asking if you can create a build configuration that includes those files and have another build configuration that does not include those files.

Eclipse definitely supports multiple build configurations and so they can be added to a Simplicity Studio 5 project.  The issue is that the Simplicity Studio Project Configurator is not designed to support multiple build configurations so as changes are made in the Project Configurator there might be some issues using the different build configurations.

I offer these suggestions for creating and dealing with multiple build configurations, but realize you might run into issues as you switch between the build configurations and make changes in the Project Configurator:

1. Create a new build configuration - Do not clone an existing build configuration

Right click the project folder and select [Build Configurations] > [Manage...] then select [New...] and check the box for the build configuration on which to base the new configuration:

Now select the new build configuration and hit [Edit...] to rename it and then click [Set Active] to make it the default build configuration:

2. Now add the unit test specific files to the project.  They can be dragged from the operating systems file browser application into the project folder in the Simplicity Studio Project Explorer window.

3. Change / Verify the Resource Configuration settings for the new file so that they are only included in the Unit Test build configuration.

Select the files / folders and then right click the selection and select  [Resource Configuration...] > [Exclude from build...] and then check the boxes for the build configurations that should not use the Unit Test files - so the Unit Test build configuration box should not be checked since the files will be included in that configuration:

I hope this helps you get started.  I do not have experience using the Unity Test Harness and I am not sure if other Application Engineers at Silicon Labs have ever used it or not.

If you do run into build issues with one of the build configurations as changes are made in the Project Configurator, then after setting the build configuration "Active", open the Project Configurator file (.slcp) and do a [Force Generation] and see if the project then builds successfully.  Also check the Resource Configuration settings for any files that are causing errors.

Thank you,

jpitt