CDQ

Hello @Fausto, I placed the board in another Raspberry Pi module and the board worked just fine. I placed another MCC172 board in the original Raspberry Pi module and saw the same issues. The problem was with the Raspberry Pi, not the MCC 172. Thank you for your patience. I have 1 (possibly 2, the second is not yet verified) MCC 172 board(s) that do have issues. Is there a way to request an RMA, or do I first need to post diagnostic details here in the forum?

OS is Raspbian Bullseye 11.6 (64 bit) I realize Digilent is discouraging the use of 64 bit OS, but I have several of these boards running smoothly in that setup so I doubt the OS is the problem. There are no 3rd party hats installed. SPI and I2C are enabled. sudo raspi-config nonint get_spi ... gives 0 (meaning SPI is enabled) sudo raspi-config nonint get_i2c ... gives 0 (meaning I2C is enabled) This device is running headless; is there a command line utility that can LIST DEVICES?

I just installed a new MCC 172 into a new Raspberry Pi 4; the example software is giving the message "Addr 0: Error: No HAT devices found' sudo daqhats_read_eeproms ... gives the message "Reading... Done" daqhats_version ... gives the message "daqhats version 1.4.0.6 is installed" daqhats_list_boards ... gives the message "0 boards found" Are there any diagnostics I can run to be sure the MCC 172 board is working properly? What am I missing? Thanks!