Unknown command run & higmac init fail! ping failed; host 192.168.1.1 is not alive

[SAki]

Hi,
AHB70XXT16 - I'm trying to throw software on Hisilicon 3521A motherboard. I connected the device to my computer with CP2102 usb to uart. I stopped the boot by pressing a button and spell the following commands. I created one tftp server. However, the run command does not work. Ping test fails.

Anyone have an idea about this?

Also, the network cable is plugged in, but the network lights are not lit. Does it have to burn? It turns on normally when I keep booting without pressing and holding a key. Network lights are on when turned on. But hisilicon does not light up on the command screen. Should it burn?

U-Boot 2010.06 (Aug 03 2015 - 09:22:58)
Check Flash Memory Controller v100 ... Found
SPI Nor(cs 0) ID: 0xc2 0x20 0x18
Block:64KB Chip:16MB Name:"MX25L128XX"
SPI Nor total size: 16MB
SPI Nand ID Table Version 1.4
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
hisilicon # ping 192.168.1.1
ETH0: PHY(phyaddr=1, rgmii) not link!
higmac init fail!
ping failed; host 192.168.1.1 is not alive
hisilicon # run ds
Unknown command 'run' - try 'help'
hisilicon # printenv
bootdelay=1
baudrate=115200
netmask=255.255.255.0
bootfile="uImage"
bootargs=mem=112M console=ttyAMA0,115200 root=/dev/mtdblock2 rootfstype=jffs2 mtdparts=hi_sfc:1M(boot),4M(kernel),11M(rootfs)
ethaddr=00-10-85-18-40-6
jpeg_addr=0x82000000
vobuf=0x99000000
jpgl_p=82000000 4d0000 30000
startvl_p0=0 0x99000000 768 160 96 720 576
startvl_p1=2 0x99000000 768 0 0 720 576
bootcmd=sf probe 0;sf read ${jpgl_p};decjpg;setvobg 0 0x00;startvo 0 0x24 17;startvl ${startvl_p0};setvobg 0 0x00;startvo 1 1 1;startvl ${startvl_p1};sf probe 0;sf read 0x82000000 0x100000 0x400000;bootm 0x82000000
filesize=0
serverip=192.168.1.151
ipaddr=192.168.1.150
gatewayip=192.168.1.1
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06 (Aug 03 2015 - 09:22:58)
Environment size: 755/262140 bytes
hisilicon #

 

[alastairstevenson]

All 'run' does is to execute multiple commands that have been defined in an environment variable, for convenience only.
The commands individually can still be executed.
'run' is specific to certain versions of the bootloader.

Use the 'help' command to list the available commands.

Does the 192.168.1.1 device exist on your network?

 

[SAki]

Hi,
@alastairstevenson
Thank you for the answer. I did not know the information about the run command.

The device 192.168.1.1 is on my network. TFTP server computer and motherboard are connected to this modem. But the lights on the motherboard are not on.

The list that comes with the help command is as follows;

SPI Nor total size: 16MB
SPI Nand ID Table Version 1.4
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
hisilicon # help
?       - alias for 'help'
base    - print or set address offset
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
ddr     - ddr training function
decjpg  - jpgd   - decode jpeg picture.

ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
getinfo - print hardware information
go      - start application at address 'addr'
help    - print command description/usage
loadb   - load binary file over serial line (kermit mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mtest   - simple RAM read/write test
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
saveenv - save environment variables to persistent storage
setenv  - set environment variables
setvobg - setvobg   - set vo backgroud color.
        - setvobg [dev color]
sf      - SPI flash sub-system
startgx - startgx   - open graphics layer.
        - startgx [layer addr stride x y w h]

startvl - startvl   - open video layer.
        - startvl [layer addr stride x y w h]

startvo - startvo   - open interface of vo device.
        - startvo [dev type sync]
stopgx  - stopgx   - close graphics layer.
        - stopgx [layer]
stopvl  - stopvl   - close video layer.
        - stopvl [layer]
stopvo  - stopvo   - close interface of vo device.
        - stopvo [dev]
tftp    - tftp  - download or upload image via network using TFTP protocol
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor version
hisilicon # help

 

[alastairstevenson]

Also, the network cable is plugged in, but the network lights are not lit. Does it have to burn?

That's a big problem if you want to load up some files over the LAN.
Maybe explore the USB commands, see if you can get files in that way.

 

[SAki]

@alastairstevenson
As I understand it, the network and usb interfaces are loaded after autoload. Since I stopped autoload by pressing a button, these interfaces are not loaded and not working. I couldn't find sample commands to launch them.

I threw the files into USB. But I do not know how to access USB and install it without the run command. For example, I found only run commands.

I can send files via ymodem over serial connection. But after sending the files with this method, I couldn't find an example command how to install them.

Here are my files;
web-x.cramfs.img
user-x.cramfs.img
u-boot.env.bin.img
u-boot.bin.img
romfs-x.cramfs.img
logo-x.cramfs.img
InstallDesc
custom-x.cramfs.img

hisilicon # usb
usb - USB sub-system

hisilicon # usbboot

** No boot device **
hisilicon #

 

[alastairstevenson]

Since I stopped autoload by pressing a button, these interfaces are not loaded and not working.

That's unusual - normally the ethernet interface works normally in the bootloader.