[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANqRtoTA=Yg5f4pQxPaNQP9L=XG3pfJWk18jsz2M15HY0yaN3Q@mail.gmail.com>
Date: Mon, 6 Jul 2015 13:42:12 +0900
From: Magnus Damm <magnus.damm@...il.com>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Simon Horman <horms@...ge.net.au>,
Kevin Hilman <khilman@...nel.org>,
Tyler Baker <tyler.baker@...aro.org>,
Borislav Petkov <bp@...en8.de>,
Geert Uytterhoeven <geert+renesas@...der.be>,
SH-Linux <linux-sh@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock
from event handler"
Hi Wolfram,
Thanks for investigating this.
On Sat, Jul 4, 2015 at 12:09 AM, Wolfram Sang <wsa@...-dreams.de> wrote:
>
>> Ok. So it's unrelated to deep idle states. Any chance of poking with
>> JTAG at the frozen box? If not, are there GPIOs which you could use to
>> monitor certain state?
>
> No JTAGger here at the moment. And no manual/schematics for this board
> :(
Since EMEV2 includes a dual Cortex-A9 you can use OpenOCD with a
Flyswatter JTAG.
I've tried the following lines for the openocd configuration file, if
you need any help let me know!
# --- emev2 (CA9 Dual) on KZM9D ---
#target create emev2.cpu0 cortex_a -chain-position auto0.tap -dbgbase
0x80010000 -coreid 0
#target create emev2.cpu1 cortex_a -chain-position auto0.tap -dbgbase
0x80012000 -coreid 1
Cheers,
/ magnus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists