• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 732 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.

Boot up using ethernet

Aneesh Peram
Expert 1255 points


Hi 

I am trying to boot up my board by using ethernet 

I have tda4 j7 evm board

I am trying to boot up linux on the board

Please help with the problem

Regards,

Aneesh

  • 0
    TI__Guru** 113810 points

    Hi Aneesh,

    Could you please provide additional details here?

    Are you trying to use tftp and/or NFS? Is that the intent?

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1255 points

    Hi Karthik,

    Yes, I am using tftp and nfs

    Regards,

    Aneesh

  • 0 in reply to Aneesh Peram
    Expert 1255 points

    Hi Karthik,

    I installed the sdk and the setup on a virtual linux machine which is runnig on windows10.

    Regards,

    Aneesh

  • 0 in reply to Aneesh Peram
    TI__Guru** 113810 points

    Hi Aneesh,

    Thanks for confirming that you are trying TFTP and NFS.

    OK. Could you please provide additional details about the problem that you are facing?

    It would be good for you to share what you have tried and what is the log of the error? Some details will be required to help you further.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1255 points

    Fullscreen 5187.log.txt Download 
    Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0, 15:28:27

Press CTRL-A Z for help on special keys

�
U-Boot SPL 2019.01-g66126341c8 (Oct 24 2019 - 03:52:25 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.8.0-v2019.08 (Terrific Llama')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Remoteproc 2 started successfully
** File not found /lib/firmware/j7-mcu-r5f0_0-fw **
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.02-rc4
NOTICE:  BL31: Built : 03:52:00, Oct 24 2019
I/TC: 
I/TC: OP-TEE version: ti2019.02-89-ge5a8779-dev (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 Thu Oct 24 03:52:22 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g66126341c8 (Oct 24 2019 - 03:52:45 +0000)
Detected: J7X-BASE-CPB rev E2
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2
ti_sci_power_domain_on: get_device(91) failed (-19)


U-Boot 2019.01-g66126341c8 (Oct 24 2019 - 03:52:45 +0000)

SoC:   J721E PG 1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM1-SOM rev E2
DRAM:  4 GiB
Flash: 0 Bytes
MMC:   ti_sci_power_domain_on: get_device(91) failed (-19)
sdhci@4f80000: 0, sdhci@4fb0000: 1
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Detected: J7X-BASE-CPB rev E2
Detected: J7X-VSC8514-ETH rev E2
Net:   eth0: ethernet@046000000
Hit any key to stop autobo 0 
=>env default -f -a
## Resetting to default environment
=>saveenv
Saving Environment to MMC... Writing to redundant MMC(0)... OK
=>reset
resetting ...�
U-Boot SPL 2019.01-g66126341c8 (Oct 24 2019 - 03:52:25 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.8.0-v2019.08 (Terrific Llama')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Remoteproc 2 started successfully
** File not found /lib/firmware/j7-mcu-r5f0_0-fw **
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.02-rc4
NOTICE:  BL31: Built : 03:52:00, Oct 24 2019
I/TC: 
I/TC: OP-TEE version: ti2019.02-89-ge5a8779-dev (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 Thu Oct 24 03:52:22 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g66126341c8 (Oct 24 2019 - 03:52:45 +0000)
Detected: J7X-BASE-CPB rev E2
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2
ti_sci_power_domain_on: get_device(91) failed (-19)


U-Boot 2019.01-g66126341c8 (Oct 24 2019 - 03:52:45 +0000)

SoC:   J721E PG 1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM1-SOM rev E2
DRAM:  4 GiB
Flash: 0 Bytes
MMC:   ti_sci_power_domain_on: get_device(91) failed (-19)
sdhci@4f80000: 0, sdhci@4fb0000: 1
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Detected: J7X-BASE-CPB rev E2
Detected: J7X-VSC8514-ETH rev E2
Net:   
Warning: ethernet@046000000 using MAC address from ROM
eth0: ethernet@046000000
Hit any key to stop autobo 0 
=>setenv serverip 192.168.1.100
=>setenv nfs_root /home/aneesh/ti-processor-sdk-linux-automotive-j7-evm-06_01_00_05/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_${kern_boot}; run get_fdt_${kern_boot}; run get_overlay_${kern_boot}; run run_kern'
=>setenv init_net 'run args_all args_net; setenv autoload no; dhcp'
=>setenv args_net 'setenv bootargs ${optargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp'
=>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 ${overlayaddr} ${overlay};fdt apply ${overlayaddr}; done'
=>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 MMC... Writing to MMC(0)... OK
=>boot
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
** Unable to read file boot.scr **
15 bytes read in 1 ms (14.6 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
am65_cpsw_start end error
am65_cpsw_start end error
am65_cpsw_start end error
am65_cpsw_start end error
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!
=> nfs
link up on port 1, speed 1000, full duplex
*** ERROR: `ipaddr' not set
=> 
link up on port 1, speed 1000, full duplex
*** ERROR: `ipaddr' not set
=> 
link up on port 1, speed 1000, full duplex
*** ERROR: `ipaddr' not set
=> dhcp
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
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16

    Hi Karthik,

    I can boot up through the sd card.

    When i try to boot up using network i am getting the problem.

    I have attched the log above.

    I am setting up the u-boot variables as tftp and nfs in script

    I have doubt with the physical connection with the evm and my host machine through ethernet .

    Can you help me to check the connection between my host and evm is perfect or not.

    Also when i boot up my evm using sd card and i try to find the ip address of evm but the i net address is in ipv6.

    Regards,

    Aneesh

  • 0 in reply to Aneesh Peram
    TI__Guru** 113810 points

    Hi Aneesh,

    If you have already prepared the SD card from the prebuilt SDK image from the installer, you will should boot to the prompt and the IP Address will be automatically acquired by the board if the network has a DHCP server running.

    If you do not have a DHCP server, then the IP Address will not be acquired. 

    Please check the network connections on your side and ensure that there is a DHCP server to serve the IP Address.

    From a quick look that seems to be the problem.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1255 points

    Hi Karthik,

    The linux host is virtual mahine on windows and i am using NAT network configuration in the virtual machineto connect with the windows and i have connected the board with the ethernet cable to the windows.

    I have a doubt with above setup. can you please help to verify wheather that setup is correct or not.

    After booting up of the kernel using sd card i cannot see the ip address of board in the minicom.

    I tried to ping the host machine from board but it is not working

    Regards,

    Aneesh

  • 0 in reply to Aneesh Peram
    TI__Guru** 113810 points

    Hi Aneesh,

    The ping will not work if the board doesn't have an IP Address.

    And, I'm not familiar with the details required to get this type of a connection that you have setup. 

    Is it possible for you to connect your Windows machine and the board to a router/switch that is running DHCP and work in that mode instead of connecting it directly to the computer?

    Regards

    Karthik