From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unable to debug UBOOT
Date: Fri, 08 May 2009 01:59:23 -0500 [thread overview]
Message-ID: <4A03D84B.3070401@gmail.com> (raw)
In-Reply-To: <7c7ce0c60905072312i74ad8bb8vbc8693e829fc4978@mail.gmail.com>
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
next prev parent reply other threads:[~2009-05-08 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 6:12 [U-Boot] Unable to debug UBOOT Vivek DALAL
2009-05-08 6:15 ` Aggrwal Poonam-B10812
2009-05-08 15:01 ` alfred steele
2009-05-09 5:21 ` Vivek DALAL
2009-05-08 6:59 ` Nishanth Menon [this message]
2009-05-08 8:44 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A03D84B.3070401@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.