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.

J721EXCPXEVM: Cannot bootup using NFS

Part Number: J721EXCPXEVM

Hi, 

Using the 8.2 SDK and following these steps here , I am unable to get the system bootup using NFS. I have the J721EXCPXEVM + J721EXSOM board.

Here is the output of sudo minicom -S bin/setupBoard.minicom

U-Boot SPL 2021.01-g15769936a5 (Dec 20 2021 - 17:09:03 +0000) Model: Texas Instruments K3 J721E SoC Board: J721EX-PM2-SOM rev E7 SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla') Trying to boot from MMC2 Starting ATF on ARM64 core... NOTICE: BL31: v2.5(release):08.01.00.006-dirty NOTICE: BL31: Built : 16:34:52, Dec 20 2021 U-Boot SPL 2021.01-g15769936a5 (Dec 20 2021 - 16:36:05 +0000) Model: Texas Instruments K3 J721E SoC Board: J721EX-PM2-SOM rev E7 SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla') Detected: J7X-BASE-CPB rev E3 Detected: J7X-VSC8514-ETH rev E2 Trying to boot from MMC2 U-Boot 2021.01-g15769936a5 (Dec 20 2021 - 16:36:05 +0000) SoC: J721E SR1.0 Model: Texas Instruments K3 J721E SoC Board: J721EX-PM2-SOM rev E7 DRAM: 4 GiB Flash: 0 Bytes MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1 In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Detected: J7X-BASE-CPB rev E3 Detected: J7X-VSC8514-ETH rev E2
Net: am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x000
eth0: ethernet@46000000
Hit any key to stop autobo 0
=>env default -f -a
## Resetting to default environment
=>saveenv
Saving Environment to FAT... OK
=>reset
resetting ...

U-Boot SPL 2021.01-g15769936a5 (Dec 20 2021 - 17:09:03 +0000)
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E7
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE: BL31: v2.5(release):08.01.00.006-dirty
NOTICE: BL31: Built : 16:34:52, Dec 20 2021

U-Boot SPL 2021.01-g15769936a5 (Dec 20 2021 - 16:36:05 +0000)
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E7
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla')
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2


U-Boot 2021.01-g15769936a5 (Dec 20 2021 - 16:36:05 +0000)

SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E7
DRAM: 4 GiB
Flash: 0 Bytes
MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
Net: am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x000
eth0: ethernet@46000000
Hit any key to stop autobo 0
=>setenv serverip 192.168.1.55
=>setenv ipaddr 192.168.1.56
=>setenv nfs_root /home/nikhil/bins/ti/jacinto7_sdk/ti-processor-sdk-linux-j7-evm-08_02_00_03/targetNFS
=>setenv name_kern Image-j7-evm.bin
=>setenv bootcmd 'run findfdt; run envboot; run setup_${kern_boot}; run init_${rootfs_boot}; run get_kern_${ker'
=>setenv init_net 'run args_all args_net; setenv autoload no; dhcp'
=>setenv args_net 'setenv bootargs console=${console} ${optargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serv'
=>setenv get_kern_net 'tftp ${loadaddr} ${name_kern}'
=>setenv get_fdt_net 'tftp ${fdtaddr} ${name_fdt}'
=>setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x100000;for overlay in ${overlay_files};do;tftp ${'
=>setenv nfs_options 'nolock,v3,tcp,rsize=4096,wsize=4096'
=>setenv setup_mmc ''
=>setenv setup_net 'setenv autoload no; dhcp'

=>setenv kern_boot net
=>setenv rootfs_boot net
=>saveenv
Saving Environment to FAT... OK
=>boot
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
483 bytes read in 9 ms (51.8 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
1 bytes read in 11 ms (0 Bytes/s)
Already setup.
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
link up on port 1, speed 1000, full duplexBOOTP broadcast 1

BOOTP broadcast 2
BOOTP broadcast 3

BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10

Retry time exceeded; starting again
am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
link up on port 1, speed 1000, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10


Retry time exceeded; starting again
am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
link up on port 1, speed 1000, full duplex
*** ERROR: `ipaddr' not set
am65_cpsw_nuss_slave ethernet@46000000: K3 CPSW: rflow_id_base: 2
link up on port 1, speed 1000, full duplex
*** ERROR: `ipaddr' not set
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Bad Linux ARM64 Image magic!

As you can see, I am setting the ipaddr variable but the uboot doesnt want to find it. After manually setting with seteven ipaddr command, I am able to ping my pc where the targetNFS folder is present.
Also, manually trying the tftp ${loadaddr} ${name_kern} command succeeds after setting the ipaddr. 

Is the NFS option only for the SKTDA4 board or does it even work with the SOM+PCP setup? If it does, what am I missing?

  • Hi,

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

    Have you tried the above set of instructions. Let me know if the above helps. Is your intent to run vision_apps using the NFS on TDA4-EVM?

    - Keerthy

  • Yes that is the intent. I have the Common Processor Board + SOM. I did the above steps but from a different source. Let me check the steps again and get back to you. 

  • I did all the steps and get to the same error. Here is the log of the final boot command - 

    I do have the ipaddr variable set to the ipaddr of the eth. I also tried setting the MAC addr and gateway. No difference. There is no issue with the mmc boot, only with the NFS boot.

    => boot
    switch to partitions #0, OK
    mmc1 is current device
    SD/MMC found on device 1
    Failed to load 'boot.scr'
    483 bytes read in 10 ms (46.9 KiB/s)
    Loaded env from uEnv.txt
    Importing environment from mmc1 ...
    Running uenvcmd ...
    1 bytes read in 11 ms (0 Bytes/s)
    Already setup.
    am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4

    Abort
    am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2

    Abort
    am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    *** ERROR: `ipaddr' not set
    am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    *** ERROR: `ipaddr' not set
    libfdt fdt_check_header(): FDT_ERR_BADMAGIC
    No FDT memory address configured. Please configure
    the FDT address via "fdt addr <address>" command.
    Aborting!
    Bad Linux ARM64 Image magic!

  • Hi,

    Is tftp set on your Ubuntu PC correctly?

    Refference: https://linuxhint.com/install_tftp_server_ubuntu/

    Best Regards,
    Keerthy

  • Also, manually trying the tftp ${loadaddr} ${name_kern} command succeeds after setting the ipaddr. 

    Missed this. So tftp setup is done correctly.]

    Is the NFS option only for the SKTDA4 board or does it even work with the SOM+PCP setup?

    It should work for TDA4 SOm as well.

    - Keerthy

  • Yes the Ubuntu PC is setup correctly as confirmed by the tftp command. Do you know what the error "ipaddr" not set means? I do set it (though it wasn't part of documentation). 

  • Hi,

    Once i key in the command 'dhcp' I get the IP Address:

    am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    DHCP client bound to address 192.168.100.196 (2418 ms)
    *** Warning: no boot file name; using 'C0A864C4.img'
    Using ethernet@46000000port@1 device
    TFTP from server 192.168.100.185; our IP address is 192.168.100.196

    So somehow that is not getting set at your end & you need to manually set IP Address.

    - Keerthy