Is it possible to chain more than 2 triggers? If it is not possible, then what should happen if the user attempts to set the chain bit of two or more consecutive triggers?
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+unsubscribe@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/54b172ef-2b6d-4956-a540-831f34f377ee%40groups.riscv.org.
What defines chaining as ANDing (e.g. trigA & trigB such as data triggering) vs. sequential (e.g. trigA followed by trigB)?
--- Bruce
From: Tim Newsome <t...@sifive.com>
Sent: Tuesday, July 3, 2018 2:24 PM
To: Joe Rahmeh <joe.r...@gmail.com>
Cc: RISC-V Debug Group <de...@groups.riscv.org>
Subject: Re: [debug] Chaining more than 2 triggers
An implementation may support chaining more than 2 triggers, but it doesn't have to. (This is true for almost any trigger feature.) It's expected that if the debugger writes a trigger that's not supported, it reads back something that is supported (WARL). I'll clarify that in the spec. A simple way to limit chain length is an implementation is wire the chain bit to 0 for every odd (or every 4th, etc) trigger to 0.
Tim
On Tue, Jul 3, 2018 at 2:07 PM, Joe Rahmeh <joe.r...@gmail.com> wrote:
Is it possible to chain more than 2 triggers? If it is not possible, then what should happen if the user attempts to set the chain bit of two or more consecutive triggers?
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+un...@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/54b172ef-2b6d-4956-a540-831f34f377ee%40groups.riscv.org.
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+un...@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/CAGDihekCf-%2BXTyKED7UDdFh5owa1-UkGkvCLCQDbPTnnaCEgUg%40mail.gmail.com.
I think it’s the “while” in mcontrol.chain:
1: While this trigger does not match, it prevents
the trigger with the next index from matching.
If that’s not clear, I’m open to suggestions.
Tim
What defines chaining as ANDing (e.g. trigA & trigB such as data triggering) vs. sequential (e.g. trigA followed by trigB)?
--- Bruce
From: Tim Newsome <t...@sifive.com>
Sent: Tuesday, July 3, 2018 2:24 PM
To: Joe Rahmeh <joe.r...@gmail.com>
Cc: RISC-V Debug Group <de...@groups.riscv.org>
Subject: Re: [debug] Chaining more than 2 triggers
An implementation may support chaining more than 2 triggers, but it doesn't have to. (This is true for almost any trigger feature.) It's expected that if the debugger writes a trigger that's not supported, it reads back something that is supported (WARL). I'll clarify that in the spec. A simple way to limit chain length is an implementation is wire the chain bit to 0 for every odd (or every 4th, etc) trigger to 0.
Tim
On Tue, Jul 3, 2018 at 2:07 PM, Joe Rahmeh <joe.r...@gmail.com> wrote:
Is it possible to chain more than 2 triggers? If it is not possible, then what should happen if the user attempts to set the chain bit of two or more consecutive triggers?
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+unsubscribe@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/54b172ef-2b6d-4956-a540-831f34f377ee%40groups.riscv.org.
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+unsubscribe@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
I think it’s the “while” in mcontrol.chain:
1: While this trigger does not match, it prevents
the trigger with the next index from matching.If that’s not clear, I’m open to suggestions.
Tim
On Tue, Jul 3, 2018 at 2:36 PM, bruce.ableidinger <bruce.ab...@gmail.com> wrote:
What defines chaining as ANDing (e.g. trigA & trigB such as data triggering) vs. sequential (e.g. trigA followed by trigB)?
--- Bruce
From: Tim Newsome <t...@sifive.com>
Sent: Tuesday, July 3, 2018 2:24 PM
To: Joe Rahmeh <joe.r...@gmail.com>
Cc: RISC-V Debug Group <de...@groups.riscv.org>
Subject: Re: [debug] Chaining more than 2 triggers
An implementation may support chaining more than 2 triggers, but it doesn't have to. (This is true for almost any trigger feature.) It's expected that if the debugger writes a trigger that's not supported, it reads back something that is supported (WARL). I'll clarify that in the spec. A simple way to limit chain length is an implementation is wire the chain bit to 0 for every odd (or every 4th, etc) trigger to 0.
Tim
On Tue, Jul 3, 2018 at 2:07 PM, Joe Rahmeh <joe.r...@gmail.com> wrote:
Is it possible to chain more than 2 triggers? If it is not possible, then what should happen if the user attempts to set the chain bit of two or more consecutive triggers?
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+un...@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/54b172ef-2b6d-4956-a540-831f34f377ee%40groups.riscv.org.
--
You received this message because you are subscribed to the Google Groups "RISC-V Debug Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+un...@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+unsubscribe@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/cddb8ae1-9b17-4f45-ad8a-bd3084d37ee5%40groups.riscv.org.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/cddb8ae1-9b17-4f45-ad8a-bd3084d37ee5%40groups.riscv.org.
To unsubscribe from this group and stop receiving emails from it, send an email to debug+unsubscribe@groups.riscv.org.
To post to this group, send email to de...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/debug/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/3137cbc3-579d-4768-872b-9ba02239c1a8%40groups.riscv.org.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/debug/3137cbc3-579d-4768-872b-9ba02239c1a8%40groups.riscv.org.