• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 280 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM6442: PRU ECAP

AM6442: Soft Reboot/Linux not working

DHardes
Intellectual 280 points

Part Number: AM6442

Hi everyone,

i'm currently working on a custom board based on the SK-AM64.

The image (generated with Yocto 4.0) is booting from SD card without issues.

Entering the system command "reboot" in Linux leads to the system locking up:

root@am64xx-evm:~# reboot                                                       
                                                                                
Broadcast message from root@am64xx-evm (ttyS2) (Fri Mar  9 12:59:30 2018):      
                                                                                
The system is going down for reboot NOW!                                        
INIT: Sending processes configured via /etc/inittab the TERM signal             
Stopping OpenBSD Secure Shell server: sshdstopped /usr/sbin/sshd (pid 299)      
.                                                                               
Stopping advanced power management daemon: no /usr/sbin/apmd found; none killed 
apmd.                                                                           
hwclock: can't open '/dev/misc/rtc': No such file or directory                  
Stopping syslogd/klogd: stopped syslogd (pid 309)                               
stopped klogd (pid 312)                                                         
done                                                                            
ALSA: Storing mixer settings...                                                 
Unmounting remote filesystems...                                                
Stopping Lighttpd Web Server: stopped /usr/sbin/lighttpd (pid 319)              
lighttpd.                                                                       
Deconfiguring network interfaces... [   21.691153] am65-cpsw-nuss 8000000.ethern
done.                                                                           
Sending all processes the TERM signal...                                        
Sending all processes the KILL signal...                                        
Deactivating swap...                                                            
Unmounting local filesystems...                                                 
[   26.840292] EXT4-fs (mmcblk1p2): re-mounted. Quota mode: none.               
Rebooting...

Entering the "reset" command in u-boot results in the system restarting as expected.

1. In comparison to the SK-AM64 we've changed the LPDDR4 module to a 2GBit one (the necessary changes to the device tree and u-boot have been made)
2. MMC is directly connected to 3.3V, therefore the necessary changes in the devicetree have been made to support only 3.3V/SDHC, the regulator GPIO has been removed
3. The same image will reboot fine on the SK-AM64

Are there suggestions on how to debug this problem or how to solve it? What additional information is necessary?

Thanks in advance

Regards,

Dave

  • 0
    TI__Guru**** 175931 points

    Hi Dave,

    Please attach the full boot log.

    (Please attach the log as a file, not just direct copy and paste to the thread, which makes the thread too long and difficult to navigate.)

  • 0 in reply to Bin Liu
    Intellectual 280 points

    Hi, i might have been to fast on creating this topic.

    it seems that the r5f cores - or to be precise, their memory carveouts - might have been the isssue.

    I did not notice that i misplaced the memory carveouts into a section which is not existing due to our 2gbit memory module - while i moved them i miscalculated the placement and still was beyond the 2gbit boarder.

    I do not fully understand why the memory carveouts did stop the system from rebooting, but this single change has fixed the problem.

    I do have additional questions about the memory carveouts of the cores, and the configuration of single- vs. multicore usage of the r5fss, but i think i should create a new topic for this.

    Regards,

    Dave