coreboot October 2004

coreboot@coreboot.org

45 participants
197 discussions

JTAG debugging
by Stephen.Kimball＠bench.com 22 Oct '04

22 Oct '04

I agree with Ron. JTAG debuggers are more robust. But I am interested in stepping through LinuxBIOS on a working target to quickly understand the code, so I'm able to attempt a port to a new target. I view it as a learning tool and a productivity tool. If you could show people how to use a product like the American Arium, you might get more help. Steve -----Original Message----- From: Ronald G. Minnich [mailto:rminnich@lanl.gov] Sent: Friday, October 22, 2004 3:06 PM To: Eric W. Biederman Cc: Kimball, Stephen; linuxbios(a)clustermatic.org Subject: Re: Makefile changes for symbols On Fri, 22 Oct 2004, Eric W. Biederman wrote: > Alternatively it might be work adding gdb stubs into LinuxBIOS. And doing > using a remote debugger that way. What a jtag interface provides > is really not much more than what gdb stubs provides. At least > not after memory is initialized. that's not quite correct. There are a host of cpu failures you can detect with a jtag interface that gdb stubs are useless for. GDB stubs requires that the processor be basically sane, jtag interfaces are not near as picky. ron

4 3

Makefile changes for symbols
by Stephen.Kimball＠bench.com 22 Oct '04

22 Oct '04

Can someone give me the Makefile changes to make a LinuxBIOS with symbols? I tried adding "-gdwarf-2" to CFLAGS, but I'm not sure where the unstripped output would be. Are there any features in the code that are useful in debugging LinuxBIOS? Any defines that should change as well? Someone must have some experience with source code level debugging of LinuxBIOS with an American Arium ECM-50. Thanks. Steve Kimball Benchmark Electronics Hudson, NH

3 3

RE: FYI: Merge in progress...S2735
by YhLu 22 Oct '04

22 Oct '04

Eric, I change sth for s2735. I don't know how to modify src/northbridge/intel/e7501/norbridge.c Can you have a look at that? Regards YH s2735 half update CVS: ---------------------------------------------------------------------- CVS: Enter Log. Lines beginning with `CVS:' are removed automatically CVS: CVS: Committing in . CVS: CVS: Modified Files: CVS: src/cpu/intel/model_f2x/Config.lb CVS: src/cpu/intel/model_f2x/model_f2x_init.c CVS: src/cpu/intel/socket_mPGA604_533Mhz/chip.h CVS: src/cpu/intel/socket_mPGA604_533Mhz/socket_mPGA604_533Mhz.c CVS: src/mainboard/tyan/s2735/Config.lb CVS: src/mainboard/tyan/s2735/auto.c CVS: src/mainboard/tyan/s2735/chip.h CVS: src/mainboard/tyan/s2735/failover.c CVS: src/mainboard/tyan/s2735/mainboard.c CVS: src/mainboard/tyan/s2735/mptable.c CVS: src/mainboard/tyan/s4880/Options.lb CVS: src/mainboard/tyan/s4882/Options.lb CVS: targets/tyan/s2735/Config.lb targets/tyan/s2735/ns2735 CVS: ---------------------------------------------------------------------- -----Original Message----- From: YhLu Sent: Friday, October 22, 2004 10:45 AM To: ebiederman(a)lnxi.com; Ronald G. Minnich Cc: Li-Ta Lo; 'LinuxBIOS' Subject: RE: FYI: Merge in progress...S2735 Eric, About S2735, in auto.c How to change #include "cpu/p6/apic_timer.c" Amd version is #include "cpu/amd/model_fxx/apic_timer.c" I can not find other apic_timer.c in src/cpu Regards YH _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

1 0

RE: Makefile changes for symbols
by Stephen.Kimball＠bench.com 22 Oct '04

22 Oct '04

Ron, Is LinuxBIOS development done with only serial port debug messages? You guys are good. Steve -----Original Message----- From: Ronald G. Minnich [mailto:rminnich@lanl.gov] Sent: Tuesday, October 19, 2004 5:25 PM To: Kimball, Stephen Cc: linuxbios(a)clustermatic.org Subject: Re: Makefile changes for symbols On Tue, 19 Oct 2004 Stephen.Kimball(a)bench.com wrote: > > Someone must have some experience with source code level debugging of > LinuxBIOS with an American Arium ECM-50. Thanks. wow! I want to hear about that when you get it going. Another FAQ entry. ron

3 3

RE: Makefile changes for symbols
by Stephen.Kimball＠bench.com 22 Oct '04

22 Oct '04

Rod, I'm using Source Point 7.0.0. I can see the source files. I can display source, disassembly or mixed. However, the disassembly doesn't match up with the source code. There is a way to give Source Point an offset when the symbols are loaded, but I can't seem to get the right value. I know the address of _start and __protected_start but these labels are not in linuxbios_c.o. I need to find the location of a symbol in linuxbios_c.o to compute the offset. Steve -----Original Message----- From: Kittleson, Rodney C. Sent: Thursday, October 21, 2004 5:42 PM To: Kimball, Stephen; linuxbios(a)clustermatic.org Cc: Jeff_Pitts(a)arium.com Subject: RE: Makefile changes for symbols Steve, What version of Source point are you using? The symbols are coming in but SourcePoint doesn't allow me to reference the source files. I mapped the linuxbios directory on my Win2000 system for SourcePoint to access. (I have samba running on my linux system) I just need to get SourcePoint working. Thanks, Rod -----Original Message----- From: Kimball, Stephen Sent: Wednesday, October 20, 2004 1:04 PM To: Kittleson, Rodney C.; linuxbios(a)clustermatic.org Cc: Jeff_Pitts(a)arium.com Subject: RE: Makefile changes for symbols The file under your target in normal/linuxbios_c.o seems to have all the symbols if you add "-gdwarf-2" to the $CFLAGS in the Makefile. Then when you open the first C module the SourcePoint software asks where the file exists, after you tell SourcePoint it seems to find the rest by itself. I recreated the same Linux directory structure on Windows. Thanks Rod! Steve -----Original Message----- From: Kittleson, Rodney C. Sent: Wednesday, October 20, 2004 11:47 AM To: Kimball, Stephen; linuxbios(a)clustermatic.org Subject: RE: Makefile changes for symbols Linuxbios_c, from the build directory, can be sucked into Sourcepoint to extract the symbols. This allows the disassembled instructions to display the symbols inline. It makes it easier to set breakpoints and follow the code, but it's a far cry from source level debugging. I haven't attempted to link the source with sourcepoint yet. I may try it later this week, let me know if you have any success. Rod -----Original Message----- From: Kimball, Stephen Sent: Tuesday, October 19, 2004 3:33 PM To: linuxbios(a)clustermatic.org Subject: Makefile changes for symbols Can someone give me the Makefile changes to make a LinuxBIOS with symbols? I tried adding "-gdwarf-2" to CFLAGS, but I'm not sure where the unstripped output would be. Are there any features in the code that are useful in debugging LinuxBIOS? Any defines that should change as well? Someone must have some experience with source code level debugging of LinuxBIOS with an American Arium ECM-50. Thanks. Steve Kimball Benchmark Electronics Hudson, NH _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios _______________________________________________ Linuxbios mailing list Linuxbios(a)clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios

4 4

RE: FYI: Merge in progress...
by YhLu 22 Oct '04

22 Oct '04

Amd_early_mtrr.c #ifndef AMD_EARLYMTRR_C #define AMD_EARLYMTRR_C #include <cpu/x86/mtrr.h> #include <cpu/amd/mtrr.h> #include "cpu/x86/mtrr/earlymtrr.c" static void amd_early_mtrr_init(void) { static const unsigned long mtrr_msrs[] = { /* fixed mtrr */ 0x250, 0x258, 0x259, 0x268, 0x269, 0x26A, 0x26B, 0x26C, 0x26D, 0x26E, 0x26F, /* var mtrr */ 0x200, 0x201, 0x202, 0x203, 0x204, 0x205, 0x206, 0x207, 0x208, 0x209, 0x20A, 0x20B, 0x20C, 0x20D, 0x20E, 0x20F, /* var iorr msr */ 0xC0010016, 0xC0010017, 0xC0010018, 0xC0010019, /* mem top */ 0xC001001A, 0xC001001D, /* NULL end of table */ 0 }; msr_t msr; const unsigned long *msr_addr; /* Enable the access to AMD RdDram and WrDram extension bits */ msr = rdmsr(SYSCFG_MSR); msr.lo |= SYSCFG_MSR_MtrrFixDramModEn; wrmsr(SYSCFG_MSR, msr); /* Inialize all of the relevant msrs to 0 */ msr.lo = 0; msr.hi = 0; for (msr_addr = mtrr_msrs; *msr_addr; msr_addr++) { wrmsr(*msr_addr, msr); } /* Disable the access to AMD RdDram and WrDram extension bits */ msr = rdmsr(SYSCFG_MSR); msr.lo &= ~SYSCFG_MSR_MtrrFixDramModEn; wrmsr(SYSCFG_MSR, msr); /* Enable memory access for 0 - 1MB using top_mem */ msr.hi = 0; msr.lo = ((CONFIG_LB_MEM_TOPK << 10) + TOP_MEM_MASK) & ~TOP_MEM_MASK; wrmsr(TOP_MEM, msr); /* Enable caching for 0 - 1MB using variable mtrr */ set_var_mtrr(0, 0, (CONFIG_LB_MEM_TOPK << 10), MTRR_TYPE_WRBACK); #if defined(XIP_ROM_SIZE) /* enable write through caching so we can do execute in place * on the flash rom. */ set_var_mtrr(1, XIP_ROM_BASE, XIP_ROM_SIZE, MTRR_TYPE_WRBACK); #endif /* Set the default memory type and enable fixed and variable MTRRs */ /* Enable Variable MTRRs */ msr.hi = 0x00000000; msr.lo = 0x00000800; wrmsr(MTRRdefType_MSR, msr); /* Enale the MTRRs in SYSCFG */ msr = rdmsr(SYSCFG_MSR); msr.lo |= SYSCFG_MSR_MtrrVarDramEn; wrmsr(SYSCFG_MSR, msr); /* Enable the cache */ enable_cache(); } #endif /* AMD_EARLYMTRR_C */

4 9

RE: Freebios2 recovery progress...
by YhLu 22 Oct '04

22 Oct '04

Design problem, should use ioapic in 8131. -----Original Message----- From: Liu Tao [mailto:liutao@safe-mail.net] Sent: Thursday, October 21, 2004 9:25 PM To: YhLu Cc: ebiederman(a)lnxi.com; LinuxBIOS Subject: Re: Freebios2 recovery progress... Why devices on amd8131 don't use ioapic in amd8131? >You can not test that in arima board. Because all device on 8131 is using >ioapic in amd8111. > >YH >

1 0

Is Linuxbios alive as of now?
by Alexander Amelkin 22 Oct '04

22 Oct '04

Hi all! With all that "Merge in progress" and "Recovery progress" stuff, is the current CVS snapshot suitable for use with EPIA MII ? Or should I wait some time before trying it? How soon is it planned to finish all that "merger"? -- With best regards, Alexander mailto:spirit@reactor.ru

4 5

Re: about i845gv ddr sdram init
by Don Elwell 22 Oct '04

22 Oct '04

I burned a ton of time on this a while ago but got nowhere. It would seem that Intel provides only partial documentation for their chipsets on their web site. I discovered that there are hidden/undocumented registers used in the DDR SDRAM setup (there are probably others). I also tried in vain to get a contact there but again came up empty handed. In the end, we ended up going with a different chipset manufacturer. Ron, where did you get information for your 855 port in v2? Is it broken for the "hidden registers" reason? -don

2 1

RE: changes today.
by YhLu 22 Oct '04

22 Oct '04

4, 6, 7 done Tuesday. 5 is not nesscery, eric have use compare resource with 0x100+res+links in dev 0x18,0. Regards YH -----Original Message----- From: Stefan Reinauer [mailto:stepan@openbios.org] Sent: Friday, October 22, 2004 7:39 AM To: YhLu Cc: Ronald G. Minnich; ebiederman(a)lnxi.com; Li-Ta Lo; linuxbios(a)clustermatic.org Subject: Re: changes today. * YhLu <YhLu(a)tyan.com> [040930 21:00]: > Ron/Eric/Stephan/Ollie, > > Please check the patch. > > 1. some tyan volatile messing because of ROMCC changes. > 2. S2882 interrupt line assignment in mptable.c > 3. exclude range for flash_rom. > 4. better ht_setup_chainx() in incoherent_ht.c ---> change share bus 0 to > different bus for different incoherent HT link. > 5. fix one bug about io and mem allocation for multi ht links. --- in > northbridge.c > Mark it if used before assign final value. > 6. enable amd/quartet to init multi incoherent HT link in auto.c --- not > test, no MB on hand. > 7. enable S2885 to init multi incoherent HT link in auto.c Have all these been commited now? Stefan

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot October 2004