In message [off-list ref] you wrote:
i have some problems with debugging my kernel. This is the first time i use bdi for kernel debugging. ELDK 3.0 is my toolchain (Target 8270).
...
Are there some options in the kernel or in the gdb to set ?
Did you enable CONFIG_DEBUG_KERNEL in your kernel configuration?
Did you read the FAQ section of the DULG, especially
http://www.denx.de/twiki/bin/view/DULG/HowToDebugLinuxExceptions
and
http://www.denx.de/twiki/bin/view/DULG/HowToSingleStepThroughRFIInstruction
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Death, when unnecessary, is a tragic thing.
-- Flint, "Requiem for Methuselah", stardate 5843.7
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Hello,
quoted
Are there some options in the kernel or in the gdb to set ?
Did you enable CONFIG_DEBUG_KERNEL in your kernel configuration?
Yes it is enabled, furthermore the "Include BDI-2000 user context switcher" is set and compiler options "Additional compile arguments: "-g -ggdb -fno-schedule-insns -fno-schedule-insns2" are set
Did you read the FAQ section of the DULG, especially
http://www.denx.de/twiki/bin/view/DULG/HowToDebugLinuxExceptions
and
http://www.denx.de/twiki/bin/view/DULG/HowToSingleStepThroughRFIInstruction
In my case i try to step through m8260_setup_arch() function to debug m8260_find_bridges() for pci support. Is there the MMU already on ?
I think it is.
When the bdi runs through the code the most time it comes to the __delay() function. Then i try "step" or "next" and it often hangs forever.
Best regards,
Wolfgang Denk
Thank you for your reply.
Best regards,
Marco
---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone: +49 (0)9929/301332
Fax: +49 (0)9929/301112
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/