Colibri iMX7 Dual 1GB V1.1Bの起動不良について

[alvaro.tx]

@kentaro

①
spi2.0 supply vdd not found, using dummy regulator
[ 5.551693] spi2.0 supply xceiver not found, using dummy regulator
⇒このメッセージを見るとSPIのVDDが見当たらないと読めますが、ハードに何か問題ありますでしょうか？

It could be a log message. Doesn’t need to be a HW issue.
Please compare that with a working Colibri iMX7 Dual 1GB V1.1B

@kentaro

[FAILED] Failed to start File System Check on Root Device.
See ‘systemctl status systemd-fsck-root.service’ for details.
⇒このメッセージではルートデバイスのファイルシステムチェックが起動しないと読めますが、①と関連がありますでしょうか？

I don’t think so. It is more likely related to 3.

@kentaro

Welcome to emergency mode! After Press Enter for maintenance
(or press Control-D to continue): [ 6.293404] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
⇒最終的にはエマージェンシーモードに移行して、停止しています。この5行前でも①と同じメッセージが出ています。
[ 5.529218] CAN device driver interface
[ 5.540248] spi2.0 supply vdd not found, using dummy regulator
[ 5.551693] spi2.0 supply xceiver not found, using dummy regulator
[ OK ] Found device /dev/ttymxc0.
[ OK ] Started Update UTMP about System Runlevel Changes.
Welcome to emergency mode! After Press Enter for maintenance
(or press Control-D to continue): [ 6.293404] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

システムが立ち上がらないので、こちらではこれ以上の調査が出来ません。
システム再書換で改善の可能性はありますでしょうか（やってみないと分からないでしょうか？）？
ハード故障の可能性があるのであれば、ご意見頂きたく。

Yes, it could be a HW issue, particularly with the eMMC: Linux is having issues loading the Root File System (like mentioned in ②). Another option is that the eMMC contents have been corrupted because some writing was done during power off.

I would reflash the SW and test if that solved the issue.