Opened 3 years ago

Closed 3 years ago

#1580 closed (fixed)

Airlink AR690w switch driver non-functional

Reported by: btechnet Owned by: Brainslayer
Keywords: ar690w Cc:

Description

It looks like the switch (RTL8366S) is being loaded on startup, but when connected with rj-45 the lights never lite, and a connection is never establish. The only line of code showing up using a serial inteface is: Rtl8366 Phy Init...<0>decode /dev/mtdblock4.

Attachments (1)

ar690w_switch.txt (7.0 KB) - added by btechnet 3 years ago.

Download all attachments as: .zip

Change History (19)

Changed 3 years ago by btechnet

comment:2 follow-up: Changed 3 years ago by Sash

we need to the gpio which are used to access the switch. this is what we need to know. the problem is that this is not easy to accomplish. there are several ways to get the info we need.
-disassemble the original binary switch driver if we could get it -from the gpl sources (that dont exist) -from a project that already supports this unit

comment:3 Changed 3 years ago by LOM

  • Owner set to Brainslayer

The RT_2880 reference design and the RT_2880 SDK has:

#define smi_SCK 2 /* GPIO used for SMI Clock Generation */ #define smi_SDA 1 /* GPIO used for SMI Data signal */

for the RT2880 <-> RTL8366SR.

Asus RT-N15 and TP-Links RT2880/RTL8366SR boards are also using those, try them in next build if not already tried.

comment:4 Changed 3 years ago by LOM

  • Owner changed from Brainslayer to LOM
  • Status changed from new to assigned

comment:5 Changed 3 years ago by LOM

  • Owner changed from LOM to Brainslayer
  • Status changed from assigned to new

comment:6 Changed 3 years ago by LOM

  • Resolution set to invalid
  • Status changed from new to closed

comment:7 Changed 3 years ago by LOM

  • Resolution invalid deleted
  • Status changed from closed to reopened

comment:8 Changed 3 years ago by LOM

/s/ TP-Link Trendnet

comment:9 in reply to: ↑ 2 Changed 3 years ago by LOM

Replying to Sash:

we need to the gpio which are used to access the switch. this is what we need to know. the problem is that this is not easy to accomplish. there are several ways to get the info we need.
-disassemble the original binary switch driver if we could get it -from the gpl sources (that dont exist) -from a project that already supports this unit

I provided the correct gpio's 2 weeks ago, what is the problem now?

comment:10 Changed 3 years ago by LOM

  • Resolution set to worksforme
  • Status changed from reopened to closed

comment:11 Changed 3 years ago by LOM

  • Resolution worksforme deleted
  • Status changed from closed to reopened

comment:12 Changed 3 years ago by LOM

I provided the correct gpio's 2 weeks ago, what is the problem now?

comment:13 Changed 3 years ago by Sash

Hi LOM, soory about the delay...i forgott to inform BS. can u plz add the info here, too?.

comment:14 Changed 3 years ago by LOM

smi_SDA = (1 << 3) ie gpio3 smi_SCLK = (1 << 4) ie gpio4 RTL8366_Reset = (1 << 5) ie gpio5

comment:15 Changed 3 years ago by BrainSlayer

from which location did you got your information. the reference design from ralink has nothing todo with this device.

comment:16 Changed 3 years ago by LOM

The gpios's are from the stock firmware as I mentioned when I sent you the info in email 24/10.

See: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=73341&start=30

comment:17 Changed 3 years ago by BrainSlayer

i found your email and answered. i guess i can provide a test build with your settings in some minutes. i will send it to you with email and i hope it will work

comment:18 Changed 3 years ago by BrainSlayer

  • Resolution set to fixed
  • Status changed from reopened to closed

next release might work. i tested the new driver on another device. so if the SDA and SCLK data is correct, it will work

Note: See TracTickets for help on using tickets.