It isn't as clear-cut as that. Please see this GitHub issue. According to one of the CircuitPython lead developers the hardware does support clock stretching. The cause of the actual problem is being studied.
As a practical workround the one I described above is fine.
Pico and BNO055 IMU
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact:
Re: Pico and BNO055 IMU
Peter Hinch
Index to my micropython libraries.
Index to my micropython libraries.
Re: Pico and BNO055 IMU
Where did you get this assumption from?
- nothing is really written about it on the data sheet.
https://datasheets.raspberrypi.com/rp20 ... asheet.pdf
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact:
Re: Pico and BNO055 IMU
This was my guess as to the cause of the fault. It proved incorrect. Hard I2C can be fixed with this patch.
Peter Hinch
Index to my micropython libraries.
Index to my micropython libraries.
Re: Pico and BNO055 IMU
pythoncoder wrote: ↑Sun Jan 16, 2022 5:11 pmThis was my guess as to the cause of the fault. It proved incorrect. Hard I2C can be fixed with this patch.
Very well.
When I have a Pi again I will compile and test the patch.
Re: The verdict
The response is a little late but CircuitPython 7.1.0 added support for asynchronous coding. For further details, see Cooperative Multitasking in CircuitPython with asyncio.pythoncoder wrote: ↑Wed Jan 12, 2022 10:00 amAs for CircuitPython it is aimed at users with less technical knowledge. As such it loses the most interesting features of MicroPython such as interrupts and asynchronous coding, but it gains in "plug and play" ease of use.
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact: