So you used three boards and none of them works.
Perhaps the problem is the pico, the cables, breadboard?
pico:
- use up to date micropython.
- check other programs if they work.
- use other I2C pins than GPIO 0, 1
- you soldered the header yourself, check solder joints. Check the GPIO pins if they work. Measure voltage on GPIO when you drive them high, low.
- I2C scanning does not work. But does register access for this chip work ?
- Do other I2C devices work? Not one of your PCA9685, but another chip.
- exchange the pico by a different one, just for testing
cables:
- perhaps one, more of your cables are broken. When the LED on the board is bright, then at least GND, Vcc 3.3V are ok. Replace the other cables.
- connect SCL and SDA with the boards SCL, SDA.
breadboard:
- perhaps the breadboard is faulty. Does not happen very often, but doublecheck if contacts from pico header pins to wires are working.
Perhaps the problem is the pico, the cables, breadboard?
pico:
- use up to date micropython.
- check other programs if they work.
- use other I2C pins than GPIO 0, 1
- you soldered the header yourself, check solder joints. Check the GPIO pins if they work. Measure voltage on GPIO when you drive them high, low.
- I2C scanning does not work. But does register access for this chip work ?
- Do other I2C devices work? Not one of your PCA9685, but another chip.
- exchange the pico by a different one, just for testing
cables:
- perhaps one, more of your cables are broken. When the LED on the board is bright, then at least GND, Vcc 3.3V are ok. Replace the other cables.
- connect SCL and SDA with the boards SCL, SDA.
breadboard:
- perhaps the breadboard is faulty. Does not happen very often, but doublecheck if contacts from pico header pins to wires are working.
Statistics: Posted by ghp — Wed May 29, 2024 5:16 am