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.

TDA4VM: cannot restart

Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need you help:

The system is started in eMMC boot mode, the system is restarted by executing the reboot command, everything else is fine, but the shutdown is not complete after the kernel calls Power down.

Try to reset from the bootloader, but fails. Also trying boot from the TF card, reboot is implementable. The following error is reported:

[ OK ] Stopped SYSV: S90mcu.sh.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Paths.
[ OK ] Stopped Dispatch Password …ts to Console Directory Watch.
[ OK ] Stopped Forward Password R…uests to Wall Directory Watch.
[ OK ] Stopped target Slices.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Sockets.
[ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Closed Docker Socket for the API.
[ OK ] Closed dropbear.socket.
[ OK ] Stopped target System Initialization.
Stopping Hardware RNG Entropy Gatherer Daemon...
[ OK ] Stopped Apply Kernel Variables.
[ OK ] Stopped Load Kernel Modules.
Stopping Network Time Synchronization...
Stopping Update UTMP about System Boot/Shutdown...
[ OK ] Stopped Network Time Synchronization.
[ OK ] Stopped Hardware RNG Entropy Gatherer Daemon.
[ OK ] Stopped Update UTMP about System Boot/Shutdown.
[ OK ] Stopped Create Volatile Files and Directories.
[ OK ] Stopped target Local File Systems.
Unmounting /media/ram...
Unmounting Temporary Directory (/tmp)...
Unmounting /var/volatile...
[ OK ] Unmounted /media/ram.
[ OK ] Unmounted Temporary Directory (/tmp).
[ OK ] Unmounted /var/volatile.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped target Swap.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Started Reboot.
[ OK ] Reached target Reboot.
[ 30.953323] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[ 30.960449] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[ 30.967359] watchdog: watchdog0: watchdog did not stop!
[ 30.985991] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 31.008425] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 31.022452] systemd-journald[164]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 31.022568] android_work: did not send uevent (0 0 0000000000000000)
[ 31.036310] android_work: did not send uevent (0 0 0000000000000000)
[ 31.050506] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 31.060027] systemd-shutdown[1]: Hardware watchdog 'K3 RTI Watchdog', version 0
[ 31.069487] systemd-shutdown[1]: Unmounting file systems.
[ 31.076440] [1302]: Remounting '/' read-only in with options '(null)'.
[ 31.113383] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
[ 31.121140] systemd-shutdown[1]: All filesystems unmounted.
[ 31.126785] systemd-shutdown[1]: Deactivating swaps.
[ 31.131841] systemd-shutdown[1]: All swaps deactivated.
[ 31.137063] systemd-shutdown[1]: Detaching loop devices.
[ 31.143974] systemd-shutdown[1]: All loop devices detached.
[ 31.149549] systemd-shutdown[1]: Detaching DM devices.
[ 31.154782] systemd-shutdown[1]: All DM devices detached.
[ 31.160173] systemd-shutdown[1]: All filesystems, swaps, loop devices and DM devices detached.
[ 31.175833] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 31.182573] systemd-shutdown[1]: Rebooting.
[ 31.187074] pci_generic_config_write32: 44 callbacks suppressed
[ 31.187080] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0xdc may corrupt adjacent RW1C bits
[ 31.202733] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 31.212451] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x9c may corrupt adjacent RW1C bits
[ 31.222228] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 31.231951] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 31.241638] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[ 31.251296] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0xdc may corrupt adjacent RW1C bits
[ 31.261028] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 31.270745] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x9c may corrupt adjacent RW1C bits
[ 31.280493] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x92 may corrupt adjacent RW1C bits
[ 31.309671] reboot: Restarting system

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi Cherry,

    Few questions:

    • Which SDK version is being used?
    • Is this a custom board or a TI EVM?
    • Whether the file system is on eMMC?

    I am able to boot from eMMC & FS in MMC-SD. I am able to get reboot working fine on Linux SDK 8.1.

    Also reset is working from U-Boot. That can be used as a quick check on your setup:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    => reset
    resetting ...
    U-Boot SPL 2021.01-g53e79d0e89 (Aug 04 2021 - 23:32:00 +0000)
    Model: Texas Instruments K3 J721E SoC
    Board: J721EX-PM2-SOM rev E6
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam')
    Trying to boot from MMC1
    init_env from device 17 not supported!
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.5(release):08.00.00.004-dirty
    NOTICE: BL31: Built : 22:30:09, Aug 4 2021
    U-Boot SPL 2021.01-g53e79d0e89 (Aug 04 2021 - 22:33:28 +0000)
    Model: Texas Instruments K3 J721E SoC
    Board: J721EX-PM2-SOM rev E6
    SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam')
    Detected: J7X-BASE-CPB rev E2
    Detected: J7X-INFOTAN-EXP rev E3
    Detected: J7X-VSC8514-ETH rev E2
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards,
    Keerthy

  • Dear Sir:

    • Which SDK version is being used?

    -->8.1

    • Is this a custom board or a TI EVM?

    -->custom borad

    • Whether the file system is on eMMC?

    -->the file system is on eMMC,and boot from emmc boot0

     

  • Hi Jin Lei,

    Do you have SD interface on your board? Does reboot work with SD on your custom board?

    - Keerthy

  • Dear Experts:

    Do you have SD interface on your board? Does reboot work with SD on your custom board?

    --->yes  and my custom board can reboot with SD card