From: Samuel Falvo II <sam.falvo@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] Signal names for trap pipeline??
Date: Fri, 17 Jul 2020 17:58:55 -0700
Message-ID: <CAEz=son5eze0Hy5T_FnGO3gxMBdaAS9vG0TRvjU7-B54dgLprg@mail.gmail.com> (raw)
I'm running into an irreconcilable property violations with the formal
properties for the trap main stage.
I'm noticing that there's repeated references to SRR0 and SRR1
registers in https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/trap/main_stage.py;h=325fb373546673df3ec19a15554e775bcc6fe9a9;hb=HEAD;
however, after spending about 30 minutes hacking away at what might be
the cause, I realized after reviewing the graphs in GTKWave that I
don't see these signals in either the top or the DUT module signals.
Looking in https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/trap/pipe_data.py;h=d2de8552a62a55bada4a5e83726c273ef943ac83;hb=HEAD
seems to confirm my suspicion that neither srr0 nor srr1 actually
exist; they are (confusingly) called fast1 and fast2. Double-checking
GTKWave's signal lists confirms that fast1 and fast2 exist.
Can anyone please advise on how to proceed? I see several ways of
resolving this going forward, but I need input from others:
1. Rename fast1 and fast2 to srr0 and srr1, or,
2. Keep fast1/fast2 and rebind them to srr0/srr1 in the main_stage.py
and prove_main_stage.py files, or,
3. ...?
Thanks.
--
Samuel A. Falvo II
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next reply index
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 0:58 Samuel Falvo II [this message]
2020-07-18 2:09 ` Samuel Falvo II
2020-07-18 2:50 ` Luke Kenneth Casson Leighton
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='CAEz=son5eze0Hy5T_FnGO3gxMBdaAS9vG0TRvjU7-B54dgLprg@mail.gmail.com' \
--to=sam.falvo@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git