uboot msg, eth1 link down FAIL

Hardware Arduino Yún
1

Hello-
I think my yun may be borked, i"ve tried (almost) everything I could find on the interwebs. Ended up with uboot, after monkeying around with it for awhile this is the end result below.

The Yun I have is 1st gen I believe as i"ve had it for 3 or 4 years. The Arduino processor works fine and the linux processor seems to work but the wifi chip doesn"t seem to want to play nice.

Bricked?

Gah! It just keep getting better....cant access the terminal anymore as the usb light is always on. One good thing, the arduino chip still loads code so I guess I have a really expensive Arduino board unless someone is aware of a workaround.

Second thought, I think i"ll just beat it to death with a hammer, (its not the yuns fault, but it hurts too much when I hit me with a hammer)

U-Boot 1.1.5-linino-g17593166-dirty (Oct  4 2015 - 02:12:32)

Linino Board (ar9331) U-boot
DRAM:  64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 218k for U-Boot at: 83fc8000
Reserving 192k for malloc() at: 83f98000
Reserving 44 Bytes for Board Info at: 83f97fd4
Reserving 36 Bytes for Global Data at: 83f97fb0
Reserving 128k for boot params() at: 83f77fb0
Stack Pointer at: 83f77f98
Now running in RAM - U-Boot at: 83fc8000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18
flash size 16777216, sector count = 256
Flash: 16 MB
In:    serial
Out:   serial
Err:   serial
Net:   eth0: b4:21:8a:00:00:00
eth1: b4:21:8a:00:00:01
eth0, eth1
autoboot in 4 seconds (stop with 'lin')...
linino> 

linino> 

linino> setenv 192.168.128.44

linino> 

linino> setenv 192.168.128.45

linino> 

linino> erase 0x9f000000 +0x40000

Erase Flash from 0x9f000000 to 0x9f03ffff in Bank # 1 
First 0x0 last 0x3 sector size 0x10000
   0   1   2   3
Erased 4 sectors
linino> 

Erase Flash from 0x9f000000 to 0x9f03ffff in Bank # 1 
First 0x0 last 0x3 sector size 0x10000
   0   1   2   3
Erased 4 sectors
linino> cp.b $fileaddr 0x9f000000 $filesize

Usage:
cp      - memory copy

linino> 

Usage:
cp      - memory copy

linino> erase 0x9f040000  +0x10000

Erase Flash from 0x9f040000 to 0x9f04ffff in Bank # 1 
First 0x4 last 0x4 sector size 0x10000
   4
Erased 1 sectors
linino> 

Erase Flash from 0x9f040000 to 0x9f04ffff in Bank # 1 
First 0x4 last 0x4 sector size 0x10000
   4
Erased 1 sectors
linino> tftp 0x80060000 openwrt-ar71xx-generic-yun-16M-kernal.bin

dup 1 speed 100
Using eth0 device




TFTP from server 192.168.1.1; our IP address is 192.168.1.2
Filename 'openwrt-ar71xx-generic-yun-16M-kernal.bin'.
Load address: 0x80060000
Loading: *T T T T T T T T T T 
Retry count exceeded; starting again
eth1 link down
FAIL
Using eth0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.2
Filename 'openwrt-ar71xx-generic-yun-16M-kernal.bin'.
Load address: 0x80060000
Loading: *T T T T T T T T T T 
Retry count exceeded; starting again
eth1 link down
FAIL
2

Thank you for including the full output of your procedure, and not just the error message (or even worse, a paraphrased version of the error message!) Having the full details is greatly improves the chances of figuring out what is happening.

potentiometer:

linino> setenv 192.168.128.44

linino> setenv 192.168.128.45

I don't believe these statements are accomplishing anything. I think what you intended to enter is:

linino> setenv serverip 192.168.128.44
linino> setenv ipaddr 192.168.128.45

The setenv command sets an environment variable (given by the first argument) to a value (given by the second argument.) For example, the last statement above sets the variable "ipaddr" to the value "192.168.128.45". In your statements, you are only including one argument, so you are defining the variable "192.168.128.44" and giving it nothing as a value.

What you are trying to do with these statements is define the IP address of the Yun, and the TFTP server it is to contact to download the software image. Without the serverip and ipaddr variables being set properly, uboot uses default values to contact the server:

TFTP from server 192.168.1.1; our IP address is 192.168.1.2

I would retry the process, but make sure to enter the setenv commands accurately.