LS2 'Double bricked?'

[slojam]

I have been using the tftp process to load various versions of firmware on the LS2 (from both a linux workstation and PC) - with no problem until today. I have been build OpenWRT images and trying various features. After one install, I can no longer successfully update the board...the tftp session connects correctly and the file is 'put' over the link without error, but the board will not come up. I have tried 3.1.1 and 3.2 of AirOS as well as 8.09 (RC1) of OpenWRT and cannot see the board at 192.168.1.1 (OpenWRT) or 192.168.1.20 (AirOS) - including ping.

I am using the mkfwimage utility to combine the kernel and file system and i inadvertantly created one image that had a large filesystem size (in the ls2-openwrt.txt file that would have 'wrapped' over FFFFFFFF). The recovery boot loader seems to be operating fine, just now can not successfully see an image load boot. I have not looked at the serial port output as of yet...need a cable.

Thanks for any ideas

[slojam]

I have since hooked up a terminal and here is what i see:

==========================

+No board configuration found!
Couldn't find valid MAC address for enet0. Using default!
Ethernet eth0: MAC address 00:03:7f:e0:02:bf
IP: 0.0.0.0/255.255.255.0, Gateway: 0.0.0.0
Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Ubiquiti Networks certified release, version 0.9.2.30 - built 20:17:02, Apr 24 8

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: Ubiquiti ar2315/6 based board
RAM: 0x80000000-0x81000000, [0x80040db0-0x80fe1000] available
FLASH: 0xbfc00000 - 0xbfff0000, 64 blocks of 0x00010000 bytes each.


So it appears the MAC address and board config are trashed. How to recover?

Thanks

[slojam]

Ping! Any thoughts on this? :?:

[UBNT-Mike.Ford]

Hey Slojam,

It definitely looks like the units is bricked and would probably need JTAG to bring it back.

Thanks,

Mike

[dp]

Hey UBNT-Mike.Ford,

I'd attempted to take a build of OpenWRT r13696 and tftp it into an NS5 Loco. Previously I'd re-flashed dozens of builds of the OpenWRT trunk on NS5's and Bullet 5's and never encountered a problem. However, upon my first attempts with NS5 Locos, I seem to have bricked a pair of them within 5 minutes. It seems that redboot no longer works as nothing/zip/zilch/nada comes up on the serial console upon rebooting or power-cycling with the reset switch held closed.

My questions to you are:

1) "Does the NS5 Loco have the same architecture as a NS5 (and therefore firmware compatible)? I assumed this to be the case but am now wondering if there's a subtle difference I was unaware of. I know from experimental evidence that the NS5 Bullet works using the same OpenWRT binaries as the NS5, and simply assumed that would be the case for the Loco.

2) If the Loco's are different architecturally and firmware-image-requirement-wise, where is this documented?

3) How can I recover these bricked units?

dp

[UBNT-Mike.Ford]

Hello,

The NS5Loco has different antenna control architecture. That is the only difference I am aware of. I will check into this for you though.

Thanks,

Mike

[dp]

Mike,

To answer one of my own questions, it appears from this post (http://www.ubnt.com/forum/viewtopic.php?t=6678) that firmware-wise the Loco and the bullet have some unspecified differences, which require a different SDK than as used for the previous XS (Nano-, Power-, Lite-, etc., stations). So, the same probably goes for OpenWRT as well, in which case I've probably bricked the Loco's and need to restore them somehow (JTAG?), so the other question (3) remains: "How can I recover these bricked units?"

dp