Jump to content

Tetra Solid Yellow light, fails to completely boot


Dystrakti0n

Recommended Posts

Powered the tetra up out of the box, got a solid yellow light on power up, tried following setup instructions in Kali, no joy, setup through Windows 7 no joy. Windows 10, no joy. Ubuntu 16.04 no joy. Been searching forums but I have yet to find a solution. Cannot connect to either setup webpage or recovery webpage. Connected to uart, here is reset output:

resetting...

U-Boot 1.1.4 (Dec 22 2015 - 12:54:58)

DB120
DRAM:
sri
Wasp 1.3
wasp_ddr_initial_config(249): (32bit) ddr2 init
wasp_ddr_initial_config(426): Wasp ddr init done
Tap value selected = 0xf [0x0 - 0x1f]
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 276k for U-Boot at: 87fb8000
Reserving 192k for malloc() at: 87f88000
Reserving 44 Bytes for Board Info at: 87f87fd4
Reserving 36 Bytes for Global Data at: 87f87fb0
Reserving 128k for boot params() at: 87f67fb0
Stack Pointer at: 87f67f98
Now running in RAM - U-Boot at: 87fb8000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x14
flash size 1MB, sector count = 16
Flash:  1 MB
*** Warning - bad CRC, using default environment

Now starting pci_init process
pci_init_board: PCIe PLL not set for 40MHz refclk
BOARD IS NOT CALIBRATED!!!
pci_init finished

In:    serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
 wasp  reset mask:c02200
WASP ----> S27 PHY
s27 reg init
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10
eth0 up
WASP ----> S27 PHY
s27 reg init lan
ATHRS27: resetting s27
ATHRS27: s27 reset done
: cfg1 0x800c0000 cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :10
athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :10
athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :10
athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :10
eth1 up
eth0, eth1
Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010 Atheros Communications, Ltd.
Ath Nand ID[87fef17c]: 2c:48:00:26:89
Attempting to use unknown device
Micronset ns -0x0-0x1000
====== NAND Parameters ======
sc = 0x87fef158 bbt = 0x87f98538 bbt_size = 0x0 nf_ctrl = 0x405
page = 0x1000 block = 0x0 oob = 0x0
size = 0MB
Setting 0xb8116290 to 0x20402d0f
Hit any key to stop autoboot:  0

Loading from device 0: ath-nand (offset 0x0)
Booting image at: 0x81000000
   Image Name:   MIPS OpenWrt Linux-3.18.23
   Created:      2015-12-22   4:23:13 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1965951 Bytes =  1.9 MB
   Load Address: 80060000
   Entry Point:  80060000
Uncompressing kernel image... OK!
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 134217728

Starting kernel ...

[    0.000000] Linux version 3.18.23 (sebkinne@buildtop) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47951) ) #3 Tue Dec 22 05:23:06 CET 2015
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[    0.000000] SoC: Atheros AR9344 rev 3
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x07ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x07ffffff]
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x07ffffff]
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line:  board=TETRA console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,256k(u-boot-env),256k(caldata),-(mb0);ar934x-nfc:2048k(kernel),-(ubi) rootfstype=squashfs noinitrd
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 125796K/131072K available (2642K kernel code, 125K rwdata, 556K rodata, 188K init, 186K bss, 5276K reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Clocks: CPU:560.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:40.000MHz
[    0.000000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[    0.070000] pid_max: default: 32768 minimum: 301
[    0.070000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.080000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.080000] NET: Registered protocol family 16
[    0.090000] MIPS: machine is tetra
[    0.530000] registering PCI controller with io_map_base unset
[    0.540000] PCI host bridge to bus 0000:00
[    0.540000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.550000] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.550000] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.560000] pci 0000:00:00.0: invalid calibration data
[    0.560000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit]
[    0.570000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
[    0.570000] pci 0000:00:00.0: using irq 40 for pin 1
[    0.580000] Switched to clocksource MIPS
[    0.580000] NET: Registered protocol family 2
[    0.590000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.590000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.600000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.600000] TCP: reno registered
[    0.610000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.610000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.620000] NET: Registered protocol family 1
[    0.620000] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.650000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.660000] msgmni has been set to 245
[    0.660000] io scheduler noop registered
[    0.670000] io scheduler deadline registered (default)
[    0.670000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
�[    0.700000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A
[    0.710000] console [ttyS0] enabled
[    0.710000] console [ttyS0] enabled
[    0.720000] bootconsole [early0] disabled
[    0.720000] bootconsole [early0] disabled
[    0.730000] m25p80 spi0.0: found s25fl008k, expected m25p80
[    0.730000] m25p80 spi0.0: s25fl008k (1024 Kbytes)
[    0.740000] 4 cmdlinepart partitions found on MTD device spi0.0
[    0.740000] Creating 4 MTD partitions on "spi0.0":
[    0.750000] 0x000000000000-0x000000040000 : "u-boot"
[    0.750000] 0x000000040000-0x000000080000 : "u-boot-env"
[    0.760000] 0x000000080000-0x0000000c0000 : "caldata"
[    0.770000] 0x0000000c0000-0x000000100000 : "mb0"
[    0.770000] nand: No NAND device found
[    0.780000] ar934x-nfc ar934x-nfc: nand_scan_ident failed, err:-19
[    0.790000] libphy: ag71xx_mdio: probed
[    1.390000] ag71xx-mdio.1: Found an AR934X built-in switch
[    1.430000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    2.030000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd042, driver=Generic PHY]
[    2.040000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    2.040000] TCP: cubic registered
[    2.050000] NET: Registered protocol family 17
[    2.050000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    2.070000] 8021q: 802.1Q VLAN Support v1.8
[    2.070000] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
[    2.080000] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    2.090000] Please append a correct "root=" boot option; here are the available partitions:
[    2.100000] 1f00             256 mtdblock0  (driver?)
[    2.100000] 1f01             256 mtdblock1  (driver?)
[    2.110000] 1f02             256 mtdblock2  (driver?)
[    2.110000] 1f03             256 mtdblock3  (driver?)
[    2.120000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    2.120000] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   78.370000] random: nonblocking pool is initialized

That is were it hangs, now no LED lights at all, no further output from uart. same results via AC power, USB only, UART only, USB +UART, USB+AC, USB+AC+UART.
I also tried to get it to load the factory reset bin via tftp, but it wouldn't see the directory as it states all interfaces are down.

I'm probably making a complete n00b mistake, so please advise.

Thank you for your time,

Marcus

Link to comment
Share on other sites

Use the wall outlet and usb eth id say if you have ubuntu or kali that would be your best bet.  Some people have had this problem before and its mainly a power issue.  but wget the wp6.sh and make it executable and I prefer to set wp6.sh manually, make sure you know your gateway IP which is most likely the ip of your wifi router (192.168.0.1 or 10.0.0.1 etc).

after setting it up with the tetra plugged into the pc make sure the script finds the pineapple. if so then proceed if not try this FAQ section on wifipineapple.com and if you haven't made it past the initial setup of flashing the latest firmware then do a firmware recovery.  If you have made it past flashing the latest firmware from the first start then try to reset the pineapple.

Link to comment
Share on other sites

13 hours ago, b0N3z said:

Use the wall outlet and usb eth id say if you have ubuntu or kali that would be your best bet.  Some people have had this problem before and its mainly a power issue.  but wget the wp6.sh and make it executable and I prefer to set wp6.sh manually, make sure you know your gateway IP which is most likely the ip of your wifi router (192.168.0.1 or 10.0.0.1 etc).

after setting it up with the tetra plugged into the pc make sure the script finds the pineapple. if so then proceed if not try this FAQ section on wifipineapple.com and if you haven't made it past the initial setup of flashing the latest firmware then do a firmware recovery.  If you have made it past flashing the latest firmware from the first start then try to reset the pineapple.

Ok, So I git cloned the repo, chmod +x ./wp6.sh
Ran through guided setup.
Do I now quit or connect using saved settings?

Sorry your answer is a bit ambiguous, or I'm extremely dense. TBH probably I'm being dense.

Link to comment
Share on other sites

42 minutes ago, Dystrakti0n said:

Ok, So I git cloned the repo, chmod +x ./wp6.sh
Ran through guided setup.
Do I now quit or connect using saved settings?

Sorry your answer is a bit ambiguous, or I'm extremely dense. TBH probably I'm being dense.

Ok, so that was an id10t error, I found the answer on the FAQ, guided setup works, but when I hit to Connect, it gets stuck on "detecting Wifi pineapple"

Cannot connect to 172.16.42.1:1471

Have solid blue light on tetra now,
Output for ifconfig:

enx001337a60dba Link encap:Ethernet  HWaddr 00:13:37:a6:0d:ba  
          inet addr:172.16.42.42  Bcast:172.16.42.255  Mask:255.255.255.0
          inet6 addr: fe80::9c09:6c45:305b:3283/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:283 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:60 (60.0 B)  TX bytes:35779 (35.7 KB)

Output from wp6.sh

sudo ./wp6.sh

               (          (                                                 
 (  (          )\ )       )\ )                                     (        
 )\))(   ' (  (()/(  (   (()/( (            (     )                )\   (   
((_)()\ )  )\  /(_)) )\   /(_)))\   (      ))\ ( /(  `  )   `  )  ((_) ))\
_(())\_)()((_)(_))_|((_) (_)) ((_)  )\ )  /((_))(_)) /(/(   /(/(   _  /((_)
\ \((_)/ / (_)| |_   (_) | _ \ (_) _(_/( (_)) ((_)_ ((_)_\ ((_)_\ | |(_))   
 \ \/\/ /  | || __|  | | |  _/ | || ' \))/ -_)/ _` || '_ \)| '_ \)| |/ -_)  
  \_/\_/   |_||_|    |_| |_|   |_||_||_| \___|\__,_|| .__/ | .__/ |_|\___|  
                                                    |_|    |_|       v6.5

    Saved Settings: Share Internet connection from wlan0
    to WiFi Pineapple at eth1 through default gateway 192.168.1.1

    Since this is the first time running the WP6 Internet Connection Sharing
    script, Guided setup is recommended to save initial configuration.
    Subsequent sessions may be quickly connected using saved settings.

    [C]onnect using saved settings
    [G]uided setup (recommended)
    [M]anual setup
    [A]dvanced IP settings
    [Q]uit

    
    WiFi Pineapple detected. Please disconnect the WiFi Pineapple from
    this computer and press any key to continue with guided setup.
    
    Step 1 of 3: Select Default Gateway
    Default gateway reported as 10.0.0.1
    Use the above reported default gateway?             [Y/n]? y

    Step 2 of 3: Select Internet Interface
    Internet interface reported as enp3s0
    Use the above reported Internet interface?          [Y/n]? y

    Step 3 of 3: Select WiFi Pineapple Interface
    Please connect the WiFi Pineapple to this computer.
    .........[Checking]
    Detected WiFi Pineapple on interface enx001337a60dba
    Use the above detected WiFi Pineapple interface?    [Y/n]? y

    Settings saved.

    Saved Settings: Share Internet connection from enp3s0
    to WiFi Pineapple at enx001337a60dba through default gateway 10.0.0.1

    [C]onnect using saved settings
    [G]uided setup (recommended)
    [M]anual setup
    [A]dvanced IP settings
    [Q]uit

    Detecting WiFi Pineapple..........................................................................................................................................................................

Output from ping:

PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data.
From 172.16.42.42 icmp_seq=1 Destination Host Unreachable
From 172.16.42.42 icmp_seq=2 Destination Host Unreachable
From 172.16.42.42 icmp_seq=3 Destination Host Unreachable
 

Attempt to screen in:

 

uboot> reset

Resetting...

U-Boot 1.1.4 (Dec 22 2015 - 12:54:58)

DB120
DRAM:
sri
Wasp 1.3
wasp_ddr_initial_config(249): (32bit) ddr2 init
wasp_ddr_initial_config(426): Wasp ddr init done
Tap value selected = 0xf [0x0 - 0x1f]
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 276k for U-Boot at: 87fb8000
Reserving 192k for malloc() at: 87f88000
Reserving 44 Bytes for Board Info at: 87f87fd4
Reserving 36 Bytes for Global Data at: 87f87fb0
Reserving 128k for boot params() at: 87f67fb0
Stack Pointer at: 87f67f98
Now running in RAM - U-Boot at: 87fb8000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x14
flash size 1MB, sector count = 16
Flash:  1 MB
*** Warning - bad CRC, using default environment

Now starting pci_init process
pci_init_board: PCIe PLL not set for 40MHz refclk
BOARD IS NOT CALIBRATED!!!
pci_init finished

In:    serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
 wasp  reset mask:c02200
WASP ----> S27 PHY
s27 reg init
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10
eth0 up
WASP ----> S27 PHY
s27 reg init lan
ATHRS27: resetting s27
ATHRS27: s27 reset done
: cfg1 0x800c0000 cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :10
athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :10
athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :10
athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :10
eth1 up
eth0, eth1
Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010 Atheros Communications, Ltd.
Ath Nand ID[87fef17c]: 2c:48:00:26:89
Attempting to use unknown device
Micronset ns -0x0-0x1000
====== NAND Parameters ======
sc = 0x87fef158 bbt = 0x87f98538 bbt_size = 0x0 nf_ctrl = 0x405
page = 0x1000 block = 0x0 oob = 0x0
size = 0MB
Setting 0xb8116290 to 0x20402d0f
Hit any key to stop autoboot:  0
uboot> httpd
Using eth0
dup 1 speed 100
MAC address: 0x0:0x3:0x7f:0x9:0xb:0xad
HTTP server is starting at IP: 192.168.1.1
HTTP server is ready!


When I attempt to connect to 192.168.1.1 via usb (should be eth1 on tetra) no joy, Connect ethernet cable (eth0 on tetra) to tetra and kali, set kali to 192.168.1.2/24, try to get to 192.168.1.1 in browser, no joy.

is there a way to force httpd to eth1?

 

 

Link to comment
Share on other sites

if your ifconfig is showing 172.16.42.42 then ICS should be enabled.  When plugged in without ICS you will get a 172.16.42.216 or something similar that is not 172.16.42.42.  when ICS is enabled it will show up as 172.16.42.42.    You cant get to the webui once that shows?  remember you have to log into 172.16.42.1:1471

Link to comment
Share on other sites

As an update, due to the nand device not being found in boot, I have submitted at ticket with hakshop support, and ordered a nano as well. Hopefully I can get this tetra RMA'd and replaced, and I'll have the Nano to use once it shows up while I am waiting for the tetra ticket to be resolved. 

Link to comment
Share on other sites

  • 4 weeks later...

Update: Got a nano in, and have that set up and running, still no contact from the hakshop on RMA, and has been a month now. Attempted recovery again, still no joy on getting to web interface when booting tetra up while holding reset down for 10 secs. I get solid yellow light, set

ifconfig eth1 192.168.1.2/24

firefox times out on 192.168.1.1 with problem loading page dialog.

Does anyone have experience with recovering this from uart?

Link to comment
Share on other sites

what is your home router ip?  is it interfering with the pineapple and id send another email if it has been that long on the RMA
 

Link to comment
Share on other sites

  • 1 month later...

Still have not heard back from support on this, just tried to boot it again for grins, this is what I get from serial:

 

Ath Nand ID[87fef17c]: 2c:48:00:26:89
Attempting to use unknown device
Micron====== NAND Parameters ======
sc = 0x87fef158 bbt = 0x87f98538 bbt_size = 0x0 nf_ctrl = 0x405
page = 0x1000 block = 0x0 oob = 0x0
size = 0MB
Setting 0xb8116290 to 0x20402d0f

 

Complete boot from serial:

uboot> reset

Resetting...

U-Boot 1.1.4 (Dec 22 2015 - 12:54:58)

DB120
DRAM:
sri
Wasp 1.3
wasp_ddr_initial_config(249): (32bit) ddr2 init
wasp_ddr_initial_config(426): Wasp ddr init done
Tap value selected = 0xf [0x0 - 0x1f]
128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 276k for U-Boot at: 87fb8000
Reserving 192k for malloc() at: 87f88000
Reserving 44 Bytes for Board Info at: 87f87fd4
Reserving 36 Bytes for Global Data at: 87f87fb0
Reserving 128k for boot params() at: 87f67fb0
Stack Pointer at: 87f67f98
Now running in RAM - U-Boot at: 87fb8000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x14
flash size 1MB, sector count = 16
Flash:  1 MB
Now starting pci_init process
pci_init_board: PCIe PLL not set for 40MHz refclk
BOARD IS NOT CALIBRATED!!!
pci_init finished

In:    serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
 wasp  reset mask:c02200
WASP ----> S27 PHY
s27 reg init
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10
eth0 up
WASP ----> S27 PHY
s27 reg init lan
ATHRS27: resetting s27
ATHRS27: s27 reset done
: cfg1 0x800c0000 cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :10
athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :10
athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :10
athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :10
eth1 up
eth0, eth1
Atheros on-chip NAND FLash Controller Driver, Version 0.1 (c) 2010 Atheros Commun                                  ications, Ltd.
Ath Nand ID[87fef17c]: 2c:48:00:26:89
Attempting to use unknown device
Micron====== NAND Parameters ======
sc = 0x87fef158 bbt = 0x87f98538 bbt_size = 0x0 nf_ctrl = 0x405
page = 0x1000 block = 0x0 oob = 0x0
size = 0MB
Setting 0xb8116290 to 0x20402d0f
Hit any key to stop autoboot:  0

Loading from device 0: ath-nand (offset 0x0)
Booting image at: 0x81000000
   Image Name:   MIPS OpenWrt Linux-3.18.23
   Created:      2015-12-22   4:23:13 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1965951 Bytes =  1.9 MB
   Load Address: 80060000
   Entry Point:  80060000
Uncompressing kernel image... OK!
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 134217728

Starting kernel ...

[    0.000000] Linux version 3.18.23 (sebkinne@buildtop) (gcc version 4.8.3 (Open                                  Wrt/Linaro GCC 4.8-2014.04 r47951) ) #3 Tue Dec 22 05:23:06 CET 2015
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 0001974c (MIPS 74Kc)
[    0.000000] SoC: Atheros AR9344 rev 3
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 08000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x07ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x07ffffff]
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x07ffffff]
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 b                                  ytes
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total page                                  s: 32512
[    0.000000] Kernel command line:  board=TETRA console=ttyS0,115200 mtdparts=sp                                  i0.0:256k(u-boot)ro,256k(u-boot-env),256k(caldata),-(mb0);ar934x-nfc:2048k(kernel                                  ),-(ubi) rootfstype=squashfs noinitrd
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 125796K/131072K available (2642K kernel code, 125K rwdata,                                   556K rodata, 188K init, 186K bss, 5276K reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.000000] Clocks: CPU:560.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:40.000                                  MHz
[    0.000000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[    0.070000] pid_max: default: 32768 minimum: 301
[    0.070000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.080000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.080000] NET: Registered protocol family 16
[    0.090000] MIPS: machine is tetra
[    0.530000] registering PCI controller with io_map_base unset
[    0.540000] PCI host bridge to bus 0000:00
[    0.540000] pci_bus 0000:00: root bus resource [mem 0x10000000-0x13ffffff]
[    0.550000] pci_bus 0000:00: root bus resource [io  0x0000]
[    0.550000] pci_bus 0000:00: No busn resource found for root bus, will use [bu                                  s 00-ff]
[    0.560000] pci 0000:00:00.0: invalid calibration data
[    0.560000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit                                  ]
[    0.570000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref]
[    0.570000] pci 0000:00:00.0: using irq 40 for pin 1
[    0.580000] Switched to clocksource MIPS
[    0.580000] NET: Registered protocol family 2
[    0.590000] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.590000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.600000] TCP: Hash tables configured (established 1024 bind 1024)
[    0.600000] TCP: reno registered
[    0.610000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.610000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.620000] NET: Registered protocol family 1
[    0.620000] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.650000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.660000] msgmni has been set to 245
[    0.660000] io scheduler noop registered
[    0.670000] io scheduler deadline registered (default)
[    0.670000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
▒[    0.700000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 250                                  0000) is a 16550A
[    0.710000] console [ttyS0] enabled
[    0.710000] console [ttyS0] enabled
[    0.720000] bootconsole [early0] disabled
[    0.720000] bootconsole [early0] disabled
[    0.730000] m25p80 spi0.0: found s25fl008k, expected m25p80
[    0.730000] m25p80 spi0.0: s25fl008k (1024 Kbytes)
[    0.740000] 4 cmdlinepart partitions found on MTD device spi0.0
[    0.740000] Creating 4 MTD partitions on "spi0.0":
[    0.750000] 0x000000000000-0x000000040000 : "u-boot"
[    0.750000] 0x000000040000-0x000000080000 : "u-boot-env"
[    0.760000] 0x000000080000-0x0000000c0000 : "caldata"
[    0.770000] 0x0000000c0000-0x000000100000 : "mb0"
[    0.770000] nand: No NAND device found
[    0.780000] ar934x-nfc ar934x-nfc: nand_scan_ident failed, err:-19
[    0.790000] libphy: ag71xx_mdio: probed
[    1.390000] ag71xx-mdio.1: Found an AR934X built-in switch
[    1.430000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    2.030000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd04                                  2, driver=Generic PHY]
[    2.040000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    2.040000] TCP: cubic registered
[    2.050000] NET: Registered protocol family 17
[    2.050000] bridge: automatic filtering via arp/ip/ip6tables has been deprecat                                  ed. Update your scripts to load br_netfilter if you need this.
[    2.070000] 8021q: 802.1Q VLAN Support v1.8
[    2.070000] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error                                   -19
[    2.080000] VFS: Cannot open root device "(null)" or unknown-block(0,0): error                                   -6
[    2.090000] Please append a correct "root=" boot option; here are the availabl                                  e partitions:
[    2.100000] 1f00             256 mtdblock0  (driver?)
[    2.100000] 1f01             256 mtdblock1  (driver?)
[    2.110000] 1f02             256 mtdblock2  (driver?)
[    2.110000] 1f03             256 mtdblock3  (driver?)
[    2.120000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknow                                  n-block(0,0)
[    2.120000] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs                                   on unknown-block(0,0)
[   82.450000] random: nonblocking pool is initialized

It is getting a bit irritating with the lack of support. I've Emailed, issued a zendesk ticket, and sent a message on keybase with no response.
ticket #36540 Order # 101773  Starting to feel a bit ripped off.

Link to comment
Share on other sites

https://hakshop.zendesk.com/hc/en-us/requests/new

make another request if that is the only support ticket you have sent, then it might have gotten lost, Im sure they were saying something about redoing an email system so it might be a safe bet to send another just in case, from everything Ive read, they are pretty quick on getting back to customers about issues and you have plenty of docs to show whats going on.

Link to comment
Share on other sites

Thanks B0N3z, I did that, logged back in and my original ticket no longer shows up, so must have gotten dumped in the rollover. As an aside, would you mind shooting me a copy of your boot serial output so I can see what it >should< look like?

Link to comment
Share on other sites

11 hours ago, Dystrakti0n said:

Thanks B0N3z, I did that, logged back in and my original ticket no longer shows up, so must have gotten dumped in the rollover. As an aside, would you mind shooting me a copy of your boot serial output so I can see what it >should< look like?

The post is long so i didnt read everything.

yellow light or frequent reboot could be due to low power, ensure sufficient power is provided to tetra. or can you share your power setup. ie how many battery

Link to comment
Share on other sites

Quote

The post is long so i didnt read everything.

You probably should.

Quote

yellow light or frequent reboot could be due to low power, ensure sufficient power is provided to tetra. or can you share your power setup. ie how many battery

The tetra is plugged into the wall with the provided power cord. The Tetra isn't fully booting, because it can't find NAND. NAND reads as 0Bytes, and there is no ROOT mount location for it to access. This induces a kernel panic.

Link to comment
Share on other sites

  • 1 year later...

IM HAVING THIS SAME ISSUE

Link to comment
Share on other sites

i sent in the ticket and they are telling me they need more info WTF?!  I told them it wont boot and solid yellow led what the helll im going to put up with bullshit i will open a class action law suit.

Link to comment
Share on other sites

16 minutes ago, tim657657 said:

im going to put up with bullshit i will open a class action law suit

just do what they ask and give them the info they ask for...  they have to be given a chance to fault find before progressing to anything else... if it can be fixed remotely then thats a win win for both you and them.

Link to comment
Share on other sites

18 hours ago, tim657657 said:

i sent in the ticket and they are telling me they need more info WTF?!  I told them it wont boot and solid yellow led what the helll im going to put up with bullshit i will open a class action law suit.

opening a class action law suit on something that you refuse to cooperate with is absolutely worthless and you will spend more money on stupid stuff that will not fix the device.  Help them help you.  Its a no brainier.  

Link to comment
Share on other sites

  • 2 weeks later...
On 6/28/2018 at 5:06 AM, tim657657 said:

i sent in the ticket and they are telling me they need more info WTF?!  I told them it wont boot and solid yellow led what the helll im going to put up with bullshit i will open a class action law suit.

I think you should put it all on black and roll the cards!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...