Heres the short version to save some time:

upgraded one of my 2300s to 1.4.3b.. after loading the linux bin, the unit said complete, then rebooting, and it never came back up.  No ping, no nothing.

I've tried going up and doing the reset button thing several times with no results.

Any way I can recover it locally or should I write it off as a brick?
 

It is possible to TFTP the image to the device.
Here are the steps:

Step 1: Hold the hardware reset button and power on the DLB2300

Step 2: Release the button after 5 seconds.

Step 3: Copy the firmware files to a directory on your computer.

Step 4: Set IP of your computer to 192.168.1.x subnet

Step 4: Open the dos command prompt, navigate to directory with files, and type:

           “tftp –i 192.168.1.6 put linux_adv.bin” and hit enter. (filename may differ)

Step 5: After it says transfer is successful, wait about 60 seconds and reboot the radio

This should reload the firmware image onto the device and it should be functional again.

-Matt

Well, it took it.  By "reboot the radio" I assume you mean just unplug and replug, which is what I did after waiting a minute or two.

Same results.  Got power and LAN LEDs, but no WLAN.  Even after rebooting several times.  No ping response, no response from the discovery tool.  Although, each time I try, the radio does boot and accept the tftp transfer as explained above.  Same routine each time.  Power and LAN, but no WLAN, and no response from the eth0 side.  *shrugs*  Any further ideas?
 

Been tinkering with it some more.  Same results.  Its almost as if it goes to boot, and hangs somewhere causing it to "lock up".  Like it never boots to the point where eth0 and wlan0 come up.

I wish I had a serial port (damn usb!) and the time/parts to build a cable to tie into the board to see whats happening. 

 Some other fiddling yielded some results.

I attempted some other firmware versions.  1.4.3b locked up, which is what I was attempting to upgrade to in the first place... as did 1.4.3a1, and 1.4.2e locked too.  When the device was new, it ran 1.2.7 I think?  The closest I had was 1.3.0, which it took and booted right away.  Did a reset to defaults on it, and then retried loading the newer firmware via the config page.  Locked up again.  Put 1.3.0 back on via tftp and tried the next lower revision.  Three hours of this process later, I found that the 2300 will boot and run with 1.3.0 or 1.3.0.2 and thats it.

Strange?  I'd say so.  It was running 1.4.0 just fine before I tried the initial attempt to upgrade to 1.4.3b.  Now it wont even take back to 1.4.0.  *shrugs*  Its partner on the other end of the link took to 1.4.3b without issue.

Thoughts? 

I just sent you an email with some more files, the default settings image and the bootloader.  TFTP both files over using the same method as above and see if that will clear the problem.  Let me know if you don't get it.

Caleb

Caleb-

Got it.  Took me several tries before the unit would boot, but the 2300 finally took to it and now the unit is working without issue.  It also easily took to 1.4.3b from 1.3.0 on the first try.

 Thanks!

Great, thanks for the update.

Caleb