SK-AM62: NFS boot: Bad Linux ARM64 Image magic!

Thorsten Lorenzen

Part Number: SK-AM62

Still I cannot boot via NFS while SD Card boot is fully functional. I have read all he the tickets for Jacinto but for Sitara it is not working.

Applying the ./setup.sh script works but always ends up with "Bad Linux ARM64 Image magic!" even it seems to load the "Image-arm62xx-evm.bin" and the "k3-am625-sk.dtb" files. I have two IP addresses and difficulties to decide what is the right one.

Any ideas what I can do?

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/984034/faq-tda4vm-how-to-enable-nfs-on-psdkra

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_02_00_06/exports/docs/vision_apps/docs/user_guide/RUN_INSTRUCTIONS.html#run_steps_linux_nfs

=> 
=> boot
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
1490 bytes read in 3 ms (484.4iB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
lready setup.in 2 ms (0 Bytes/s)
link up on port 1, speed 1000, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 82
*** Unhandled DHCP Option in OFFER/ACK: 82
DHCP client bound to address 192.168.178.126 (172 ms)
link up on port 1, sed 1000, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 82
*** Unhandled DHCP Option in OFFER/ACK: 82
DHCP client bound  address 192.168.178.126 (192 ms)
link up on port 1, speed 1000, full duplex
Using etherne8000000port@1 device
TFTP from server 192.168.178.1; our IP aress is 192.168.178.126
Filename 'Image-am62xx-evm.bin'.
Load address: 0x8200000
                       Loading: T T T T T T T T T T 
Retry count exceeded; starting again
link up on port 1, spe 1000, full duplex
Using ethernet@8000000port@1 device
TFTP om server 192.168.178.1; our IP address is 192.168.178.126
Filename 'k3-am625k.dtb'.
Load address: 0x88000000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
libfdt fdt_check_heade): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command
                                                Aborting!
Bad Linux ARM64 Image magic!
=>

over 3 years ago

0 Schuyler Patton over 3 years ago

TI__Mastermind 41330 points

Hi,

I may be missing something but I don't see where any files are loading. All I see are timeouts. You need to verify there is communication with the server. Try pinging the server address after this boot sequence exits. You will need to an ip address already such as the 192.168.178.126.

Which SDK are you using? What is providing the role of the tftp server?

Best Regards,

Schuyler

0 Thorsten Lorenzen over 3 years ago in reply to Schuyler Patton

TI__Genius 17101 points

Hi Schuyler, sorry took me time to understand what needs to be changed.

First of all I had to switch the VirtualBox into "Bridged Mode" in order the Ubuntu host receives a dedicated IP address from my router.

Now not just the windows machine (192.168.178.129) but even Ubuntu VM guest (192.168.178.130 ) have own unique IP address for tftp to function. The EVM even received the IP address (192.168.178.111). I can ping all IPs (WIN PC, Ubuntu VM, EVM).

What I found is in the log of the terminal the "FTP from server 192.168.178.1" is my router. Shouldn't it be "FTP from server 192.168.178.130" to address the Ubuntu host VM in order to connect via tftp/ftp?

Any idea?

Thorsten