Hi Michael,

I am not sure if this answer was meant to be posted on this forum question? If not, please clarify. This post included driver related questions while using the CP2102N. 

Hi all,

The issues being reported on this thread have been fixed in a new revision of the chip - the CP2102N-A02. In addition to this, the drivers in all supported OSes have also been updated to address the issue. If you continue seeing the same problem in Linux, please rebuild the driver using the latest source file available on the website - https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers. 

Please use the latest revision of the chip with the latest drivers and create a new forum post if you continue experiencing any issues.  

Hi,

Sorry for the delayed response. I missed this notification. Our legacy driver(v6.7) supports Windows XP (not embedded Windows XP). Silicon Labs is no longer actively supporting or testing on Windows XP or Vista, although a software package, DLL, or driver may still work on these platforms. For more information, please refer to this Knowledge Base Article - https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/01/10/legacy_os_softwarea-bgvU. 

Hi,

I have a few questions here to understand the issue better -

1. What CP210x device are you using?

2. Was the board designed by you or is this a third party board using the CP210x?

3. What version of the driver are you using?

4. Where did you download the driver from? 

请先确认驱动文件是否存在于下面路径：

/Library/Extensions/SilabsUSBDriver.kext

参考以下文章看是否有帮助？

KB - Debugging Issues with the Mac VCP Driver

KB - VCP Driver location on Mac OS

KB - Troubleshooting the CP210x USB to UART Bridge VCP Drivers on a Mac

请提供使用的USB设备的具体型号， 是Silicon Labs的CP210x芯片还是其它厂商提供的产品吗？

https://www.silabs.com/products/interface/usb-bridges

Silicon Labs 芯片的USB VID = 0x10C4

查看已连接到电脑的USB设备，可以使用下面命令：

$ ioreg -p IOUSB -l
$ system_profiler SPUSBDataType

Problem

Some mobile devices may have connection problems after updating BGX13 to 1.2.2045.0.

SIlicon Labs recently updated the firmware for BGX13 to version 1.2.2045.0.

https://docs.silabs.com/gecko-os/1/bgx/latest/release-notes

This version has some feature improvements, but these improvements required that we make some changes to the GATT attributes. Because of this, some phones may experience connection problems after the BGX13 firmware is updated.

Reason for Problem

Some mobile devices remember the GATT attributes of devices that have been paired or bonded in the past. When the GATT attributes are changed after the 1.2 update, the mobile device cached GATT information is misaligned between the two devices. This causes invalid handles to bluetooth services and characteristics. As a result attempts to connect to the device may no longer work, or some feature may not work such as sending or receiving data between a phone and the specific BGX for which this invalid bonding exists.

Invalid/misaligned bonding data must be cleared and then the bond should be re-established using the correct GATT attributes.

Solution

The problem may manifest in the following ways.

On iOS, you may see a message on the device details screen reading "SOME_OTHER_MODE".

On either Android or iOS, you may also see a password dialog appear at an inappropriate time or when no password has been set. You might also see that data is not being sent from the phone to the BGX or from the BGX to the phone.

To solve this problem, perform the following operations:

1. If you have access to the BGX command line interface such as through a Terminal emulator connected to the serial interface, enter the command 'clrb' to clear the bonding information from the BGX.
2. On your phone, open the Bluetooth Settings and locate the BGX device. Click a "i" icon, gear icon, or other details icon for the device in the Bluetooth settings and choose "Forget" or "Unpair". 
3. On your phone, turn Bluetooth off and then back on. This has been particularly noted as a necessary step on iOS 13. Alternatively, you could reboot the phone itself. However, rebooting is not a substitute for "forgetting" the device in the Bluetooth settings.
4. Kill the BGX Commander app as you would any app on your iOS or Android phone.
5. Restart BGX Commander and re-connect to the device. It should work correctly now. 

Also refer to https://docs.silabs.com/gecko-os/1/bgx/latest/firmware-update#problems-after-upgrade

In order to program the MCU I have to set clock dividers, I/O pin direction, up or down input pin trigger, pull-up/pull-down resistor control and so on. How do I do that? 

It is done very similar to Atmel parts, ie you set some SFRs, but the Silabs parts are a little more complex, in that a most minimal pgm needs to also config the watchdog,. and enable the port pins.

More typical pgms also need to map the Peripherals to pins, using the cross-bar. The info is all n the data sheets / reference manuals.

Attached is a minimal ASM pgm that blinks pins on a SiLabs part, so you can see those steps. This uses the 3 LEDs and 1 PB on common eval boards, to give 2 blink speeds.

As Erik says, there is a configurator that allows forms-based code , and there are many examples included you can cut/paste from.

Maurice,

We are now talking about two different issues. Your previous response sent on Friday stated this - 

The task the CP2615 has to do is simpel. It should set the PDN line from High to Low. Then programm 7 adresses with one Bite in the AK4137 and set the PDN line from Low to High. Thats all.     Question do you have better documentation or examples for programming of GPIO pins from the CP2615 

My response was specifically to this question. Now, in your latest response, you mentioned - 

Do you have a other tool to programm the CP2615. 

and

After saving the new content and 3 times failure programming the device CP2615 It says after programming " verified"  But after readout  the CP2615 it has his original I2C settings. Nothing happened.

This is a different problem than what we started off with. I hope that is clear. Now, my question is - 

Can you program a CP2615 EK with your settings? If you have not tried this so far, I recommend giving this a shot and then getting back to me. 

You need a HID to I2C bridge like the CP2112 to program the CP2615 directly from Xpress Configurator. 

Per your schematic, you don't have a USB to I2C interface in your device. I was under the impression that you were still using the eval kit to first test the configuration, but that does not seem to be the case per your latest response.

You do, however, raise a valid point about programming the CP2615 without a CP2112 to act as the programming interface. I will need to check with our dev teams to see if they have any inputs on how this can be done. Since this is a discussion with other teams, this will take some time depending on everyone's availability and will result in delays. I'd appreciate your patience while we look for a solution for your issue. 

Hi Mer,

The 'C' (0x43) and 'c' (0x63) tokens described in CP2615 datasheet Table 3.9 can be used to assert and deassert the 'GPIO.10/RESETOUTb' pin, presuming that it is configured as RESETOUTb.

Xpress Configurator provides a command interpreter that allows the user to generate I2C strings using human-readable statements (this is from AN1044):

This screenshot shows the typical usage of resetting the codec at the beginning of the 'Codec Initialize' section.  After RESETOUTb has been asserted and deasserted, the required codec register writes are performed.

This Xpress Configurator screenshot shows GPIO.10 configured as RESETOUTn (only GPIO.10 supports the RESETOUTn alternate function):

It is also possible for the host application to drive GPIO.10 and initiate I2C Write and Read transactions, but I'd recommend doing this only if the configuration mechanism described above is not suitable for some reason.  If the you want to use host-initiated GPIO and I2C, the details can be found in AN1139 (CP2615 I/O Protocol).