<Melkhior>
so I'm guessing it doesn't break that much :-)
<Melkhior>
TIA
<Melkhior>
(my design had a SBus -> Wishbone bridge, and occasionally my bridge returns a 'rerun' because it didn't receive a Wishbone ACK in time ; limit is 50 SBus cycles, or about 200 Wishbone cycles...)
<Melkhior>
(in about 0.5-2% of read accesses)
FabM has quit [Ping timeout: 268 seconds]
cr1901 has quit [Quit: Leaving.]
cr1901 has joined #litex
peeps[zen] has joined #litex
peepsalot has quit [Ping timeout: 264 seconds]
jersey99 has joined #litex
peepsalot has joined #litex
peeps[zen] has quit [Ping timeout: 268 seconds]
indy has quit [Remote host closed the connection]
indy has joined #litex
mithro has quit [Ping timeout: 244 seconds]
mithro has joined #litex
zyp has quit [Ping timeout: 244 seconds]
zyp has joined #litex
alanvgreen_ has joined #litex
guan_ has joined #litex
alanvgreen has quit [*.net *.split]
guan has quit [*.net *.split]
alanvgreen_ is now known as alanvgreen
guan_ is now known as guan
<jersey99>
Thanks sajattack[m]
<jersey99>
I agree that it is super slow.
<jersey99>
Another noob question: When using a litedram core, the default firmware/cpu code that gets loaded into the bios to run the dram calibration doesn't execute (essentially the bios doesn't boot) until I explicitly open the terminal. Is this intentional? If so, how to have it run automatically with a timer, say?
<cr1901>
The BIOS code waiting for you to open a terminal sounds specifically like a USB serial thing. If you are using a plain old UART, Idk what could be wrong
<tpw_rules>
i think the jtag uart has a buffer full flag the BIOS can spin on