AM5718: AM5718 reset

Rakesh Muralidharan

Part Number: AM5718
Other Parts Discussed in Thread: TMDXIDK5718

Hi,

In my custom board I have adopted reset scheme from AM572x GP EVM board.

I am running Linux on custom board. While I try to reboot via Linux command in custom board , it halts at "Restarting system"". And board does not restart.

Where as on AM5718 EVM (TMDXIDK5718) it works properly.

What is the hardware dependence for implementing reset??

I guess PORZ has 3 sources as per EVM design

1. PMIC reset out

2. SoC's RSTOUTn

3. Hardware RESET (via reset button)

I guess Linux has to trigger reset via PMIC or Self Generate RSTOUT.

Please advice on the mechanism for reboot in Linux build for AM5718.

over 5 years ago

0 Anupama Sreekumar over 5 years ago

Intellectual 390 points

Hi,

My Linux rebbot log is attached below

Fullscreen 2548.reboot_log.txt Download

am57xx-evm login: root
root@am57xx-evm:~# reboot
[  OK  ] Stopped target Multi-User System.
         Stopping D-Bus System Message Bus...
         Stopping Job spooling tools...
         Stopping Hardware RNG Entropy Gathere         Stopping Serial Getty on ttyS2...
         Stopping Periodic Command Scheduler...
         Stopping TI MultiCore Tools Daemon...
         Stopping NFS status monitor for NFSv2/3 locking....
[  OK  ] Stopped target Containers.
         Stopping Redis In-Memory Data Store...
         Stopping TI IPC Daemon...
[  OK  ] Stopped Session c1 of user root.
         Stopping User Manager for UID 0...
         Stopping Lightning Fast Webserver With Light System Requirements...
[  OK  ] Stopped Matrix GUI.
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily Cleanup of Temporary Directories.
         Stopping strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf...
[  OK  ] Stopped Daily rotation of log files.
[  OK  ] Stopped target System Time Synchronized.
         Stopping Save/Restore Sound Card State...
         Stopping Simple Network Management Protocol (SNMP) Daemon....
         Stopping Getty on tty1...
         Stopping Kernel Logging Service...
[  OK  ] Stopped System Logging Service.
[  OK  ] Stopped TI IPC Daemon.
[  OK  ] Stopped D-Bus System Message Bus.
[  OK  ] Stopped Avahi mDNS/DNS-SD Stack.
[  OK  ] Stopped Job spooling tools.
[  OK  ] Stopped Kernel Logging Service.
[  OK  ] Stopped Periodic Command Scheduler.
[  OK  ] Stopped Hardware RNG Entropy Gatherer Daemon.
[  OK  ] Stopped TI MultiCore Tools Daemon.
[  OK  ] Stopped Simple Network Management Protocol (SNMP) Daemon..
[  OK  ] Stopped Lightning Fast Webserver With Light System Requirements.
[  OK  ] Stopped NFS status monitor for NFSv2/3 locking..
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped Serial Getty on ttyS2.
[  OK  ] Stopped strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
[  OK  ] Stopped User Manager for UID 0.
[  OK  ] Stopped thermal-zone-init.service.
[  OK  ] Stopped Redis In-Memory Data Store.
[  OK  ] Stopped Save/Restore Sound Card State.
         Stopping gdbserverproxy.service...
[  OK  ] Removed slice User Slice of root.
         Stopping Login Service...
[  OK  ] Removed slice system-serial\x2dgetty.slice.
         Stopping Permit User Sessions...
[  OK  ] Removed slice system-getty.slice.
         Stopping RPC Bind Service...
[  OK  ] Stopped target Host and Network Name Lookups.
[  OK  ] Stopped Login Service.
[  OK  ] Stopped RPC Bind Service.
[  OK  ] Stopped gdbserverproxy.service.
[  OK  ] Stopped Permit User Sessions.
         Stopping LSB: Redis, a key-value store...
[  OK  ] Stopped LSB: Redis, a key-value store.
         Stopping rng-tools.service...
[  OK  ] Stopped target Network is Online.
         Stopping Network Name Resolution...
[  OK  ] Stopped Wait for Network to be Configured.
[  OK  ] Stopped rng-tools.service.
[  OK  ] Stopped Network Name Resolution.
[  OK  ] Stopped target Network.
         Stopping Network Service...
         Stopping thttpd.service...
[  OK  ] Stopped thttpd.service.
[  OK  ] Stopped Network Service.
         Stopping telnetd.service...
[  OK  ] Stopped telnetd.service.
         Stopping weston.service...
[  OK  ] Stopped weston.service.
[  OK  ] Stopped target Remote File Systems.
         Stopping rc.pvr.service...
[  OK  ] Stopped rc.pvr.service.
         Stopping uim-sysfs.service...
[  OK  ] Stopped uim-sysfs.service.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
[  OK  ] Stopped Dispatch Password Requests to Console Directory Watch.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Closed RPCbind Server Activation Socket.
[  OK  ] Closed dropbear.socket.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped Apply Kernel Variables.
         Stopping Update UTMP about System Boot/Shutdown...
         Stopping Load/Save Random Seed...
[  OK  ] Stopped Load Kernel Modules.
         Stopping Network Time Synchronization...
[  OK  ] Stopped Update is Completed.
[  OK  ] Stopped Rebuild Journal Catalog.
[  OK  ] Stopped Rebuild Hardware Database.
[  OK  ] Stopped Rebuild Dynamic Linker Cache.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Load/Save Random Seed.
[  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 /run/media/mmcblk0p1...
         Unmounting Temporary Directory (/tmp)...
         Unmounting /run/user/0...
         Unmounting /var/volatile...
[  OK  ] Unmounted /media/ram.
[  OK  ] Unmounted /run/media/mmcblk0p1.
[  OK  ] Unmounted Temporary Directory (/tmp).
[  OK  ] Unmounted /run/user/0.
[  OK  ] Unmounted /var/volatile.
[  OK  ] Stopped target Swap.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[  317.288161] watchdog: watchdog0: watchdog did not stop!
[  317.300103] systemd-shutdow: 22 output lines suppressed due to ratelimiting
[  317.363852] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[  317.378877] systemd-journald[72]: Received SIGTERM from PID 1 (systemd-shutdow).
[  317.421901] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  317.435665] systemd-shutdown[1]: Hardware watchdog 'OMAP Watchdog', version 0
[  317.445249] systemd-shutdown[1]: Unmounting file systems.
[  317.451405] systemd-shutdown[1]: Remounting '/' read-only with options 'data=ordered'.
[  317.498757] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
[  317.515692] systemd-shutdown[1]: Remounting '/' read-only with options 'data=ordered'.
[  317.523783] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
[  317.529740] systemd-shutdown[1]: All filesystems unmounted.
[  317.535563] systemd-shutdown[1]: Deactivating swaps.
[  317.540660] systemd-shutdown[1]: All swaps deactivated.
[  317.545965] systemd-shutdown[1]: Detaching loop devices.
[  317.601582] reboot: Restarting system

0 Dwarakesh Radhakrishnan over 5 years ago in reply to Anupama Sreekumar

Guru 13660 points

Hi,

Have you tried the following

1. force reboot with following command

# reboot -f

2. Waited for a long time in minutes to check if it is rebooting ?

0 Anupama Sreekumar over 5 years ago in reply to Dwarakesh Radhakrishnan

Intellectual 390 points

Hi,

We tried "reboot -f" and waited for about 10 minutes. System is not restarting. we got the following print:

------------------------------------------------

root@am57xx-evm:~# reboot -f
Rebooting.
[ 38.602123] reboot: Restarting system

----------------------------------

We had deleted rtc node as given below as our custom board was not booting if this was enabled. Does this have any effect on reboot command ?

-----------------------------------------------------------------------

am57xx-idk-common.dtsi

aliases {
rtc0 = &tps659038_rtc;
/*rtc1 = &rtc; */
display0 = &hdmi0;
ethernet2 = &pruss2_emac0;
ethernet3 = &pruss2_emac1;
};

chosen {
stdout-path = &uart3;
};

ocp {
/delete-node/ rtc@48838000;
};

----------------------------------------------

0 Dwarakesh Radhakrishnan over 5 years ago in reply to Anupama Sreekumar

Guru 13660 points

Hi Anupama,

Can you check if the RSTOUTn pin is asserted by probing with an oscilloscope ? Ball number F23, rstoutn pin. Ideally after reboot command, it would set a warm reset in PRCM register and once that is done system would enter a reset sequence and also indicate it by rstoutn pin.

Also can you stop in autoboot of uboot and issue the below command and check if it is rebooting ?

# reset

0 Rakesh Muralidharan over 5 years ago in reply to Dwarakesh Radhakrishnan

Expert 2810 points

Cause was a hardware issue on board . When resolved , reboot functions properly .

Processors

Processors forum

AM5718: AM5718 reset