From: Gabriel Tisan <gabriel.tisan@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: debugging on board
Date: Thu, 5 Apr 2012 08:43:12 +0200 [thread overview]
Message-ID: <CAD9ZU8ACc_p2bTq-QtwhHXWz6NP=J-VkKS=0O2vdHkO2oRQUDw@mail.gmail.com> (raw)
In-Reply-To: <20120405063322.GV3852@pengutronix.de>
Thanks !
I have an ARM from Freescale, i.MX35.
Regards,
Gabriel
On Thu, Apr 5, 2012 at 8:33 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Gabriel,
>
> On Thu, Apr 05, 2012 at 08:11:47AM +0200, Gabriel Tisan wrote:
>> Hi !
>>
>> What should I do to be able to see any debug messages ? On the serial console I
>> could see the Barebox version but after that nothing. I suppose that
>> is something
>> regarding nand.
>
> This means that your console is already running, a first step can then
> be to put a '#define DEBUG' above the includes in common/startup.c. This
> will cause the initcalls to be printed which will give you a first clue
> where execution stops.
>
> Also you should have the following options enabled:
>
> CONFIG_MMU
> ARM_EXCEPTIONS
> CONFIG_ARM_UNWIND
> CONFIG_KALLSYMS
>
> This gives you a stack dump when something bad happens.
>
>>
>> If I have no JTAG debugger what should I do to be able to debug ? For
>> other board I
>> could not see any messages on console.
>
> That's more difficult. If you have for example a U-Boot as first stage
> loader then you can add some register writes to the UART send register
> in the early startup code. Otherwise you are stuck with LED debugging
> (Just configure a gpio connected to a LED and see where you can still
> turn it on)
>
> What machine are you working on?
>
> Sascha
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-04-05 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 6:11 Gabriel Tisan
2012-04-05 6:33 ` Sascha Hauer
2012-04-05 6:43 ` Gabriel Tisan [this message]
2012-04-05 6:54 ` Sascha Hauer
2012-04-05 7:06 ` Gabriel Tisan
2012-04-05 9:27 ` Sascha Hauer
2012-04-05 12:28 ` Gabriel Tisan
2012-04-05 16:21 ` Sascha Hauer
2012-04-06 2:59 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-25 15:08 ` Gabriel Tisan
2012-04-30 15:25 ` Jean-Christophe PLAGNIOL-VILLARD
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='CAD9ZU8ACc_p2bTq-QtwhHXWz6NP=J-VkKS=0O2vdHkO2oRQUDw@mail.gmail.com' \
--to=gabriel.tisan@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox