Неделю назад обновил контроллер до последней прошивки 2310.
Сегодня контроллер перестал работать.
В дебаг консоли куча ошибок
[ 223.578243] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1534: inode #2587: comm cron: reading directory lblock 0
[ 223.626837] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1534: inode #2: comm (bash): reading directory lblock 0
[ 223.641720] EXT4-fs warning (device mmcblk0p2): dx_probe:767: inode #14505: lblock 0: comm cron: error -5 reading directory block
[ 223.677906] EXT4-fs warning (device mmcblk0p2): dx_probe:767: inode #14505: lblock 0: comm cron: error -5 reading directory block
[ 224.897901] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1534: inode #3571: comm (-manager): reading directory lblock 0
[ 224.940988] EXT4-fs warning (device mmcblk0p2): dx_probe:767: inode #26596: lblock 0: comm (-manager): error -5 reading directory block
[ 226.890594] EXT4-fs error (device mmcblk0p2): __ext4_find_entry:1534: inode #2: comm (bash): reading directory lblock 0
Попытался сбросить до заводских настроек прошивкой через USB. Также куча ошибок чтения/записи.
Will use wb6_update_FACTORYRESET.fit from USB Flash Drive
##############################################################################
FACTORY RESET REQUESTED
This WILL destroy ALL YOUR DATA: configuration, scripts,
files in home directory!
If you are ABSOLUTELY SURE that you want to reset Wiren Board
to factory condition, hold the FW button for 4 seconds.
If you will not do it in 10 seconds, the controller will reboot
without firmware update.
If you want to perform a regular firmware update, rename
FIT file to "wbX_update.fit" without "factory-reset" suffix.
##############################################################################
ooooo....
Factory reset is confirmed!
===============================================================================
Wed Jan 10 10:28:42 UTC 2024: started update from /disk/wb6_update_FACTORYRESET.fit
===============================================================================
Description: WirenBoard firmware update
Compatible device: contactless,imx6ul-wirenboard61
Firmware version: 202312270833
Firmware compatible: +single-rootfs +force-repartition
Release name: wb-2310
Release suite: stable
Release target: wb6/bullseye
Release repo prefix:
Time of creation: Wed Dec 27 08:35:51 UTC 2023
===============================================================================
>>> Checking SHA1 hash of install
PROGRESS: 0%
>>> SHA1 hash of install ok
>>> Wiping data partition (factory reset)
[ 22.195526] EXT4-fs (mmcblk0p6): recovery complete
[ 22.251433] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)
32+0 records in
32+0 records out
16384 bytes (16 kB, 16 KiB) copied, 0.00927888 s, 1.8 MB/s
>>> Firmware seems to be compatible with this controller
>>> Extracting install script
>>> Running install script
>>> Console logging enabled; tempfile /tmp/tmp.GEus2C, final file /disk/wb-console.log will be written on exit
[ 33.767627] vref-3v3: disabling
>>> Checking SHA1 hash of rootfs
PROGRESS: 100%
>>> SHA1 hash of rootfs ok
>>> rootfs is valid, installing firmware update
>>> Partition table seems to be changed already, continue
>>> rootfs enlarged!
>>> Configuring environment for repartitioned eMMC
>>> Will install to /dev/mmcblk0p2
[ 73.754938] EXT4-fs (mmcblk0p2): recovery complete
[ 73.760904] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
>>> Cleaning up /dev/mmcblk0p2
>>> Cleaning up using rsync
>>> Mounting /dev/mmcblk0p2 at /tmp/tmp.uNHXQc
[ 88.355632] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
>>> Extracting files to new rootfs
/tmp/tmp.uNHXQc /
PROGRESS: 55%[ 145.247633] sdhci-esdhc-imx 2194000.mmc: Card stuck in wrong state! card_busy_detect status: 0xe00
[ 145.257243] mmc0: cache flush error -110
[ 146.560612] mmc0: tried to HW reset card, got error -110
[ 146.565987] mmcblk0: recovery failed!
[ 146.570097] blk_update_request: I/O error, dev mmcblk0, sector 838928 op 0x1:(WRITE) flags 0x0 phys_seg 32 prio class 0
[ 146.581131] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8767 starting block 104868)
[ 146.592454] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8768 starting block 104869)
[ 146.603779] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8769 starting block 104870)
[ 146.615062] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8770 starting block 104879)
[ 146.626342] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8771 starting block 104880)
[ 146.637621] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8772 starting block 104881)
[ 146.648955] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8773 starting block 104882)
[ 146.660233] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8774 starting block 104884)
[ 146.671506] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8775 starting block 104885)
[ 146.682776] EXT4-fs warning (device mmcblk0p2): ext4_end_bio:345: I/O error 10 writing to inode 8780 starting block 104886)
[ 146.698597] blk_update_request: I/O error, dev mmcblk0, sector 839440 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0
Логи:
Загрузка: boot.txt (79,1 КБ)
Попытка перепрошивки: reset.txt (63,7 КБ)
Загрузка после перепрошивки: boot2.txt (2,0 КБ)
Попытка перепрошивки #2: reset2.txt (23,2 КБ)
Нашел похожую проблему: Не стартует контроллер
Что можно сделать?