Tool/software: Linux
I have successfully booted the AM572 for remote nfs but the kernel failed to load.Here's the edited output,
=>boot
switch to partitions #0, OK
mmc0 is current device
reading uEnv.txt
574 bytes read in 4 ms (139.6 KiB/s)
Importing environment from mmc0 ...
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.32.1; our IP address is 192.168.32.2
Filename 'zImage-am57xx-evm.bin'.
Load address: 0x82000000
Loading: #################################################################
#########
625 KiB/s
done
Bytes transferred = 3703368 (388248 hex)
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.32.1; our IP address is 192.168.32.2
Filename 'am57xx-evm-reva3.dtb'.
Load address: 0x88000000
Loading: #####################
3.9 MiB/s
done
Bytes transferred = 106832 (1a150 hex)
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffe2000, end 8ffff14f ... OK
Starting kernel ...
I note that the entire targetNFS structure was not downloaded. There were a number of logs in /www/logs that did not make the passage for instance.
There were three fails but it appears that the last two pertained to the first.
[ OK ] Started Remount Root and Kernel File Systems.
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[ OK ] Started Network Service.
[FAILED] Failed to start TI MultiCore Tools Daemon.
See 'systemctl status ti-mct-daemon.service' for details.
[ OK ] Started Enable and configure wl18xx bluetooth stack.
[FAILED] Failed to start Synchronize System and HW clocks.
See 'systemctl status sync-clocks.service' for details.
Plainly these are some major snafus. The system did not come up. Can you refer me to some material that might shed light on the shortcomings of my remote mount.
Here are the feedbacks from the suggested systemctl commands
After issuing systemctl status systemd-modules-load.service
I received
[[0;1;31m●[[0m systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2017-09-26 21:42:50 UTC; 5min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 162 ExecStart=/lib/systemd/systemd-modules-load [[0;1;31m(code=exited, status=1/FAILURE)[[0m
Main PID: 162 (code=exited, status=1/FAILURE)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
After issuing systemctl status ti-mct-daemon.service I received
0;1;31m��●[[0m ti-mct-daemon.service - TI MultiCore Tools Daemon
[[0;1;31m��●[[0m ti-mct-daemon.service - TI MultiCore Tools Daemon
Loaded: loaded (/lib/systemd/system/ti-mct-daemon.service; enabled; vendor preset: enabled)
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2017-09-26 21:42:54 UTC; 25min ago
Process: 268 ExecStart=/usr/bin/ti-mctd [[0;1;31m(code=exited, status=1/FAILURE)[[0m
Sep 26 21:42:52 am57xx-evm systemd[1]: Starting TI MultiCore Tools Daemon...
Sep 26 21:42:53 am57xx-evm ti-mctd[268]: Shared Memory heaps created, size 131072 bytes
Sep 26 21:42:53 am57xx-evm ti-mctd[268]: CMEM Error: init: Failed to open /dev/cmem: 'No such file or directory'
Sep 26 21:42:53 am57xx-evm ti-mctd[268]: TIOCL FATAL: The cmemk kernel module is not installed. Consult the OpenCL UserGuide at http://software-dl.ti.co
m/mctools/esd/docs/opencl/index.html
Sep 26 21:42:54 am57xx-evm systemd[1]: [[0;1;39mti-mct-daemon.service: Control process exited, code=exited status=1[[0m
Sep 26 21:42:54 am57xx-evm systemd[1]: [[0;1;31mFailed to start TI MultiCore Tools Daemon.[[0m
Sep 26 21:42:54 am57xx-evm systemd[1]: [[0;1;39mti-mct-daemon.service: Unit entered failed state.[[0m
Sep 26 21:42:54 am57xx-evm systemd[1]: [[0;1;39mti-mct-daemon.service: Failed with result 'exit-code'.[[0m
After issuing
systemctl status sync-clocks.service, I received:
[[0;1;31m��●[[0m sync-clocks.service - Synchronize System and HW clocks
Loaded: loaded (/etc/systemd/system/sync-clocks.service; enabled; vendor preset: enabled)
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2017-09-26 21:42:57 UTC; 28min ago
Process: 614 ExecStart=/sbin/hwclock --systohc [[0;1;31m(code=exited, status=1/FAILURE)[[0m
Main PID: 614 (code=exited, status=1/FAILURE)
Sep 26 21:42:56 am57xx-evm systemd[1]: Starting Synchronize System and HW clocks...
Sep 26 21:42:56 am57xx-evm hwclock[614]: hwclock: can't open '/dev/misc/rtc': No such file or directory
Sep 26 21:42:57 am57xx-evm systemd[1]: [[0;1;39msync-clocks.service: Main process exited, code=exited, status=1/FAILURE[[0m
Sep 26 21:42:57 am57xx-evm systemd[1]: [[0;1;31mFailed to start Synchronize System and HW clocks.[[0m
Sep 26 21:42:57 am57xx-evm systemd[1]: [[0;1;39msync-clocks.service: Unit entered failed state.[[0m
Sep 26 21:42:57 am57xx-evm systemd[1]: [[0;1;39msync-clocks.service: Failed with result 'exit-code'.[[0m
To this let me add some history: When I received this unit and fired it up with the included sd card, it worked. Only after I had started it with minicom attached and dialogging did it fail to initialize properly, presumably with the failures noted above. This now happens even when minicom is not attached. Could you send me a new penguin card so I can verify the significance of this chain of events.
I created a different sd card from scratch using the latest release and it too exhibits these defects.
I am using ubuntu 16.04.
There are a lot of potential issues here. Please suggest where to look for a solution to this problem.
