01:41
Degi_ has joined #amaranth-lang
01:41
Degi has quit [Ping timeout: 265 seconds]
01:41
Degi_ is now known as Degi
02:34
RufousNightjar has joined #amaranth-lang
02:35
RufousNightjar has quit [Client Quit]
03:14
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark 906d33f - Log latency of CXXRTL server commands.
03:14
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark 324949c - Reimplement Reference Items / Query Interval using the new approach.
04:07
FFY00_ has joined #amaranth-lang
04:07
FFY00 has quit [Read error: Connection reset by peer]
07:50
Wanda[cis] has joined #amaranth-lang
07:50
<
Wanda[cis] >
ohh py3.13 is out
08:45
d_olex has quit [Ping timeout: 248 seconds]
13:25
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark ede2a3d - Implement observer-based debug item value display.
13:38
jorolf[m] has joined #amaranth-lang
13:38
<
jorolf[m] >
Looking at lib.fifo.FIFOInterface, wouldn't it make sense to change the read and write ports to use lib.stream?
13:39
whitequark[cis] has joined #amaranth-lang
13:39
<
whitequark[cis] >
there's an undocumented stream adapter already
13:39
<
whitequark[cis] >
ideally the FIFOs would be fully stream based, but that's more tricky than it looks
13:39
<
jorolf[m] >
whitequark[cis]: Where would that be?
13:41
<
jorolf[m] >
FIFOInterface.w_stream? 🤔
15:05
d_olex has joined #amaranth-lang
16:54
key2 has joined #amaranth-lang
17:38
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark f23addd - Factor out debug session management.
17:38
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark a9492ad - Implement watch list management.
17:45
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark de28e8a - Implement watch list management.
18:43
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark 8ddd697 - Implement configurable radix.
18:46
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark 7d7fe67 - Implement configurable radix.
18:48
<
_whitenotifier >
[amaranth-lang/rtl-debugger] whitequark 4ea4944 - Use small caps to approximate look&feel of VS Code native tree view headers.
18:59
phire_ has joined #amaranth-lang
18:59
phire has quit [Ping timeout: 260 seconds]
21:34
John_K has joined #amaranth-lang
21:36
<
John_K >
hey folks, I'm trying to implement my first amaranth project and have been having a bit of trouble determining the newest / best way to connect everything together. I'm currently requesting resources from a platform object in my enumerate function, but this seems to be impossible to do in Simulation since the simulator class hard codes platform to
21:37
<
John_K >
I'm implementing a 4-bit bidirectional bus with a unidirectional clk and control line
21:40
<
John_K >
would welcome any advice on how to deal with the bidirectional signals better as well
21:48
zyp[m] has joined #amaranth-lang
21:48
<
zyp[m] >
first of all I'd make the data signals one 4-bit signal rather than four independent single bit signals each
22:53
John_K has quit [Quit: Client closed]
23:02
John_K has joined #amaranth-lang
23:02
<
John_K >
well, it can operate in 1 or 4 bit mode
23:03
<
John_K >
rather, it starts in 1-bit, then switches to 4-bit. But that should still be possible as one 4-bit signal
23:08
duskwuff[m] has joined #amaranth-lang
23:08
<
duskwuff[m] >
I'd highly recommend looking at the Glasgow QSPI controller - there's a lot of thematic similarities
23:09
<
duskwuff[m] >
ignore the non-gateware bits (QSPIControllerInterface and QSPIControllerApplet)
23:54
<
John_K >
I had originally used that as inspiration, but then couldn't follow directly because of the Glasgow Ports that are used
23:54
<
John_K >
it has been a bit confusing to look at pads vs ports vs grabbing stuff from platform to figure out what pins to connect up to the logic
23:55
<
John_K >
I settled on platform as it seemed the cleanest, but then I can't simulate