Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "W.P." <laurentp@wp.pl>
To: linux-mips@linux-mips.org
Subject: Re: Beginning with REALTEK RTL-8186.
Date: Sat, 27 Jan 2007 00:55:43 +0100	[thread overview]
Message-ID: <45BA94FF.4080301@wp.pl> (raw)
In-Reply-To: <5C1FD43E5F1B824E83985A74F396286E041B10FB@bby1exm08.pmc_nt.nt.pmc-sierra.bc.ca>

Użytkownik Don Hiatt napisał:

>I'd certainly like to here about it. Well done.
>
>Cheers,
>
>don
> 
>
Let it be ;)

0). Model: EDIMAX BR-6204Wg, CPU: Realtek RTL-8186, bridge/NIC:
RTL-83055C, Flash: 1x MX-29LV160CBTC-70G, RAM: 2x PSC-.....

1). First of all, i have disassembled the device to get to it's serial
port. On PCB i've found a 4-pins header labeled JP2. Optical inspection
followed by ohmometer use shown that it is RTL's serial port. Pin
functions (from center to egde): +3.3Vcc, RxD (RTL's receiver), GND, TxD
(RTL's transmitter).
Then i connected an MAX232 level translator to those pins, using +3.3V
as power (CAUTION: 232 from Ti did not work @ 3.3V), as proposed on
mips-wiki pages. Parameters of transmission: 38400/8N1. BTW Edimax tech
support for Europe refused to tell if that header is serial.

2). On username/pass prompt working configuration was super/@gogolinux -
again from wiki.

3). Software instalation that comes from Edimax lacks nearly everything
;( no vi, not even ln.

4). Downloaded sources from Edimax Taiwanese site:
http://www.edimax.com.tw/download/drivers/GPL/BR-6204WG_GNU.tgz a little
71.5MB package. ;)
4a). what lacks from that tarball: /web directory, *.sh scripts from /bin
4b). using default build instructions found in tarball leads to lack of
webserver (webs), and two important other execs: /bin/setup and
/bin/flash. The latter is, as i realize an interface to store/fetch
variables from flash. The setup file SHOULD be in tarball: it is
referenced in build chain, but is missing (whole directory AP/console).
4c). I launched build, then I copied missing files from working system
and  then blocked script in rtl-11g-GPL/AP/mkimg/app_11g_script to NOT
regenerate top.11g directory. Then i ran build once again.

5). Flashed resulting bin file onto Edimax.

6). Boots OK, but have to manually start init.sh and webs& from serial
console.
6a). Much more options in Busybox enabled. ex: vi, ln, etc.

7). For this moment i have returned back to original (downloaded 1.48)
Edimax firmware.

Tomorrow I'll upload photos and boot-progress files somewhere.

W.P.

PS, there is a lot in configuration of this system, that i do not
understand clearly: ex: ifconfig shows: br0, br1 WITH ip-addresses,
eth0, eth1, wlan0 WITHOUT ip....
I'll have to investigate config files/scripts.

  reply	other threads:[~2007-01-26 23:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 21:36 Beginning with REALTEK RTL-8186 Don Hiatt
2007-01-26 23:55 ` W.P. [this message]
2007-01-27 13:04   ` RTL-8186 follow-up W.P.
     [not found]     ` <200701271354.41905.florian.fainelli@int-evry.fr>
2007-01-27 15:46       ` W.P.
2007-01-27 17:31       ` W.P.
2007-01-27 21:38         ` Florian Fainelli
2007-01-27 22:32           ` W.P.
2007-01-29 19:54       ` RTL-8186 follow-up2 W.P.
  -- strict thread matches above, loose matches on Subject: below --
2007-01-26 21:32 Beginning with REALTEK RTL-8186 W.P.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45BA94FF.4080301@wp.pl \
    --to=laurentp@wp.pl \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox