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

[kentaro]

@alvaro.tx
Colibri iMX7 Dual 1GB V1.1Bで起動不良が発生しています。
起動ログを見て気になるところがありますので、ご確認頂けると助かります。

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

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

③
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.

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

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

It seems you’re encountering some boot issues with your Colibri iMX7 Dual 1GB V1.1B module. Let’s address the concerns you’ve raised:

1. SPI Error Messages: The messages “spi2.0 supply vdd not found, using dummy regulator” and “spi2.0 supply xceiver not found, using dummy regulator” suggest that the system is defaulting to a dummy regulator because it cannot find the expected power supply for the SPI device. This is typically a configuration issue rather than a hardware fault. I recommend checking your device tree configuration to ensure that the SPI device is correctly defined and that any necessary regulators are specified.

2. File System Check Failure: The error “Failed to start File System Check on Root Device” indicates a problem with performing a file system check on the root partition, which could be due to file system corruption. Running a manual file system check (fsck) on the root partition might help resolve this issue. If your root file system is on an eMMC, ensure it is properly configured and accessible.

3. Emergency Mode and FAT-fs Warning: The system entering emergency mode and the message “FAT-fs (mmcblk0p1): Volume was not properly unmounted” suggest that the file system was not cleanly unmounted, potentially leading to data corruption. Running fsck on the affected partition can often resolve this.

Re-flashing the system using the Toradex Easy Installer could potentially resolve software-related issues, especially if the file system is corrupted. Please ensure you have a backup of any important data before proceeding with re-flashing.

I hope this helps you address the issues you’re facing. If you have further questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Apalis T30 system hang problem

Hello, I have a problem with an Apalis T30 and ixora carrier board. The system as worked (and work if I reinstall) with the angstrom version 2.6. I have tried to instal the 2.8b6 legacy image, and I have a stange behaviour. Pratically, with a fresh installation (without any other thing installed) the board boot correcly and all seems to be ok. After some amount of uptime (generally 3-4 hours) the system hang, without an apparently reason. I have connected the debug over serial port, but the…

Error building Boot to Qt for Embedded Linux on Colibri iMX7

Hello, We are trying to build a Yocto image with Boot to Qt for Colibri iMBX7, using QT_EDITION set to “opensource”. As suggested by the Toradex support we have followed steps here: Boot to Qt for Embedded Linux. Instead of apalis-imx8 target, we use colibri-imx7. We have used Yocto Pyro release as indicated by the guide. Our host machine is a Ubuntu Desktop 18.04.02 (running into VirtualBox). When we launch bitbake b2qt-embedded-qt5-image command we have this warning: Host distribution "ub…

Colibri iMX7 LCD Display.

[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.