From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] Introduce low-level debug for ARM architecture
Date: Mon, 18 Aug 2014 19:14:07 -0700 [thread overview]
Message-ID: <53F2B2EF.9010707@freescale.com> (raw)
In-Reply-To: <1408256217-3706-1-git-send-email-yamada.m@jp.panasonic.com>
On 08/16/2014 11:16 PM, Masahiro Yamada wrote:
> I have been in trouble for a while to debug some nasty problem
> where neighter a debugger nor printf() function is available.
>
> I found the lowlevel debug feature in ARM Linux can be used as is
> in U-Boot too.
>
> I tested this series on our SoCs (32bit ARM, specificly Coretex-A9).
> Because I was not sure about aarch64, I have this feature
> depend on "! ARM64".
>
> 1/4 and 2/4 refactor a bit and move CONFIG_ARM64 to Kconfig.
>
> 3/4 imports some source files from Linux 3.16 and
> 4/4 adds the Kconfig menu.
Dear Masahiro,
How do you use this debug facility? Do you print to memory?
I don't know enough to comment on the patch. I don't see CP15 co-process in the
SoC I am debugging.
York
next prev parent reply other threads:[~2014-08-19 2:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 6:16 [U-Boot] [PATCH 0/4] Introduce low-level debug for ARM architecture Masahiro Yamada
2014-08-17 6:16 ` [U-Boot] [PATCH 1/4] vexpress64: kconfig: consolidate CONFIG_TARGET_VEXPRESS_AEMV8A_SEMI Masahiro Yamada
2014-08-25 18:01 ` Steve Rae
2014-08-17 6:16 ` [U-Boot] [PATCH 2/4] kconfig: armv8: move CONFIG_ARM64 to Kconfig Masahiro Yamada
2014-08-17 6:16 ` [U-Boot] [PATCH 3/4] arm: debug: import debug files from Linux 3.16 Masahiro Yamada
2014-08-19 11:01 ` Stefan Roese
2014-08-20 13:53 ` Masahiro YAMADA
2014-08-25 9:03 ` Przemyslaw Marczak
2014-08-26 3:26 ` Masahiro Yamada
2014-08-27 14:27 ` Przemyslaw Marczak
2014-08-17 6:16 ` [U-Boot] [PATCH 4/4] arm: debug: add Kconfig entries for lowlevel debug Masahiro Yamada
2014-08-19 2:14 ` York Sun [this message]
2014-08-19 7:45 ` [U-Boot] [PATCH 0/4] Introduce low-level debug for ARM architecture Masahiro Yamada
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=53F2B2EF.9010707@freescale.com \
--to=yorksun@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox