Linux/AM5728: Boot issue : swtching from am57xx-evm-02.00.02.11 to linux-am57xx-evm-03.01.00.06

shweta mishra80

Part Number: AM5728

Tool/software: Linux

Hello,

For LPAE support, I am switching from am57xx-evm-02.00.02.11 to linux-am57xx-evm-03.01.00.06, but system is boot properly but with multiple warnings like:

This architecture does not have kernel memory protection.
Failed to start Load Kernel Modules.
disagrees about version of symbol module_layout etc
also my project init script in not running from rc5.d which is workinf with old SDK and file system

Please note I have created file system using below steps:
$ sudo ./setup-targetfs-nfs.sh
$ Update zImage and DTB file in targetNFS/boot/ then packe it again.
$ above steps work fine with older SDK

HW clock is also not initialized

root@am57xx-evm:~# hwclock
hwclock: can't open '/dev/misc/rtc': No such file or directory

1258.sdk3_0.txt

4863.Log_working_for_ref_SDK2_00.txt

Please let me know what can be the possible issue.

Thanks

Shweta

over 8 years ago

0 Kemal R. Shakir over 8 years ago

TI__Guru 55345 points

Hello shweta,

By separately running ./setup-targetfs-nfs.sh you have changed the rootfs but the kernel and device tree files still remain the old ones, that is why you are facing all these errors. The setup-targetfs-nfs.sh should be invoked by setup.sh script. Please, set-up the Processor SDK as explained at this wiki page.

Best regards,
Kemal

0 Yordan Kovachev over 8 years ago

TI__Guru**** 161600 points

Hi Sweta,

In addition to Kemal's answer:

also my project init script in not running from rc5.d which is workinf with old SDK and file system

You need to create a systed service, which invokes your init scripts, see this post for reference:
e2e.ti.com/.../539060

Failed to start Load Kernel Modules.
disagrees about version of symbol module_layout etc

Note that you need to rebuild all modules located in /lib/modules/<kerenl_version>/kernel/ & update them in your file system, so that the build tags of the .ko files & the zImage match. This will take care of the above quoted problems

Best Regards,
Yordan

0 shweta mishra80 over 8 years ago in reply to Yordan Kovachev

Intellectual 340 points

Thanks Kemal and Jordam,

I will try this today to resolve the module version errors, anything about the RTC error ?

root@am57xx-evm:~# hwclock
hwclock: can't open '/dev/misc/rtc': No such file or directory

Regards,
Shweta

0 shweta mishra80 over 8 years ago in reply to shweta mishra80

Intellectual 340 points

Thanks Yordan and Kemal,

Your inputs are very helpful, system is booting properly RTC is also working, reason was because module authentication check.

Can you please let me know what is logs for, it says,

fail to load kernel module,
mounting debug file system
failed to synchronize with hardware clock.

below are the logs:

[    4.212500] systemd[1]: sysinit.target: Found ordering cycle on sysinit.target/start
[    4.220386] systemd[1]: sysinit.target: Found dependency on alignment.service/start
[    4.228085] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    4.235389] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    4.242880] systemd[1]: sysinit.target: Found dependency on rpcbind.socket/start
[    4.250331] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    4.257763] systemd[1]: sysinit.target: Breaking ordering cycle by deleting job alignment.service/start
[    4.267219] systemd[1]: alignment.service: Job alignment.service/start deleted to break ordering cycle starting with sysinit.target/start
[ SKIP ] Ordering cycle found, skipping alignment.service
[    4.301832] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    4.329381] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    4.359247] systemd[1]: Listening on Syslog Socket.
[  OK  ] Listening on Syslog Socket.
[    4.380388] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    4.409326] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[    4.439254] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    4.469225] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[    4.499254] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    4.519220] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    4.549131] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    4.569352] systemd[1]: Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Audit Socket.
[    4.599290] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[    4.629123] systemd[1]: Reached target Paths.
[  OK  ] Reached target Paths.
[    4.649176] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    4.679616] systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
[    4.709656] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    4.739601] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    4.809338] systemd[1]: Starting Setup Virtual Console...
         Starting Setup Virtual Console...
[    4.851430] systemd[1]: Starting Create list of required static device nodes for the current kernel...
         Starting Create list of required st... nodes for the current kernel...
[    4.919178] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[    4.936690] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[    4.971643] systemd[1]: Mounting Temporary Directory...
         Mounting Temporary Directory...
[    5.011899] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
[    5.034102] cmemk: disagrees about version of symbol module_layout
[    5.042757] systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems...
[    5.058186] cryptodev: disagrees about version of symbol module_layout
[    5.069277] systemd[1]: Reached target Slices.
[  OK  ] Reached target Slices.[    5.076741] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

[    5.081051] gdbserverproxy: disagrees about version of symbol module_layout
[    5.101415] uio_module_drv: disagrees about version of symbol module_layout
[    5.119440] systemd[1]: Mounting Debug File System...
         Mounting Debug File System...
[    5.145302] systemd[1]: Mounted POSIX Message Queue File System.
[  OK  ] Mounted POSIX Message Queue File System.
[    5.179217] systemd[1]: Mounted Debug File System.
[  OK  ] Mounted Debug File System.
[    5.199236] systemd[1]: Mounted Temporary Directory.
[  OK  ] Mounted Temporary Directory.
[    5.219391] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[  OK  ] Started Setup Virtual Console.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting Rebuild Hardware Database...
         Starting Rebuild Dynamic Linker Cache...
         Mounting Configuration File System...
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Mounted Configuration File System.
[    5.809977] systemd-journald[138]: Received request to flush runtime journal from PID 1
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /media/ram...
         Mounting /var/volatile...
[  OK  ] Mounted /var/volatile.
[  OK  ] Mounted /media/ram.
         Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Rebuild Journal Catalog...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started Rebuild Journal Catalog.
         Starting Opkg first boot configure...
         Starting Update UTMP about System Boot/Shutdown...
         Starting Network Time Synchronization...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
         Starting Synchronize System and HW clocks...
[  OK  ] Started Rebuild Hardware Database.
[FAILED] Failed to start Synchronize System and HW clocks.
See 'systemctl status sync-clocks.service' for details.
         Starting udev Coldplug all Devices...
[  OK  ] Started udev Coldplug all Devices.
[    7.699313] vpe 489d0000.vpe: Device registered as /dev/video0
[    7.976890] omap-rproc 58820000.ipu: assigned reserved memory node ipu1_cma@9d000000

Regards,

Shweta

0 shweta mishra80 over 8 years ago in reply to shweta mishra80

Intellectual 340 points

Hello,

Also I didn’t see any print from intrc, I have added simple hello script in runlevel 5 but not showing my msg in boot time.

attaching logs for your reference, please let me know what may be responsible for now running script from runlevel.

2402.sdk3_0.txt

Note i follow the simple steps:

Login to the root file system
Change directory to the standard initscript directory /etc/init.d
create helloworld.sh add some echo "++++++"
Give the init script executable permissions so that it can be run and test it
cd /etc/rc5.d
ln -s ../init.d/helloworld.sh S99helloworld
reboot

In previous version SDK logs are like:

INIT: Entering runlevel: 5
Configuring network interfaces... [   12.599622] net eth0: initializing cpsw version 1.15 (0)
[   12.681390] net eth0: phy found : id is : 0x221622
done.
Starting system message bus: dbus.
UIM SYSFS Node Found at /sys/./devices/platform/kim/install
Starting uim-sysfs daemon.
uim:@ main
uim:install = /sys/./devices/platform/kim/install
uim:dev_name = /sys/./devices/platform/kim/dev_name
uim:baud_rate = /sys/./devices/platform/kim/baud_rate
uim:flow_cntrl = /sys/./devices/platform/kim/flow_cntrl
uim:begin polling...
[   13.441799] PVR_K: UM DDK-(3699939) and KM DDK-(3699939) match. [ OK ]
Loaded PowerVR consumer services.
Starting Dropbear SSH server: [   13.597126] NET: Registered protocol family 10
[   13.606188] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
dropbear.
Starting telnet daemon.
Starting tiipclad daemon
GateMP support enabled on host

Opened log file: lad.txt

numProcessors = 5 id = 0 baseId = 0

Spawned daemon: /usr/bin/lad_dra7xx

Regards

Shweta

0 Kemal R. Shakir over 8 years ago in reply to shweta mishra80

TI__Guru 55345 points

In linux-am57xx-evm-03.01.00.06 systemD service manager is used instead of systemV. Please, see the Yordan's answer:
e2e.ti.com/.../2071795

0 shweta mishra80 over 8 years ago in reply to Kemal R. Shakir

Intellectual 340 points

Thanks Kemal,

That issue is resolved now, I am able to run my script using service manager.

Could you please to resolve other errors, what i mentioned in previous comment .
e2e.ti.com/.../2072142

Regards,
Shweta

0 Kemal R. Shakir over 8 years ago in reply to shweta mishra80

TI__Guru 55345 points

What is the content of systemctl status systemd-modules-load.service and systemctl status sync-clocks.service commands? Can you share?

0 shweta mishra80 over 8 years ago in reply to Kemal R. Shakir

Intellectual 340 points

Thanks Kemal,

Its working now I have recompiled the modules that resolved all the issues. and added systed service.

Regards,
Shweta

Processors

Processors forum

Linux/AM5728: Boot issue : swtching from am57xx-evm-02.00.02.11 to linux-am57xx-evm-03.01.00.06