Donk

Fausto, Thanks. Nothing worked. Found a spare MCC152 and everything worked. The board in question is in the garbage. thanks again, donk

Good Morning, As requested $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" $ cat /proc/cpuinfo | grep Model Model : Raspberry Pi 3 Model B Plus Rev 1.3

I'm leaving for the weekend, but SPI and I2C are enabled. Yes both were installed previously, and worked. Thanks, donk

pi@afspi02:~$ sudo daqhats_read_eeproms Reading... Found EEPROM at address 0 Found EEPROM at address 1 Done pi@afspi02:~$ uname -a Linux afspi02 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux pi@afspi02:~$ cat /etc/debian_version 11.8 The open button on the MCC 152 window does nothing. It does work for the MCC128. When running my application I get the error code "Could not communicate with the device."

I have an MCC152, that previously worked. I ran an update yesterday. SPI is still on, I2C is off, Today I get the error "Can't Open MCC152". The board is detected, and the eeprom can be read. Is it toast, or is there something else I should check?