en:bpi-r4:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:bpi-r4:start [2024/04/21 12:48] – [thermal] frank | en:bpi-r4:start [2024/05/07 07:56] (current) – [Network] frank | ||
---|---|---|---|
Line 31: | Line 31: | ||
{{: | {{: | ||
+ | |||
+ | |||
+ | |||
===== thermal ===== | ===== thermal ===== | ||
+ | |||
+ | cat / | ||
Uses lvts driver | Uses lvts driver | ||
Line 80: | Line 85: | ||
NETSYS: V2 for mt7986 (bpi-r3) V3 for mt7988 (bpi-r4) | NETSYS: V2 for mt7986 (bpi-r3) V3 for mt7988 (bpi-r4) | ||
+ | |||
+ | Daniel tells me that lro should be enabled via userspace with | ||
+ | |||
+ | ethtool -N $ifname flow-type tcp4 dst-ip $lan_ip loc 0 | ||
==== Wifi ==== | ==== Wifi ==== | ||
Line 125: | Line 134: | ||
{{ : | {{ : | ||
+ | ===== eeprom ===== | ||
+ | |||
+ | BPI-R4 has an eeprom on i2c-mux channel 0 | ||
+ | |||
+ | [ 1.515672] at24 2-0057: 256 byte 24c02 EEPROM, writable, 1 bytes/write | ||
+ | |||
+ | write-mode (wp-gpio is linked to green led): | ||
+ | < | ||
+ | # echo 0 > / | ||
+ | root@bpi-r4-v11: | ||
+ | # echo " | ||
+ | root@bpi-r4-v11: | ||
+ | # hexdump -C / | ||
+ | 00000000 | ||
+ | 00000010 | ||
+ | * | ||
+ | 00000100 | ||
+ | root@bpi-r4-v11: | ||
+ | # echo 1 > / | ||
+ | root@bpi-r4-v11: | ||
+ | </ | ||
+ | |||
+ | ===== rtc ===== | ||
+ | |||
+ | Battery connection looks like charging circuit for ml2032. You should not connect non-rechargeable battery like cr2032. | ||
+ | |||
+ | https:// | ||
+ | |||
+ | Connector is JST with 1.25mm pitch | ||
+ | |||
+ | RTC time will survive software reboot | ||
+ | < | ||
+ | # dmesg | grep rtc | ||
+ | [ 1.479923] rtc-pcf8563 2-0051: low voltage detected, date/time is not reliable. | ||
+ | [ 1.487390] rtc-pcf8563 2-0051: registered as rtc0 | ||
+ | [ 1.493378] rtc-pcf8563 2-0051: low voltage detected, date/time is not reliable. | ||
+ | [ 1.500771] rtc-pcf8563 2-0051: hctosys: unable to read the hardware clock | ||
+ | root@bpi-r4-v11: | ||
+ | # date -s " | ||
+ | Sat Apr 27 07:55:00 UTC 2024 | ||
+ | root@bpi-r4-v11: | ||
+ | # hwclock -w | ||
+ | root@bpi-r4-v11: | ||
+ | # hwclock -r | ||
+ | 2024-04-27 07: | ||
+ | root@bpi-r4-v11: | ||
+ | # reboot | ||
+ | ... | ||
+ | root@bpi-r4-v11: | ||
+ | # dmesg | grep rtc | ||
+ | [ 1.480067] rtc-pcf8563 2-0051: registered as rtc0 | ||
+ | [ 1.486061] rtc-pcf8563 2-0051: setting system clock to 2024-04-27T07: | ||
+ | root@bpi-r4-v11: | ||
+ | # date | ||
+ | Sat Apr 27 08:00:46 UTC 2024 | ||
+ | root@bpi-r4-v11: | ||
+ | </ | ||
===== uboot/ATF ===== | ===== uboot/ATF ===== | ||
Line 130: | Line 196: | ||
currently use these: | currently use these: | ||
- | * uboot: https:// | + | * uboot: https:// |
* ATF: https:// | * ATF: https:// | ||
en/bpi-r4/start.1713696487.txt.gz · Last modified: 2024/04/21 12:48 by frank