nic-loopback test fails in Chipyard 1.10.0

80 views
Skip to first unread message

Sabra Ossen

unread,
Apr 1, 2024, 12:39:01 AM4/1/24
to Chipyard
Hi All,

I've been using the nic-loopback test as a sanity check for a working baremetal NIC.

This test works as expected and provides the correct output in Chipyard 1.9.0 with the following output.

Trial 0
send/recv 7221 cycles
Trial 1
send/recv 5513 cycles
Trial 2
send/recv 5016 cycles
All correct

However, fails in Chipyard 1.10.0, and is stuck at

Trial 0

We're using FireSim 1.17.0 and AFAIU we need to use Chipyard 1.10.0 for compatibility.

Is there another recommended approach for testing the behavior of the NIC or can we use Chipyard 1.9.0 with FireSim 1.17.0?

Joonho Whangbo

unread,
Apr 1, 2024, 1:25:45 AM4/1/24
to Chipyard
Hi,

In the 1.10.0 release, the NIC loopback config in chipyard has a clock domain bug.
I believe it is fixed in 1.11.0

Best,
Joonho
--
You received this message because you are subscribed to the Google Groups "Chipyard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chipyard+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chipyard/d4be09ec-90a0-47be-a0f0-ed44c9eb26b4n%40googlegroups.com.
Message has been deleted

Sabra Ossen

unread,
Apr 5, 2024, 10:51:40 PM4/5/24
to chip...@googlegroups.com
Can the clock domain bug be patched in 1.10.0 or when I upgrade to 1.11.0 would I also have to upgrade FireSim to 1.18.0 (is it officially released? the docs are still on 1.17.1)?

I've been identifying compatible versions by checking the Chipyard commit in the FireSim repo. (https://github.com/firesim/firesim/tree/1.18.0/target-design)

Thanks,
Sabra


You received this message because you are subscribed to a topic in the Google Groups "Chipyard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chipyard/s7Wen1qffNY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chipyard+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chipyard/19b52cf6-8e94-430e-9b5e-8bd19acb6318%40Spark.


--

Jerry Zhao

unread,
Apr 5, 2024, 11:58:57 PM4/5/24
to chip...@googlegroups.com
You can patch it..

Personally, I recommend switching to the latest version of chipyard and firesim on the main branches of each.
We have not had time to push a release recently, but these should be stable, and it is easier for us to immediately push bug fixes into main, instead of backporting.

-Jerry

On Fri, Apr 5, 2024 at 7:51 PM Sabra Ossen <sabr...@gmail.com> wrote:
Can that clock domain bug be patched while I use 1.10.0 or if I upgrade it to 1.11.0 does that mean I have to also use FireSim 1.18.0 (is it an official release)?

I've been identifying compatible versions by checking the Chipyard commit associated with a FireSim tag (https://github.com/firesim/firesim/tree/1.18.0/target-design).
Reply all
Reply to author
Forward
0 new messages