Gp2x Delfault Runing 298mhz !!!


best case scenario (but probably impossible)-

Gp2X menus run at 298mhz, but when a .gpe is launched the clockspeed reverts to 200mhz.
It would explain this and the battery life, and would allow increased performance through overclocking at a later date.

Maybe I am just too optimistic.
 
declaration posted on Dec 9 2005 at 06:15 PM said:
best case scenario (but probably impossible)-

Gp2X menus run at 298mhz, but when a .gpe is launched the clockspeed reverts to 200mhz.
It would explain this and the battery life, and would allow increased performance through overclocking at a later date.

Maybe I am just too optimistic.

I hope you are right, i really hope, this would be great.
Wow, does that mean the gp2x is @298 Mhz (or 260, does not matter) when i read a */txt file :blink: :lol:
 
Last edited by a moderator:
DijiTao posted on Dec 9 2005 at 07:45 PM said:
/me Waits patiently for reputable source to clarify the situation

If a developer is not a reputable source, then who is? Mrs. Hong?
 
Last edited by a moderator:
Yuglooc posted on Dec 9 2005 at 06:45 PM said:
I guess the last three is in Hz, so

Sys Freq: 298,6Mhz M 73 P 0 S 0
UCLK :Freq: 95,8Mhz
ACLK :Freq: 147,4Mhz

And I guess thats where They have gotten the number 298 from

I wondered that too, but it says Mhz.
 
Last edited by a moderator:
declaration posted on Dec 9 2005 at 06:15 PM said:
best case scenario (but probably impossible)-

Gp2X menus run at 298mhz, but when a .gpe is launched the clockspeed reverts to 200mhz.
It would explain this and the battery life, and would allow increased performance through overclocking at a later date.

Maybe I am just too optimistic.



if you turn the speed to 130 with the clock utility, the emus get slower :p

so, no :D

but on mine , the software says 210, not more, is it because the soft doesn't go higher?

i also had a few crashes after having changed the speed, with makes me wondering...........
also , emus don't seem slower AT ALL if the speed is manually set to 200, so is my GP running at 210 instead of 298 ? (firmware 1.0 ;) )
 
Last edited by a moderator:
nik166 posted on Dec 9 2005 at 07:46 PM said:
also , emus don't seem slower AT ALL if the speed is manually set to 200, so is my GP running at 210 instead of 298 ? (firmware 1.0 ;) )
I have not flashed my firmware and I also get a frequency of 210 reported. However if I select 210 then there is a noticible change in the display - it looks washed out in comparison.
 
Last edited by a moderator:
The best way to determine the true clock speed is writing an assembly loop with a known cycle count (which runs for millions of cycles) and counting how many times it executes within a known time (checking for a keypress to stop it would be simplest to make). Just stopwatch it for 10 seconds or so... I did this for my Casio Algebra FX 2.0 a while back, and it came out to about 8 mhz (cool ass calculator btw... x86 processor, runs ROM-DOS built in...)
 
at 210 i see the flicker passing slooooooowly over the screen :D

(i'd say 2.5 waves per second :p )

but i don't see any speed difference in the emus, i would almost say they feel faster:/

if you set a speed of 133, the flicker is back ! :D
 
I'd say that they have their multipliers / clock speeds from crystal detected wrong.

A properly designed software loop should detect to speed of the proc. True it might of off my 5% in either direction but it should prove what the default is.

nearly 300Mhz in a menu... OVERKILL.

(prolly get away with 50Mhz... Its a menu geez)
 
nik166 - do you notice a change in the intensity of the colours when you select 210 ? I get no flicker before or after - just a 'washing out' of the colour.
 
I have not yet read the datasheet yet but usually it works like this: You have a crystal or clock generator which generates a clock. (The value (Hz) is written on it.) This is then scaled (divided or multiplied by a PLL) in the chip. By simply checking the crystal and the reading the appropriated registers in from the chip you should be able to calculate the clock. Sometimes you are able to let the chip generate its own clock but this is (nearly always) very inaccurate.
I don't have my hardware yet :( so I am not able to check things at the moment.
 
digitaljez posted on Dec 9 2005 at 07:07 PM said:
nik166 - do you notice a change in the intensity of the colours when you select 210 ? I get no flicker before or after - just a 'washing out' of the colour.


nothing like that here, only the "flicker wave" passing at a different speed, it's a brighter wave but that's all :D


but i still have firmware 1.0 cuz i can't flash, so maybe the flicker would be gone with the 1.0.1 and i would see something else when changing the speed ;)
 
Last edited by a moderator:
Quiest posted on Dec 9 2005 at 07:45 PM said:
Yuglooc posted on Dec 9 2005 at 06:45 PM said:
I guess the last three is in Hz, so

Sys Freq: 298,6Mhz M 73 P 0 S 0
UCLK :Freq: 95,8Mhz
ACLK :Freq: 147,4Mhz

And I guess thats where They have gotten the number 298 from

I wondered that too, but it says Mhz.

Yap, me too, someone willing to find this out??
or explain what ACLK /UCLK is?
w8, *google*

EDIT: Google didn't make me wiser this time...
 
Last edited by a moderator:
nik166 posted on Dec 9 2005 at 08:11 PM said:
but i still have firmware 1.0 cuz i can't flash, so maybe the flicker would be gone with the 1.0.1 and i would see something else when changing the speed ;)
I have not flashed mine either - I wonder if we are talking about the same thing ? You say it is brighter and I am calling it 'washed out' - but it could amount to the same thing.
It might be useful if we can establish if those who have flashed are getting 298 while those on 1.0 are getting 210. The question is, why does selecting 210 when it already reports as being 210 make a difference to nik166 and I ?
Also I am not getting the UCLK/ACLK text or values displayed.
 
Last edited by a moderator:
There's been a misundertanding. It's not the processor that's running at 298 MHz, it's the system clock. The problem is that those values don´t seem to fit with the actual speed the processor is running at, i.e. there's no pair of integers which can divide that 298 down to 200 or 266 easily.

By the way, some of you may be using an older aplication which shows a '210' from startup. That's not the cpu speed but a limit the developer has set in order for users not to burn their units. Go and get the newer version which displays the detected speed instead.
 
digitaljez posted on Dec 9 2005 at 07:23 PM said:
we are talking about the same thing ? You say it is brighter and I am calling it 'washed out' -

i say the passing wave is brighter, not the screen, how about you ? ;)
 
Last edited by a moderator:
iluntasun posted on Dec 9 2005 at 08:04 PM said:
By the way, some of you may be using an older aplication which shows a '210' from startup.


downloaded an hour ago from a link on this topic :p


where's that new one you're talking about? ;)
 
Last edited by a moderator:
Back
Top