Ok, I only just checked it now with the AC adapter, but earlier today I was running some emulators that have the ability to up the CPU speed to 333mhz, while running Nester my game locked up, the power light started flashing on and off, and my PSP shut off, I just assumed this was due to my battery being kind of low, and shrugged it off.
I just checked my PSP now with the AC adapter plugged in, and it does not turn on at all... So I'm assuming something happened running it at 333mhz, just a warning to you guys :\
I really can't think of what else it could have been.
Running homebrew emu's at 333mhz MAY have killed my PSP
Running homebrew emu's at 333mhz MAY have killed my PSP
Last edited by kemical on Tue Jun 14, 2005 3:20 pm, edited 1 time in total.
-
Guest
Well, i dont know for sure if it was from overclocking it, does the power light near the battery switch usually flash on and off if the battery is low? (the emulator froze also..)
I was running Nester at the time, so I don't know the coding specific stuff, I just had it set on 333mhz and had been playing for a while, prior to that I had been messing with all other emulators that have recently had the CPU adjustment added (it really helps get extra fps..!)
I was running Nester at the time, so I don't know the coding specific stuff, I just had it set on 333mhz and had been playing for a while, prior to that I had been messing with all other emulators that have recently had the CPU adjustment added (it really helps get extra fps..!)
Well Sony locked the clock at 222 MHz because the battery would run out quickly, but I'm sure there are other reasons why they don't allow developers to run their code at 333 MHz.
Sony really only said the clock goes from 1 to 333 MHz. They never said it was safe to run a PSP at 333 MHz, they just said it can do it because it looks better on specs sheets.
What emulators run at 333 MHz besides Nester anyway?
Sony really only said the clock goes from 1 to 333 MHz. They never said it was safe to run a PSP at 333 MHz, they just said it can do it because it looks better on specs sheets.
What emulators run at 333 MHz besides Nester anyway?
Yes it does. Also, the PSP usually goes into sleep mode automatically if the battery gets too low, so that's probably what's happened - except of course the emulators don't support sleep mode. I'm not sure how you do a cold boot on a PSP - maybe take the battery out, wait 30 seconds, then put it back in?kemical wrote:Well, i dont know for sure if it was from overclocking it, does the power light near the battery switch usually flash on and off if the battery is low? (the emulator froze also..)
Dan Jackson
I don't think that this is because of the overclock.
I'm a moderator at a Swedish PSP Forum and I've seen two maybe three members getting the same problem, during normal use (no overclock and one of them was/is using his PSP for homebrew).
I will ask one of them how he solved the problem.
Edit: Do not empty your battery, if you notice the little green light flash, turn your PSP off (or at least put it in sleep mode)!
I'm a moderator at a Swedish PSP Forum and I've seen two maybe three members getting the same problem, during normal use (no overclock and one of them was/is using his PSP for homebrew).
I will ask one of them how he solved the problem.
Edit: Do not empty your battery, if you notice the little green light flash, turn your PSP off (or at least put it in sleep mode)!
Were these people who had this problem able to fix their PSP or did they remain dead?Soir wrote:I don't think that this is because of the overclock.
I'm a moderator at a Swedish PSP Forum and I've seen two maybe three members getting the same problem, during normal use (no overclock and one of them was/is using his PSP for homebrew).
I will ask one of them how he solved the problem.
Edit: Do not empty your battery, if you notice the little green light flash, turn your PSP off (or at least put it in sleep mode)!
-
0xdeadface
- Posts: 62
- Joined: Tue May 31, 2005 5:11 am
Well... by saying "I will ask one of them how he solved the problem." and "one of them was/is using his PSP for homebrew" I would say it's obvious. In other words, yes they did fix it. I belive that it was no big deal.Shapyi wrote:Were these people who had this problem able to fix their PSP or did they remain dead?
I'm waiting for him to logon so I can ask him this (MSN). I will inform you ASAP =]
Edit: 0xdeadface: Hehe, I was writing when you posted that =P
Last edited by Soir on Wed Jun 15, 2005 12:24 am, edited 1 time in total.
Let's just make this clear.
This member played on his PSP until the little light flashed and his PSP shut down... he could not re-activate the PSP because of the low-power (it would seem that there was not much power at all left in the battery). When he tried to charge it, nothing happend. The PSP didn't charge the battery and he could therefor not even get the slightest signal from his PSP.
I don't know if your problem is similar so please write back, kemical.
This member played on his PSP until the little light flashed and his PSP shut down... he could not re-activate the PSP because of the low-power (it would seem that there was not much power at all left in the battery). When he tried to charge it, nothing happend. The PSP didn't charge the battery and he could therefor not even get the slightest signal from his PSP.
I don't know if your problem is similar so please write back, kemical.
This just sounds like your PSP went into standby and that crashed Nester because it didn't know how to handle the powerstate callback.kemical wrote:Soir, thats exactly what seems to be happening, I didn't get a chance to try it again today, but I will when I get home.
Have you tried turning off your PSP properly rather than just putting in and out of standby? If you slide the power switch up and hold it there for about 5 seconds it will power off completely. Then try powering it back on.
Steddy
Before you try this:
definitely try this:try to remove the backup battery from the mainboard for a few hours
I know for a fact I could get my 1.0 PSP into an "unknown state" where it didn't want to do anything and wasn't responding to the power button. holding the power button for ~10-15 seconds was required sometimes.[/quote]Have you tried turning off your PSP properly rather than just putting in and out of standby? If you slide the power switch up and hold it there for about 5 seconds it will power off completely. Then try powering it back on.
Kemical... I think a lot of people here are waiting from you to fully test if you can bring back your PSP to live here or not.
And if it is really due to a 333Mhz overclock.
By spreading wrong information, a lot of people are afraid or wait to use a feature that is may be doing NO DAMAGE whatsoever to the hardware.
If you are busy / had no time to answer, we all understand.
Else please see that the thread you started may spread very bad rumours about the PSP clocking feature.
Please inform us ASAP of all the things that you have checked.
Thanks for your understanding.
And if it is really due to a 333Mhz overclock.
By spreading wrong information, a lot of people are afraid or wait to use a feature that is may be doing NO DAMAGE whatsoever to the hardware.
If you are busy / had no time to answer, we all understand.
Else please see that the thread you started may spread very bad rumours about the PSP clocking feature.
Please inform us ASAP of all the things that you have checked.
Thanks for your understanding.
To be honest, I would rather see people use lower clockrates (or lowest possible for each software) and learn how to better optimize their code. So I wouldn't mind if too high clockrates damage the PSP ;), although I don't really believe that (as long as it's below 333).
just my two cents as an assembler optimizing freak :)
just my two cents as an assembler optimizing freak :)
infj
I agree. Although it is harder and takes more work, we would get a lot better results if the coders optimized their code better to run on PSP. I mean a straight port won't deliever the best results and using 333 MHz as a crutch really isn't a good idea.Saotome wrote:To be honest, I would rather see people use lower clockrates (or lowest possible for each software) and learn how to better optimize their code. So I wouldn't mind if too high clockrates damage the PSP ;), although I don't really believe that (as long as it's below 333).
just my two cents as an assembler optimizing freak :)
I mean a lot of people assume that Sony just limited the CPU to 222 MHz for battery conservation. I mean its untested territory we are talking about that doesn't have an official stamp of approval. And if your PSP fries, then Sony really won't do anything about it.