OpenWrt Forum Archive

Topic: Realtek SoC support in OpenWrt

The content of this topic has been archived between 22 Sep 2016 and 30 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi all,

regarding nprove.in:
I had the same problem, but on
http://main.lv/writeup/building_openwrt … 8196c.html
there is a note about that and a link to
http://git.advem.lv/

So to my "problem":
I was able (by replacing several URLs and other small stuff I don't remember) to get "everything" from there compiled.
And I have a serial connection to my Edimax 6200NL, so I can get access to the Bootloader.
(Sadly the original running system doesn't start a shell for the console when it is running...)

My current situation might be specific to my device, but I think it is a more general thing:
Currently I have stopped to try things, because I did not understand what would happen next!

I think TFTP to the device will work, but when I would do so: What file will I upload to the device?
The uImage of the kernel? I expect something else generated during the compile, but what?
Maybe it is explained somewhere, but then I did miss that piece of information...

I can't imagine I can upload the whole system, or will the tftp write directly to the flash memory?
So would I be able (for testing/repair?) to upload the original firmware that way?

If it is a complete firmware:
Do I have to provide an address or something to get the device boot my image?
There are specific offsets in the "original" firmware images, at least I found three parts and
their offsets in the original firmware files with binwalk...

Maybe it is even much simpler than tftp:
Currently I still have the original web interface, and I could use that firmware update:
But I never told the compiling process anything about my specific hardware:
I still expect I have missed one important thing.

Maybe "tomate" can light me up a bit, as he (she?) has successfully used the same deivce?

Thanks,

  Baerle (also from Germany)

Hi baerle,

firstly thanks for the actual woking links!

I didn't work on this stuff for longer time, but I think I can help you anyway.

First be sure you have Edimax 3G-6200nL V2 (it is marked on the case), because the 3G-6200nL has a different chipset and you would brick this device! Only the V2 has the realtek chipset.

Flashing via tftp is very simple and if you have configured and compiled correctly all would flash fine.

When you start menuconfig you have to check in the submenu "Target Images" if the addresses are correct for your system.
For me it's this address config:

(0x80500000) Load address of kernel in ram
(10000) Offset of kernel in flash rom (HEX)
(130000) Offset of filesystem in flash rom (HEX)
(0x800000) size of the flash rom
(530000) FLATFS image offset in flash

This addresses are contained in the images and tftp burns automatically to the right location.

On the tftp console I did these commands:

connect 192.168.1.6
put bin/realtek/openwrt-realtek-rtl8196c-nprove-squashfs.bin
put bin/realtek/openwrt-realtek-rtl8196c-nprove-kernel.bin

It's important to flash the squashfs image first, because after burning the kernel image the device reboots automatically. If you do it the other way round the firmware doesn't work because of the missing filesystem.

The only thing you must take care of is that your image doesn't exceed the flash size. I had this one time and after that the bootloader was overwritten. Luckily the device has a serial flash chip and I made a backup of the original flash, so I could solder out the chip and restore to factory defaults.

Hope this helps you!


P.S.: I still have the problem, that I can't access via LAN with my firmware (the problem I mentioned at the beginning of the thread). I was fed of it and that's the reason why I didn't work on that stuff any longer.

vitasonline wrote:

andygo,
Hello!
I bought a router UR-825AC
The official firmware does not suit me.
Let us together make OpenWrt?

yes, sure! could you provide me with sources of the last one?
(https://yadi.sk/d/ZP726zQEdwWQu)

Hi,

Wow, thank you Tomate, that really has helped:

It is a bit late, so I first didn't understand why I always got a wrong checksum and nothing was flashed:
Then I switched to binary in tftp...
And it worked!

At least the board has booted, and I have a shell now.

Enough for now, it is a bit late.

Ciao,

  Baerle

Hi all,

So it was a big success:
I don't know what kind of LAN problem you have Tomate, at least for me it works (or it seems to do so?):
- I have running the luci web interface
- my phone can connect via wifi
- "ddserver" is running.

That last thing was my (new) main purpose for this device (the original plan was to use it for something more special, but there I have used a openwrt "standard" hardware)

So now the device isn't useless anymore:I just have to build a battery for that now, and then I can use everywhere with dslrdashboard. Ok, I haven't connected it to my camera, but I don't expect problems from that part.

A nice extra would be to able to use the button, the LED or some other GPIO Pins:
Then I can also use it to control some more things. We will see!

So thanks all here for making this possible!

Baerle

baerle wrote:

Hi all,

So it was a big success:
I don't know what kind of LAN problem you have Tomate, at least for me it works (or it seems to do so?):
- I have running the luci web interface
- my phone can connect via wifi
- "ddserver" is running.

That last thing was my (new) main purpose for this device (the original plan was to use it for something more special, but there I have used a openwrt "standard" hardware)

So now the device isn't useless anymore:I just have to build a battery for that now, and then I can use everywhere with dslrdashboard. Ok, I haven't connected it to my camera, but I don't expect problems from that part.

A nice extra would be to able to use the button, the LED or some other GPIO Pins:
Then I can also use it to control some more things. We will see!

So thanks all here for making this possible!

Baerle

Hi baerle,

nice to hear that it works fine for you. smile
If I would know what's my problem I would solve it wink

Which system did you use to cross compile? Maybe that's the reason for my fault, because it's a bit old openSUSE 12.1. Perhaps I should start again from the beginning.
Would it be possible to share your .config and images? Than I could try if your stuff works on my hardware.


Tomate

Hi,

Of course I can provide you the files you want. I think I will create something on github for that.

But in fact: "Zu früh gefreut" on my side:
The USB doesn't work: Kernel side seems to be fine,  but no device is found:

I have seen there are some codes different from "my" kernel to the GPL Sources I found for that device, especially there are a few "USB_PWR" things, so I'm sure I can solve that:
I expect there is at least one GPIO or something that needs to be activated.
So I have to work a bit more on the software side :-(

Of course I'm open for tipps here, too!

Thanks,
  Baerle

PS:
I used Ubuntu 14.04 to build...

(Last edited by baerle on 26 Jan 2015, 00:45)

OK, I started from the beginning again. And now it works! I can access via LAN, works fine.

The problem with the USB is, that it the power can be switched off by GPIO. With my former firmware I could turn it on by simply echoing 1 to a file. But I don't remember which file it was....and I don't find it in my actual firmware....maybe I have to switch back to the old firmware an have a look.

A bit Documentation about that board (Edimax 3G-6200nL V2)

GPIO2, 13 and 14 can control the LEDs on the side
GPIO5 is connected to the button
GPIO6 controls the USB Power
GPIO16 control the LED between USB and the button

To control the LEDs, one has to write 0x343FC0 to /sys/module/gpio_rtl819x/parameters/rtl819x_mux
See /etc/init.d/sysled for this.
At least that file isfunny, as it disabled my USB power...

But my problems are not solved yet:
Even with USB power I didn't got a USB-device working yet.

(Last edited by baerle on 28 Jan 2015, 19:21)

Hi baerle,

where did you get this information?

The number I have to write to rtl819x_mux is 0x340c00.

According to your info, I can read the button on GPIO5 and set the LED on GPIO2. Writing on GPIO 6, 13, 14 or 16 does nothing. I was not able to switch on USB Power.

I flashed my old firmware (where network isn't working) and tried there the same. I can read the button, switch the LED on GPIO2 and can switch the USB Power on GPIO6. The other GPIOs aren't changing anything here, too.

I read here: https://dev.openwrt.org/ticket/13201#comment:18 that JTAG wasn't disabled and that was the problem the GPIO didn't work. Maybe that's the same reason here?

Hi Tomate,

I got this information by educated guessing:

1st: I have found a PDF Datasheet for the 8196C: There the PIN_MUX register was explained. I searched the sources and found a few accesses, but nothing 100% clear for me what might be wrong.

2nd: Then I noticed that USB power was on(!) during booting, and then "suddenly" stopped:
So I knew there was a trigger in "userspace", obviously something from the init part. I didn't notice the led-file earlier.

3rd: in the PDF the LED part for the Ethernet-switch LEDs was explained, so I tried to change them to GPIO and it worked:
For that you have to use that other 0x343FC0 value. I decided to post this information here, as it is at least nice to know.
Edit: To make it clear: the additional bits configure the MUX to connect the "internal GPIO" with the external pin. So writing to the GPIO without changing that Mux will not change the Pin. It depends what you want: Ethernet Information or GPIO controlled LEDs. Both is possible.

4th: I searched in the Edimax GPL Sources and noticed there was GPIO6 used for the usb power, so that matched:
GPIO6 is the usb power. I don't have a "power LED" on my board.
Edit: but it is inverted, so the write in that init-file disabled the power.

Then there was still one LED missing: The one between USB and the button:
So I took photos from both sides of the board, loaded them to inkscape, rotated a bit and mirrored. I also placed the pin-out graphic from the PDF on top of the chip: I never did something like that before, but it worked really well: I got both sides on top of each other and then could easily follow the lines: USB was as already noticed on GPIO6, and the last LED was controlled by PortC[0], so GPIO16. I also did this to check the other GPIO pins: Pin 102 is at the edge of the chip and seems not to be used: If I want to control a hardware, that would be a nice pin I expect.
(I edited my posting for that, so all LEDs are "documented" now)

Currently I'm comparing the kernel of that GPL-things, and the one I'm using:
There is one strange thing that might be the reason for my problem:
In the Edimax "GPL" Kernel there is an "ehci-rtl8652.c" driver used (not the rtl-819x.c).
And I found a "realtek patch" in "check_reset_complete" that will do 3 retries in that code.
I know that this 8652 driver is used (you can find messages from it in this thread, and there is also a
#if defined(CONFIG_RTL_8196C)
inside, so I'm sure it is for "our" chip.

(Last edited by baerle on 29 Jan 2015, 12:24)

Strike!!!

[    4.670000] usb 1-1: new full speed USB device using rtl819x-ohci and address 2
[    5.380000] usb 1-1: New USB device found, idVendor=0d8c, idProduct=000c
[    5.390000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    5.400000] usb 1-1: Product: C-Media USB Headphone Set 
[    5.620000] usb 1-1: configuration #1 chosen from 1 choice

Don't know if everything is fine, but at least that rtl8652 made me another step forward!

Really don't know what still might be wrong (I started to expect the worst...)

But I have the image of my dslr camera on my smartphone now!
Via ddserver and WLAN from that "Edimax 6200nL v2" device.

(And I made a tar copy from my whole build dir, so I cannot lose it:
currently to many edits in to many files...)

Edit:
I will try to make it reproducable: Currently I have edited directly in the kernel sources. My plan is to get something that allows "everyone" to generate the images. If there is a good place for uploading, I can provide my files there: Any ideas?
If not, I think I can upload my work to github.

I noticed you can get that device waiting for tftp by pressing the button when connecting the power:
Just hold it for a while, then the bootloader will stop (and start waiting for an upload).
So this way you can flash a new firmware and kernel without ever connecting a serial console, and you don't even have to open it.
It is a rather cheap (less than 26 Euro) but nice (small, external antenna, USB) box. (thats why I bought it for my original plan)

(Last edited by baerle on 29 Jan 2015, 12:44)

Thanks for your efforts, baerle!

It would ge great if you can put all in a patch or create something like a manual.
I'm trying to solve this for myself based on your infos here.

For uploading I think github would be the best.

If I can help you with something then tell me. I'll try my best!


And I bought this router for the same reasons as you wink Rather cheap and nice.

andygo wrote:
vitasonline wrote:

andygo,
Hello!
I bought a router UR-825AC
The official firmware does not suit me.
Let us together make OpenWrt?

yes, sure! could you provide me with sources of the last one?
(https://yadi.sk/d/ZP726zQEdwWQu)

I have no source of firmware. Her gave me a support service upvel.ru, but it is no different from the previous fw-UR-825AC-19.11.14.zip  All errors remain.

I'm currently creating a repository with all my changes and a short "walkthrough" to get openwrt to that device.

Edit:
You can find it here:

https://github.com/utessel/edimax

I don't have my experiments to get usb working there yet, as I would like to understand what is going wrong.

(Last edited by baerle on 1 Feb 2015, 20:35)

Thanks baerle (especially for the credits in the readme file smile )

Sadly I didn't get USB working as well. I also tried the original Edimax driver, and it didn't work. But here some things I noticed, maybe they help to find the problem:
The original Edimax driver uses irq9, in the Openwrt driver irq10 is used. I changed it on both but it had no effect.
On USB I have a flash drive with power LED on it. I took my camera and made a 250fps video to find out when the USB power goes off. It is after the "new USB bus registered" and before the "irq10, io mem 0x18021000" message.

[    3.850000] mtd: partition "rootfs" set to be root filesystem
[    3.860000] mtd: partition "rootfs_data" created automatically, ofs=3F0000, len=410000
[    3.870000] 0x0000003f0000-0x000000800000 : "rootfs_data"
[    3.890000] 0x000000010000-0x000000800000 : "firmware"
[    3.910000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.920000] rtl819x-ehci rtl819x-ehci: Realtek rtl819x On-Chip EHCI Host Controller
[    3.940000] rtl819x-ehci rtl819x-ehci: new USB bus registered, assigned bus number 1
[    3.990000] rtl819x-ehci rtl819x-ehci: irq 10, io mem 0x18021000
[    4.030000] rtl819x-ehci rtl819x-ehci: USB 2.0 started, EHCI 1.00

What I don't know how long it takes between power off and LED off. The USB Power is buffered with 470µF so this might be some 10 to 100ms....

Hi,

I now have "understood" why I got a USB device working: the ehci driver wasn't running (One init call or so was missing). This makes a bit sense that the ohci part takes over with USB1.1.

@tomate:
Do you still have an issue with the power?
As I don't have any problems there anymore: At least USB is working when the EHCI part is not initialized somehow.

Do you have the boot messages from the original firmware?
I would like to compare them with "my" kernel, but also compare them with the source:
I'm always a bit more confident I'm reading the right source if I know the messages are really printed.

Hmm: You said you had network problems with an earlier version: But the USB did work? Do you still have the state of the git repository you have used? There must be one path that helped with the LAN problem, and another one that stopped USB....

Her e are the messages from the original firmware:

---RealTek(RTL8196C)at 2012.03.22-07:08+0800 version v1.1f [16bit](390MHz)


<=== GPIOA6 off/on 9/1 2202918 times ===>

Jump to image start=0x80500000...

decompressing kernel:
Uncompressing Linux... done, booting the kernel.
done decompressing kernel.
start address: 0x80003630
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 26656k/32768k available (2650k kernel code, 6112k reserved, 667k data, 108k init, 0k highmem)
Calibrating delay loop... 388.30 BogoMIPS (lpj=1941504)
Mount-cache hash table entries: 512
net_namespace: 528 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
msgmni has been set to 52
io scheduler noop registered
io scheduler cfq registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Realtek GPIO Driver for Flash Reload Default
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x18002000 (irq = 8) is a 16550A
PPP generic driver version 2.4.2
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
usbcore: registered new interface driver asix
RTL8192C/RTL8188C driver version 1.4 (2010-08-11)
=====>>INSIDE rtl8192cd_init_one <<=====
vendor_deivce_id=819110ec
=====>>EXIT rtl8192cd_init_one <<=====
=====>>INSIDE rtl8192cd_init_one <<=====
=====>>EXIT rtl8192cd_init_one <<=====
=====>>INSIDE rtl8192cd_init_one <<=====
=====>>EXIT rtl8192cd_init_one <<=====
=====>>INSIDE rtl8192cd_init_one <<=====
=====>>EXIT rtl8192cd_init_one <<=====
=====>>INSIDE rtl8192cd_init_one <<=====
=====>>EXIT rtl8192cd_init_one <<=====
=====>>INSIDE rtl8192cd_init_one <<=====
=====>>EXIT rtl8192cd_init_one <<=====



Probing RTL8186 10/100 NIC-kenel stack size order[3]...
chip name: 8196B, chip revid: 0
  Set 8196C PHY Patch OK
NOT YET
Set threshould idx 0
eth0 added. vid=9 Member port 0x1...
eth1 added. vid=8 Member port 0x10...
eth2 added. vid=10 Member port 0x2...
eth3 added. vid=11 Member port 0x4...
eth4 added. vid=12 Member port 0x8...
[peth0] added, mapping to [eth1]...
SPI INIT
flash device: 0x400000 at 0xbfe00000
SPI 1
Physically mapped flash: Found an alies 0x800000 for the chip at 0x0, MX25L6405D device detect.
Creating 2 MTD partitions on "Physically mapped flash":
0x000000000000-0x000000800000 : "boot+cfg+linux+rootfs"
0x000000120000-0x000000800000 : "root fs"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
reg 0xe0 not correct
USB 2.0 PHY Patch Done.
rtl8652-ehci rtl8652-ehci.0: RTL8652 On-Chip EHCI Host Controller
rtl8652-ehci rtl8652-ehci.0: new USB bus registered, assigned bus number 1
read synopsys=0
read synopsys2=0
rtl8652-ehci rtl8652-ehci.0: irq 9, io base 0x18021000
rtl8652-ehci rtl8652-ehci.0: USB 0.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: RTL8652 On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.30.9 ehci_hcd
usb usb1: SerialNumber: rtl8652-ehci.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
rtl8652-ohci rtl8652-ohci.0: RTL8652 OHCI
rtl8652-ohci rtl8652-ohci.0: new USB bus registered, assigned bus number 2
rtl8652-ohci rtl8652-ohci.0: irq 9, io mem 0x18020000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: RTL8652 OHCI
usb usb2: Manufacturer: Linux 2.6.30.9 ohci_hcd
usb usb2: SerialNumber: rtl8652
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (512 buckets, 2048 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
init 461 Check Point!
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
VFS: Mounted root (squashfs filesystem) readonly on device 31:1.
Freeing unused kernel memory: 108k freed

init started: BusyBox v1.11.1 (2012-06-11 18:01:16 CST)

starting pid 666, tty '': '/etc/init.d/rcS'

Please press Enter to activate this console. 
starting pid 669, tty '': '-/bin/sh'


BusyBox v1.11.1 (2012-06-11 18:01:16 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Sat Jan  1 00:00:00 UTC 2011
Running: USB is enabled

<=== USB PWR on ===>
Running: usb/internet led off
Fast Nat 
Fast Nat end
killall: pptp.sh: no process killed
killall: pppoe.sh: no process killed
killall: comgt: no process killed
killall: failover.sh: no process killed
killall: ppp3gloop.sh: no process killed
killall: dhcp3gloop.sh: no process killed

--------------------------------------------------------------------------------
/bin/disconnect.sh all
--------------------------------------------------------------------------------
=== Close Wan Interface!! ===
=== Finish running disconnect.sh ===
=== clean /tmp/disconnect.pid ===
Initialize WLAN interface


Running: wlan blink
Setup BRIDGE interface

ifconfig: ioctl 0x8913 failed: No such device
ifconfig: ioctl 0x8913 failed: No such device
bridge br0 doesn't exist; can't delete it
Setup bridge...
device eth0 entered promiscuous mode
device wlan0 entered promiscuous mode
===> Load_92C_Firmware
<=== Load_92C_Firmware
br0: port 2(wlan0) entering forwarding state
br0: port 1(eth0) entering forwarding state


WiFi Simple Config v1.17 (2010.06.04-06:14+0000).

device eth1 is not a slave of br0
route: ioctl 0x890c failed: No such process
device eth0 is already a member of a bridge; can't enslave it to bridge br0.
**********************************************************************
*                           Running Diagd                            *
**********************************************************************
**********************************************************************
*                          Enable WSC_UPnP                           *
**********************************************************************
IEEE 802.11f (IAPP) using interface br0 (v1.7)

**********************************************************************
*                            Start WPS_daemon                        *
**********************************************************************
**********************************************************************
*                            Enable LLTD                             *
**********************************************************************

killall: lld2d: no process killed


**********************************************************************
*                       Enable GPIO Interrupt                        *
**********************************************************************
Start AP as Enrollee daemon !!


killall: watchdog.sh: no process killed
killall: radiusd: no process killed
RADIUS server disable !!
ReInit APMIB
**********************************************************************
*                       FREE Page,Dentries and Inodes Cache          *
**********************************************************************
MemFree:           14972 kB
Cached:             3100 kB
=== LAN_WAN_SEL is NOT defined ===
=== Starting WAN ===
killall: pppd: no process killed
killall: runppp.sh: no process killed
killall: pptp.sh: no process killed
killall: pppoe.sh: no process killed

--------------------------------------------------------------------------------
/bin/disconnect.sh all
--------------------------------------------------------------------------------
=== Close Wan Interface!! ===
=== Finish running disconnect.sh ===
=== clean /tmp/disconnect.pid ===
killall: ppp3gloop.sh: no process killed
=== Setup WAN interface ===

--------------------------------------------------------------------------------
/bin/disconnect.sh all 0
--------------------------------------------------------------------------------
=== Close Wan Interface!! ===
=== Finish running disconnect.sh ===
=== clean /tmp/disconnect.pid ===
device eth0 left promiscuous mode
br0: port 1(eth0) entering disabled state
device eth0 entered promiscuous mode
br0: port 1(eth0) entering forwarding state




udhcp client (v0.9.9-pre) started
ReInit APMIB
into eth1.deconfig
WEBS Restarting !
Start AP as Enrollee daemon !!
Start AP as Enrollee daemon !!

I didn't try your firmware yet, so I have already problems with USB power. Hope your firmware will work then wink

Yes, on my first try with nprove firmware USB worked an LAN did not. Maybe I can restore the state of the repository, I only backuped the images.....

Guys, I've got a question regarding sources you use to build a firmware. It seems like you follow git repo made available by former nprove employee and looking into sources it looks like realtek target there is based on 2.6.30 kernel. At the same time I was able to find and download tarball named 00002778-rtk_openwrtSDK_v2.1_20140314_full.tar.gz (there was a link posted earlier in this thread) which claims to contain the SDK for realtek-based routers based on OpenWRT. Checking its contents reveals that it is based on a more fresh snapshot of openwrt and realtek target is based on kernel 3.10.

Thus I'm curious about two things:
1) Had you tried using "rtk_openwrtSDK_v2.1_20140314" to check if USB works with it out of the box?
2) Does anyone here have any idea what is the source of "rtk_openwrtSDK_v2.1_20140314"? Is it an official release from realtek or is it some internal project that had leaked to public somehow?

Hi Lexa2,

Thanks for your hint.
My primary interest was to get that router hardware work for me, not a specific kernel or openwrt version, not even "current" was important: I don't plan to use it as a "router", so I don't see security issues: I will typically not connect it to the internet at all. Tomate has mentioned he had tried it on the same hardware, so I thought, give it a try, and if it works with my software, I'm done with it.
If I would have got the GPL packet from Edimax compiled, I would have used that for my "problem".
(Edit: I was able now to compile that and load the generated image to the device, it runs and USB works with that)

As I have found a few things like those GPIO things, I wanted to publish that, maybe someone else has the same questions?
And while compiling the original git I had to solve a few little problems: it didn't work out of the box as a few URLs where out of date or whatever, so I published these changes: At least I had these question, nothing difficult, but it might help someone. Another copy of that repository doesn't hurt I think?

I know nothing about 2), but for 1):
I didn't take a look to that package you mentioned when I started, but now I have downloaded the file:
I'm not sure it will help after having a first look: My router has a rtl8196c. No default config for that chip: That tar-ball mentions these chips:
rtl8198C
rtl8954E
rtl8197D
rtl8196E
rtl8881A
I can't even select the right one (for me) in menuconfig. So: Nothing I plan to dig into.

(Last edited by baerle on 4 Feb 2015, 16:50)

Lexa, did you find a download of that tarball that wasn't infected with adware? The link previously mentioned in this thread was, along with everything I could find on a search...

I'm just curious: How can one infect a gzipped tarball with adware?

Accourding the USB problem:
To compile the edimax GPL things, I did exactly what they have written in their docu:
Installed Fedora 8, code in /home/..., Then I got it compiled:
Seems some parts rely on real old environments...
This is in fact not related to openwrt, but at least I should be able to instrument both kernels with that.

It wasn't a simple tgz... the link in the thread pointed to an htm page that downloaded a tar.gz.exe  Your recent link, to the tgz, was just fine, of course, and raised no flags.

This is endpoint of following the link from earlier in our thread, from my Downloads list (points to a non-existent file, now):

http://get.bedinstall.com/n/3.2.96/1375 … 0e6c9d572f

The file, when downloaded, raised a flag in AVG for BundleApp_r.

My actual process was to click on chiajiao's link:

2014-06-04 23:00:15
Re: Realtek SoC support in OpenWrt (174 replies, posted in Hardware Hacking)
New url http://www.solidfiles.com/d/473dd51828/ … ull.tar.gz

That took me to a solidfiles page with a download button, which had the .exe link quoted above...
Unless I've got some kind of link editting virus.... try it yourself, please.

(Last edited by dickms on 5 Feb 2015, 17:54)

I had no troubles (except for slow download speed for "free download") fetching tar.gz and it was what I expected it to be. No adware or any other binaries from Windows world. I suspect that you might press on the wrong link and get some adware or so-called "download-manager downloader" instead of fetching a direct link. It is typical for file hosting sites to place nice and big "DOWNLOAD IT NOW" buttons that lead to anything except for the real file you want to download. Try again and keep as much attention as you can on what you click and you should end up with a real download link.

P.S. Just tried pressing that big fancy green download button on solidfiles site using Google Chrome running under Linux Mate DE. Got normal tar.gz as expected and not *.tar.gz.exe.

(Last edited by lexa2 on 6 Feb 2015, 18:13)