Do you see any activity on the pins if you view it with an oscilloscope?

Do you see any activity if, instead of using printf you write directly to the SBUF1 register?

Regards,

Joe

Hi Alexander,

There is a help menu inside the config2 program that gives an overview of how to use the tool.  If you can give more specific information about the error I may be able to help you.

Also consider the configurator tool which is part of Simplicity Studio.  This tool is newer and is better supported than config2.

Regards,

Joe

Vishal,

The three wire mode supported by the 'F411 has no chip select.  To implement what you have described you should use 4 wire mode.  You can simply not connect the MOSI pin, or not route it through the crossbar.

SPI is a synchronous protocol, so transmit and receive happens at the same time.  To start a SPI transaction, write data to the SPI0DAT register.  Since you are not actually using the transmit, the data you write will not matter.  After the SPI transaction is complete, the data you received will be in the same register.

Regards,

Joe

TResell,

Typically, XRAM is used for global variables.  How are you declaring the variables that use XRAM?  Can you tell me more about your application and your memory requirements?

Regards,

Joe

Hi Michel,

Do you have system view installed?  It should be in the path: STUDIO_SDK_LOC\util\third_party\segger\systemview

It might not be installed based on the products/SDKs you have in Studio.

Regards,

Joe

JTAG based 8 bit MCUs support watchpoints, but c2 based ones do not.

Regards,

Joe

See if attachments in this KBA is what you are looking for?

https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/06/09/cp2615_evaluationki-MpKq

If you have installed the Simplicity Studio, you could also get the pdf format schematic via it.

You can take a look at this document.

https://www.silabs.com/documents/public/application-notes/an976-cp2102-3-4-9-to-cp2102n-porting-guide.pdf

Hi Alva,

Does this issue happen on the latest DLL from our website, or does it only happen with the other version you have?

Regards,

Joe