Hey, guys! This problem has been solved. It's not a software problem. It's a hardware error. Don't connect the ground wire of I2C equipment to 19 of the gecko development board. The manual says that the hardware is not a power source, but a common pin。

Another point is that do you have external pull-up for the I2C pin?

If you could upload your schematic it may helps. 

Usually to debug the I2C communication you could use a scope to monitor the signal, if you have done this do you mind to upload the picture your captured.

Another point is that do you have external pull-up for the I2C pin?

If you could upload your schematic it may helps. 

Usually to debug the I2C communication you could use a scope to monitor the signal, if you have done this do you mind to upload the picture your captured.

Is this a Silabs radio board, what debugger adapter you are using?

https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2014/05/21/unlock_a_brickede-xkAm

I am sorry I did not catch your point here.

Do you elaborate a bit in detail your question.

Do you mean you need to program a target MCU via a host MCU?

if you could upload a picture to show what you needed to realize, it may helps.

Unfortunately, the datasheet and your assessment are correct - the standard UART interface on the CP2105 does not support UART break.

You may be able to emulate the break by configuring the TXD in open-drain and tying TXD to an unused GPIO (also in open drain mode), then issuing a GPIO toggle command for the UART break. There is also no way to pull all pins to low state.

Try programming the serial number of the two devices so that they're different, if they are currently the same. I've attached utilities to this post, you'll want to try running CP210xSetIDs.exe and change the "Serial Number" field to be unique on each device.

Interestingly, it is common for people to have the opposite problem. Make sure that you haven't somehow installed the driver so that Windows ignores serial numbers: https://www.silabs.com/community/interface/knowledge-base.entry.html/2014/11/19/getting_dpinst_toig-Pt4X

Hi QiangHuang,

You are correct with 1, 2, and 3.

The reason DMA callback is only called twice is because of its parameters. There are 3 parameters in the DMA callback function, but the userPtr is set to a pointer pointing to adcSampleDataQueue. The callback parameters and the userPtr need to match. Because you can only pass arguments to the callback function through the userPtr, you will need to change your DMA callback function to accept one pointer as an argument.

Regards,

Dayoung Lee

Hi Leandre,

You're right - the RTCC doesn't have a way to account for the fact that years divisible by 100 (but not by 400) will not be leap years. As a quick test here, I confirmed that the RTCC will indeed think that every '00' year is a leap year.

You will need to track the hundreds/thousands place of the year manually and then set the DATE register manually to correct for no leap years during certain centuries. For example, when the RTCC increments to Feb 29, 2100, you'll need to update the date to Mar 1 instead.

-Brian