Zack,

I strongly recommend using flow control at those speeds and amounts of data.  I think if you enable hardware flow control the problem you are seeing will go away.

Regards,

Joe

Hi Zack,

Are you using flow control on both ports?  Which direction is losing data?  UART to USB, USB to UART, or both?

Regards,

Joe

Is your example using LESENSE?  If you monitor the touch pads with an oscilloscope, do you still see the ACMP waveform when the part goes into low energy mode?

Regards,

Joe

Hi Black Lin,

Can you show the code you are using to call HidSmbus_GetReadResponse, including declaration and initalization of the parameters?  Are status, buffer, and numBytesRead valid pointers?

Regards,

Joe

The header file compiler_defs.h and the definitions it provides are deprecated, and have been removed from the latest SDK of the Silicon Lab IDE (5.50).  The header has been replaced by si_toolchain.h.  All of the example code provided with the Silicon Labs IDE now uses si_toolchain.h and its definitions.

The main difference between the two headers is the name of some of the defines.  For example, SI_SBIT replaces SBIT, uint16_t replaces U16, and SI_INTERRUPT replaces INTERRUPT.

In order to migrate a project from one header to another:

1.  Remove _compiler_defs.h from the project and add si_toolchain
2.  Replace "#include <compiler_defs.h>" with "#include <si_toolchain.h>
3.  Change defines used in file.  Search and replace is useful for this

For more information on why this change was made, see this KB article: https://www.silabs.com/community/mcu/8-bit/knowledge-base.entry.html/2017/03/31/software_licensinga-qzLc

I recommend a 1 kOhm pull up resistor on the reset pin, other than that the schematic looks ok.

Does using an EVK work as expected on your computer?  Are you using the latest drivers?  When you plug the board in, does the CP2104 appear in the list of usb devices you get when you use the "lsusb" command?

Regards,

Joe

Hi Nick,

Not a lot has changed with these utilities, I don't expect there is a new readme file.  There is a VerifyUSB function separate from DownloadUSB, so you will need to run them separately.

The error code is returned by the program.  To get the error code from the command line you can use %errorlevel% if you are using cmd, and $? if you are using bash.  See this link for more information: https://stackoverflow.com/questions/334879/how-do-i-get-the-application-exit-code-from-a-windows-command-line

For your last question, try verifying the part against a different image than you programmed to it, and see if that gives you an error.

Regards,

Joe

David,

Some suggestions:

 - Enable the "Smart download" option from the options menu

 - Close open debug , dissasembly, and memory view windows

Regards,

Joe

David,

I'm checking with the IDE developers to see what may be causing this.  Is this running on a custom PCB?  Have you tried using Simplicity Studio to program the part, and if so, do you see the same delay?

Regards,

Joe

Hi,

The screenshots you have posted show the product updates tab open.  There may be new SDKs in the SDK tab.  The SDKs do not automatically install new versions, you will have to select which ones you want to install.

Regards,

Joe