OpenWrt Forum Archive

Topic: Update on Linksys WRT1900AC support

The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

nyt wrote:

could be.  I don't feel like taking mine apart to test.  The TX/RX pins are in the right locations.

'k

Thx, I just want to be sure smile

gufus wrote:
nyt wrote:

serial hookup...

pin3  is rx, pin 5 is tx

Is this riight?

http://victek.is-a-geek.com/images/wrta … al_two.jpg

It is right. Unbricked my WRT1900AC couple of days ago using that picture as a reference. Flashing BB from AA messed it up. Restored by tftping Linksys stock FW over the serial connection.

I followed the topic but i didnt found clear information.

It is possible to compile whole OpenWRT for WRT1900AC or there are only precompiled images?

I need the toolchain/build enviroment for this platform to compile own packages/sources etc.

For other platforms i can build with buildroot custom images and compile other. It is possible there now?

Or can use ready image and compile some sources?

arybak wrote:

I followed the topic but i didnt found clear information.

It is possible to compile whole OpenWRT for WRT1900AC or there are only precompiled images?

I need the toolchain/build enviroment for this platform to compile own packages/sources etc.

For other platforms i can build with buildroot custom images and compile other. It is possible there now?

Or can use ready image and compile some sources?

Yes, you can build a BB tree with broken wifi, or a working AA tree.

Has anyone given compiling openssh a try? I'm about to go down that road since it seems opkg can't find it @ http://downloads.openwrt.org/snapshots/ … u/packages

And has anyone done an opkg update; opkg upgrade? I'm hesitant to do a mass upgrade.

DaedalusX wrote:

Has anyone given compiling openssh a try? I'm about to go down that road since it seems opkg can't find it @ http://downloads.openwrt.org/snapshots/ … u/packages

And has anyone done an opkg update; opkg upgrade? I'm hesitant to do a mass upgrade.

packages are not available for this in an online repo.  If you build your own and update the address it will be.

Even in AA there's something not quite right with the wifi driver on 5ghz... lots of this... and mini freezes

[665315.439735] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665354.446986] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665396.453962] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665481.445943] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665552.455509] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665596.444126] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665637.436794] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665676.441257] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665716.454131] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665759.443433] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665849.445991] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665903.447493] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[666028.447082] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[666076.428919] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf

(Last edited by nyt on 13 Jun 2014, 01:28)

nyt wrote:

Even in AA there's something not quite right with the wifi driver on 5ghz... lots of this... and mini freezes

[665315.439735] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665354.446986] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665396.453962] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665481.445943] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665552.455509] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665596.444126] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665637.436794] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665676.441257] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665716.454131] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665759.443433] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665849.445991] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[665903.447493] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[666028.447082] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf
[666076.428919] WLAN(wdev1ap0): MLME - Wireless client connected: 00236c97d7cf

I have noticed lots of problems when connecting after I wake my device from sleep/hibernate...

Lots of devices with bad drivers have problems after waking from sleep/hibernate. And it's usually the device's fault, not the network.

qasdfdsaq wrote:

Lots of devices with bad drivers have problems after waking from sleep/hibernate. And it's usually the device's fault, not the network.

Yes you are correct, but the problem was pronounced with this router...

My testing seems to indicate a driver issue with 5ghz "A" protocol.

Has anyone else noticed this?

Does setting 5ghz wireless to "N Only" and auto channel width solve the wireless issues?

sids73 wrote:
gufus wrote:
nyt wrote:

serial hookup...

pin3  is rx, pin 5 is tx

Is this riight?

http://victek.is-a-geek.com/images/wrta … al_two.jpg

It is right. Unbricked my WRT1900AC couple of days ago using that picture as a reference. Flashing BB from AA messed it up. Restored by tftping Linksys stock FW over the serial connection.

Hi

BTY

Do you know the voltage of your USB to TTL adaptor?

Thx!

3.3v mate.

Does the voltage matter?

there are many of us who have the wrt1900ac and are looking forward to a stable build

i'd just like to say thanks guys for diving in and testing / fixing these builds and stuff

gufus wrote:

Does the voltage matter?

Yes. Anything significantly over 3.3V should end up frying the router circuits. Old serial specs run anywhere from 3.3V to 25V.

gufus wrote:

Does the voltage matter?

Yup..  The uart of these modern chipsets work at 3.3v. Same applies with other routers manufacturers i.e. Asus.

guitarman wrote:
gufus wrote:

Does the voltage matter?

Yup..  The uart of these modern chipsets work at 3.3v. Same applies with other routers manufacturers i.e. Asus.

'k

Thx!

gufus wrote:
guitarman wrote:
gufus wrote:

Does the voltage matter?

Yup..  The uart of these modern chipsets work at 3.3v. Same applies with other routers manufacturers i.e. Asus.

'k

Thx!

Make sure the cable is TTL. TTL and RS232 are different communication standards not to mention voltages.

Chadster766 wrote:
gufus wrote:
guitarman wrote:

Yup..  The uart of these modern chipsets work at 3.3v. Same applies with other routers manufacturers i.e. Asus.

'k

Thx!

Make sure the cable is TTL. TTL and RS232 are different communication standards not to mention voltages.

Hi

So, this adapter wouldn't work?

http://www.ebay.ca/itm/CP2102-USB-2-0-T … OU:CA:3160

gufus wrote:
Chadster766 wrote:
gufus wrote:

'k

Thx!

Make sure the cable is TTL. TTL and RS232 are different communication standards not to mention voltages.

Hi

So, this adapter wouldn't work?

http://www.ebay.ca/itm/CP2102-USB-2-0-T … OU:CA:3160

It should work it's TTL designed for the job smile

For my windows computer I purchased the below and found it at a local retailer:
http://www.adafruit.com/products/954

(Last edited by Chadster766 on 14 Jun 2014, 22:18)

Chadster766 wrote:

It should work it's TTL designed for the job smile

But it's 5v (Default 5V), is that ok?

gufus wrote:
Chadster766 wrote:

It should work it's TTL designed for the job smile

But it's 5v (Default 5V), is that ok?

Yes it should be fine. You know I first tried standard computer Serial coms with RS232 cable I wired up. That would have been 12v and it didn't destroy it thank GOD.

Ya, lucky you didn't fry something eh smile

I have 2 adaptors, (5v and 3.3v) I'm going to use the 3.3v if need be.

Cheers!

(Last edited by gufus on 14 Jun 2014, 23:45)