OpenWrt Forum Archive

Topic: OpenWRT on a Sitecom WLR-6000

The content of this topic has been archived between 1 Apr 2018 and 18 Apr 2018. Unfortunately there are posts – most likely complete pages – missing.

Post #51
Timeless
22 Aug 2016, 10:21

Ok, the network part is working now.

So the only remaining issues are:

[Flash]

The current mtd layout is:

root@lede:/# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "factory"
mtd3: 00713000 00010000 "firmware"
mtd4: 0007d000 00010000 "manufacture"
mtd5: 00010000 00010000 "backup"
mtd6: 00010000 00010000 "storage"

And it seems that the first 4MB is locked.

[WiFi]

(Last edited by Timeless on 23 Aug 2016, 09:22)

Post #52
Timeless
23 Aug 2016, 09:21

[UPDATE]

[FLASH]
Ok the flash is also working. mkresin spotted a misalignment in the rootfs and rootfs_data partition. The router can be flashed with sysupgrade from now on.

[WiFi]
Next issue is wireless.
For some reason the RT3592 does not engage after a cold boot when the RT3883 has not been enabled yet.

Example 1 (in this order):

1*. SCAN RT3592 ---> No results
2*. SCAN RT3883 ---> Got results
3*. SCAN RT3592 ---> Got results

*Note: AP/Station configurations are removed, the wireless chips are only in wlan#.temp scan mode.

Example 2:

1. Enable AP on both RT3883 & RT3592.
2. Both are working fine.
3. Disable RT3883.
4. RT3592 continues to work..
5. Reboot WLR-6000.
6. RT3592 does not work anymore.
7*. Enable RT3883.
8. RT3592 is working now.

*Note: It's enough to use the RT3883 just for scanning in step 7 without even enabling its AP

Long story short:
So for some reason the RT3592 does not work when the RT3883 has not been enabled during the current power-up state.

Regards,
Timeless

The discussion might have continued from here.