Is the Pico i2C implementation less robust than a typical Arduino boards?

This page summarizes the projects mentioned and recommended in the original post on /r/raspberrypipico

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • micropython-tinyrtc-i2c

    MicroPython driver for TinyRTC I2C modules with DS1307 RTC and AT24C32N EEPROM

  • I just recently started messing around with the RP Pico and Pico W and was considering using it for a project that would be running 24/7 and needing a battery backed up RTC to ensure time after a reset/power cycle. However, in trying to get a common tiny RTC (DS1307), I have failed to get it to work with the library I found (I'm using micropython), here link. The RTC appear to be the same as that shown in the github link. Also, interestingly when I run i2c.scan, I get results for both devices (RTC and EEPROM) as follows: i2c devices found: 2 Decimal address: 80 | Hexa address: 0x50 Decimal address: 104 | Hexa address: 0x68

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts