vladvanderwolf
03/23/2023, 7:25 PMteslamax
03/26/2023, 9:38 AMvladvanderwolf
03/28/2023, 6:42 PMteslamax
03/28/2023, 6:46 PMWARNING:The register which controls the power to each board is backed by an EEPROM. Don't set all bits in there to 0, otherwise you won't be able to boot and correct it. A fix is to set register 0xF4 to 1 which would send the writes to the shadow SRAM, instead of the EEPROM. A fix for this is to connect an external raspberry pi to the I2C External pins and reset the registers
vladvanderwolf
03/29/2023, 2:11 PMteslamax
03/30/2023, 4:15 AMsudo i2cdetect -y 1
on your Raspberry Pi 400, what does it output?sudo i2cdetect -y 0
?dtoverlay
settings inside /boot/config.txt
on your Raspberry Pi 400themaudalorian
04/03/2023, 11:43 PMvladvanderwolf
04/08/2023, 10:04 PMthemaudalorian
04/08/2023, 11:21 PMvladvanderwolf
04/09/2023, 3:02 PMteslamax
04/10/2023, 9:13 PMI2C
myselfvladvanderwolf
04/11/2023, 7:35 AMteslamax
04/11/2023, 9:12 PMthemaudalorian
04/14/2023, 8:24 PMvladvanderwolf
04/14/2023, 8:59 PMthemaudalorian
04/14/2023, 9:14 PMvladvanderwolf
04/14/2023, 9:16 PMthemaudalorian
04/14/2023, 9:16 PMvladvanderwolf
04/14/2023, 9:17 PMthemaudalorian
04/14/2023, 9:17 PMvladvanderwolf
04/14/2023, 9:53 PMthemaudalorian
04/14/2023, 10:02 PMteslamax
04/15/2023, 12:10 AMthemaudalorian
04/15/2023, 12:38 AMteslamax
04/15/2023, 12:42 AMthemaudalorian
04/15/2023, 12:45 AMteslamax
04/15/2023, 12:46 AMthemaudalorian
04/15/2023, 12:48 AMteslamax
04/15/2023, 12:52 AMthemaudalorian
04/15/2023, 2:32 AMteslamax
04/21/2023, 3:40 AM_dhanos_
04/21/2023, 3:41 AMteslamax
04/21/2023, 3:41 AM_dhanos_
04/21/2023, 3:45 AMteslamax
04/21/2023, 3:46 AM| 1 | 2 | 3 | 4 |
| GND | VCC | SCL | SDA |
1. GND (black)
2. VCC (red)
3. SDA (blue)
4. SCL (yellow)
dietpi@T1-BMC:~$ sudo i2cset -y -m 0x04 1 0x57 0xf2 0x00
dietpi@T1-BMC:~$ sudo i2cset -y -m 0x04 1 0x57 0xf2 0xff
themaudalorian
04/26/2023, 4:12 AMteslamax
04/26/2023, 4:14 AMdietpi@T1-BMC:~$ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- 57 -- -- 5a -- 5c -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU
70: -- -- -- -- -- -- -- --
57
is the Turing Pi 1's I2C expander; 5c
is the Turing Pi 1's RTL8370 Ethernet switch5a
is the microcontroller on my ATX Watchdog HAT https://www.tindie.com/products/tomtibbetts/atx-watchdog-for-compute-module-4/6f
is the Turing Pi 1's RTC chip, unavailable because it's driver is loadedthemaudalorian
05/03/2023, 4:55 PMteslamax
05/03/2023, 11:10 PM_dhanos_
05/09/2023, 5:56 PMteslamax
05/09/2023, 6:11 PMadmin@raspberrypi:~ $ ls /dev/i2c
/dev/i2c-1 /dev/i2c-20 /dev/i2c-21
MuadDib007
06/06/2023, 5:34 PMsudo i2cset -m 0xfc -y 1 0x57 0xf2 0x00
and sudo i2cset -m 0x02 -y 1 0x57 0xf2 0x00
to also turn off the master, I can use my Rpi4 connected to i2c to confirm all the nodes are down: sudo i2cget -y 1 0x57 0xf2
return: 0x01
. After that I can use the Rpi4 to start everything again issueing the command sudo i2cset -m 0xfe -y 1 0x57 0xf2 0xff
after which all the nodes turn on. What I do find to be strange is that when you only connect SDA, SDL and Gnd, i2c does not work between TP1 and RPi4. After connecting 3.3v as well the i2c started working. Is that expected behavior?sudo i2cset -m 0xfc -y 1 0x57 0xf2 0x00
the system was in deadlock again. Unable to power up anything over i2c. although i2cget showed that the values changed, the modules did not power on. Now i removed the power cord from the AC Power brick to the TP1, left the RPi4 on i2c and waited for the power led of the Power Brick to die out. Then I removed the i2C cables and plugged the AC cable back into the power brick. NOW it really starts.... Damn what a p.i.t.a. system if you treat it wrongfully.teslamax
06/09/2023, 6:24 AMSDA
,SCL
,GND
, and 3.3v
all connected for I2C to work correctlyvladvanderwolf
06/13/2023, 7:48 PM