Is it possible to recover if ethernet doesn't work and no Linux or failsafe?

When I performed the upgrade, it bricked my Linux - no WiFi, no Ethernet. I have been trying to recover using these instructions. But this depends on being able to establish communications via the Ethernet wired connection. This is the one thing I cannot confirm worked prior to upgrading (never had a need for it) so I am hoping there is some procedure I can follow to get it to work. I have tried:

  1. patch cable to my router - WAN led blinks orange, router LED indicates connection, but no IP address is registered on the device table in my router (also tftp server cannot find it)
  2. patch cable to PC - WAN LED blinks orange and the PC (Win7) indicates an "unknown connection", No internet (expected) but the tftp server still cannot connect. I tried setting the PC to 192.168.0.37 and the Yun to 192.168.0.64 as well as leaving the Yun at 192.168.1.2 and the PC at 192.168.1.3.
  3. cross-over cable to PC - same result as patch

Also, in the terminal I see:
U-Boot 1.1.4-gd995931a-dirty (Aug 7 2013 - 16:16:04)
...
ATHRS26: s26 reset done
eth1 up
eth0, eth1

Does the "-dirty" label imply something is amiss? Is it recoverable?

Here is the log from one of my attempts. I should mention that I have successfully used the tftp server for other projects in the past so I am confident it is configured and running.

U-Boot 1.1.4-gd995931a-dirty (Aug  7 2013 - 16:16:04)

Arduino Yun (ar9331) U-boot

DRAM:  64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 142k for U-Boot at: 83fdc000
Reserving 192k for malloc() at: 83fac000
Reserving 44 Bytes for Board Info at: 83fabfd4
Reserving 36 Bytes for Global Data at: 83fabfb0
Reserving 128 for oot aram() at 83f8fb0
tackPoiner a: 83fbf98
Now running in RAM - U-Boot at: 83fdc000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18
flash size 16777216, sector count =256
Flash 16 M
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7240_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
: cfg1 0x5 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
: cfg1 0xf cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
athrs26_reg_init_lan
ATHRS26: resetting s26
ATHRS26: s26 reset done
eth1 up
eth0, eth1
Hit any key to stop autoboot:  4  3  2  1  0 
ar7240> setenv serverip 192.168.1.3

ar7240> tftp 0x80060000 openwrt-ar71xx-generic-linino-u-boot.bin;

dup 1 speed 100
Using eth0 device
TFTP from server 192.168.1.3; our IP address is 192.168.1.2
Filename 'openwrt-ar71xx-generic-linino-u-boot.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.3; our IP address is 192.168.1.2
Filename 'openwrt-ar71xx-generic-linino-u-boot.bin'.
Load address: 0x80060000
Loading: *T T T T T T T T T T 
Retry count exceeded; starting again
eth1 link down
FAIL
...

You did almost everything: you just skipped a step

setenv ipaddr 192.168.0.146;

TickTock:

  1. patch cable to my router - WAN led blinks orange, router LED indicates connection, but no IP address is registered on the device table in my router (also tftp server cannot find it)

Indeed the router will NOT assign an IP, you have to input one: pick one that is not used by one of your home computers

TickTock:
Does the "-dirty" label imply something is amiss? Is it recoverable?

No, that's just a label

I did that deliberately for this particular log. I had done a printenv to learn that the ipaddr default address is 192.168.1.2 so I tried putting my PC on 192.168.1.3 for a peer2peer connection on this attempt. I have tried many different permutations trying to get it to connect (including setting the ipaddr to 192.168.0.64 and serverip to 192.168.0.41 using the router - my DHCP assigns to 192.168.0.x). I have not even been able to get a ping back from the Yun with any of the attempts although the router does indicate it has a connection on the front panel indicator and the WAN LED on the Yun sometimes blinks orange erratically like it is getting traffic.

So.. no other way to recover when ethernet is down? Can I use the microSD or did I just buy a $75 paperweight?

TickTock:

[quote author=Federico Fissore link=topic=261471.msg1846716#msg1846716 date=1408374748]
You did almost everything: you just skipped a step

setenv ipaddr 192.168.0.146;

I did that deliberately for this particular log. I had done a printenv to learn that the ipaddr default address is 192.168.1.2 so I tried putting my PC on 192.168.1.3 for a peer2peer connection on this attempt. I have tried many different permutations trying to get it to connect (including setting the ipaddr to 192.168.0.64 and serverip to 192.168.0.41 using the router - my DHCP assigns to 192.168.0.x). I have not even been able to get a ping back from the Yun with any of the attempts although the router does indicate it has a connection on the front panel indicator and the WAN LED on the Yun sometimes blinks orange erratically like it is getting traffic.
[/quote]Like so many others, you are a bit thin on some of the networking info, considering that you mention both 192.168.1.x and 192.168.0.x IP addresses. Assuming a default /24 netmask (255.255.255.0 in dotted-decimal notation), those addresses don't mix.
If you are running Windows on your host PC, download and run "Angry IP Scanner" one the host PC's subnet (class C?) range. Maybe the IP address assigned to the Yun is not what you think it is...

Ralf

Thanks for the suggestions. At this point I am open to any ideas but in particular I'd like to know if the uSD can be used by uboot. Sorry for the lack of details. I have tried dozens of scenarios and didn't want to clutter the post with minutia (it would have been pages long if I documented all my attempts). I think that was a good call since, even shortened, the point about the 192.168.1.x being a different experiment than the 192.168.0.x was overlooked. Yes, I am using 255.255.255.0. I have done this dozens of times with other devices so it's either some unique configuration requirement with the Yun or the ethernet driver is corrupt. I did, however, go ahead and try the AngryIP app but was unable to locate any "stray" responders.

I am new to uboot. I found a list of commands here and briefly got my hopes up that ext2load could be a means to use the uSD instead of tftp, but it appears those commands are not supported on this version of uboot. Anyone have any suggestions on how to do an update without ethernet (wired or wireless)?

TickTock:
... I have not even been able to get a ping back from the Yun with any of the attempts although the router does indicate it has a connection on the front panel indicator and the WAN LED on the Yun sometimes blinks orange erratically like it is getting traffic.

No Internet Control Message Protocols (ICMP) support at Uboot.

Testing tftp server setup.

http://www.gunnalag.com/2013/08/05/how-to-test-tftp-server-from-a-client-system-in-windows/

tftp -i 192.168.2.40 GET openwrt-ar71xx-generic-yun-16M-rootfs-squashfs.bin

Plan B: get RMA from vendor.

TickTock:
I did that deliberately for this particular log. I had done a printenv to learn that the ipaddr default address is 192.168.1.2 so I tried putting my PC on 192.168.1.3 for a peer2peer connection on this attempt.

If I understood correctly, you tried following a modified version of the instructions and that failed, right?
If so, can you now try to follow them exactly, without using commands that are not mentioned, step by step?

We struggle to make complicated things simple: make everyone happy by finding what's not working on that instructions or by making them even simpler.

That was the very first thing I tried.

OK. I went back and repeated the instructions exactly (even matching IPs this time). On the PC, I brought up Properties of the connection, went to TCP/IPv4 settings, selected "Used the following IP address", entered 192.168.0.231 and 255.255.255.0. Clicked OK. Opened a cmd prompt, typed IPCONFIG /ALL to confirm the IP was set. Then I reset the Yun and followed the instructions. Here is the Serial output:

U-Boot 1.1.4-gd995931a-dirty (Aug  7 2013 - 16:16:04)

Arduino Yun (ar9331) U-boot

DRAM:  64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 142k for U-Boot at: 83fdc000
Reserving 192k for malloc() at: 83fac000
Reserving 44 Bytes for Board Info at: 83fabfd4
Reserving 36 Bytes for Global Data at: 83fabfb0
Reserving 128 forbootparam() at 83fbfb0
Stac Poiner at 83fbf98
Now running in RAM - U-Boot at: 83fdc000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18
flash size 16777216, sector count  256
Flash 16MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7240_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
: cfg1 0x5 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
: cfg1 0xf cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
athrs26_reg_init_lan
ATHRS26: resetting s26
ATHRS26: s26 reset done
eth1 up
eth0, eth1
Hit any key to stop autoboot:  4  0 
ar7240> setenv serverip 192.168.0.231

ar7240> setenv ipaddr 192.168.0.146

ar7240> tftp 0x80060000 openwrt-ar71xx-generic-yun-16M-kernel.bin;

dup 1 speed 100
Using eth0 device
TFTP from server 192.168.0.231; our IP address is 192.168.0.146
Filename 'openwrt-ar71xx-generic-yun-16M-kernel.bin'.
Load address: 0x80060000
Loading: *T T T T T T T T T T 
Retry count exceeded; starting again
eth1 link down
FAIL

I then went back to the PC and typed ping 192.168.0.146 and got the following response:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : <deleted>
   Primary Dns Suffix  . . . . . . . : <deleted>
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : <deleted>

Wireless LAN adapter Wireless Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205
   Physical Address. . . . . . . . . : <deleted>
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
   Physical Address. . . . . . . . . : <deleted>
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.231(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\>ping 192.168.0.146

Pinging 192.168.0.146 with 32 bytes of data:
Reply from 192.168.0.231: Destination host unreachable.
Reply from 192.168.0.231: Destination host unreachable.
Reply from 192.168.0.231: Destination host unreachable.
Reply from 192.168.0.231: Destination host unreachable.

Ping statistics for 192.168.0.146:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\>

In all my subsequent tests, I just tried the ping. If I cannot ping the Yun, tftp isn't going to work. I have also tried on a completely different (but also Win7) computer with the same results.

I guess I failed to mention that I connected a patch cord between the PC and the Yun (tried both patch and crossover - result is the same). The WAN light blinks and then goes steady orange after a minute or so but no communication. If I send another ping, the orange LED starts blinking again (but still see "host unreachable" on the PC).

sonnyyu:
...
No Internet Control Message Protocols (ICMP) support at Uboot.

Testing tftp server setup.

How to test TFTP server from a Client system in Windows – GUNNALAG

tftp -i 192.168.2.40 GET openwrt-ar71xx-generic-yun-16M-rootfs-squashfs.bin

...

at tftp/uboot stage no ICMP/ping support at Yun.

Very last thing turn off windows' firewall and antivirus software, use second windows machine substitute Yun to test tftp server setup.

If you can not got RMA, then unsolder flash IC, re-flash it might be last resolve.

Thanks. I use the tftp server by solarwinds and have been successful using that with other devices. I did order a 2nd Yun so I will confirm that it connects properly before submitting the RMA.

Just for grins, I downloaded the tftp utility suggested in the instructions with the same results.

OK. New Yun arrived today. Plugged it in and tried the tftp procedure. Worked first try (see below) but I stopped short of committing it to the flash - learned my lesson. Going to request an RMA on the first and send it back. Key take-away : if it ain't broke, don't fix it.

U-Boot 1.1.4-gd995931a-dirty (Aug  7 2013 - 16:16:04)

Arduino Yun (ar9331) U-boot

DRAM:  64 MB
Top of RAM usable for U-Boot at: 84000000
Reserving 142k for U-Boot at: 83fdc000
Reserving 192k for malloc() at: 83fac000
Reserving 44 Bytes for Board Info at: 83fabfd4
Reserving 36 Bytes for Global Data at: 83fabfb0
Reserving 128k for boot params() at: 83f8bfb0
Stack Pointer at: 83f8bf98
Now running in RAM - U-Boot at: 83fdc000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x18
flash size 16777216, sector count = 256
Flash: 16 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7240_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
: cfg1 0x5 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
: cfg1 0xf cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
athrs26_reg_init_lan
ATHRS26: resetting s26
ATHRS26: s26 reset done
eth1 up
eth0, eth1
Hit any key to stop autoboot:  4  3  2  1  0 
ar7240> setenv serverip 192.168.0.37;

ar7240> setenv ipaddr 192.168.0.42;

ar7240> tftp 0x80060000 openwrt-ar71xx-generic-yun-16M-kernel.bin;

dup 1 speed 100
Using eth0 device
TFTP from server 192.168.0.37; our IP address is 192.168.0.42
Filename 'openwrt-ar71xx-generic-yun-16M-kernel.bin'.
Load address: 0x80060000
Loading: *#################################################################
	 #################################################################
	 #################################################################
	 #################################################
done
Bytes transferred = 1245184 (130000 hex)
ar7240>

Once you set the IP on your PC, were you still able to access internet? If not, there is a routing problem and that's why the yun cannot access the pc (and viceversa)

Never had any problems accessing the internet. Irrelevant, though, at this point now that I've proven that the Yun was the problem (if it was a router or other external problem, the new Yun wouldn't work either).

TickTock:
...
if it ain't broke, don't fix it.
...

1+

sonnyyu:

TickTock:
...
if it ain't broke, don't fix it.
...

1+

Well, all depends on how you define "broke"... :wink:

Ralf