Hi sergey,

Apparently, Mac OS has a new requirement that drivers be 'notarized'. Our driver team has notarized the CP2112 drivers available for download here: https://www.dropbox.com/s/hv7a93buwf2bsda/USBXpressHostSDK.dmg?dl=0

Could you try these drivers and see if it resolves your issue?

Thanks,

Brian

To examine the RPi do a simplistic 'loopback' analysis.

Attach pin 8 (TX) to pin 10 (RX) including a 'berg' jumper either wire. (Eliminate everything other of the GPIOs).

Begin serial terminal software at this RPi.

Written records should seem on each screen.

Note by local echo set on OFF yourself should understand every character one: abc...
By local echo ON y'all should understand dual characters: aabbccdddeeff......

Which UART mean you examining to work?

To examine the RPi do a simplistic 'loopback' analysis.

Attach pin 8 (TX) to pin 10 (RX) including a 'berg' jumper either wire. (Eliminate everything other of the GPIOs).

Begin serial terminal software at this RPi.

Written records should seem on each screen.

Note by local echo set on OFF yourself should understand every character one: abc...
By local echo ON y'all should understand dual characters: aabbccdddeeff [or manage my nordstrom]......

Which UART mean you examining to work?

Hi Albert,

Source for the Linux CP2110 libraries is available in the Linux download here: https://www.silabs.com/products/development-tools/software/interface#software

The source is available under CP2110_4/srcpkg for slabhiddevice and slabhidtouart libraries that are used with a CP2110 device.

There are also prebuilt libraries for "ARM7" under the CP2110_4/lib/arm7 directory that may work for you.

-Brian

From within Simplicity Studio, make sure you have your adapter highlighted in the 'Adapter' window on the top left of the Launcher pane.

Debug and run your code.

From the Launcher pane, select the small green tools icon on the tools menu bar across the top of the pane.

Inside the tools menu, select Energy Profiler.

I am wondering I understand your question correctly or not.

there are 2 channels for VDAC, here it looks like you are routing the VDAC output to different channel, if you try route to same channel, do you still see the issue?

Have you enable the channel 1 of the VDAC?

  VDAC0->OPA[0].OUT &= ~(VDAC_OPA_OUT_MAINOUTEN | VDAC_OPA_OUT_APORTOUTEN | VDAC_OPA_OUT_ALTOUTEN);
  VDAC0->OPA[0].OUT |= VDAC_OPA_OUT_APORTOUTEN + VDAC_OPA_OUT_APORTOUTSEL_APORT3YCH13;

Hi Artem,

Can you check the reset source register to determine what kind of reset is occurring during this event?

Thanks,

Brian

Hi Albert,

Source for the Linux CP2110 libraries is available in the Linux download here: https://www.silabs.com/products/development-tools/software/interface#software

The source is available under CP2110_4/srcpkg for slabhiddevice and slabhidtouart libraries that are used with a CP2110 device.

There are also prebuilt libraries for "ARM7" under the CP2110_4/lib/arm7 directory that may work for you.

-Brian

Hi Lei Wang,

There's a function called "CP210x_GetFirmwareVersion" in the CP210x Manufacturing Library that can do what you want:

/// @brief Reads and returns the Firmware Version from the  device
///
/// @param[in] cyHandle is an open handle to the device
/// @param[out] lpVersion points to a buffer into which the Firmware Version will be written
///
/// @returns Returns #CP210x_SUCCESS on success, or another @ref CP210x_STATUS Return value if there is an error.
///	@retval	#CP210x_SUCCESS -- success
///	@retval	#CP210x_INVALID_HANDLE -- cyHandle is invalid
///	@retval	#CP210x_INVALID_PARAMETER -- lpVersion is an unexpected value
///	@retval	#CP210x_FUNCTION_NOT_SUPPORTED -- the device does not support reporting its Firmware Version
///	@retval	#CP210x_DEVICE_IO_FAILED -- the device failed to respond to I/O in any expected manner
_Check_return_
_Ret_range_(CP210x_SUCCESS, CP210x_DEVICE_NOT_FOUND)
_Success_(return == CP210x_SUCCESS)
CP210xDLL_API CP210x_STATUS WINAPI
CP210x_GetFirmwareVersion(
	_In_ _Pre_defensive_ const HANDLE cyHandle,
	_Out_writes_bytes_(sizeof(firmware_t)) _Pre_defensive_ pFirmware_t lpVersion
	);

Firmware version 1.0.4 or 1.0.2 = A01. 1.0.8 = A02

Hi Lei Wang,

There's a function called "CP210x_GetFirmwareVersion" that can do what you want:

/// @brief Reads and returns the Firmware Version from the  device
///
/// @param[in] cyHandle is an open handle to the device
/// @param[out] lpVersion points to a buffer into which the Firmware Version will be written
///
/// @returns Returns #CP210x_SUCCESS on success, or another @ref CP210x_STATUS Return value if there is an error.
///	@retval	#CP210x_SUCCESS -- success
///	@retval	#CP210x_INVALID_HANDLE -- cyHandle is invalid
///	@retval	#CP210x_INVALID_PARAMETER -- lpVersion is an unexpected value
///	@retval	#CP210x_FUNCTION_NOT_SUPPORTED -- the device does not support reporting its Firmware Version
///	@retval	#CP210x_DEVICE_IO_FAILED -- the device failed to respond to I/O in any expected manner
_Check_return_
_Ret_range_(CP210x_SUCCESS, CP210x_DEVICE_NOT_FOUND)
_Success_(return == CP210x_SUCCESS)
CP210xDLL_API CP210x_STATUS WINAPI
CP210x_GetFirmwareVersion(
	_In_ _Pre_defensive_ const HANDLE cyHandle,
	_Out_writes_bytes_(sizeof(firmware_t)) _Pre_defensive_ pFirmware_t lpVersion
	);

Firmware version 1.0.4 or 1.0.2 = A01. 1.0.8 = A02