Profile

BrianL

Profile Data

Screen Name: BrianL

Screen Name*

Title

First Name

Address:

Last Name

URL (i.e. Company, Github, LinkedIn)

Email

LinkedIn account

Company

Phone number

Country

Bio

Indicates required field*

My Activities

Member	Action	Date
BrianL	Replied to Windows 10 Pro version 1803 https://www.silabs.com/community/interface/forum.topic.html/cp210x_driver_v101-91Gl Thanks for pointing out this issue. We currently have a work-around, but this requires disabling driver signing when installing the driver. An alternative is rolling back Windows to a previous build. Our current schedule to have a public fixed driver is mid-June. Show more	22 days ago
BrianL	Updated CP210x Driver v10.1.1 issue with Windows 10, build 1803 on Forum Hi All, We've recently become aware of an issue with a new update to Windows 10 and our CP210x VCP "Universal" Driver for Windows 10, driver version v10.1.1. When attempting to install the driver, an error is given by Windows that states "A service installation section in this INF is invalid." This occurs because Windows has changed drive INF requirements slightly, and our current driver's INF file does not meet these requirements. We currently are working to fix this issue, although due to testing and recertification requirements, we do not expect the fixed driver to be available until mid-June. A work-around exists currently, but it involves manually editing the .INF file for the driver. This causes another issue - the driver is no longer signed in this case, so the driver must be forced to install, and Windows will show a warning that the driver is unsigned. Firstly, the work-around is as follows: Download the Windows 10 Universal driver from here: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers Edit the .inf file with this driver, performing the following modifications: On or around line 118, change/edit from this: ServiceBinary = %13%\silabser.sys to this: ServiceBinary = %12%\silabser.sys And on or around line 160, change/edit from this: Silabser_CopyFiles_FileListSection = 13 ; Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository ) (was 12 Drivers directory (%SystemRoot%\system32\drivers)) to this: Silabser_CopyFiles_FileListSection = 12 ; Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository ) (was 12 Drivers directory (%SystemRoot%\system32\drivers)) I.e. replace every 13 in the file with 12. Once these changes are made, attempt to re-install the driver. A warning will be shown that the driver is unsigned, but you can ignore this for now. If you do not receive a warning issue, or if Windows refuses to install the unsigned driver (you may get an error about the hash being invalid), you can disable driver signing enforcement by following these instructions: https://www.maketecheasier.com/install-unsigned-drivers-windows10/ Alternatively, rolling back to a previous build of Windows also resolves the issue. Show more	22 days ago
BrianL	Posted CP210x Driver v10.1.1 issue with Windows 10, build 1803 on Forum Hi All, We've recently become aware of an issue with a new update to Windows 10 and our CP210x VCP "Universal" Driver for Windows 10, driver version v10.1.1. When attempting to install the driver, an error is given by Windows that states "A service installation section in this INF is invalid." This occurs because Windows has changed drive INF requirements slightly, and our current driver's INF file does not meet these requirements. We currently are working to fix this issue, although due to testing and recertification requirements, we do not expect the fixed driver to be available until mid-June. A work-around exists currently, but it involves manually editing the .INF file for the driver. This causes another issue - the driver is no longer signed in this case, so the driver must be forced to install, and Windows will show a warning that the driver is unsigned. Firstly, the work-around is as follows: Download the Windows 10 Universal driver from here: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers Edit the .inf file with this driver, performing the following modifications: On or around line 118, change/edit from this: ServiceBinary = %13%\silabser.sys to this: ServiceBinary = %12%\silabser.sys And on or around line 160, change/edit from this: Silabser_CopyFiles_FileListSection = 13 ; Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository ) (was 12 Drivers directory (%SystemRoot%\system32\drivers)) to this: Silabser_CopyFiles_FileListSection = 12 ; Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository ) (was 12 Drivers directory (%SystemRoot%\system32\drivers)) I.e. replace every 13 in the file with 12. Once these changes are made, attempt to re-install the driver. A warning will be shown that the driver is unsigned, but you can ignore this for now. If you do not receive a warning issue, or if Windows refuses to install the unsigned driver, you can disable driver signing enforcement by following these instructions: https://www.maketecheasier.com/install-unsigned-drivers-windows10/ Show more	22 days ago
BrianL	Updated CP2114 B02 I2C Command Array Generator on Knowledge Base Attached to this article is a python 3 script to generate the I2C command arrays for a CP2114-B02 device. This script interprets the following commands to construct the command byte-array. write(slaveAddress, data) - writes an array of data to the i2c slave with the address slaveAddress, without issuing an I2C stop command at the end of the transaction write_stop(slaveAddress, data) - writes an array of data to the i2c slave with the address slaveAddress, issuing an I2C stop command at the end of the transaction stop() - issues an I2C stop command delay_ms(delay) - delays the next command by delay milliseconds delay_us(delay) - delays the next command by delay microseconds reenumerate() - immediately reenumerates the CP2112 device setGPIO(state, gpioNum) - sets the gpio gpioNum to state, where 1 = high, 0 = low In addition to these commands, the command list must begin with one of the following sequence identifiers: RESET_SEQUENCE - identifies this sequence of commands to be issued after reset SUSPEND_SEQUENCE - identifies this sequence of commands to be issued before entering suspend mode ACTIVE_SEQUENCE - identifies this sequence of commands to be issued when exiting suspend mode into active mode Note - only one sequence can be generated at a time with this script. If all three sequences are needed, they will need to be generated individually, then appended together into one large byte array. Here is an example image of the script running: The left panel is the 'input' field, where commands are typed. The right panel is the 'output' field, where the byte array is generated. The byte array is refreshed any time return/enter are pressed in the input field. The bottom panel is for any errors that may arise. As an example, this is the input text required to generate a configuration for the CS42L55 codec: RESET_SEQUENCE setGPIO(0, 4) delay_us(250) delay_us(250) delay_us(250) delay_us(250) setGPIO(1, 4) delay_us(1) write_stop(0x94, [0x00, 0x99]) write_stop(0x94, [0x2E, 0x30]) write_stop(0x94, [0xB2, 0x07, 0xFD, 0xF8, 0xDC, 0xF8, 0x6C]) write_stop(0x94, [0x3A, 0xF8]) write_stop(0x94, [0xBC, 0xD3, 0x23, 0x81, 0x46]) write_stop(0x94, [0x00, 0x00]) write_stop(0x94, [0x03, 0x0A]) write_stop(0x94, [0x84, 0x02, 0x09]) write_stop(0x94, [0x06, 0x20]) write_stop(0x94, [0x2A, 0x00]) write_stop(0x94, [0x9A, 0xC4, 0xC4, 0xC4, 0xC4]) write_stop(0x94, [0x02, 0x08]) delay_ms(75) write_stop(0x94, [0x9A, 0x7A, 0x00, 0x00]) This generates the following binary array: F9 6E 00 47 04 64 FA 64 FA 64 FA 64 FA 47 84 64 01 57 03 94 00 99 50 57 03 94 2E 30 50 57 08 94 B2 07 FD F8 DC F8 6C 50 57 03 94 3A F8 50 57 06 94 BC D3 23 81 46 50 57 03 94 00 00 50 57 03 94 03 0A 50 57 04 94 84 02 09 50 57 03 94 06 20 50 57 03 94 2A 00 50 57 06 94 9A C4 C4 C4 C4 50 57 03 94 02 08 50 44 4B 57 05 94 9A 7A 00 00 50 00 Syntax errors will be displayed in the bottom panel: Note, the first version of this script, attached to the article, had bugs that created invalid outputs. The fixed script is attached as cp2114_b02_commandGenerator_FIXED.zip. In this version the escape key is used to evaluate the input and generate the output. Show more	51 days ago
BrianL	Posted USB to UART Bridge VCP driver, installation on Mac OSX High Sierra 10.13 on Knowledge Base As macOS High Sierra 10.13 introduces a new feature that requires user approval before loading new third-party kernel extensions, referring to Apple Technical Note TN2459: https://developer.apple.com/library/content/technotes/tn2459/_index.html When you download the Mac OSX CP210x VCP driver v5 from the Silicon Labs website, approve the CP210x driver by clicking "Allow" in the Security & Privacy System Preferences panel as TN2459 mentioned to complete the installation of the driver. Show more	55 days ago
BrianL	Posted Flash bank organization on devices that support Read-While-Write on Knowledge Base Generally, devices with 512 KB of flash or more have the ability to read from one area of flash while writing to another. This feature is called Read-While-Write, and will be described in the MSC chapter of the device's datasheet, if the device supports it. On these devices, flash is organized into two or more banks. The Read-While-Write feature takes advantage of this. Normally, reading from flash is stalled while a flash write or erase is occurring. However, with Read-While-Write, one flash block can be in the process of performing a write or page erase while reads, such as code fetches, are performed in another block. The organization of flash is such that the first half of flash is in one bank (for example, addresses 0x00000000 - 0x000800000 on devices with 1024 KB of flash), while the upper half of flash, and the 'information' pages (Lock bits page, Device Info page, User Data page) occupy the other bank. This means that, if you are erasing a page in the upper half of the flash, you can continue reading flash from the lower half, but cannot read from the information pages until the erase completes. One exception to this is Series 0 Giant Gecko. On these devices, the information pages occupy a third block of flash, allowing reading from the information pages while erasing a page in the upper or lower half of flash. Show more	55 days ago
BrianL	Updated CP2615 with a codec without I2C on Knowledge Base It is possible to use the CP2615 USB-to-Audio bridge with a codec that does not have an I2C interface. However, an incorrect configuration of the CP2615 can prevent correct operation. Primarily of concern is that the CP2615, if it is programmed to send I2C data to the codec, will hang if no I2C device is present. This occurs because the CP2615 will retry any failed I2C transactions forever. To prevent this from occurring, clear all I2C Strings from the configuration of the CP2615. Also make sure to disable [Enable Playback Mute via Register] to prevent the CP2615 from attempting to use I2C commands to mute the codec. Show more	55 days ago
BrianL	Posted CP2615 with a codec without I2C [Review] on Knowledge Base It is possible to use the CP2615 USB-to-Audio bridge with a codec that does not have an I2C interface. However, an incorrect configuration of the CP2615 can prevent correct operation. Primarily of concern is that the CP2615, if it is programmed to send I2C data to the codec, will hang if no I2C device is present. This occurs because the CP2615 will retry any failed I2C transactions forever. To prevent this from occurring, clear all I2C Strings from the configuration of the CP2615. Also make sure to disable [Enable Playback Mute via Register] to prevent the CP2615 from attempting to use I2C commands to mute the codec. Show more	55 days ago
BrianL	Updated CP2114 B02 I2C Command Array Generator on Knowledge Base Attached to this article is a python 3 script to generate the I2C command arrays for a CP2114-B02 device. This script interprets the following commands to construct the command byte-array. write(slaveAddress, data) - writes an array of data to the i2c slave with the address slaveAddress, without issuing an I2C stop command at the end of the transaction write_stop(slaveAddress, data) - writes an array of data to the i2c slave with the address slaveAddress, issuing an I2C stop command at the end of the transaction stop() - issues an I2C stop command delay_ms(delay) - delays the next command by delay milliseconds delay_us(delay) - delays the next command by delay microseconds reenumerate() - immediately reenumerates the CP2112 device setGPIO(state, gpioNum) - sets the gpio gpioNum to state, where 1 = high, 0 = low In addition to these commands, the command list must begin with one of the following sequence identifiers: RESET_SEQUENCE - identifies this sequence of commands to be issued after reset SUSPEND_SEQUENCE - identifies this sequence of commands to be issued before entering suspend mode ACTIVE_SEQUENCE - identifies this sequence of commands to be issued when exiting suspend mode into active mode Note - only one sequence can be generated at a time with this script. If all three sequences are needed, they will need to be generated individually, then appended together into one large byte array. Here is an example image of the script running: The left panel is the 'input' field, where commands are typed. The right panel is the 'output' field, where the byte array is generated. The byte array is refreshed any time return/enter are pressed in the input field. The bottom panel is for any errors that may arise. As an example, this is the input text required to generate a configuration for the CS42L55 codec: RESET_SEQUENCE setGPIO(0, 4) delay_us(250) delay_us(250) delay_us(250) delay_us(250) setGPIO(1, 4) delay_us(1) write_stop(0x94, [0x00, 0x99]) write_stop(0x94, [0x2E, 0x30]) write_stop(0x94, [0xB2, 0x07, 0xFD, 0xF8, 0xDC, 0xF8, 0x6C]) write_stop(0x94, [0x3A, 0xF8]) write_stop(0x94, [0xBC, 0xD3, 0x23, 0x81, 0x46]) write_stop(0x94, [0x00, 0x00]) write_stop(0x94, [0x03, 0x0A]) write_stop(0x94, [0x84, 0x02, 0x09]) write_stop(0x94, [0x06, 0x20]) write_stop(0x94, [0x2A, 0x00]) write_stop(0x94, [0x9A, 0xC4, 0xC4, 0xC4, 0xC4]) write_stop(0x94, [0x02, 0x08]) delay_ms(75) write_stop(0x94, [0x9A, 0x7A, 0x00, 0x00]) This generates the following binary array: F9 6E 00 47 04 64 FA 64 FA 64 FA 64 FA 47 84 64 01 57 03 94 00 99 50 57 03 94 2E 30 50 57 08 94 B2 07 FD F8 DC F8 6C 50 57 03 94 3A F8 50 57 06 94 BC D3 23 81 46 50 57 03 94 00 00 50 57 03 94 03 0A 50 57 04 94 84 02 09 50 57 03 94 06 20 50 57 03 94 2A 00 50 57 06 94 9A C4 C4 C4 C4 50 57 03 94 02 08 50 44 4B 57 05 94 9A 7A 00 00 50 00 Syntax errors will be displayed in the bottom panel: Show more	57 days ago
BrianL	Updated CP2114 B02 I2C Command Array Generator on Knowledge Base Attached to this article is a python 3 script to generate the I2C command arrays for a CP2114-B02 device. This script interprets the following commands to construct the command byte-array. write(slaveAddress, data) - writes an array of data to the i2c slave with the address slaveAddress, without issuing an I2C stop command at the end of the transaction write_stop(slaveAddress, data) - writes an array of data to the i2c slave with the address slaveAddress, issuing an I2C stop command at the end of the transaction stop() - issues an I2C stop command delay_ms(delay) - delays the next command by delay milliseconds delay_us(delay) - delays the next command by delay microseconds reenumerate() - immediately reenumerates the CP2112 device setGPIO(state, gpioNum) - sets the gpio gpioNum to state, where 1 = high, 0 = low In addition to these commands, the command list must begin with one of the following sequence identifiers: RESET_SEQUENCE - identifies this sequence of commands to be issued after reset SUSPEND_SEQUENCE - identifies this sequence of commands to be issued before entering suspend mode ACTIVE_SEQUENCE - identifies this sequence of commands to be issued when exiting suspend mode into active mode Note - only one sequence can be generated at a time with this script. If all three sequences are needed, they will need to be generated individually, then appended together into one large byte array. Here is an example image of the script running: The left panel is the 'input' field, where commands are typed. The right panel is the 'output' field, where the byte array is generated. The byte array is refreshed any time return/enter are pressed in the input field. The bottom panel is for any errors that may arise. As an example, this is the input text required to generate a configuration for the CS42L55 codec: RESET_SEQUENCE setGPIO(0, 4) delay_us(250) delay_us(250) delay_us(250) delay_us(250) setGPIO(1, 4) delay_us(1) write_stop(0x94, [0x00, 0x99]) write_stop(0x94, [0x2E, 0x30]) write_stop(0x94, [0xB2, 0x07, 0xFD, 0xF8, 0xDC, 0xF8, 0x6C]) write_stop(0x94, [0x3A, 0xF8]) write_stop(0x94, [0xBC, 0xD3, 0x23, 0x81, 0x46]) write_stop(0x94, [0x00, 0x00]) write_stop(0x94, [0x03, 0x0A]) write_stop(0x94, [0x84, 0x02, 0x09]) write_stop(0x94, [0x06, 0x20]) write_stop(0x94, [0x2A, 0x00]) write_stop(0x94, [0x9A, 0xC4, 0xC4, 0xC4, 0xC4]) write_stop(0x94, [0x02, 0x08]) delay_ms(75) write_stop(0x94, [0x9A, 0x7A, 0x00, 0x00]) This generates the following binary array: F9 6E 00 47 04 64 FA 64 FA 64 FA 64 FA 47 84 64 01 57 03 94 00 99 50 57 03 94 2E 30 50 57 08 94 B2 07 FD F8 DC F8 6C 50 57 03 94 3A F8 50 57 06 94 BC D3 23 81 46 50 57 03 94 00 00 50 57 03 94 03 0A 50 57 04 94 84 02 09 50 57 03 94 06 20 50 57 03 94 2A 00 50 57 06 94 9A C4 C4 C4 C4 50 57 03 94 02 08 50 44 4B 57 05 94 9A 7A 00 00 50 00 Syntax errors will be displayed in the bottom panel: Show more	57 days ago

Level 6

Level 5

Following 0

Followers 3