The writeAP() function times out after 200 retries.  Is it hung, or still attempting the retries?

Some other things you can check:

 - Delay slightly longer than 150 us in case the AAP window has not started yet

 - Try the extended AAP window feature described in section 4.4 of AN0062

 - Compare the behavior of your program to our tools such as Simplicity Commander.  Observe the SWDIO and SWCLK signals on a scope

Regards,

Joe

Simplicity Studio supports the USB debug adapters (UDA), and the J-Link interface on the STKs.  It does not support 3rd party programmers.

If you are interested in programming an 8 bit device with a C8051F380, see AN127.  This application note does not support debugging, only programming.

Regards,

Joe

Hi Inkyu,

I think you have the PRS pin assignments set incorrectly in setupPrs() in your second code example.  According to the BG13 datasheet, PD10 is location #1 on PRS CH4, and PD11 is location #1 on PRS CH5.

For general diagnostic methods (if the above does not resolve the problem), I would try reading the values of PD10 and PD11 as gpio to verify the right levels are on the pin, then set up PRS and read the state of the PRS signals (in the PRS_PEEK register) to verify they are routed to PRS properly.  After that you can troubleshoot the PCNT peripheral.

Please let me know if you have any further questions.

Regards,

Joe

Hi Madhav,

You don't mention which part you are using, but most devices still have options for not using the universal configurator.  For example, for PG22 there is a blink_baremetal project that uses direct emlib calls.  If you have seen our peripheral examples (available in Studio or on Github) these do not use configurator either.

Please let me know if you have any further questions.

Regards,

Joe

I think this is possible, you can take a look at the uart bootloader document and implement it on your product : 

https://www.silabs.com/documents/public/application-notes/AN533.pdf

https://www.silabs.com/documents/public/application-notes/AN778.pdf

Ryohei,

You are correct that the value specified in the datasheet is time from POR to code execution.  Debug connection should be available soon after that.  Typically when a debug connection is needed from the start, the debugger will reset the part, then run code with the debugger.

Are you interested in having the debugger connected from the start of the program, or are you particularly interested in connecting right after Power On Reset?

Regards,

Joe

After posting my question, I developed this:

1. Conversion of two eight bit registers to an integer Y;

Register A (8 bits) & Register B (8bits), where A is the MSByte

Integer Y = A * 256 + B

2. Conversion of Y to two eight bit registers A & B;

Register A (8 bits) & Register B (8 bits), where 0<= Y <= 65535

Register A = int ( Y / 256 ), where Register A is the MSByte

Register B = int (Y ) - A * 256

Hi SoCal,

There are some timer0 examples, including 16 bit in Simplicity Studio, for example EFM8BB1_Timer0_16bit.  Which EFM8 part are you using?

There aren't any library functions to break a 16 bit variable into two 8 bit registers (and the other way around), but it can be done with bit masking and shifting.

Please let me know if you have any further questions.

Regards,

Joe

Hi Sebastian,

We have discussed this on a support ticket as well, but I think there is another source of power consumption on your board.  The crossbar is not required to be disabled in sleep mode.

Regards,

Joe