[U-Boot] Unable to debug UBOOT
Hello guys
I am newbie in bootloader. I am trying to port latest uboot on omap2430(poseidon board). Currently support for omap2430 is not present in uboot; so I made changes accordingly.
I am putting it in RAM using Trace 32 debugger. But unable to get prompt. Code hangs but giving message *"DRAM: 64MB" ...* Please suggest me different ways of debugging uboot. I tried using Trace 32(LAUTERBACH JTAG debugger). Loaded uboot elf file(u-boot) into RAM. I am getting symbols and function names. But unable to put breakpoints. Also C code is not visible even after changing mode.
Please suggest me ways to debug uboot.
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Vivek DALAL Sent: Friday, May 08, 2009 11:43 AM To: U-Boot@lists.denx.de Subject: [U-Boot] Unable to debug UBOOT
Hello guys
I am newbie in bootloader. I am trying to port latest uboot on omap2430(poseidon board). Currently support for omap2430 is not present in uboot; so I made changes accordingly.
I am putting it in RAM using Trace 32 debugger. But unable to get prompt. Code hangs but giving message *"DRAM: 64MB" ...* Please
Looks like you are reinitializing the DDR , when u are already executing from it, you may want to comment out that code, which initializes DDR.
suggest me different ways of debugging uboot. I tried using Trace 32(LAUTERBACH JTAG debugger). Loaded uboot elf file(u-boot) into RAM. I am getting symbols and function names. But unable to put breakpoints. Also C code is not visible even after changing mode.
Please suggest me ways to debug uboot.
-- Cheers
Vivek Dalal === He who angers you conquers you ===
Looks like you are reinitializing the DDR , when u are already executing from it, you may want to comment out that code, which initializes DDR.
To add to that, if you have cloned code for an already existing platform config file, See if the "CONFIG_SKIP_RELOCATE_UBOOT" and "CONFIG_SKIP_LOWLEVEL_INIT" flags in your config file(include/configs) are enabled. If these flags are not enabled, you might need to enable them,s o that the early initialization code is skipped.
Thanks.
Thanks for your help guys. I will looking into all the pointers you guys had given...
thanks alot
Vivek Dalal On Fri, May 8, 2009 at 8:31 PM, alfred steele alfred.jaquez@gmail.comwrote:
Looks like you are reinitializing the DDR , when u are already executing from it, you may want to comment out that code, which initializes DDR.
To add to that, if you have cloned code for an already existing platform config file, See if the "CONFIG_SKIP_RELOCATE_UBOOT" and "CONFIG_SKIP_LOWLEVEL_INIT" flags in your config file(include/configs) are enabled. If these flags are not enabled, you might need to enable them,s o that the early initialization code is skipped.
Thanks.
Vivek DALAL said the following on 05/08/2009 01:12 AM:
I am newbie in bootloader. I am trying to port latest uboot on omap2430(poseidon board). Currently support for omap2430 is not present in uboot; so I made changes accordingly.
would be nice to see your patches when you are ready :).. it might even pave way to get sdp2430 support in place..
I am putting it in RAM using Trace 32 debugger. But unable to get prompt. Code hangs but giving message *"DRAM: 64MB" ...* Please suggest me different ways of debugging uboot. I tried using Trace 32(LAUTERBACH JTAG debugger). Loaded uboot elf file(u-boot) into RAM. I am getting symbols and function names. But unable to put breakpoints. Also C code is not visible even after changing mode.
Please suggest me ways to debug uboot
I would recommend you start with reading Lauterbach user manual(hitting F1 key when trace32 runs will help). IMHO, Lauterbach will be the best tool to go ahead and use esp for OMAP2-3 processors. When you read the user manual, pay close attention to 'd.load.elf ... /strippart /lowerpath' option also s.path..
Regards, Nishanth Menon
Dear Vivek DALAL,
In message 7c7ce0c60905072312i74ad8bb8vbc8693e829fc4978@mail.gmail.com you wrote:
I am putting it in RAM using Trace 32 debugger. But unable to get prompt. Code hangs but giving message *"DRAM: 64MB" ...*
You are running into exactly the type of problems tha cause us to add the FAQ entry:
http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStarted...
The summary of this is: unless you know *exactly* what you are doing (which seems not to be the case for you), you better don't attempt doing this.
Best regards,
Wolfgang Denk
participants (5)
-
Aggrwal Poonam-B10812 -
alfred steele -
Nishanth Menon -
Vivek DALAL -
Wolfgang Denk