Maybe this is the only method to show the people the consequences of overvolting a cpu and what electromigration does. First becomes unstable at higher clocks, no matter the voltage used; more voltage, more deterioration. If voltage is not reduced, the cpu will become unstable even at officially...
The "detector" pic shows that you are measuring resistance and not voltage. Put the selector in 2000m or 20v and check again. The red and black wires order isn't important, i'll show negative or positive but always the same value. T7 is Black (GND) and T8 is Red (vcore).
If you read a few posts above, I found that point T7 is GND and T8 vcore. Check the voltage measuring this two points. :)
Greetings and good luck
P.S. Remember that anything above 1.95v is DANGEROUS even if it works fine. The GP32 CPU is 0.18 micron built, like Intel Pentium III 600-1000 MHz...
The broken gp32 which I used for testing the mod does not overclock more at 1.95v than default 1.78v... only 156 MHz stable. Very frustrating... so I attempt the mod on my working GP32, also only 156 stable by default. The results are a bit better, is stable at 166 MHz with 1.95v...
Well, i'm still researching and i've found some things:
- About 20 or 30 blind-attempts with 2v or more and the CPU still lives :D
- More than 1.96v does not boot my gp32
- Pencil increases conductivity during the first hours applied:
Put some and CPU gets 1.90v.
Two hours after and with no...
That is right, I put two passes of pencil and the reading was the same, 1.78v. Added 2 more but with more pressure and in a second powered, the polymeter read 2.48v
Removed pencil and GP32 is still alive :o
Ok, before apply the mod i've looking for the points where the polymeter should read vcore and I think T7 is GND and T8 vcore... at least my flu gives 1.78v in that points. Anyone knows if this is true?
I opened my flu and found something extrange...
On top of R48 I can read 300 and on top of R52 640
I thought all GP32 had R48 of 200K and R52 of 470K ... or are there some kind of encrypted codes to assign valors to SMD components?
My 6GB-notebook-Hard-Disk-USB2.0-cased works perfectly :)
But my 256mb pendrive-mp3player-USB1.0 doesn't work :(
Any news of Toholl and his SMC Kernel module writing improvement?
Yesterday I attached a "6-Gb-2.5-inch-usb-boxed-hard-disk" to my flu and voilá! kernel detects it!
I have compiled busybox static-linked for arm and i'll try to compile nanox... I want to get the point which is now gp32linux... and maybe try some new challenges :)
Well, I patched the kernel to get SquashFS support and as I expect, the input-key-events sent are working on opie :D ... except special keys as enter, shift, tab... :unsure:
I'll continue working on it after weekend, I have to prepare my last exam :angry:
Where could we find the squashfs patch for linux-2.4.13-gp32? The official site has patches for kernels 2.4.19 and up :huh:
I'd like to test my pad-keyboard kernel module with opie but my own kernels can't mount squashfs initrd...
Well... my original idea was to code a kernel module to get chars from gp32 pad in a style like arcade hi-score input: up and down to change char, left and right to move cursor and one button as enter, other as tab... etc.
I'd be using input core events, so this module could send keyboard...
I made a "keyboard wrapper" kernel module using input core to introduce chars using gp32 pad and it works on PC... but on GP32 the chars are not assigned as in /linux/input.h kernel header.
Anyone knows how to fix this assignment?