Hey list I currently working on a Igel Thin Client 3210. The board is very closer to bcom/winnetp680. CN700 northbridge VT8237R southbridge W83679HF SuperIO A try with this tree did not work. I'm not new to coreboot and think that the first debug message should apear on the serial-console, but nothing happens.
I have compiled nearly all via boards to test the ROMs with qemu. And get always this message: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ qemu: fatal: Trying to execute code outside RAM or ROM at 0x000a0000
EAX=00000004 EBX=00000000 ECX=00000000 EDX=00000001 ESI=00000000 EDI=00000000 EBP=ffef7fe8 ESP=ffef7fb8 EIP=0009ff66 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] CS =0008 00000000 ffffffff 00cf9b00 DPL=0 CS32 [-RA] SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] DS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] FS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] GS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy GDT= fff8df54 00000017 IDT= 00000000 00000000 CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000 DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000 DR6=ffff0ff0 DR7=00000400 CCS=00000004 CCD=000000c4 CCO=ADDB EFER=0000000000000000 FCW=037f FSW=0000 [ST=0] FTW=ff MXCSR=00001f80 FPR0=0000000000000000 0000 FPR1=0000000000000000 0000 FPR2=0000000000000000 0000 FPR3=0000000000000000 0000 FPR4=0000000000000000 0000 FPR5=0000000000000000 0000 FPR6=0000000000000000 0000 FPR7=0000000000000000 0000 XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000 XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000 XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000 XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000 Abgebrochen +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ nothing more ... There is no "Coreboot Starting bla, bla" message
Amd or Intel boards break later.
Is it a problem with Qemu and Via C7 CPUs or is their something wrong in the via tree.
Is anybody working on a cn700 board for now. There are hints for Rev. 3566 code for the southbridge? Is this important. Does the current code not working?
Thanks Chris
For problems at this level with qemu I would usually use Bochs with debug enabled so I could watch every instruction. You might want to try that.
ron
Christian wrote:
I currently working on a Igel Thin Client 3210. The board is very closer to bcom/winnetp680. CN700 northbridge VT8237R southbridge W83679HF SuperIO A try with this tree did not work.
What CPU do you have? Is CN700 usable exclusively with C7? What generation C7 do you have? Does VIA have updated setup code for your model CPU?
I have compiled nearly all via boards to test the ROMs with qemu. And get always this message: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ qemu: fatal: Trying to execute code outside RAM or ROM at 0x000a0000
EAX=00000004 EBX=00000000 ECX=00000000 EDX=00000001 ESI=00000000 EDI=00000000 EBP=ffef7fe8 ESP=ffef7fb8 EIP=0009ff66
So code at 9ff66 is trying to jump to a0000. This is all sorts of wrong. Start by looking at what is going on at 9ff66. Obviously make sure that your toolchain is working. I believe VIA startup has some assembly. Verify that your disassembled binaries have 1:1 of the source. All basic bringup.
Is anybody working on a cn700 board for now.
No, I don't think anyone is.
There are hints for Rev. 3566 code for the southbridge? Is this important.
A more precise reference to the code you have in mind would allow more efficient collaboration.
Thanks.
//Peter
What CPU do you have? Is CN700 usable exclusively with C7? What
Yes it is a Via C7
vendor_id : CentaurHauls cpu family : 6 model : 13 model name : VIA Eden Processor 600MHz stepping : 0
generation C7 do you have? Does VIA have updated setup code for your model CPU?
I don`t know
qemu: fatal: Trying to execute code outside RAM or ROM at 0x000a0000
EAX=00000004 EBX=00000000 ECX=00000000 EDX=00000001 ESI=00000000 EDI=00000000 EBP=ffef7fe8 ESP=ffef7fb8 EIP=0009ff66
So code at 9ff66 is trying to jump to a0000. This is all sorts of wrong. Start by looking at what is going on at 9ff66. Obviously make sure that your toolchain is working. I believe VIA startup has some assembly. Verify that your disassembled binaries have 1:1 of the source. All basic bringup.
I will check this.
There are hints for Rev. 3566 code for the southbridge? Is this important.
A more precise reference to the code you have in mind would allow more efficient collaboration.
In the Wiki Status for BCOM/Winnetp680 and Status for Jetway/J7F2
Thanks.
//Peter
EAX=00000004 EBX=00000000 ECX=00000000 EDX=00000001 ESI=00000000 EDI=00000000 EBP=ffef7fe8 ESP=ffef7fb8 EIP=0009ff66
So code at 9ff66 is trying to jump to a0000. This is all sorts of wrong. Start by looking at what is going on at 9ff66. Obviously make sure that your toolchain is working. I believe VIA startup has some assembly. Verify that your disassembled binaries have 1:1 of the source. All basic bringup.
I will check this.
It could be something wrong in
src/cpu/via/car/cache_as_ram.inc
Here are my bases and sizes, always default
CONFIG_DCACHE_RAM_BASE=0xffef0000 CONFIG_DCACHE_RAM_SIZE=0x8000 CONFIG_XIP_ROM_SIZE=0x100000 CONFIG_XIP_ROM_BASE=0xfff00000 CONFIG_RAMTOP=0x200000 CONFIG_RAMBASE=0x100000
In this file are many calculations, but my assembler lessons are ten years ago :)
thanks chris
On Wed, 2012-03-07 at 21:54 +0100, Christian wrote:
Here are my bases and sizes, always default
CONFIG_DCACHE_RAM_BASE=0xffef0000 CONFIG_DCACHE_RAM_SIZE=0x8000 CONFIG_XIP_ROM_SIZE=0x100000 CONFIG_XIP_ROM_BASE=0xfff00000 CONFIG_RAMTOP=0x200000 CONFIG_RAMBASE=0x100000
XIP_ROM_SIZE should be 64k and _BASE is obsolete.
I think AMD Agesa leaks it's Kconfig, try with the attached patch.
KM
Am Mittwoch, den 07.03.2012, 23:19 +0200 schrieb Kyösti Mälkki:
On Wed, 2012-03-07 at 21:54 +0100, Christian wrote:
Here are my bases and sizes, always default
CONFIG_DCACHE_RAM_BASE=0xffef0000 CONFIG_DCACHE_RAM_SIZE=0x8000 CONFIG_XIP_ROM_SIZE=0x100000 CONFIG_XIP_ROM_BASE=0xfff00000 CONFIG_RAMTOP=0x200000 CONFIG_RAMBASE=0x100000
XIP_ROM_SIZE should be 64k and _BASE is obsolete.
I think AMD Agesa leaks it's Kconfig, try with the attached patch.
Thanks for the patch. Now I get
$:~/coreboot> make clean $:~/coreboot> make menuconfig src/mainboard/amd/inagua/Kconfig:48:error: found recursive dependency: AMD_AGESA -> AMD_AGESA -> CPU_AMD_SOCKET_C32 -> CPU_AMD_MODEL_10XXX -> SET_FIDVIDmake: *** [menuconfig] Fehler 1 $:~/coreboot>
I will try to fix it.
chris
On Thu, 2012-03-08 at 20:25 +0100, Christian wrote:
Am Mittwoch, den 07.03.2012, 23:19 +0200 schrieb Kyösti Mälkki:
I think AMD Agesa leaks it's Kconfig, try with the attached patch.
Thanks for the patch. Now I get
$:~/coreboot> make clean $:~/coreboot> make menuconfig src/mainboard/amd/inagua/Kconfig:48:error: found recursive dependency: AMD_AGESA -> AMD_AGESA -> CPU_AMD_SOCKET_C32 -> CPU_AMD_MODEL_10XXX -> SET_FIDVIDmake: *** [menuconfig] Fehler 1 $:~/coreboot>
I will try to fix it.
Sorry, I forgot to mention this explicitly:
http://review.coreboot.org/#/c/773/
KM
I will try to fix it.
Sorry, I forgot to mention this explicitly:
OK, now CONFIG_XIP_ROM_SIZE=0x10000
qemu and bochs don`t work with the romfile Tomorrow I will try it on real hardware.
thanks chris
KM
-
Christian -
christian.suehs＠online.de
-
Kyösti Mälkki -
Peter Stuge -
ron minnich