AC-88U Assistance needed to recover paperweight.

[chris n]

finally got it hooked up to a ttl cable. erased nvram, set ip and redid tftp file get. image succeeded,router reboot and is again in a boot loop.(pasted snippet below) . i think it might have to do with not seiing a mtd5, but i hjave no idea, any help or ideas would be appreciated.... THANKS!



/ # help
/bin/sh: help: not found
/ # cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "boot"
mtd1: 00180000 00020000 "nvram"
mtd2: 03e00000 00020000 "linux"
mtd3: 03c49e38 00020000 "rootfs"
mtd4: 04000000 00020000 "brcmnand"


/ # ls dev
console mtd0 network_throughput ram3
cpu_dma_latency mtd0ro null ram4
device mtd1 nvram ram5
full mtd1ro port ram6
fuse mtd2 ppp ram7
gpio mtd2ro ptmx ram8
kmsg mtd3 pts ram9
loop0 mtd3ro ram0 random
loop1 mtd4 ram1 root
loop2 mtd4ro ram10 shm
loop3 mtdblock0 ram11 tty
loop4 mtdblock1 ram12 ttyS0
loop5 mtdblock2 ram13 ttyS1
loop6 mtdblock3 ram14 urandom
loop7 mtdblock4 ram15 zero
mem network_latency ram2
/ #

 

[chris n]

Decompressing...done


CFE version 7.14.131.1608 (r589038) based on BBP 1.0.37 for BCM947XX (32bit,SP,)
Build Date: 二 10月 13 18:19:30 CST 2015 (ham@xpdev)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
DDR Clock: 800 MHz
Info: DDR frequency set from clkfreq=1400,*800*
et1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.1608 (r589038)
CPU type 0x0: 1400MHz
Tot mem: 524288 KBytes

CFE mem: 0x00F00000 - 0x017ABEC8 (9092808)
Data: 0x00F5401C - 0x00F549C4 (2472)
BSS: 0x00F549D0 - 0x00FA9EC8 (349432)
Heap: 0x00FA9EC8 - 0x017A9EC8 (8388608)
Stack: 0x017A9EC8 - 0x017ABEC8 (8192)
Text: 0x00F00000 - 0x00F4A1E0 (303584)

rtl8354mb initialized(0)(retry 0)
rtk port_phyEnableAll ok
rtk port_macForceLink_set ext_Port1 ok
get ok, chk 0x1311:1016(0x1016), 0x1305:c010(b4~b7:0x1)
Device eth0: hwaddr F8-32-E4-52-94-38, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.
boot the image...
go load
Loader:raw Filesys:tftp Dev:eth0 File:: Optionsnull)
Loading: TFTP Server.
..tftp retry wait 0
Failed.
Could not load :: Timeout occured
Loader:raw Filesys:raw Dev:nflash0.os File: Optionsnull)
Loading: .... 4367776 bytes read
Entry at 0x00008000
Closing network.
Starting program at 0x00008000
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117) is a 16550
brd: module loaded
loop: module loaded
pflash: found no supported devices
bcmsflash: found no supported devices
Boot partition size = 524288(0x80000)
lookup_nflash_rootfs_offset: offset = 0x200000
nflash: squash filesystem with lzma found at block 29
Creating 4 MTD partitions on "nflash":
0x000000000000-0x000000080000 : "boot"
0x000000080000-0x000000200000 : "nvram"
0x000000200000-0x000004000000 : "linux"
0x0000003b61c8-0x000004000000 : "rootfs"
PPP generic driver version 2.4.2
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPTP driver version 0.8.5
=== PPTP init ===
Mirror/redirect action on
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (8047 buckets, 32188 max)
ctnetlink v0.93: registering with nfnetlink.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
L2TP core driver, V2.0
PPPoL2TP kernel driver, V2.0
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Registering the dns_resolver key type
Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
NAND device: Manufacturer ID: 0xc8, Chip ID: 0xd1 (Unknown NAND 128MiB 3,3V 8-bit)
Spare area=64 eccbytes 56, ecc bytes located at:
2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Available 7 bytes at (off,len):
(1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
Scanning device for bad blocks
Options: NO_AUTOINCR,NO_READRDY,
Creating 1 MTD partitions on "brcmnand":
0x000004000000-0x000008000000 : "brcmnand"
VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
devtmpfs: mounted
Freeing init memory: 288K
## mknod /dev/null: File exists
## mknod /dev/console: File exists
1: set_action 0


Hit ENTER for console...

firmware version: 3.0.0.4.380.64_2
killall_tk: waiting name=envrams n=9
killall_tk: waiting name=envrams n=8
killall_tk: waiting name=envrams n=7
killall_tk: waiting name=envrams n=6
killall_tk: waiting name=envrams n=5
killall_tk: waiting name=envrams n=4
killall_tk: waiting name=envrams n=3
killall_tk: waiting name=envrams n=2
killall_tk: waiting name=envrams n=1
killall_tk: waiting name=envrams n=0
killall_tk: SIGKILL name=envrams n=9
killall_tk: SIGKILL name=envrams n=8
killall_tk: SIGKILL name=envrams n=7
killall_tk: SIGKILL name=envrams n=6
killall_tk: SIGKILL name=envrams n=5
killall_tk: SIGKILL name=envrams n=4
killall_tk: SIGKILL name=envrams n=3
killall_tk: SIGKILL name=envrams n=2
killall_tk: SIGKILL name=envrams n=1
killall_tk: SIGKILL name=envrams n=0
_ifconfig: name=lo flags=1043 IFUP addr=127.0.0.1 netmask=255.0.0.0
route_manip: cmd=ADD name=lo addr=127.0.0.0 netmask=255.0.0.0 gateway=0.0.0.0 metric=0
killall_tk: waiting name=envrams n=9
[1 preinit:init_nvram +10] init_nvram for model(47)

## Restoring defaults... ##
num_of_mssid_support(0x0093): [mssid] support [3] mssid
num_of_mssid_support(0x0093): [mssid] support [3] mssid
done


gmac3_override_nvram

rtl8365mb: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
rtl8365mbrtl8365mb initialized(0)(retry:1)
rtk port_phyEnableAll ok

register rtl8365mb done (link down at first)
et_module_init: passivemode set to 0x0
et_module_init: txworkq set to 0x0
et_module_init: et_txq_thresh set to 0xce4
et_module_init: et_rxlazy_timeout set to 0x3e8
et_module_init: et_rxlazy_framecnt set to 0x20
et_module_init: et_rxlazy_dyn_thresh set to 0
fwd0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.4402 (r628786)
fwd1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.4402 (r628786)
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.4402 (r628786)
hotplug net INTERFACE=fwd1 ACTION=add
hotplug net INTERFACE=fwd0 ACTION=add
hotplug net INTERFACE=eth0 ACTION=add
hotplug net INTERFACE=agg ACTION=add
config_location(0x003b): [tcode] location is []
config_location(0x003d): [tcode] no location setting, using default location
config_location(0x0053): [tcode] config location: [0:ccode]=[Q2], [0:regrev]=[992]
config_location(0x005d): [tcode] set_wl_country, 0, [Q2], [992]
config_location(0x0073): [tcode] config location 5G: [1:ccode]=[Q2], [1:regrev]=[992]
config_location(0x007e): [tcode] set_wl_country, 1, [Q2], [992]
set_wltxpower(0x023b): unit: 0, txpower: 100
set_wltxpower(0x023b): unit: 1, txpower: 100
hotplug net INTERFACE=dpsta ACTION=add
PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
dhd_attach(): thread:dhd_watchdog_thread:183 started
ring_info_raw: 56
dc 53 3f 00 ac 64 3f 00 c0 66 3f 00 d4 68 3f 00
da 68 3f 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 0a 01 00 00
CUR_ETHERADDR : 6
f8 32 e4 52 94 38
Dongle Host Driver, version 1.369.1 (r628771)
Compiled in drivers/net/wireless/bcmdhd on May 30 2016 at 14:06:44
Register interface [eth1] MAC: f8:32:e4:52:94:38

PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
hotplug net INTERFACE=eth1 ACTION=add
dhd_attach(): thread:dhd_watchdog_thread:187 started
External imprecise Data abort at addr=0xa3000000, fsr=0x1406, pc=0x8030f234 lr=0x7f08947c ignored.

^C




^C^C^C


Digital core power voltage set to 1.05V
Decompressing...done
Digital core power voltage set to 1.05V

 

[RMerlin]

There isn't any error message before your reboot, not even a kernel panic. Sound like a spontaneous reboot, I'd RMA the router.

 

[chris n]

There isn't any error message before your reboot, not even a kernel panic. Sound like a spontaneous reboot, I'd RMA the router.

ty Merlin for the sanity check, in CFE the thing lets me set IP, i can interupt and get to CAT, but anytime i try to book it just loops. unfortunetaly i have a ac-5300 with the exact same issue , sounds like i might have a HW issue

 

[RMerlin]

ty Merlin for the sanity check, in CFE the thing lets me set IP, i can interupt and get to CAT, but anytime i try to book it just loops. unfortunetaly i have a ac-5300 with the exact same issue , sounds like i might have a HW issue

Be warned that the RT-AC5300 has a firmware bug where it will reboot itself three times if you have one of the three wifi radios disabled. If you let it retry, it will complete its boot after the third attempt.

I fixed this issue in 380.65 beta 2, and was told that Asus are also aware of the issue on their end.

 

[sfx2000]

There isn't any error message before your reboot, not even a kernel panic. Sound like a spontaneous reboot, I'd RMA the router.

SW issue - things are coming up before the PCI-e bus is ready...

One can always ignore the abort by returning zero from the handler..

 

[chris n]

SW issue - things are coming up before the PCI-e bus is ready...

One can always ignore the abort by returning zero from the handler..

so your thinking its a SW issue: how would you do " ignore the abort by returning zero from the handler.." ?


Ty

 

[hggomes]

There isn't any error message before your reboot, not even a kernel panic. Sound like a spontaneous reboot, I'd RMA the router.

RMA after opening it / Serial?

 

[chris n]

RMA after opening it / Serial?

cant hurt to try, asus accepted my RMA request. if they send it back well i guess ill be pulling off ICs till i get it working... lol

 

[hggomes]

Have you took off the Warranty seal?

 

[chris n]

Have you took off the Warranty seal?

didnt even see one, all i saw were two stickers on the screws behind the rubber feet.

 

[hggomes]

Those are the ones, have you read what was written on them? "warranty seal" or "warranty void if removed".

 

[RMerlin]

SW issue - things are coming up before the PCI-e bus is ready...

If that were true, then it would mean that it wouldn't work for ANYONE, since this is the same code as it exists in every single router. He didn't modify it.

Beside, that's not what I see. The only thing sitting on that PCIe bus that came up in this log was the dhd daemon, and it does come up right after the PCIe bus probe completed. So, I don't see anything abnormal there.

RMA after opening it / Serial?

Worth a try. I don't remember seeing any warranty sticker on most of mine. Can't speak for the RT-AC88U specifically, Asus had already opened it before sending it to me.

 

[hggomes]

All routers have a warranty seal, there's no exceptions, could you imagine if that wasn't the case?

Your routers were not purchased / retail, that's why, the same happened here with some models received / not purchased.

IMO you will have a refusal, but if this makes you feel better I already seen a case where a RT-N66U was accepted even with a JTAG port added inside and no warranty seal at all / removed, maybe someone got distracted? Who knows?

PS: Why you haven't RMA it in the first place? RT-AC88U is not a cheap model...

I hope you can have a replacement, good luck.

 

[chris n]

If that were true, then it would mean that it wouldn't work for ANYONE, since this is the same code as it exists in every single router. He didn't modify it.

Beside, that's not what I see. The only thing sitting on that PCIe bus that came up in this log was the dhd daemon, and it does come up right after the PCIe bus probe completed. So, I don't see anything abnormal there.



Worth a try. I don't remember seeing any warranty sticker on most of mine. Can't speak for the RT-AC88U specifically, Asus had already opened it before sending it to me.

man you should see some of the stuff ive RMA with ASUS, sometime they give me a bit of static, but its either like $80 to fix a horribly mangled CPU socket, or just a new board. ASUS RMA is like jekly and hide tho,ive had some horrible expierences back in the day. trying to get my A7v to boot was a exercise in frustration ,3 RMAs to get a working one... they owe me , lol

 

[chris n]

All routers have a warranty seal, there's no exceptions, could you imagine if that wasn't the case?

Your routers were not purchased / retail, that's why, the same happened here with some models received / not purchased.

IMO you will have a refusal, but if this makes you feel better I already seen a case where a RT-N66U was accepted even with a JTAG port added inside and no warranty seal at all / removed, maybe someone got distracted? Who knows?

PS: Why you haven't RMA it in the first place? RT-AC88U is not a cheap model...

I hope you can have a replacement, good luck.

of course i bought it and the ac-5300 second hand . i honestly will scrape the PCB and take pictures of the schematic. honestly wanted to get more hand in hand of R/E consumer stuff, i got my bus pirate,oscillioscope,reworking station, etc.

 

[hggomes]

Seems promising.

 

[RMerlin]

man you should see some of the stuff ive RMA with ASUS, sometime they give me a bit of static, but its either like $80 to fix a horribly mangled CPU socket, or just a new board. ASUS RMA is like jekly and hide tho,ive had some horrible expierences back in the day. trying to get my A7v to boot was a exercise in frustration ,3 RMAs to get a working one... they owe me , lol

And here, my recent experiences at work have been simply really surprising.

1) PA248Q monitor that had a slightly discolored spot in one area. Was on its last 2 weeks of warranty, and issue required you to display an all white screen to spot it. Asus still replaced it with a brand new one, including all cables.

2) ROG Maximus motherboard (can't recall exact model), was less than a month old. Kept failing POST. Again, was replaced with a brand new, complete with all of its cables and components (so we got a spare LCD panel/remote).

Those two are surprising, first one due to the nature of the complain, but for both of them for the fact that they sent us a complete, brand new replacement instead of shipping just the monitor or just the motherboard, and they weren't even refurbished.

And not strictly an RMA: a few years ago, a customer purchased a motherboard based on AMD's Skulltrail platform. Turns out the customer purchased the wrong SKU (Asus had two different SKU depending on whether you wanted to one type or another of RAM, or something like that). Supplier wouldn't take it back. Out of despair, we contacted Asus. They told us the only difference between both SKUs were the BIOS. They asked us to send it back to them, they would crossflash it to the other BIOS, turning it effectively into the other SKU. That's what we ended up doing.

 

[RMerlin]

of course i bought it and the ac-5300 second hand . i honestly will scrape the PCB and take pictures of the schematic. honestly wanted to get more hand in hand of R/E consumer stuff, i got my bus pirate,oscillioscope,reworking station, etc.

Might be worth testing with another AC adapter, just in case.

 

[sfx2000]

If that were true, then it would mean that it wouldn't work for ANYONE, since this is the same code as it exists in every single router. He didn't modify it.

No, it means a bad chip - RMA as a dead on arrival device...