Jump to content
WWVB

Micro-USB ETH1 Port Dead

Recommended Posts

Up until yesterday, I was able to attach the micro-USB cable to ETH1 on the Tetra and would be presented with a USB-Ethernet port on my computer.  Today, this no longer happens.

I have:

  • confirmed that the cable is not the issue as when I move to the UART port, it is presented to my computer with no issue
  • SSH'd in via WiFi and bounced ETH1 up/down several times from the command line (ifconfig eth1 up / down)
  • performed a factory reset of the Tetra, but the problem still persists
  • NOT performed a firmware reset as ETH1 is needed to recover from that, so my fear is that if the ETH1 port is dead, I will not be able to complete a firmware recovery

I am running a Linux Ubuntu 18.04 VM on a Macbook Pro using VMware Fusion. (As mentioned before, the UART does present to the Macbook host and the Ubuntu VM when connected)

Here is the networking info from the web interface:

br-lan    Link encap:Ethernet  HWaddr 00:13:37:A7:34:BB
          inet addr:172.16.42.1  Bcast:172.16.42.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:39338 errors:0 dropped:234 overruns:0 frame:0
          TX packets:61354 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9940063 (9.4 MiB)  TX bytes:32841110 (31.3 MiB)

eth0      Link encap:Ethernet  HWaddr 00:13:37:A7:34:BD
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:5

eth1      Link encap:Ethernet  HWaddr 00:13:37:A7:34:BB
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:862 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:224358 (219.0 KiB)
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:651 errors:0 dropped:0 overruns:0 frame:0
          TX packets:651 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:61665 (60.2 KiB)  TX bytes:61665 (60.2 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:13:37:A7:34:BB
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:576 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:191856 (187.3 KiB)

wlan0-1   Link encap:Ethernet  HWaddr 02:13:37:A7:34:BB
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38797 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61455 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10396517 (9.9 MiB)  TX bytes:34575925 (32.9 MiB)

wlan1     Link encap:Ethernet  HWaddr 00:13:37:A7:34:BC
          inet addr:10.20.20.152  Bcast:10.20.20.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69911 errors:0 dropped:594 overruns:0 frame:0
          TX packets:34144 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:34275165 (32.6 MiB)  TX bytes:9419920 (8.9 MiB)

 

Please advise with additional troubleshooting steps.

Thank you!

Share this post


Link to post
Share on other sites
17 minutes ago, WWVB said:

NOT performed a firmware reset as ETH1 is needed to recover from that, so my fear is that if the ETH1 port is dead, I will not be able to complete a firmware recovery

Actually you can use this as a test - follow the process of booting up with reset help to invoke uboot recovery.  sort your network as per instructions etc. If you don't flash a file and just power cycle the pineapple it will boot like normal again after. But if the USB eth (eth1) works with uboot recovery but not in normal boot you might still have a chance of complete restoration from a firmware recovery.

Also just to rule it out did you try on another hardware machine?

Edited by Just_a_User

Share this post


Link to post
Share on other sites

Thank you @Just_a-User!  The micro-USB ETH1 port did function while following this procedure.  I have the Tetra plugged into a wall outlet for power, have downloaded upgrade-2.5.4.bin, confirmed the SHA-256 hash and pushed it to the Tetra following the procedure.  I received the notice:

UPDATE IN PROGRESS

Your file was successfully uploaded! Update is in progress and you should wait for automatic reset of the device.
Update time depends on image size and may take up to a few minutes. You can close this page.

and have waited in excess of 20-minutes for the Tetra to reboot.  Thus far, no automatic reboot of the Tetra and the yellow LED remains solid.  

I am no longer able to ping 192.168.1.1, so I will leave it plugged in and see if it eventually reboots.

Share this post


Link to post
Share on other sites
5 minutes ago, WWVB said:

have downloaded upgrade-2.5.4.bin, confirmed the SHA-256 hash and pushed it to the Tetra following the procedure.

Thats an upgrade file not the factory version of the frimware mentioned in the firmware recovery instructions - use this link or scroll to the bottom of tetra firmware download screen. See if that improves your results.

Edited by Just_a_User

Share this post


Link to post
Share on other sites
8 minutes ago, WWVB said:

I am no longer able to ping 192.168.1.1, so I will leave it plugged in and see if it eventually reboots.

It will try to flash and then reboot returning to the 172.16.42.1:1471 address, so you have to reconfigure your network settings and browse there after flashing.

Share this post


Link to post
Share on other sites

Thank you @Just_a-User, this appears to have worked!  My newb status is showing as I was mislead by the 'Firmware' heading and did not scroll down to see what else is there.

micro-USB ETH1 is back to functioning.  Will continue on with the device configuration.

Thank you again!

WiFi Pineapple TETRA Firmware

Search
 
 
Release Date Version SHA256 Checksum  
2019-04-25 2.5.4 48a6a55e37223da27c69fd6e70b2af3b7859dbe401de01865049e03a469cf8dd cloud_download
 
 
description
 
 
       

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...