VxWorks 5.5.1 or 6.0 on Intel D865GBF motherboard.

VxWorks 5.5.1 or 6.0 on Intel D865GBF motherboard.

Post by Jon » Sat, 14 May 2005 02:34:47


Hi all,

Is anyone using VxWorks (5.5.1 or 6.0) on an Intel D865GBF motherboard?
The bootrom loads and runs, but the kernel hangs right after loading.
I can run the same bootrom & kernel on other platforms, so presumably
it's something special about this motherboard. I disabled all the
onboard controllers and such, but alas, it still hangs. :-(

Any ideas or suggestions?

advTHANKSance. (Thanks in advance :-)

-Jon
5/12/2005
 
 
 

VxWorks 5.5.1 or 6.0 on Intel D865GBF motherboard.

Post by David Hame » Sun, 15 May 2005 19:29:16


I suspect the problem is with the processor, not the chipset.
Certain recent Pentium4 processors hang when reading model specific
registers that are not actually present. Unfortunately, certain
registers present on P6 cores are no longer present on P7 cores and
vxWorks mistakenly attempts to read these registers.

To prove that this is the case for you, try a vanilla Pentium BSP,
(CPU=PENTIUM). That configuration will avoid reading the problem
registers. If this fixes the problem, call Wind River tech support and
get a patched version of pentiumLib.o

 
 
 

VxWorks 5.5.1 or 6.0 on Intel D865GBF motherboard.

Post by David Hame » Sun, 15 May 2005 19:29:38


I suspect the problem is with the processor, not the chipset.
Certain recent Pentium4 processors hang when reading model specific
registers that are not actually present. Unfortunately, certain
registers present on P6 cores are no longer present on P7 cores and
vxWorks mistakenly attempts to read these registers.

To prove that this is the case for you, try a vanilla Pentium BSP,
(CPU=PENTIUM). That configuration will avoid reading the problem
registers. If this fixes the problem, call Wind River tech support and
get a patched version of pentiumLib.o
 
 
 

VxWorks 5.5.1 or 6.0 on Intel D865GBF motherboard.

Post by Jon » Thu, 02 Jun 2005 08:26:41

Hi David,

Thanks for the suggestion. Unfortunately we're already compiling for
just Pentium so I'm still struggling with the problem. For the past few
weeks I've been playing with various combinations of hardware and
software and discovered that the CPU does have at least some impact. In
my original tests with the Intel D865GBF motherboard, I was using a
2.0GHz Celeron. With that I was able to get to the bootrom, but no luck
getting to the kernel. I switched the CPU to a 2.8GHz Pentium 4 and the
board wouldn't even get into the bootrom -- it would reboot as soon as
it attempted to load the bootrom (or maybe it was when it loaded the
bootload; that was a couple weeks ago and I don't remember clearly).

Long story short, I was not able to get a similar Intel motherboard
working (one had an onboard 100baseTX NIC and the other a 1GBit NIC).
However, I was able to successfully boot an Asus motherboard using the
2.0GHz Celeron and our modified bootom and kernel, so there's some
strange interaction between processor, motherboard, bootrom/kernel and
possibly phase of the moon... Since we have other fires to stamp out,
we might just box up one of the Intel motherboards, ship it to Wind
River and say "Please make this work." >8)

However, in the mean time I'm open to any other suggestions. :^)

-Jon
5/31/2005
 
 
 

VxWorks 5.5.1 or 6.0 on Intel D865GBF motherboard.

Post by dan » Sun, 05 Jun 2005 07:12:39

The Intel 865 chipset is "stealing" memory from the CPU for the graphics
component.

The vxWorks autosize function is walking off the end of the CPU memory and
crashing the chipset.

Turn off autosize in the BSP and set the memory size to 8, 16 or 32 less
than the real amount or I can show you how to use BIOS INT15 in romInit.s to
find the real top of memory...

- dan