Let me know how I can get a serial log for you and I'll get it
ill be willing to help too, i have build jtag cables in the past to fix some wrt54g's, so maybe building a serial cable is not that hard, maybe , if someone points me to the right direction i can hel for sure, ....
Open the loco m2, find the serial port which either is 4 or 5 solder holes filled with solder or is a pin header connector.
Of these you need to connect ground, tx, and rx - the remaining pin(s) is 3.3 volt and sometimes a 5th unused pin.
You need a multimeter to identify which pin is ground and which is 3.3 volt if not marked on the circuit board.
tx and rx will be the remaining ones in a 4 hole/pin connector.
Connect the routers serial port to your computers serial port through a RS232<->TTL 3.3 volt level shifter (routers serial port is 3.3 volt, don't connect without level shifter because RS-232 is up to 12 volt ).
You can also use a USB<-> TTL 3.3V cable, mobile phone cables like Nokia DKU-5 or CA-42 can be had for $3-4 from Ebay or Amazon.
The windows driver included on the CD you get will create virtual serial ports in windows.
Use a terminal program like puTTY to communicate serially with the router. _________________ Kernel panic: Aiee, killing interrupt handler!
Sorry i would not be able to helpas i cant get that serial cable , hope someone ealse can help us...perhapps SASH, wich stated that has several ubiquiti products working properly. Can you sash? please.
I've read online about these serial cables, not that hard to make one really.
Unfortunately my customer needed his Bullet M2 to work NOW, so I had to go back and install it yesterday. I got it working with OpenWRT for the time being, but I'm out of UBNT devices for testing now...
I created a virtual wireless client in its own network called WWAN. Then I created another virtual wireless in AP mode, this one is in the LAN network next to the eth0. And it just works, it connects to the DLink's ESSID with WPA2-PSK AES, and it broadcasts its own ESSID with different name and passphrase.
Thanks for all your help so far guys, I wish I still had the device here so we could make it work.
I've read online about these serial cables, not that hard to make one really.
Unfortunately my customer needed his Bullet M2 to work NOW, so I had to go back and install it yesterday. I got it working with OpenWRT for the time being, but I'm out of UBNT devices for testing now...
I created a virtual wireless client in its own network called WWAN. Then I created another virtual wireless in AP mode, this one is in the LAN network next to the eth0. And it just works, it connects to the DLink's ESSID with WPA2-PSK AES, and it broadcasts its own ESSID with different name and passphrase.
Thanks for all your help so far guys, I wish I still had the device here so we could make it work.
They look so much like the ones for nextel but they are nokia so i cant seem to find one here locally, so DDWRT mods, maybe you should warn ubquiti users users not to update to airos5.5 if not necesary.
I think he means:
"Do not upgrade your UBNT device to later than 5.3.x if you want to be able to install DD-WRT on it because starting with AirOS 5.5 the bootloader changes permanently."
Joined: 06 Jun 2006 Posts: 101 Location: Germany, Bensheim
Posted: Tue Jun 12, 2012 11:47 Post subject:
Hi,
i updated a locoM2 to airos 5.5 and flashed dd-wrt from the gui and also over tftp without issues.
The builds need to be greater than 17592, since that was the change we made to the version number that is in the header (ubnt firmwares refused to flash firmwares with no version information).
The bootloader of my locoM2 was not changed, it reamains as:
U-Boot 1.1.4.2 (Apr 1 2010 - 10:24:23)
If there are still problems, i think then there might be hardware out with a newer bootloader. Hopefully somebody can send me that newer bootloader, we haven't seen hardware with newer bootloader here yet. _________________ NewMedia-NET GmbH
Christian Scheele (CEO)
http://www.dd-wrt.com