Hi All.
When we stop auto-booting and printenv, a serverip is listed. However, when trying to ftp a kernel-image, it shows serverip is not set.
##################################################################### => printenv baudrate=115200 bootcmd=run load_img; run load_dtb; booti 0x48080000 - 0x48000000 bootdelay=3 ethact=ravb ethaddr=2E:09:0A:01:A0:6D fdt_high=0xffffffffffffffff fileaddr=7a000000 filesize=f0d200 initrd_high=0xffffffffffffffff ipaddr=192.168.0.2 load_dtb=tftpboot 0x48000000 hidden load_img=tftpboot 0x48080000 Image load_ker=ext4load mmc 0:1 0x48080000 /boot/Image loadimg=tdtbftpboot 048000000 hidden serverip=192.168.56.1 stderr=serial stdin=serial stdout=serial ver=U-Boot 2015.04 (Mar 28 2018 - 16:00:07)
Environment size: 587/131068 bytes => setenv bootargs => tftp 0x7a000000 Image ravb:0 is connected to ravb. Reconnecting to ravb ravb Waiting for PHY auto negotiation to complete..... done ravb: 1000Base/Full *** ERROR: `serverip' not set #####################################################################
If I then indeed set a serverip, two copies of serverip are listed .. !!
##################################################################### => setenv serverip 192.168.0.1 => saveenv Saving Environment to MMC... Writing to MMC(1)... done => printenv baudrate=115200 bootcmd=run load_img; run load_dtb; booti 0x48080000 - 0x48000000 bootdelay=3 ethact=ravb ethaddr=2E:09:0A:01:A0:6D fdt_high=0xffffffffffffffff fileaddr=7a000000 filesize=f0d200 initrd_high=0xffffffffffffffff ipaddr=192.168.0.2 load_dtb=tftpboot 0x48000000 hidden load_img=tftpboot 0x48080000 Image load_ker=ext4load mmc 0:1 0x48080000 /boot/Image loadimg=tdtbftpboot 048000000 hidden serverip=192.168.56.1 serverip=192.168.0.1 stderr=serial stdin=serial stdout=serial ver=U-Boot 2015.04 (Mar 28 2018 - 16:00:07)
Environment size: 610/131068 bytes #####################################################################
In summary, whatever I do, I am unable to clear the entry serverip=192.168.56.1 (already tried editenv, still did not work).
Anybody else faced a similar issue? Or there is no option but to go the build-uboot -> flash -> debug route? (Wanting to avoid it, as currently the uboot has been shipped with the device directly, so don't want to change too many things).
Thanks and Regards, Ajay