OpenWrt Forum Archive

Topic: TP-Link TL-WDR3600 (AR9344) overclocking

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

pepe2k wrote:

It will be available later, because I'm on my holidays.

Have a nice time wink.

pepe2k wrote:
headless.cross wrote:

is OC available for AR9344?

It will be available later, because I'm on my holidays.

When you planning publish OC code ?

Evgeniy1 wrote:
pepe2k wrote:
headless.cross wrote:

is OC available for AR9344?

It will be available later, because I'm on my holidays.

When you planning publish OC code ?

Here is my current to-do list, regarding to my U-Boot mod project:

1. O/C recovery mode and more O/C profiles for AR9331 (also for underclocking).
2. AR9341 support (MR3420v2 etc.).
3. O/C recovery mode and O/C profiles for AR9344/AR9341.
4. Solution for OFW kernel loading bug.

Censored
datasheet

Great! smile
Did you find also datasheet for AR9341?

pepe2k wrote:

Great! smile
Did you find also datasheet for AR9341?

No, I have not found it.

Unless we have significant differences in architecture?
There is a press release of these two processors (AR9341 / AR9344) - so that we could compare its characteristics?


P.S.
By the way, can someone help and show me: what the answer openwrt-console (on ar9344 and/or ar9331 device of course) with following commands?

ls /sys/bus/platform/drivers/ar933x-uart/

ls /sys/bus/platform/drivers/serial8250/

Thanks anyway.

(Last edited by Dioptimizer on 4 Dec 2013, 06:11)

root@OpenWrt:/# ls /sys/bus/platform/drivers/serial8250/
bind          serial8250    serial8250.0  uevent        unbind

root@OpenWrt:/# ls /sys/bus/platform/drivers/ar933x-uart/
ar933x-uart  bind         uevent       unbind

Any news about OC for 9344 ?

Evgeniy1 wrote:

Any news about OC for 9344 ?

The project is currently at the highlighted stage smile

1. O/C recovery mode and more O/C profiles for AR9331 (also for underclocking).
2. AR9341 support (MR3420v2 etc.).
3. O/C recovery mode and O/C profiles for AR9344/AR9341.
4. Solution for OFW kernel loading bug.
5. QCA955x support.

Overclocking for AR9331 platform is already done, I'm working on the AR9341 support (WR841Nv8 is working, but I need to make some changes in network driver). After that, I am going to rebuild PLL initialization for AR934x (currently it is based on SRIF which isn't documented) and add options to save and load all PLL configuration registers to/from FLASH (like for AR9331).

Hi pepe2k I faced the following issue.
I upgrade the flash to 16MB Winbond Chip and compiled the code using GCC 4.6. openwrt toolchain.
Occasionally it will boot occasionally it will not boot, especially from a cold boot.
Do you face a similar issue?
I check the RAM which I also upgraded to 64MB using memtester so that should not be an issue.
I forgot to mention my machine is MR3420v2 HW V 2.2.

(Last edited by alphasparc on 11 Jan 2014, 09:50)

alphasparc wrote:

Hi pepe2k I faced the following issue.
I upgrade the flash to 16MB Winbond Chip and compiled the code using GCC 4.6. openwrt toolchain.
Occasionally it will boot occasionally it will not boot, especially from a cold boot.
Do you face a similar issue?
I check the RAM which I also upgraded to 64MB using memtester so that should not be an issue.
I forgot to mention my machine is MR3420v2 HW V 2.2.

Hi alphasparc, can you post an output/bootlog from UART console?
Or maybe you already know which stage it hangs at?

pepe2k wrote:
alphasparc wrote:

Hi pepe2k I faced the following issue.
I upgrade the flash to 16MB Winbond Chip and compiled the code using GCC 4.6. openwrt toolchain.
Occasionally it will boot occasionally it will not boot, especially from a cold boot.
Do you face a similar issue?
I check the RAM which I also upgraded to 64MB using memtester so that should not be an issue.
I forgot to mention my machine is MR3420v2 HW V 2.2.

Hi alphasparc, can you post an output/bootlog from UART console?
Or maybe you already know which stage it hangs at?

I only have access to serial console the problem is that if it boots it boots successfully otherwise it hangs.
I can't get any output from the serial consoles if it fails.

When it boots successfully
1)All the LED lights up then only power LED Remains lighted
When it fails
1)Only Power LED lights up and remains lighted up indefinitely.(Hang no output at all)

(Last edited by alphasparc on 11 Jan 2014, 12:53)

alphasparc wrote:

I only have access to serial console the problem is that if it boots it boots successfully otherwise it hangs.
I can't get any output from the serial consoles if it fails.

When it boots successfully
1)All the LED lights up then only power LED Remains lighted
When it fails
1)Only Power LED lights up and remains lighted up indefinitely.(Hang no output at all)

It seems to be a serious problem. I don't have now any MR3420v2, only WR841Nv8 (but it's almost the same hardware, so I'm able to make some tests).

I changed behavior of the LEDs for this model. In original TP-Link U-Boot version, the LEDs are turned on from the beginning and turned off later. In my modification, LEDs are turned off earlier (before low level initialization) and then lights up during network initialization. So, I think that in your case, the device hangs somewhere in low level initialization - maybe there is a problem with PLL and clocks, because I haven't yet checked and rewritten it.

I suppose that this problem doesn't exist with default U-Boot from original TP-Link's firmware (have you checked that)?
Please, try this version (http://www.tech-blog.pl/pliki/u-boot_mod_mr3420v2.rar) and let me know if it helped.

Could also read full mark from your AR9341? For example, on my WR841Nv8 I have AR9341-AL1A, but I have seen already different, probably newer, revisions.

pepe2k wrote:

It seems to be a serious problem. I don't have now any MR3420v2, only WR841Nv8 (but it's almost the same hardware, so I'm able to make some tests).

I changed behavior of the LEDs for this model. In original TP-Link U-Boot version, the LEDs are turned on from the beginning and turned off later. In my modification, LEDs are turned off earlier (before low level initialization) and then lights up during network initialization. So, I think that in your case, the device hangs somewhere in low level initialization - maybe there is a problem with PLL and clocks, because I haven't yet checked and rewritten it.

I suppose that this problem doesn't exist with default U-Boot from original TP-Link's firmware (have you checked that)?
Please, try this version (http://www.tech-blog.pl/pliki/u-boot_mod_mr3420v2.rar) and let me know if it helped.

Could also read full mark from your AR9341? For example, on my WR841Nv8 I have AR9341-AL1A, but I have seen already different, probably newer, revisions.

I checked my cpu revision is the same AR9341-AL1A
I will be testing your uboot will be back with replies soon.

I downloaded and tested your version.
Works Perfect 100% successful boot.
Now I am puzzled, is it the compiler?

I uploaded the source here
Btw great job!

(Last edited by alphasparc on 11 Jan 2014, 17:03)

alphasparc wrote:

I downloaded and tested your version.
Works Perfect 100% successful boot.
Now I am puzzled, is it the compiler?

Compiler, linker... I don't know.

To be sure in 100% that it works, please make more tests. And, if you can, send me please your binary image and any changes which you have made in sources (in Makefile, I suppose).

any update of AR9344 OC profile? Thanks

snowrice wrote:

any update of AR9344 OC profile? Thanks

Working on that.

How's the work going? tongue

I saw from the tests that 780/480/240 is a stable setting and I want to try it out. However I did not see in the source files any define for 780/480/240, how do you set it ? Many thanks.

idaniel wrote:

I saw from the tests that 780/480/240 is a stable setting and I want to try it out. However I did not see in the source files any define for 780/480/240, how do you set it ? Many thanks.

Btw 780 is not stable for me only 700 is.
Take a look here.
u-boot/board/ar7240/common/lowlevel_init_934x.S

#if !defined(CONFIG_AP123)
/*    refdiv    nint    nfrac */
li    t4,    ((0x8 << 27) | (112 << 18) | 0);// cpu freq = (40 MHz refclk/refdiv 8) * Nint
li    t5,    ((0x8 << 27) | (90 << 18) | 0);    // ddr freq = (40 MHz refclk/refdiv 8) * Nint
j    2f
nop
1:
li    t4,    ((0x5 << 27) | (112 << 18) | 0);// cpu freq = (25 MHz refclk/refdiv 5) * Nint
li    t5,    ((0x5 << 27) | (90 << 18) | 0);    // ddr freq = (25 MHz refclk/refdiv 5) * Nint
j    2f
nop
#else /* defined(CONFIG_AP123) */
/*    refdiv    nint    nfrac */
li    t4,    ((0x8 << 27) | (107 << 18) | 0);// cpu freq = (40 MHz refclk/refdiv 8) * Nint
li    t5,    ((0x8 << 27) | (160 << 18) | 0);// ddr freq = (40 MHz refclk/refdiv 8) * Nint
j    2f
nop
1:
li    t4,    ((0x5 << 27) | (107 << 18) | 0);// cpu freq = (25 MHz refclk/refdiv 5) * Nint
li    t5,    ((0x5 << 27) | (160 << 18) | 0);// ddr freq = (25 MHz refclk/refdiv 5) * Nint
j    2f
nop
#endif /* !defined(CONFIG_AP123) */

I am able to compile firmware from GIT. Now how do I modify the above code to overclock?

Is it possible to write to registers during standard U-boot console, in a unmodified platform?

I.e:

1>I tap into U-boot menu, from serial console of a ar9344 based thing
2>write to the registers from command line
3> call kernel entry point, and let device boot

The discussion might have continued from here.