Tuesday, 2020-11-17

*** tpb has joined #litex00:00
*** lf has quit IRC00:45
*** lf has joined #litex00:46
*** FFY00 has quit IRC01:56
*** FFY00 has joined #litex01:56
*** FFY00 has quit IRC01:58
*** FFY00 has joined #litex01:58
*** FFY00 has quit IRC02:00
*** FFY00 has joined #litex02:04
*** FFY00 has quit IRC02:07
*** FFY00 has joined #litex02:07
*** FFY00 has quit IRC02:09
*** Degi has quit IRC02:11
*** FFY00 has joined #litex02:12
*** Degi has joined #litex02:12
*** FFY00 has quit IRC02:12
*** FFY00 has joined #litex02:13
*** FFY00 has quit IRC02:15
*** FFY00 has joined #litex02:16
*** FFY00 has quit IRC02:25
*** FFY00 has joined #litex02:26
*** FFY00 has quit IRC02:38
*** FFY00 has joined #litex02:39
*** alanvgreen has quit IRC04:19
*** alanvgreen has joined #litex04:19
*** felix__ has joined #litex08:28
*** felix_ has quit IRC08:28
*** felix__ is now known as felix_08:31
*** kgugala_ has joined #litex08:37
*** kgugala has quit IRC08:38
*** kgugala_ has quit IRC08:46
*** kgugala has joined #litex08:46
*** Dolu has joined #litex09:07
*** lkcl has quit IRC09:21
*** lkcl has joined #litex09:27
*** TMM has quit IRC10:34
*** TMM has joined #litex10:34
leonsIs there a way to use litex_sim with a preloaded ram file, but to not autoboot (i.e. still get the shell in bios)?11:11
*** st-gourichon-fid has quit IRC11:18
*** st-gourichon-fid has joined #litex11:18
leonsIn general, how should I approach debugging with litex_sim best? I have a binary which works on an ArtyA7. The mem regions match up. Even a simple binary  loaded using `--mem-init` which just writes a byte to the UART txrx-register (3 basic instructions) doesn't seem to work :/11:49
_florent_leons: you can abort the boot sequence with Q or ESC11:50
_florent_leons: maybe you could look at: https://github.com/litex-hub/linux-on-litex-vexriscv/blob/master/sim.py, we are using the same binaries for the simulation and hardware11:52
_florent_leons: this one can also be interesting: https://github.com/enjoy-digital/litex_vexriscv_smp/blob/master/sim.py11:53
leonsflorent: Those are great references, thanks! I tried aborting the boot sequence with Q, but the window is too small. Also, with ethernet enabled, the simulation is just stuck somehow... I'll investigate11:56
_florent_leons: you can just press ESC or Q when you see the LiteX banner, it will also works11:58
leonsOkay, weirdly enough everything works just fine as long as a put my binary in the ROM, using `litex_sim.py` with `--ram-init` does not work and I'm still not sure why...13:06
leonsMaybe there are some issue with accessing the data in RAM? I've tried using SDRAM like linux-on-litex does, but I don't get past the memcheck, even when I set the bus,data,addr size to 0, as done in the sim.py of linux-on-litex13:08
_florent_leons: i could have a look, so you are just usign litex_sim with --ram-init and aborting the boot to check the ram content?13:13
leons_florent_: That'd be awesome, but you of course don't have to. I'm using `litex_sim.py` from master with `--ram-init` and want to check the RAM content, though I don't manage to abort the boot13:35
leonsI suppose I could undefine the `ROM_BOOT_ADDRESS`13:35
leonsIt appears like the binary is loaded correctly...13:38
leons_florent_: Thanks for your help! I'll definitely continue to look into my issue, but for now I'm incredibly happy that my binary works in ROM!13:52
_florent_leons: not sure to understand, so this is working with --rom-init but not --ram-init?13:53
leons_florent_: exactly. Of course I'm changing the base offsets in my ELF, but that shouldn't even matter as the first three instructions should already output a character on the UART13:59
_florent_leons: ok strange that if works on hardware14:00
leons_florent_: I agree. I'm using pretty much the same binary, so the RAM addresses are the same. Just stripping out some peripherals such as the LED, etc.14:01
_florent_leons: would you mind creating an issue in LiteX for this with the software or binary and steps to reproduce? I'm in a middle of something else so can't help that much now but i could have a closer look later14:02
leons_florent_:  sure!14:02
*** kgugala_ has joined #litex14:26
*** kgugala has quit IRC14:27
*** kgugala has joined #litex14:40
*** kgugala_ has quit IRC14:43
*** peeps[zen] has joined #litex16:32
*** peepsalot has quit IRC16:34
*** peepsalot has joined #litex16:52
*** peeps[zen] has quit IRC16:53
*** somlo has quit IRC17:52
*** somlo has joined #litex18:38
leons_florent_: Would you be open to adding a `--timer-uptime` command line parameter to soc_core.py? I've come to use it quite frequently and would happily create a PR20:35
_florent_leons: yes sure, this can indeed be useful, thanks.20:42
*** awordnot has quit IRC21:32
*** awordnot has joined #litex21:58
acathlaOn an iCE40up5k I already have 12MHz and 48MHz for USB (fomu style), I need a 24MHz clock. What's the best way to add it?22:07
acathlaI added a self.sync.usb_48 += self.cd_ir_24.clk.eq(~self.cd_ir_24.clk)22:08
acathlaBut since it's linked to the 48MHz it does not always pass the timing analysis22:09
acathlaOr... my design is just a bit too full22:15
*** awordnot has quit IRC22:53
*** awordnot has joined #litex22:54
*** cjearls has quit IRC23:00
*** peepsalot has quit IRC23:26
*** peepsalot has joined #litex23:44

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!