Hi Paul,
I solved it in the meantime by installing a "pullup" R (45,5k/.5% T)
from +5V to FB pin and getting a clean 1.004V output (using a resistor
array for exoerimenting), while setting the VID1-5 to 01111 to get a
min. of 1.100V. Pourly the BIOS don't allow to boot up then. I tried
all three A7N8X-E Deluxe, A7N8X-X and A7N8X-E with this (all have a
nearly identical BIOS). They work good after using a standard e.g XP
Barton (after putting the VRM to standard). My hope was to use an
NVidia based board instead of the K400VM we already using. Upgrading
the BIOS to 1010 didn't help either.
Anyway the Geode is the best CPU I've seen in years (The P-M was quite
nice before). It outperforms it VIA C3 rival by far and even consums
less power. But same as P4M: it has different (incompatible) VID and
CPU-ID.
Thanks for your reply it gave me the right direction. The pic'd have
helped me to find out how we reenginered the A7V8X without having one
at hand.
Cheers
Sam
There are some things you could try:
First off, I traced an Asus motherboard a while back, and found
a circuit that looks like this:
---------- -------- VID ---------------
|processor|---|series |-------+------------|Vcore regulator
|VID pins |---|resistor|---------+----------|chip
---------- -------- | | ---------------
| |
-----------
| SuperI/O |
| overrides |
| VID |
-----------
^ ^
| |
BIOS programming
Basically, the idea is, the Super I/O chip has some GPIO pins
that are tristated at powerup. The logic 0 or 1 value from the
processor VID pins propagates to the Vcore regulator. The
processor receives its nominal voltage just after reset is
deasserted. The series resistors give the processor "weak"
control over the VID signals.
If the user enters the BIOS and changes the VID code from the
default, then the Super I/O chip enables the drivers on the
GPIO pins, and the BIOS then has control of the VID values.
The GPIO driver strength is sufficient to override the
processor VID code.
So, for absolute control over VID, bend up the VID pins on
the Vcore regulator chip, and hardwire logic 0 or logic 1
directly to the Vcore regulator. That will prevent the BIOS
from changing things on you.
Secondly, with an AthlonXP in the socket, enter the BIOS
and disable Vcore monitoring. It should be in the hardware
monitor page, and maybe if you select [disable] for Vcore,
the processor won't react to the abnormally low Vcore.
If this still doesn't work, trace the Vcore voltage signal
which is fed to the hardware monitor chip. Clip one probe
of the ohmmeter, to the Vcore copper plane around the
processor socket. Do a "lap of the pins" of the ASB100 with
the ohmmeter, looking for a pin that is connected to Vcore.
The magnitude of Vcore is low enough, that a voltage divider
network is not likely to be used in the path from Vcore.
If you can manage to find where the ASB100 monitors Vcore,
then bend up that pin, and make a two resistor voltage divider,
and tie the top of the divider to +3.3V. Select resistors to
give 1.65V, which could be a couple of 1K ohm resistors if you
want. By doing that, you will "blind" the BIOS, so it cannot
sense the abnormally low voltage.
The only other issue would be the Vcore regulator itself. It
has internal detection of out of range voltage, so be careful
to not overdo it with the FB resistor. I would try setting 1.1V
directly to the VID pins on the regulator, and not bother using
FB, until you can get the BIOS sufficiently "blind" so it
won't stop the booting.
It is also possible the voltage is not an issue, and the Geode
just isn't recognized by the BIOS as a valid processor.
HTH,
Paul
