①
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.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your concerns about the boot issues on your Colibri iMX7 Dual 1GB V1.1B module. Let’s address the points you’ve raised:
SPI Supply Errors: The messages indicating that the SPI device is using a dummy regulator suggest a configuration issue, likely within the device tree. This typically does not indicate a hardware fault and should not prevent the system from booting. Reviewing and adjusting the device tree to ensure proper power supply settings for the SPI device might resolve these messages.
File System Check Failure: The failure to start a file system check on the root device could be due to file system corruption. This is a critical issue that can prevent the system from booting properly. Running a file system check (fsck) on the affected partition might help resolve this.
Emergency Mode and FAT-fs Error: Entering emergency mode and the message about the FAT file system not being properly unmounted suggest potential data corruption. Again, running fsck could address this issue.
Recommendations:
Re-flashing the System: Reinstalling the operating system using the Toradex Easy Installer may resolve file system corruption issues. This process will overwrite the existing system, so please ensure any important data is backed up beforehand.
Device Tree Configuration: Ensure that the device tree is correctly configured, especially for SPI devices, to provide the necessary power supply settings.
These steps should help address the issues you’re experiencing. If problems persist after re-flashing and configuration adjustments, further investigation into the software setup may be necessary.
I hope this helps, and please feel free to reach out if you have further questions.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem: