<_florent_>
chmouss: I also tested with the CPU (ie without --cpu-type=None) and it's also working
pftbest has joined #litex
pftbest has quit [Ping timeout: 260 seconds]
pftbest has joined #litex
<chmouss>
_florent_: Thanks, I see exactly the same behaviour with your bitstream so it must be an issue on my side (WSL maybe?). Will try with another computer.
chmouss has quit [Ping timeout: 246 seconds]
<Melkhior>
_florent_ You were right - seems HW was OK, but i wasn't enabling the interrupts in the driver :facepalm:
<Melkhior>
I have event in /dev/input/event0 now when I hit a key
<Melkhior>
at least when arkbd serio enables the keyboard which isn't reliable (yet)
<_florent_>
Melkhior: ok nice
<_florent_>
sajattack[m]: Sorry, I'll look at the Acorn CLE215 / SPIFlash today
lkcl has quit [Ping timeout: 252 seconds]
lkcl has joined #litex
chipdsgnr has quit [Quit: Connection closed]
thorns514 has joined #litex
cr1901_modern1 has joined #litex
cr1901_modern has quit [Ping timeout: 258 seconds]
thorns514 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
pftbest has quit [Remote host closed the connection]
pftbest has joined #litex
Bertl_zZ is now known as Bertl
thorns514 has joined #litex
thorns514 has quit [Client Quit]
pftbest has quit [Remote host closed the connection]
<nickoe>
_florent_: Hmm, ok, cool, so it was something about the CR vs LF things as you mentioned
<_florent_>
yes, a workaround that has been introduced at some point or for a specific use case and that was not longer required
<nickoe>
I am trying to catch up with my SDRAM to AXI strema
<nickoe>
I got the tracing working with the analyzer, but I think I should be able to trace for way longer just using the --trace option to litex_sim, right?
rj has joined #litex
<_florent_>
yes indeed
<_florent_>
it's also possible to enable/disable the tracing from your logic dynamically
<_florent_>
to only capture the parts that are relevant and avoid too large traces
<nickoe>
I don't seem to get a vcd, I am doing "litex_sim --ram-init demo.bin --trace --trace-start 1 --trace-end 2000"
<nickoe>
So that is withourt the analyzer
<nickoe>
What am I missing?
<nickoe>
mmm, there is a file in the build dir! but it is empt?
<nickoe>
mithro: Are you replyig to me or asking anyone in the channel?
<mithro>
Anyone.
<_florent_>
nickoe: it seems we may have broke trace-start/end with recent changes in the simulation, I would have to look at that. You can eventually just use --trace and a Finish in your Simulation.
<_florent_>
If you don't really need to go to hardware and can do it in simulation, I recommend continue in simulation
rj has joined #litex
<_florent_>
The analyzer is useful for debugging things that are difficult to simulate, or to understand the behaviour on the hardware before eventually try to reproduce it in simulation and fix the issue
<nickoe>
Yeah, I mean, for the part I want to wrap my head around on how to get work... I want to run it in simulation to debug and verify it easier. But IIRC, I may also have had some trouble loading a boot.json or --ram-init together with the --rom-init?
<nickoe>
yay, I can see the "rolling" leds for the LED chanser 2s sim :D
cr1901_modern has joined #litex
<Finde>
_florent_ is correct about ComputeDRAM
<mithro>
Is the ComputeDRAM in a public repo anywhere?
rj has quit [Ping timeout: 240 seconds]
rj has joined #litex
Bertl is now known as Bertl_oO
rj has quit [Ping timeout: 240 seconds]
rj has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 252 seconds]
rj has quit [Ping timeout: 240 seconds]
rj has joined #litex
<nickoe>
_florent_: Can I filter the vcd at trace time, such that I don't get some modules dumped?
<nickoe>
I mean together with the --trace?
<_florent_>
it's possible to configure the trace depth with Verilator, but not sure this is exposed in LiteX
<_florent_>
Not sure for tracing only selected modules with Verilator, but at least I know this is not supported in LiteX...
<nickoe>
OK, thanks.
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 265 seconds]
rj has quit [Ping timeout: 240 seconds]
d_olex has joined #litex
rj has joined #litex
kgugala has quit [Ping timeout: 260 seconds]
kgugala has joined #litex
lkcl has quit [Ping timeout: 240 seconds]
<nickoe>
_florent_: If I make my own "litex" project specific repo, am I required to add the "Copyright 2012-2020 / LiteX-Hub community" as I am essentially just making it "alike" but not really forking it as it is a new board?
<nickoe>
My project being MIT licensed
rj has quit [Ping timeout: 240 seconds]
lkcl has joined #litex
rj has joined #litex
Melkhior has quit [Quit: Connection closed]
<sajattack[m]>
<_florent_ "sajattack: Sorry, I'll look at t"> yay
<Finde>
mithro: no not yet, the original version was based on softmc which is kind of a strange project
<Finde>
don't know all the details of the current dev status with litedram
Melkhior has joined #litex
rj has quit [Ping timeout: 240 seconds]
rj has joined #litex
<_florent_>
nickoe: for the copyright, this is your project :) so you are free to use your copyright. Happy to have feedback about your project or what you do with the tools.
<nickoe>
which is based directly from the litex_sim becuase I had trouble tracing stuff initially
Melkhior has quit [Quit: Connection closed]
rj has quit [Ping timeout: 240 seconds]
rj has joined #litex
rj has quit [Ping timeout: 240 seconds]
rj has joined #litex
<nickoe>
Hmm, how long does it take for the simulator to laod a 4k file form tftp boot from a boot.json?
rj has quit [Remote host closed the connection]
rj has joined #litex
<nickoe>
mm, ok, if I remove my first thing it boots the demo.bin just fine... it was test_data.cs16": { "0x41000000", demo.bin": "0x40000000" }, but just {"demo.bin": "0x40000000"} seem to work quick!
<nickoe>
mmm, it just .mmm, does not seem to like that second file
<nickoe>
or location
<nickoe>
Are there certain requirements for the file? maybe size boundaries?
<nickoe>
hmm, no, my file is exactly 4kiB
pftbest has quit [Remote host closed the connection]