This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[参考译文] AM62L-PROCESSOR-SDK:SW-Reboot 问题

Guru**** 2382480 points
请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1501340/am62l-processor-sdk-sw-reboot-issue

器件型号:AM62L-PROCESSOR-SDK

工具/软件:

您好、

在使用 AM62L3时、我遇到了有关 sw-reboot 的问题。 但它似乎在我的另一个2GB RAM 板工作正常与相同的 SD 卡用于启动在板有问题.
根据我的知识,该板是直接进入 UART 模式后重置. 这可能是什么问题。我已尝试检查 SD 卡相关的针脚、它们似乎工作正常。请检查我的主板卡住的附件打印件。


 OK  ] Unmounted Temporary Directory /tmp.
[  OK  ] Unmounted /var/volatile.
[  OK  ] Stopped target Swaps.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped File System Check on /dev/mmcblk0p1.
[  OK  ] Stopped File System Check on /dev/mmcblk0p2.
[  OK  ] Stopped File System Check on /dev/mmcblk1p1.
[  OK  ] Removed slice Slice /system/systemd-fsck.
[  OK  ] Stopped target Preparation for Local File Systems.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create Static Device Nodes in /dev gracefully.
[  OK  ] Reached target System Shutdown.
[  OK  ] Reached target Late Shutdown Services.
[  OK  ] Finished System Reboot.
[  OK  ] Reached target System Reboot.
[  197.250374] audit: type=1334 audit(1736362290.150:26): prog-id=16 op=UNLOAD
[  197.258431] audit: type=1334 audit(1736362290.150:27): prog-id=15 op=UNLOAD
[  197.266458] audit: type=1334 audit(1736362290.162:28): prog-id=5 op=UNLOAD
[  197.274124] audit: type=1334 audit(1736362290.162:29): prog-id=4 op=UNLOAD
[  197.281895] audit: type=1334 audit(1736362290.162:30): prog-id=3 op=UNLOAD
[  197.312224] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[  197.319173] watchdog: watchdog0: watchdog did not stop!
[  197.347072] systemd-shutdown[1]: Using hardware watchdog 'K3 RTI Watchdog', version 0, device /dev/watchdog0
[  197.357251] systemd-shutdown[1]: Modifying watchdog hardware timeout is not supported, reusing the programmed timeout.
[  197.367990] systemd-shutdown[1]: Watchdog running with a hardware timeout of 1min.
[  197.458105] systemd-shutdown[1]: Syncing filesystems and block devices.
[  197.476936] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[  197.504752] systemd-journald[109]: Received SIGTERM from PID 1 (systemd-shutdow).
[  197.536953] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  197.557473] systemd-shutdown[1]: Unmounting file systems.
[  197.566294] (sd-remount)[970]: Remounting '/' read-only with options ''.
[  197.608298] EXT4-fs error (device mmcblk1p2): ext4_mark_recovery_complete:6236: comm (sd-remount): Orphan file not empty on read-only fs.
[  197.620868] EXT4-fs (mmcblk1p2): re-mounted a158077c-bd78-4f71-af1a-ea8a8832a048 ro. Quota mode: none.
[  197.638309] systemd-shutdown[1]: All filesystems unmounted.
[  197.644208] systemd-shutdown[1]: Deactivating swaps.
[  197.649497] systemd-shutdown[1]: All swaps deactivated.
[  197.654772] systemd-shutdown[1]: Detaching loop devices.
[  197.665997] systemd-shutdown[1]: All loop devices detached.
[  197.671706] systemd-shutdown[1]: Stopping MD devices.
[  197.677243] systemd-shutdown[1]: All MD devices stopped.
[  197.682599] systemd-shutdown[1]: Detaching DM devices.
[  197.688071] systemd-shutdown[1]: All DM devices detached.
[  197.693496] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[  197.703159] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[  197.710046] systemd-shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy
[  197.719441] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[  197.726313] watchdog: watchdog0: watchdog did not stop!
[  197.743580] systemd-shutdown[1]: Syncing filesystems and block devices.
[  197.750502] systemd-shutdown[1]: Rebooting.
[  197.765838] reboot: Restarting system
02000000011a0000616d36326c0000000000000048534653000001000000010002a6000000000000fe73d96bbf79f784d9aee9fc5698d1093936556f93abf79f3ec7ce923079c478f837b12296da2a81a2fa024cb9d2423a14511488622a9ca591e5ee057175b142adC

-- Dheeraj

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Dheeraj:

    引导电路板时、请在 u-boot 提示符处停止、并运行以下命令以获取引导模式设置。

    => MD.l 43010030 1.

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您是否使用 SDK v11.0.0.3或 v11.0.5.2?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、

    使用最新版本11.0.5.2的 Im 和该命令的输出、

    iWave-G69M > Md.l 43010030 1.
    43010030:00000e43 c...



  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    主引导模式为 sdcard、备用模式为 UART。 问题似乎是、热复位 ROM 无法从 sdcard 引导、然后切换到从 UART 引导。

    每次 Linux 重新启动时是否都会出现问题?

    是否在每个电路板上都出现问题? 此故障电路板与另一个工作的2GB-DDR 电路板之间的硬件差异是什么?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    此外、当问题发生(从 UART 引导)并对电路板进行下电上电时、它是否会从 sdcard 引导?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、

    SDIO 时钟引脚存在一些硬件问题。现在问题已解决。  
    谢谢你

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    感谢您的更新!