I am trying to port SerialICE to my Geode GX2 board and wanted to use rdmsr /
wrmsr for serial init but they seem a little different to the Coreboot
Am i right that the extra "key" value always has to be: 9c5a203a and acts as a
extra safety measure ?
Thanks , Nils.
I get several warnings and errors and would like to know if they are my fault.
This warning i get when i first do make menuconfig.
The target is then still qemu.
This warnings i get always after compiling SerialICE.
This Segmentation fault i get sometimes when compiling.
After doing again make clean and make it succeeds without segfault.
This backtrace i get sometimes when compiling.
After doing again make clean and make it succeeds without backtrace.
As nobody seems to have time to answer, i will answer to myself now that i get
some response on the serial port. :)
Op zaterdag 16 april 2011 23:47:49 schreef u:
> I am trying to port SerialICE to my Geode GX2 board and wanted to use rdmsr
> / wrmsr for serial init but they seem a little different to the Coreboot
> Am i right that the extra "key" value always has to be: 9c5a203a and acts
> as a extra safety measure ?
Working on an Atom D500/NM10 system, trying to get some info on memory
init. Everything seems to go alright up to when it starts pulling SPD
data from the SMBus, but for some reason, the stock BIOS performs an
SMBus read at 0x60, checks and sees that the read completed
successfully, clears the success bit, and then, without reading the
data, tries 0x64, and does the same thing. It then moves on to 0x9c,
0xd3, and 0xd2. I've attached a log file, don't mind my notes. Any
ideas what might be causing this, and how to work around it?