[coreboot] Hello,,,I've been trying to bring coreboot up on an EP80579 reference platform (not Truxton) and I have thus far been thwarted.,,I'm using svn revision 5442 and the boot hangs with just the welcome to coreboot line:,,coreboot-4.0-r5422M Tue Apr 13 18:13:08 PDT 2010 starting...,,I've put several print_info statements in romstage.c and narrowed it down to the following line in i3100_early_lpc.c:,,pci_write_config32(dev, 0x44, pci_read_config32(dev, 0x44) | (1 << 7)); ,,Further debug shows that in general I can not read a value and then use the value. If I just perfrom a read operation it executes the instruction and contiues. But if I do a read and try to use a print_info_hexXX function it just hangs.,,I'm really at a loss where to go from here for debugging. I don't have a JTAG TAP that I can step through code to identify the assembly code I'm getting stuck on. I've tried the Truxton BIOS in my reference board and this works fine. I can also get the boot farther along if I remove the pci_read_config32 commands (for example in the above line I just use the default value for register 0x44 instead of reading it in).,,I'm using gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5),,Any ideas on what to try next? Is there a recommended toolchain?

[Dustin Harrison]

Hello,

I've been trying to bring coreboot up on an EP80579 reference platform 
(not Truxton) and I have thus far been thwarted.

I'm using svn revision 5442 and the boot hangs with just the welcome to 
coreboot line:

coreboot-4.0-r5422M Tue Apr 13 18:13:08 PDT 2010 starting...

I've put several print_info statements in romstage.c and narrowed it 
down to the following line in i3100_early_lpc.c:

pci_write_config32(dev, 0x44, pci_read_config32(dev, 0x44) | (1 << 7));

Further debug shows that in general I can not read a value and then use 
the value.  If I just perfrom a read operation it executes the 
instruction and contiues.  But if I do a read and try to use a 
print_info_hexXX function it just hangs.

I'm really at a loss where to go from here for debugging.  I don't have 
a JTAG TAP that I can step through code to identify the assembly code 
I'm getting stuck on.  I've tried the Truxton BIOS in my reference board 
and this works fine.  I can also get the boot farther along if I remove 
the pci_read_config32 commands (for example in the above line I just use 
the default value for register 0x44 instead of reading it in).

I'm using gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5)

Any ideas on what to try next?  Is there a recommended toolchain?

Thanks in advance for any help!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20100413/8b4be9d4/attachment.html>