2022-06-14 06:58 AM
2022-06-14 09:46 AM
And ST doesn't provide BSP for components they don't use.
You'll likely have to port whatever materials TDK can supply, presumably interfacing with I2C, and merge in some I2C wedge/shim type implementation from the ST side examples for I2C Master devices.
Register level I2C devices (8 or 16-bit), should be able to use relatively high-level HAL I2C functions.
2022-06-14 09:46 AM
And ST doesn't provide BSP for components they don't use.
You'll likely have to port whatever materials TDK can supply, presumably interfacing with I2C, and merge in some I2C wedge/shim type implementation from the ST side examples for I2C Master devices.
Register level I2C devices (8 or 16-bit), should be able to use relatively high-level HAL I2C functions.
2022-06-15 07:45 AM
Thank you for your fast response
2022-11-17 01:29 AM
Hi @TBert.2, did you manage to get communication with the CH101 sensor? We use a CH201 sensor with functions taken over from the chirp sources, but I see my I2C gets stuck (infinite clock stretching) when accessing the sensor in programming mode. Since the chirp example is really low level in the I2C interface I wonder if you succeeded using the STM HAL functions for I2C?
2022-11-18 05:22 AM
Hello,
Unfortunately I did a quick and dirty workaround to get the prototype running (reading the serial output of the evalution board, using raspberry pi). We did not further investigate on this topic since we won't use the CH101 sensor for our product.