Stormwind_mobile has quit [Ping timeout: 268 seconds]
sb0 has joined #m-labs
cedric has quit [Ping timeout: 268 seconds]
bluebugs has joined #m-labs
bluebugs has joined #m-labs
bluebugs has quit [Changing host]
pie_ has joined #m-labs
Dar1us has quit [Ping timeout: 246 seconds]
Dar1us has joined #m-labs
pie_ has quit [Ping timeout: 258 seconds]
<mtrbot-ml>
[mattermost] <rikstarmans> @sb10q that might solve part of my issues; I request the main clock pin so I can pass it as an input to an instance. The platform builder also request this pin when building the module. A pin can't be requested twice and as a result the build fails.
<mtrbot-ml>
[mattermost] <rikstarmans> The only solution i see so far is driving an other signal with the main clock using self.sync and then passing this signal to the Instance.
rohitksingh has joined #m-labs
bluebugs has quit [Ping timeout: 260 seconds]
cedric has joined #m-labs
cedric has quit [Changing host]
cedric has joined #m-labs
<mtrbot-ml>
[mattermost] <sb10q> well if you want to put the FSM in another clock domain, that's what you should use
<mtrbot-ml>
[mattermost] <sb10q> if the FSM and its parent module are all using the same domain only, you can also simply put ClockDomainsRenamer on that parent module
Getorix has joined #m-labs
Getorix_ has quit [Ping timeout: 260 seconds]
pie_ has joined #m-labs
pie_ has quit [Ping timeout: 248 seconds]
pie_ has joined #m-labs
Stormwind_mobile has joined #m-labs
en0k has joined #m-labs
cedric has quit [Ping timeout: 240 seconds]
cedric has joined #m-labs
cedric has quit [Changing host]
cedric has joined #m-labs
<mtrbot-ml>
[mattermost] <rikstarmans> @sb10q thanks... it does solve the issue of my FSM in another clock domain.
<mtrbot-ml>
[mattermost] <rikstarmans> the problem I have here is don't know how to declare. A 8 bit wide 255 bit deep register in migen. The examples in migen all consider 1 dimensional signal and not reg [ 7:0] mema [255:0];
<mtrbot-ml>
[mattermost] <sb10q> use Memory - there's an example
<mtrbot-ml>
[mattermost] <rikstarmans> i have used memory... but icestorm doesn't infer block rams from it
<mtrbot-ml>
[mattermost] <sb10q> are you using a supported BRAM configuration?
<mtrbot-ml>
[mattermost] <rikstarmans> no
<mtrbot-ml>
[mattermost] <sb10q> things like async read don't work on many FPGAs (I don't know about ice40)
<mtrbot-ml>
[mattermost] <sb10q> and that's a hardware limitation
<mtrbot-ml>
[mattermost] <rikstarmans> okay.. so that's why it is not inferring it?
<mtrbot-ml>
[mattermost] <sb10q> what do you want it to infer if there's no corresponding hardware?
<mtrbot-ml>
[mattermost] <rikstarmans> Memory is still not inferred, my guess is that i need to capture it in a module block
<mtrbot-ml>
[mattermost] <rikstarmans> I guess this is not possible in migen as it does not support hierarchical RTL designs like nmigen
Stormwind_mobile has joined #m-labs
<whitequark>
rikstarmans: please use a pastebin service, your pastes are very disruptive on IRC
<whitequark>
regarding your question, you should read yosys logfile, because it explains exactly why it infers or does not infer a BRAM
<whitequark>
there is no need to guess
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
rohitksingh has joined #m-labs
mwk_ has joined #m-labs
mwk_ is now known as mwk
rohitksingh has quit [Ping timeout: 260 seconds]
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
<Astro-_>
@sb10q that issue happens very often to me. I work around it by starting openocd with "ftdi_layout_init 0x20e0 0x3feb" and "ftdi_layout_signal nSRST -data 0x2000" which don't work but cause something like a power-cycling.
<Astro-_>
I admin that's not even a hack but sheer luck, hence not committed anywhere.
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
<_whitenotifier-5>
[nmigen] Fatsie commented on issue #285: Making Instance with clock compatible with EnableInserter - https://git.io/JeN0h
<_whitenotifier-5>
[nmigen] whitequark commented on issue #285: Making Instance with clock compatible with EnableInserter - https://git.io/JeNES
<_whitenotifier-5>
[nmigen] whitequark commented on issue #285: Add EnableSignal, useful for making Instances compatible with EnableInserter - https://git.io/JeNE7
Stormwind_mobile has quit [Ping timeout: 258 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 248 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 248 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
X-Scale has quit [Ping timeout: 260 seconds]
X-Scale has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 258 seconds]
pie_ has quit [Remote host closed the connection]
pie_ has joined #m-labs
_whitelogger has joined #m-labs
en0k has quit [Ping timeout: 265 seconds]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Read error: Connection reset by peer]
Stormwind_mobile has joined #m-labs
Stormwind_mobile has quit [Ping timeout: 248 seconds]
cr1901_modern has quit [Quit: Leaving.]
cr1901_modern1 has joined #m-labs
cr1901_modern1 has quit [Client Quit]
cr1901_modern1 has joined #m-labs
cr1901_modern1 has quit [Client Quit]
cr1901_modern1 has joined #m-labs
pie_ has quit [Quit: No Ping reply in 180 seconds.]