TDA4VM-Q1: Problem connecting to TDA4VM EVM from Ubuntu (VMWare) host

Hi,

VM is always a problem when it comes to Ethernet and/or UART, you really don't need a VM to check the EVM in first place.

1. Use teraterm on Windows to connect to EVM

2. On the EVM, just try assigning a static IP with the command 'ifconfig eth0 192.168.1.5'

3. Assign a static IP on windows in same subnet and then try pinging the board from Windows terminal (Make sure firewall doesn't interfere)

Regards

Vineet

Hi,

I do not see any issue with UART in Ubuntu but its never getting recognized in windows as I do not have a specific driver. Irrespective of that we want to use the kit for feature development so we want to get it fixed it in Ubuntu. 

My PC is connected to WiFi and the ethernet of device is connected to host. I am attaching the setup script log

arunshankar@ubuntu:~/ti_sdk$ ./setup.sh
-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 12.04 LTS, Ubuntu 14.04, or Ubuntu 14.04 LTS is being used, continuing..
--------------------------------------------------------------------------------

Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.

User 'arunshankar' is already apart of the 'dialout' group

-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/arunshankar/ti_sdk/targetNFS ] ^Z
[1]+ Stopped ./setup.sh
arunshankar@ubuntu:~/ti_sdk$ sudo ./setup.sh
[sudo] password for arunshankar:
-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 12.04 LTS, Ubuntu 14.04, or Ubuntu 14.04 LTS is being used, continuing..
--------------------------------------------------------------------------------

Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.

Are you running this script using sudo? The detected username is 'root'.
Verify and enter your Linux username below
[ root ]

This script will automatically add the user 'root' to the 'dialout' group
Your user was successfully added to the 'dialout' group.

Unfortunately, once a user is added to the 'dialout' group the change won't be picked up until the user logouts.
Until then you will be required to use sudo when accessing a serial device.
Please logout now and log back in so that the group changes are in effect.

Press return to continue
-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/arunshankar/ti_sdk/targetNFS ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/arunshankar/ti_sdk/targetNFS

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/arunshankar/ti_sdk/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] s
Skipping filesystem extraction
WARNING! Keeping the previous filesystem may cause compatibility problems if you are upgrading the SDK
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
/home/arunshankar/ti_sdk/targetNFS/home/root/j7-evm

The files will be available from /home/root/j7-evm on the target.

This setting can be changed later by editing Rules.make and changing the
EXEC_DIR or DESTDIR variable (depending on your SDK).

Press return to continue
Rules.make edited successfully..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will export your target filesystem for NFS access.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/arunshankar/ti_sdk/targetNFS already NFS exported, skipping..

* Stopping NFS kernel daemon [ OK ]
* Unexporting directories for NFS kernel daemon... [ OK ]
* Exporting directories for NFS kernel daemon... [ OK ]
* Starting NFS kernel daemon [ OK ]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
[ /tftpboot ]
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the tftp server in the /tftpboot directory.

Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue

/tftpboot already exists, not creating..

/tftpboot/*Image-j7-evm.bin already exists. The existing installed file can be renamed and saved under the new name.
(r) rename (o) overwrite (s) skip copy
[r] s
Skipping copy of *Image-j7-evm.bin, existing version will be used

/tftpboot/k3-j721e-common-proc-board.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-common-proc-board.dtb, existing version will be used

/tftpboot/k3-j721e-eaik.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-eaik.dtb, existing version will be used

/tftpboot/k3-j721e-proc-board-tps65917.dtb already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-proc-board-tps65917.dtb, existing version will be used

/tftpboot/k3-j721e-common-proc-board-infotainment.dtbo already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-common-proc-board-infotainment.dtbo, existing version will be used

/tftpboot/k3-j721e-eaik-csi2-ov5640.dtbo already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-eaik-csi2-ov5640.dtbo, existing version will be used

/tftpboot/k3-j721e-eaik-rpi-cam-imx219.dtbo already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-eaik-rpi-cam-imx219.dtbo, existing version will be used

/tftpboot/k3-j721e-edgeai-apps.dtbo already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-edgeai-apps.dtbo, existing version will be used

/tftpboot/k3-j721e-vision-apps.dtbo already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of k3-j721e-vision-apps.dtbo, existing version will be used

/tftpboot/ti-fs-firmware-j721e-gp.bin already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of ti-fs-firmware-j721e-gp.bin, existing version will be used

/tftpboot/ti-fs-firmware-j721e-hs-cert.bin already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of ti-fs-firmware-j721e-hs-cert.bin, existing version will be used

/tftpboot/ti-fs-firmware-j721e-hs-enc.bin already exists. The existing installed file can be renamed and saved under the new name.
(o) overwrite (s) skip copy
[o] s
Skipping copy of ti-fs-firmware-j721e-hs-enc.bin, existing version will be used

/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..

Restarting tftp server
xinetd stop/waiting
xinetd start/running, process 11344
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development

For boards that contain a USB-to-Serial converter on the board such as:
* BeagleBone
* Beaglebone Black
* AM335x EVM-SK
* AM57xx EVM
* K2H, K2L, and K2E EVMs

the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.

For other boards, the serial will defualt to /dev/ttyS0. Please update based
on your setup.

--------------------------------------------------------------------------------

NOTE: If your using any of the above boards simply hit enter
and the correct port will be determined automatically at a
later step. For all other boards select the serial port
that the board is connected to.
Which serial port do you want to use with minicom?
[ /dev/ttyS0 ] ttyUSB0

Copied existing /home/arunshankar/.minirc.dfl to /home/arunshankar/.minirc.dfl.old

Configuration saved to /home/arunshankar/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
--------------------------------------------------------------------------------
Autodetected the following ip address of your host, correct it if necessary
[ 192.168.0.20 ]

Select Linux kernel location:
1: TFTP
2: SD card

[ 1 ] 1

Select root file system location:
1: NFS
2: SD card

[ 1 ] 1

Available kernel images in /tftproot:
Image-j7-evm.bin
k3-j721e-common-proc-board-infotainment.dtbo
k3-j721e-common-proc-board.dtb
k3-j721e-eaik-csi2-ov5640.dtbo
k3-j721e-eaik-rpi-cam-imx219.dtbo
k3-j721e-eaik.dtb
k3-j721e-edgeai-apps.dtbo
k3-j721e-proc-board-tps65917.dtb
k3-j721e-vision-apps.dtbo
ti-fs-firmware-j721e-gp.bin
ti-fs-firmware-j721e-hs-cert.bin
ti-fs-firmware-j721e-hs-enc.bin

Which kernel image do you want to boot from TFTP?
[ Image-j7-evm.bin ]
--------------------------------------------------------------------------------
Would you like to create a minicom script with the above parameters (y/n)?
[ y ] y

Successfully wrote /home/arunshankar/ti_sdk/bin/setupBoard.minicom

Detecting connection to board... /dev/ttyUSB2

--------------------------------------------------------------------------------
Would you like to run the setup script now (y/n)?

Please connect the ethernet cable as described in the Quick Start Guide.
Once answering 'y' on the prompt below, you will have 300 seconds to connect
the board and power cycle it before the setup times out

After successfully executing this script, your EVM will be set up. You will be
able to connect to it by executing 'minicom -w' or if you prefer a windows host
you can set up Tera Term as explained in the Software Developer's Guide.
If you connect minicom or Tera Term and power cycle the board Linux will boot.

[ y ] y

Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Nov 15 2018, 20:20:04.
Port /dev/ttyUSB2, 15:09:53

Press CTRL-A Z for help on special keys

Hi Arun,

Arunshankar Dhandayuthapany said:

I do not see any issue with UART in Ubuntu but its never getting recognized in windows as I do not have a specific driver. Irrespective of that we want to use the kit for feature development so we want to get it fixed it in Ubuntu. 

My PC is connected to WiFi and the ethernet of device is connected to host. I am attaching the setup script log

Ok, and what issue do you see here, I fail to notice anything stand out in the logs. If you can't see UART port on Windows but see it on VM it's fine. You should be able to work with that

Is your problem still the ethernet connection with VM ? Have you tried setting a fixed IP and then pinging from Windows machine ?

Also let me know which SDK version this is

Regards

Vineet

SDK version: ti-processor-sdk-linux-j7-evm-08_00_00_08

Ethernet connection - PC -> EVM is this correct?

I assume you mean setting static IP in EVM. As I informed before EVM does not provide root access ie I cannot access its command line through Minicom and I cannot use it in windows as its driver not detecting. 

My understanding(correct me if wrong)

EVM does not have base set up as ./setup.sh is not able to complete NFS and TFTP to have kernel and file system

env default -f -a
## Resetting to default environment
=> saveenv
Saving Environment to MMC... Writing to redundant MMC(0)... OK
=> setenv serverip 192.168.0.109
=> setenv nfs_root /home/arunshankar/ti_sdk/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_overl
ay_${kern_boot}; run run_kern'
=> 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=${serverip}:${nfs_root},${nfs_options} ip=dhcp'
> setenv get_kern_net 'tftp ${loadaddr} ${name_kern}'
> help
<INTERRUPT>
=> 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=${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 overla
y 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
0 bytes read in 1 ms (0 Bytes/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
link up on port 1, speed 1000, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 23
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 23
DHCP client bound to address 192.168.0.110 (1017 ms)
link up on port 1, speed 1000, full duplex
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 23
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 23
DHCP client bound to address 192.168.0.110 (1065 ms)
link up on port 1, speed 1000, full duplex
Using ethernet@46000000 device
TFTP from server 192.168.0.1; our IP address is 192.168.0.110
Filename 'Image-j7-evm.bin'.
Load address: 0x82000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
link up on port 1, speed 1000, full duplex
Using ethernet@46000000 device
TFTP from server 192.168.0.1; our IP address is 192.168.0.110
Filename 'k3-j721e-common-proc-board.dtb'.
Load address: 0x88000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
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!

printenv response in Uboot

addr_fit=0x90000000
arch=arm
args_all=setenv optargs earlycon=ns16550a,mmio32,0x02800000 ${mtdparts}
args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUI
D=${uuid} rw rootfstype=${mmcrootfstype}
args_net=setenv bootargs console=${console} ${optargs} rootfstype=nfs root=/dev/
nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp
args_ufs=setenv devtype scsi;setenv bootpart 1:1;run ufs_finduuid;setenv bootarg
s console = ${console} ${optargs}root=PARTUUID=${uuid} rw rootfstype=${scsirootf
stype};setenv devtype scsi;setenv bootpart 1:1
autoload=no
baudrate=115200
board=j721e
board_name=j721e
boot=mmc
boot_fdt=try
boot_fit=0
boot_rprocs=if test ${dorprocboot} -eq 1 && test ${boot} = mmc; then rproc init;
run boot_rprocs_mmc;fi;
boot_rprocs_mmc=env set rproc_id;env set rproc_fw;for i in ${rproc_fw_binaries}
; do if test -z "${rproc_id}" ; then env set rproc_id $i;else env set rproc_fw $
i;run rproc_load_and_boot_one;env set rproc_id;env set rproc_fw;fi;done
bootargs=console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 mtdparts=470
40000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128
k(ospi.env.backup),1m(ospi.sysfw),57216k@8m(ospi.rootfs),128k(ospi.phypattern);4
7034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env
),1m(hbmc.sysfw),-@8m(hbmc.rootfs) rootfstype=nfs root=/dev/nfs rw nfsroot=192.1
68.0.1:/home/arunshankar/ti_sdk/targetNFS,nolock,v3,tcp,rsize=4096,wsize=4096 ip
=dhcp
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_b
oot}; run run_kern
bootdelay=2
bootdir=/boot
bootenvfile=uEnv.txt
bootm_size=0x10000000
bootpart=1:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
console=ttyS2,115200n8
cpu=armv8
default_device_tree=k3-j721e-common-proc-board.dtb
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;tib
oot3.bin.raw raw 0x0 0x400 mmcpart 1;tispl.bin.raw raw 0x400 0x1000 mmcpart 1;u-
boot.img.raw raw 0x1400 0x2000 mmcpart 1;u-env.raw raw 0x3400 0x100 mmcpart 1;sy
sfw.itb.raw raw 0x3600 0x800 mmcpart 1
dfu_alt_info_mmc=boot part 1 1;rootfs part 1 2;tiboot3.bin fat 1 1;tispl.bin fat
1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1;sysfw.itb fat 1 1
dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000;tispl.bin raw 0x080000 0x200000;u
-boot.img raw 0x280000 0x400000;u-boot-env raw 0x680000 0x020000;sysfw.itb raw 0
x6c0000 0x100000;rootfs raw 0x800000 0x3800000
dfu_alt_info_ram=tispl.bin ram 0x80080000 0x100000;u-boot.img ram 0x81000000 0x1
00000
dfu_bufsiz=0x40000
dnsip=75.75.75.75
dorprocboot=0
dtboaddr=0x89000000
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmc
dev};if run loadbootscript; then run bootscript;else if run loadbootenv; then ec
ho Loaded env from ${bootenvfile};run importbootenv;fi;if test -n $uenvcmd; then
echo Running uenvcmd ...;run uenvcmd;fi;fi;fi;
ethact=ethernet@46000000
fdt_addr_r=0x88000000
fdtaddr=0x88000000
fdtfile=k3-j721e-common-proc-board.dtb
fileaddr=82000000
filesize=0
findfdt=setenv name_fdt ${default_device_tree};setenv fdtfile ${name_fdt}
finduuid=part uuid mmc ${bootpart} uuid
gatewayip=192.168.0.1
get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${name_fdt}
get_fdt_net=tftp ${fdtaddr} ${name_fdt}
get_fdt_ufs=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
get_fit_mmc=load mmc ${bootpart} ${addr_fit} ${bootdir}/${name_fit}
get_kern_mmc=load mmc ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_kern_net=tftp ${loadaddr} ${name_kern}
get_kern_ufs=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_overlay_mmc=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $name_
overlays;do;load mmc ${bootpart} ${dtboaddr} ${bootdir}/${overlay} && fdt apply
${dtboaddr};done;
get_overlay_net=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in ${over
lay_files};do;tftp ${overlayaddr} ${overlay};fdt apply ${overlayaddr}; done
get_overlay_ufs=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $name_
overlays;do;load scsi ${bootpart} ${dtboaddr} ${bootdir}/${overlay} && fdt apply
${dtboaddr};done;
get_overlaystring=for overlay in $name_overlays;do;setenv overlaystring ${overla
ystring}'#'${overlay};done;
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${
loadaddr} ${filesize}
init_mmc=run args_all args_mmc
init_net=run args_all args_net; setenv autoload no; dhcp
init_ufs=ufs init; scsi scan; run args_ufs
ipaddr=192.168.0.110
kern_boot=net
kernel_addr_r=0x82000000
loadaddr=0x82000000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
loadbootscript=load mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
loadimage=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
mmcboot=mmc dev ${mmcdev}; devnum=${mmcdev}; setenv devtype mmc; if mmc rescan;
then echo SD/MMC found on device ${mmcdev};if run loadimage; then run args_mmc;
if test ${boot_fit} -eq 1; then run run_fit; else run mmcloados;fi;fi;fi;
mmcdev=1
mmcloados=if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadf
dt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bo
otz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcrootfstype=ext4 rootwait
mtdids=nor0=47040000.spi.0,nor0=47034000.hyperbus
mtdparts=mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boo
t),128k(ospi.env),128k(ospi.env.backup),1m(ospi.sysfw),57216k@8m(ospi.rootfs),12
8k(ospi.phypattern);47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.
u-boot),256k(hbmc.env),1m(hbmc.sysfw),-@8m(hbmc.rootfs)
name_fdt=k3-j721e-common-proc-board.dtb
name_fit=fitImage
name_kern=Image-j7-evm.bin
netmask=255.255.255.0
nfs_options=nolock,v3,tcp,rsize=4096,wsize=4096
nfs_root=/home/arunshankar/ti_sdk/targetNFS
optargs=earlycon=ns16550a,mmio32,0x02800000 mtdparts=47040000.spi.0:512k(ospi.ti
boot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128k(ospi.env.backup),1m(os
pi.sysfw),57216k@8m(ospi.rootfs),128k(ospi.phypattern);47034000.hyperbus:512k(hb
mc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),1m(hbmc.sysfw),-@8m(hb
mc.rootfs)
partitions=name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}
pxefile_addr_r=0x80100000
ramdisk_addr_r=0x88080000
rd_spec=-
rdaddr=0x88080000
rootfs_boot=net
rproc_fw_binaries=2 /lib/firmware/j7-main-r5f0_0-fw 3 /lib/firmware/j7-main-r5f0
_1-fw 4 /lib/firmware/j7-main-r5f1_0-fw 5 /lib/firmware/j7-main-r5f1_1-fw 6 /lib
/firmware/j7-c66_0-fw 7 /lib/firmware/j7-c66_1-fw 8 /lib/firmware/j7-c71_0-fw
rproc_load_and_boot_one=if load mmc ${bootpart} $loadaddr ${rproc_fw}; then if r
proc load ${rproc_id} ${loadaddr} ${filesize}; then rproc start ${rproc_id};fi;f
i
run_fit=bootm ${addr_fit}#${fdtfile}${overlaystring}
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
scriptaddr=0x80000000
scsirootfstype=ext4 rootwait
serverip=192.168.0.1
setup_mmc=
setup_net=setenv autoload no; dhcp
soc=k3
ufs_finduuid=part uuid scsi ${bootpart} uuid
update_to_fit=setenv loadaddr ${addr_fit}; setenv bootfile ${name_fit}
vendor=ti

Environment size: 7160/131067 bytes

Adding additional info:

Pinged the server fro Uboot and it was able to reach server

=> ping 192.168.0.1
link up on port 1, speed 1000, full duplex
Using ethernet@46000000 device
host 192.168.0.1 is alive

Hi,

Sorry for the delay. Is the issue resolved ? Do you still need help ?

Regards

Vineet