Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Thanks a lot! I have done some testing again, this time with Qi: the default QtMoko kernel (2.6.29-rc3) gives an error/kernel panic when booting with the (*any*) overclocked Qi, while the SHR-U kernel (2.6.32) *does* boot. I haven't tested SHR-U any further, but if you're saying it suspends and resumes fine, I believe you :-) I get nothing but a black screen and flashing AUX button with the QtMoko kernel, while the SHR-U kernel boots fine. So there is quite a difference in kernel config, or maybe even kernel version. I hope someone can find out what kernel config (or bootloader adjustments) is needed for the overclock to be successful (both under u-boot and Qi), because this still is very promising! Especially the different CPU voltages are very nice to experiment with, that should give a good balance between speed, heat and power consumption. Cheers, Tha_Man -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5242777p5282436.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
2010/7/4 Tha_Man jeroenb...@hotmail.com Hi again, I couldn't resist to do some more testing, so I copied my QtMoko SDcard installation to NAND. QtMoko from NAND boots fine in most cases (see overview), it's suspend and resume that fails when overclocked. However, suspend and resume works fine with the original NAND U-boot and your default clocked U-boot. I've flashed the overclocked images exactly as you posted and flashed u-boot_env.in as well, no errors were reported during flashing. Here's an overview: Tested under QtMoko v24, using different u-boot images flashed in NAND: + u-boot-gta02v5-1.3.1: works fine + u-boot.udfu_400_100_1.7: works fine - u-boot.udfu_450_112_1.65_1.9: won't boot (hangs on 'Starting kernel...') - u-boot.udfu_450_112_1.7_1.9_sdmax: won't boot (hangs on 'Starting kernel...') * u-boot.udfu_500_83_1.7: fails to resume after suspend * u-boot.udfu_500_83_1.7_1.8_CLK2: fails to resume after suspend * u-boot.udfu_533_88_1.7: fails to resume after suspend * u-boot.udfu_533_88_1.7_1.8_CLK2: fails to resume after suspend So most u-boot images boot fine with QtMoko v24 and report the correct speeds, but my phone doesn't wake up after suspend with any of the overclocked images; I have to remove the battery to be able to boot again. Even the 450Mhz-images you reported as 'working under qtmoko' fail with me, but I'm not sure if you tested suspend and resume. I'm using the default v24-kernel, based on 2.6.29 I believe. I hope my tests are of any help, if I need to test something else, please let me know. Cheers, Tha_Man -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5242777p5253190.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Hi, I'm using QtMoko on SD from a long time and wanted to give these uboot versions (500 and 533) a try. I kept my uboot env because yours doesn't seem to add any new parameters. They worked well but I have the same problems as Tha_Man : my FR doesn't resume after suspend. Back to your 400 uboot, the same QtMoko (same partitions and uboot env) suspends and resumes well. SHR-U suffers from the same symptoms. I hope you'll be able to track and solve this problem because FR is really faster at 500 or 533 Mhz and that's great. -- David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
On Sat, Jul 10, 2010 at 19:19, David Vermeille dve...@gmail.com wrote: 2010/7/4 Tha_Man jeroenb...@hotmail.com Hi again, I couldn't resist to do some more testing, so I copied my QtMoko SDcard installation to NAND. QtMoko from NAND boots fine in most cases (see overview), it's suspend and resume that fails when overclocked. However, suspend and resume works fine with the original NAND U-boot and your default clocked U-boot. I've flashed the overclocked images exactly as you posted and flashed u-boot_env.in as well, no errors were reported during flashing. Here's an overview: Tested under QtMoko v24, using different u-boot images flashed in NAND: + u-boot-gta02v5-1.3.1: works fine + u-boot.udfu_400_100_1.7: works fine - u-boot.udfu_450_112_1.65_1.9: won't boot (hangs on 'Starting kernel...') - u-boot.udfu_450_112_1.7_1.9_sdmax: won't boot (hangs on 'Starting kernel...') * u-boot.udfu_500_83_1.7: fails to resume after suspend * u-boot.udfu_500_83_1.7_1.8_CLK2: fails to resume after suspend * u-boot.udfu_533_88_1.7: fails to resume after suspend * u-boot.udfu_533_88_1.7_1.8_CLK2: fails to resume after suspend So most u-boot images boot fine with QtMoko v24 and report the correct speeds, but my phone doesn't wake up after suspend with any of the overclocked images; I have to remove the battery to be able to boot again. Even the 450Mhz-images you reported as 'working under qtmoko' fail with me, but I'm not sure if you tested suspend and resume. I'm using the default v24-kernel, based on 2.6.29 I believe. I hope my tests are of any help, if I need to test something else, please let me know. Cheers, Tha_Man -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5242777p5253190.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Hi, I'm using QtMoko on SD from a long time and wanted to give these uboot versions (500 and 533) a try. I kept my uboot env because yours doesn't seem to add any new parameters. They worked well but I have the same problems as Tha_Man : my FR doesn't resume after suspend. Back to your 400 uboot, the same QtMoko (same partitions and uboot env) suspends and resumes well. SHR-U suffers from the same symptoms. I hope you'll be able to track and solve this problem because FR is really faster at 500 or 533 Mhz and that's great. -- David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Try 450 or 465 versions. With them suspend and resume works well for me :) -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi, Gennady suggested the same thing, but the 450Mhz-settings fail on kernel start (see my previous message, I haven't tried the 465 settings). These settings need a recompiled kernel according to Gennady's first message, did you recompile your kernel? If not, I'm very curious why it doesn't work for me! I'm assuming you're running QtMoko v24 as well, either from SD or NAND. Cheers, Tha_Man -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5242777p5278457.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
On Sat, Jul 10, 2010 at 21:23, Tha_Man jeroenb...@hotmail.com wrote: Hi, Gennady suggested the same thing, but the 450Mhz-settings fail on kernel start (see my previous message, I haven't tried the 465 settings). These settings need a recompiled kernel according to Gennady's first message, did you recompile your kernel? If not, I'm very curious why it doesn't work for me! I'm assuming you're running QtMoko v24 as well, either from SD or NAND. Cheers, Tha_Man 450/112 and 465/116 settings work for me even with 1.55V (just tested) and it seems to not work for others, as they need at least 1.65V :x But I can't use 533/88 nor CLK3, so it seems to be kind of deal ;) (or just component tolerance :D) I'm using SHR with our default 2.6.32 kernel. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
On Sat, Jul 10, 2010 at 21:36, Sebastian Krzyszkowiak d...@dosowisko.net wrote: On Sat, Jul 10, 2010 at 21:23, Tha_Man jeroenb...@hotmail.com wrote: Hi, Gennady suggested the same thing, but the 450Mhz-settings fail on kernel start (see my previous message, I haven't tried the 465 settings). These settings need a recompiled kernel according to Gennady's first message, did you recompile your kernel? If not, I'm very curious why it doesn't work for me! I'm assuming you're running QtMoko v24 as well, either from SD or NAND. Cheers, Tha_Man 450/112 and 465/116 settings work for me even with 1.55V (just tested) and it seems to not work for others, as they need at least 1.65V :x But I can't use 533/88 nor CLK3, so it seems to be kind of deal ;) (or just component tolerance :D) I'm using SHR with our default 2.6.32 kernel. If someone wants to test: http://dos.openmoko.pl/overclock/qi-s3c2442-master_c38b062a609f1442-dos-465-116-1.55-1.8.udfu Qi with CPU clocked at 465MHz with 1.55V and memory at 115MHz with 1.8V (so no kernel patch needed) http://dos.openmoko.pl/overclock/465-116-1.55-1.8.patch It works for me and so far seems to be stable, but most of you will probably need memory voltage being bumped to 1.9V and for that you need to patch kernel. I have GTA02A5 with date code 20080621. U-Boots compiled by gena2x are available at http://bsdmn.com/openmoko/uboot500/ -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
On Sat, Jul 10, 2010 at 22:22, Sebastian Krzyszkowiak d...@dosowisko.net wrote: On Sat, Jul 10, 2010 at 21:36, Sebastian Krzyszkowiak d...@dosowisko.net wrote: On Sat, Jul 10, 2010 at 21:23, Tha_Man jeroenb...@hotmail.com wrote: Hi, Gennady suggested the same thing, but the 450Mhz-settings fail on kernel start (see my previous message, I haven't tried the 465 settings). These settings need a recompiled kernel according to Gennady's first message, did you recompile your kernel? If not, I'm very curious why it doesn't work for me! I'm assuming you're running QtMoko v24 as well, either from SD or NAND. Cheers, Tha_Man 450/112 and 465/116 settings work for me even with 1.55V (just tested) and it seems to not work for others, as they need at least 1.65V :x But I can't use 533/88 nor CLK3, so it seems to be kind of deal ;) (or just component tolerance :D) I'm using SHR with our default 2.6.32 kernel. If someone wants to test: http://dos.openmoko.pl/overclock/qi-s3c2442-master_c38b062a609f1442-dos-465-116-1.55-1.8.udfu Qi with CPU clocked at 465MHz with 1.55V and memory at 115MHz with 1.8V (so no kernel patch needed) http://dos.openmoko.pl/overclock/465-116-1.55-1.8.patch It works for me and so far seems to be stable, but most of you will probably need memory voltage being bumped to 1.9V and for that you need to patch kernel. I have GTA02A5 with date code 20080621. U-Boots compiled by gena2x are available at http://bsdmn.com/openmoko/uboot500/ More Qi's to test at http://dos.openmoko.pl/overclock/ -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi, Do you have the PLL divider values (not sure if that is the correct term) for the other speeds? Here is values i used: Freq MDIV PDIV SDIV 450 142 21 465 147 21 480 152 21 500 117 11 533 125 11 549 175 21 564 133 11 Yeah, 549/CLK3 worked too, but it need a voltage of 1.75, and i have no idea is it in range. You may use s3c manual, which has formula to calculate dividers for almost any frequency. I tried to find good rounded values for some key frequnces like 500 or 533 or 450. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi,
Thanks for your research into reclocking. I've tried the 533-CLK2
version on one of my freerunners and it seems to work well. I am trying
to put your changes into my qi build. You have one patch posted for the
500-83 uboot which wasn't too difficult to adapt to qi.
Do you have the PLL divider values (not sure if that is the correct
term) for the other speeds?
Ben
Here is is the diff for the 500mhz version with CLK 2 (be careful, might
fry your fr, etc)
diff --git a/src/cpu/s3c2442/gta02.c b/src/cpu/s3c2442/gta02.c
index e9bc0a3..aadb495 100644
--- a/src/cpu/s3c2442/gta02.c
+++ b/src/cpu/s3c2442/gta02.c
@@ -35,7 +35,7 @@
#define GTA02_DEBUG_UART 2
#define PCF50633_I2C_ADS 0x73
-#define BOOST_TO_400MHZ 1
+#define BOOST_TO_533MHZ 1
static int battery_condition_reasonable = 0;
@@ -85,12 +85,12 @@ const struct pcf50633_init pcf50633_init[] = {
{ PCF50633_REG_AUTOENA, 0x01 }, /* always on */
- { PCF50633_REG_DOWN1OUT,0x1b }, /* 1.3V (0x1b * .025V +
0.625V) */
+ { PCF50633_REG_DOWN1OUT,43 }, /* 1.3V (0x1b * .025V +
0.625V) */
{ PCF50633_REG_DOWN1ENA,0x02 }, /* enabled if GPIO1 =
HIGH */
{ PCF50633_REG_HCLDOOUT,21 }, /* 3.0V (21 * 0.1V +
0.9V) */
{ PCF50633_REG_HCLDOENA,0x01 }, /* ON by default*/
- { PCF50633_REG_DOWN1OUT,0x1b }, /* 1.3V (0x1b * .025V +
0.625V) */
+ { PCF50633_REG_DOWN1OUT,43 }, /* 1.3V (0x1b * .025V +
0.625V) */
{ PCF50633_REG_DOWN1ENA,0x02 }, /* enabled if GPIO1 =
HIGH */
{ PCF50633_REG_INT1M, 0x00 },
@@ -299,10 +299,12 @@ void port_init_gta02(void)
PCF50633_I2C_ADS,
PCF50633_REG_BVMCTL) 1);
if (battery_condition_reasonable) {
- /* change CPU clocking to 400MHz 1:4:8 */
+ /* change CPU clocking to 533MHz 1:6:12 */
- /* clock divide 1:4:8 - do it first */
- *CLKDIVN = 5;
+ /* clock divide 1:6:12 - do it first */
+ *CLKDIVN = 7;
+unsigned int* CAMDIVN = (unsigned int*)0x4C18;
+ *CAMDIVN |= (18);
/* configure UPLL */
*UPLLCON = ((88 12) + (4 4) + 2);
/* Magic delay: Page 7-19, seven nops between UPLL and
MPLL */
@@ -316,7 +318,7 @@ void port_init_gta02(void)
nop\n
);
/* configure MPLL */
- *MPLLCON = ((42 12) + (1 4) + 0);
+ *MPLLCON = ((117 12) + (1 4) + 1);
/* get debug UART working at 115kbps */
serial_init_115200_s3c24xx(GTA02_DEBUG_UART, 50 /*
50MHz */);
@@ -666,7 +668,9 @@ const struct board_api board_api_gta02 = {
.get_ui_keys = get_ui_keys_gta02,
.get_ui_debug = get_ui_debug_gta02,
.set_ui_indication = set_ui_indication_gta02,
console=tty0
console=ttySAC2,115200
init=/sbin/init
diff --git a/src/cpu/s3c2442/lowlevel_init.S
b/src/cpu/s3c2442/lowlevel_init.S
index 2a1654c..9ba45a5 100644
--- a/src/cpu/s3c2442/lowlevel_init.S
+++ b/src/cpu/s3c2442/lowlevel_init.S
@@ -105,22 +105,22 @@
#define B5_PMC 0x0 /* normal */
#define B6_MT 0x3 /* SDRAM */
-#define B6_Trcd0x1 /* 3clk */
+#define B6_Trcd0x0 /* 23clk */
#define B6_SCAN0x1 /* 9bit */
#define B7_SCAN0x1 /* 9bit */
#define B7_MT 0x3 /* SDRAM */
-#define B7_Trcd0x1 /* 3clk */
+#define B7_Trcd0x0 /* 2clk */
/* REFRESH parameter */
#define REFEN 0x1 /* Refresh enable */
#define TREFMD 0x0 /* CBR(CAS before RAS)/Auto
refresh */
-#define Trp0x1 /* 3clk */
-#define Trc0x3 /* 7clk */
-#define Tchr 0x2 /* 3clk */
-//#define REFCNT 1113/* period=15.6us,
HCLK=60Mhz, (2048+1-15.6*60) */
+#define Trp0x0 /* 2clk */
+#define Trc0x1 /* 5clk */
+#define Tchr 0x0 /* 3clk */
+//#define REFCNT 997 /* period=17.5us,
HCLK=60Mhz, (2048+1-15.6*60) */
#define REFCNT 997 /* period=17.5us, HCLK=60Mhz,
(2048+1-15.6*60) */
/**/
@@ -129,6 +129,7 @@ lowlevel_init:
ldr r0, =SMRDATA
ldr r1, =BWSCON /* Bus Width Status Controller */
+ mov r2, #0
add r2, r0, #13*4
0:
ldr r3, [r0], #4
@@ -158,5 +159,5 @@ SMRDATA:
.word
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
[cut] I suspend my phone when I booted from u-boot, it won't resume... I'm using a QtMoko installation on my SD card, I haven't tried QtMoko on NAND-flash yet (can anyone confirm it should work?). Hi, I am using QtMoko on non-overclocked FR from NAND and it suspends/resume fine. -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Email secured by Check Point ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi again, I couldn't resist to do some more testing, so I copied my QtMoko SDcard installation to NAND. QtMoko from NAND boots fine in most cases (see overview), it's suspend and resume that fails when overclocked. However, suspend and resume works fine with the original NAND U-boot and your default clocked U-boot. I've flashed the overclocked images exactly as you posted and flashed u-boot_env.in as well, no errors were reported during flashing. Here's an overview: Tested under QtMoko v24, using different u-boot images flashed in NAND: + u-boot-gta02v5-1.3.1: works fine + u-boot.udfu_400_100_1.7: works fine - u-boot.udfu_450_112_1.65_1.9: won't boot (hangs on 'Starting kernel...') - u-boot.udfu_450_112_1.7_1.9_sdmax: won't boot (hangs on 'Starting kernel...') * u-boot.udfu_500_83_1.7: fails to resume after suspend * u-boot.udfu_500_83_1.7_1.8_CLK2: fails to resume after suspend * u-boot.udfu_533_88_1.7: fails to resume after suspend * u-boot.udfu_533_88_1.7_1.8_CLK2: fails to resume after suspend So most u-boot images boot fine with QtMoko v24 and report the correct speeds, but my phone doesn't wake up after suspend with any of the overclocked images; I have to remove the battery to be able to boot again. Even the 450Mhz-images you reported as 'working under qtmoko' fail with me, but I'm not sure if you tested suspend and resume. I'm using the default v24-kernel, based on 2.6.29 I believe. I hope my tests are of any help, if I need to test something else, please let me know. Cheers, Tha_Man -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5242777p5253190.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi, I couldn't resist to do some more testing, Thanks for testing :) u-boot.udfu_450_112_1.65_1.9: won't boot (hangs on 'Starting kernel...') u-boot.udfu_450_112_1.7_1.9_sdmax: won't boot (hangs on 'Starting kernel...') As i already told to use 450 or 465 you need kernel patch, and hang in 'Statring kernel ...' means exactly that you need kernel patch to test this kernels. so, to test it you need to get andy-tracking kernel from git and apply some similar patch on it (my patch is against .34). but my phone doesn't wake up after suspend with any of the overclocked images; currently i am trying completely other optimization idea. then i'll finish with it I return to overclocking and try to fix resume or other bugs, also push all this to wiki. PS. Hm seem i were not right, as i didn't applied patchs to qtmoko kernel- so seem I tested 500mhz (not 450) with qtmoko, but i tried so many configs, that i can't recall which one exactly i tested with it. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Thanks a lot for the clarification! I successfully flashed my Freerunner with u-boot.udfu_533_88_1.7_1.8_CLK2 and got the following results (from QtMoko/Debian): neo:~# dmesg | grep -i mhz [0.00] S3C244X: core 532.000 MHz, memory 88.666 MHz, peripheral 44.333 MHz neo:~# cat /proc/cpuinfo Processor : ARM920T rev 0 (v4l) BogoMIPS: 265.42 Features: swp half thumb CPU implementer : 0x41 CPU architecture: 4T CPU variant : 0x1 CPU part: 0x920 CPU revision: 0 Hardware: GTA02 Revision: 24420360 Compared to the original clocks: neo:~# dmesg | grep -i mhz [0.00] S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz neo:~# cat /proc/cpuinfo Processor : ARM920T rev 0 (v4l) BogoMIPS: 199.47 Features: swp half thumb CPU implementer : 0x41 CPU architecture: 4T CPU variant : 0x1 CPU part: 0x920 CPU revision: 0 Hardware: GTA02 Revision: 24420360 -- So basically from 200 bogoMIPS at 400Mhz to 265 bogoMIPS at 533Mhz, very nice! The QtMoko interface seemed even more responsive, I was able to operate my phone normally and start Navit for example. However, QtMoko seems to have a problem with booting from u-boot using an SD card and suspending. I tried both with *and* without the overclock, but when I suspend my phone when I booted from u-boot, it won't resume... I'm using a QtMoko installation on my SD card, I haven't tried QtMoko on NAND-flash yet (can anyone confirm it should work?). This is obviously a QtMoko problem and not related to the overclock, but still I am curious: is it possible to achieve the overclock when booting with Qi, by setting kernel parameters or something? Thanks for your efforts and I hope others will test it as well! Cheers, Tha_Man -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5242777p5251377.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi, have you been able to test for stability over a few days of normal operation? I am using mostly 533/88/clk2 now and over versions for may be 5 days. So far i have no problems. I run tests on all recommended versions, also run cpu-intensive video decoding without problems. But i'm on .34 and can't test some features, like suspend, sound, gsm, but things i tested works good (usb, glamo video and mmc, cpu). I tried qtmoko and it were working for 450 version. Freerunner feels warmer, so i measured temperature, but without opening that shielding. While 100% cpu load shield temperature is 32C. Also i noticed it can't stand overnight without usb and suspend due to bigger power consumption, but with suspend this should be ok. i know 3 people who tryed it. one were unable to run any clk2 versions, so he tried 533/clk3. but he very able to run 465 version with default 1.8 on memory bus. One man reported he is unable to suspend, may be kernel need some fixes to suspend/resume properly, but currently my .34 can't suspend more than once anyway, so i didn't test this. So far no unrecoverable errors reported. No fried frs. One man reported flash error but this turned out to be bad sector on NAND, and he begun experiments on NAND after changing clock, and we were unable to attribute this to overclocking. I will need to patch/recompile my kernel besides flashing a new Uboot. No, you need to recompile/patch kernel only for versions with modified memory bus voltage (forth number, if prefent in file name and != 1.8), so 533/88, 500/83 versions may be tried without patches. If you not were familiar with u-boot, here is instruction: 1. flash u-boot environment: from nor u-boot on fr: sudo dfu-util -a u-boot_env -D u-boot_env.in 2. check if default u-boot can boot you system and become familiar with environment: power off, boot with pressing power and in 0.5 sec holding aux for a while. 3. flash reclocked u-boot: sudo dfu-util -a u-boot -D u-boot.udfu_533_88_1.7_1.8_CLK2 4. try to boot it in similar way. if not boots, try u-boot.udfu_533_88_1.7 , you may try also with more risk u-boot.udfu_465_116_1.65_1.9 this may work without kernel patch. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
This is seriously cool! Great to see an overview at different speeds, have you been able to test for stability over a few days of normal operation? If I understand correctly, I will need to patch/recompile my kernel besides flashing a new Uboot. Is this is easy to do for kernels of popular distro's, such as SHR and QtMoko? I'm willing to give it a try, but I'm very curious for other users' experiences on speed, stability and power consumption! -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cpu-reclocking-to-500Mhz-overclocking-to-533Mhz-performance-tests-and-bootloader-images-tp5233089p5237705.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Impressive indeed, I think I will try the safe overclock soon :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
cpu reclocking to 500Mhz, overclocking to 533Mhz, performance tests and bootloader images
Hi, list. This time i decided to try to look at performace from other side: check clocking, sdram timing and other things, so here is my report. I already announced it on IRC. Foreword: WARNING!!! Do it at your own risk nobody will be responsible in any case of problems, Only thing i can say: all configurations were at least tried here. Some were also tested. I will use something of 533/88/clk2 or 465/116, or finally 500/83/clk2 in case of any troubles. I'm not hw engineer. Foreword 2: I hope some hardware expert review my findings. --- Theory: 1. CPU Facts: In BOM, it is stated our CPU is stated as '500mhz 1.7v'. Unfortunately I have only manual for 400Mhz version, so i can't tell for sure which voltage range can be applied to it. Voltage: according to schematic, voltage is used only to feed CPU. So.. conclusion: 500mhz and 1.7 voltage is native for our cpu so this never will hurt it, but board were not designed for 1.7V. may be some hw expert may review this. 2.Memory. Facts: We have 2 sdram modules - 1 inside cpu and 1 outside. both have same timings. both are clk3 at up to 133Mhz, and clk2 at up to 83mhz. Idea: So, conclusion: at 100Mhz, memory not show all it's potential, as we have to run it on clk3 and (according tests) 88mhz/clk2-2-2 is same speed to 100mhz/clk3-3-3. Also it SDRAM itself should run up to 133Mhz without troubles. Bus: Memory is on same bus as: part of glamo, nand (internal), wifi. sdram (internal), nor flash, and may be something else so it's generally bad idea to increase it's voltage. If we need to rise memory voltage it will not be really good idea, and i in fact didn't checked all harware for compatibility, but here is what i checked: sdram in cpu - up to 1.95 ok sdram - up to 1.95 ok cpu - up to 1.95 ok glamo - up to 1.9 ok nand voltage on any pin relative to Vss - -0.5-2.45 unsure, but sounds ok ok. 3. USB usb have separate clock, so forget it. 4. overall frequency CPU freq may be to almost any value, but it is limited to rate 1:3:6 or 1:4:8 or 1:6:12. no 1:5. (ratings CPU/MEMORY/PERIPHERIAL). --- Practice: i saved different uboots which sets differents speed: www.bsdmn.com/openmoko/uboot500 many of them are not working, all were tried here. once i even thought my fr i dead, but at the end i found that it is just my AUX desoldered. so i fixed AUX and continue tests bravely :) if you not planning to dive deep in this topic i consider you be interested in slightly overclocked: www.bsdmn.com/openmoko/uboot500/u-boot.udfu_533_88_1.7_1.8_CLK2 you need nothing to test it. in case of troubles it will be useful to try non-overclocked, in-spec version: www.bsdmn.com/openmoko/uboot500/u-boot.udfu_500_83_1.7_1.8_CLK2 for whoose who like a bit more speed, risk to hardware and work, assume your fr is fried before trying this, but this works here and is fastest config: www.bsdmn.com/openmoko/uboot500/u-boot.udfu_465_116_1.65_1.9 and in case of trouble a bit slower: www.bsdmn.com/openmoko/uboot500/u-boot.udfu_450_112_1.65_1.9 default u-boot is 400_100_1.5_1.8_CLK3. so, CPUCLOCK_MEMCLOCK_CPUVOLTAGE_MEMVOLTAGE. if something not mentioned in file name - it is default. as you see last 2 configs use modified memory voltage. to use it you need patch to the kernel. by default kernel will reset voltage to 1.8. patched kernel allow 1.8-1.9 range, see patch and end of mail. I tested all working configs to Xorg, on .34 kernel. decoded some videos on both u-boot.udfu_465_116_1.7_1.9_sdmax and u-boot.udfu_533_88_1.7_1.8_CLK2 --- u-boot setup help for whoose who not familiar with u-boot setup i provided www.bsdmn.com/openmoko/uboot500/u-boot_env.in flash it with: dfu-util -D u-boot_env.in -a u-boot_env use power - wait 0.3s -hold aux for nand uboot menu. --- Power consumption: sorry, no tests :( may be someone? --- Performance testing: i tested several working configurations with lmbench: www.bsdmn.com/openmoko/uboot500/lmbench.txt as you can see, 462/116 version seem best from kernel subsystem point of view. of course, pure computation will be better with 533/500Mhz. 550Mhz is excluded as it requires 1.75V CPU, and CLK2 version also 1.9V mem and were not 100% stable. for whoose who not familiar with u-boot: you may flash setting partition, use file u-boot_env and flash it with -a u-boot_env. press power and and 0.5 sec aux for NAND uboot menu. --- Patches uboot clk2:http://www.bsdmn.com/openmoko/uboot500/CLK2.patch uboot frequency setting sample:http://www.bsdmn.com/openmoko/uboot500/500_83_1.7.patch kernel patch to allow 1.9v on memory/other peritherials bus:http://www.bsdmn.com/openmoko/uboot500/kernel_memvoltage.patch Hope you'll have fun with faster fr :) Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
