Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christian Gagneraud <chgans@gmail.com>
To: Peter Schauer <peterschauer@gmx.net>
Cc: gdb@sourceware.org
Subject: Re: HW watchpoint on Linux/ARM
Date: Sun, 16 Jul 2017 09:42:00 -0000	[thread overview]
Message-ID: <CABxGUTi7Sxt=U1mhgaRXfyo0XqSUAtSrashi9SQ8UDL28_Y23Q@mail.gmail.com> (raw)
In-Reply-To: <201707160852.v6G8qFsw000816@licht.localdomain>

On 16 July 2017 at 20:52, Peter Schauer <peterschauer@gmx.net> wrote:
>> But on i.mx6, it does. From memory, the kernel told me that I have
>> access to 5 HW breakpoints and 1 HW watchpoint (I don't have the board
>> at hand, but will post details on Monday).
>
> I had the same problem with an i.mx6 board three years ago.
> I don't remember all the details, but it had to do with the
> ARM secure debug mode, which is active when the SPIDEN pin is pulled low
> in hardware.
>
> I had a kernel hack back then, which enabled the hardware break mechanism
> even if the SPIDEN pin is pulled low, but it disables the secure debug mode,
> and worked only for my arm architecture (I couldn't test others), so
> I didn't post it to the kernel group.
>
> If your problem is caused by SPIDEN low, and you are interested in
> the kernel hack, please let me know.
> I could also send you a detailed analysis of the problem in german,
> in case you are interested.

Hi Peter,

Yes please, I'm interested by your hacky patch, and i'll take the
german analysis too! ;)

Thanks,
Chris

>
> --
> Peter Schauer                   Peter.Schauer@mytum.de


      parent reply	other threads:[~2017-07-16  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16  1:19 Christian Gagneraud
     [not found] ` <201707160852.v6G8qFsw000816@licht.localdomain>
2017-07-16  9:42   ` Christian Gagneraud [this message]

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='CABxGUTi7Sxt=U1mhgaRXfyo0XqSUAtSrashi9SQ8UDL28_Y23Q@mail.gmail.com' \
    --to=chgans@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=peterschauer@gmx.net \
    /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