gsomlo

Why do you think the `i686` version of `glibc-devel` is needed? Seems to work fine on my end with the native `x86_64` version. Something about the precompiled riscv toolchain maybe?...

On Fri, Nov 19, 2021 at 07:07:49AM -0800, enjoy-digital wrote: > Thanks @gsomlo, that's useful to know Linux-on-LiteX-Rocket's build is > Fedora-based. Also, I've been using Fedora for many years...

On Fri, Nov 26, 2021 at 06:10:22AM -0800, enjoy-digital wrote: > Thanks @gsomlo, sorry for the late answer. I just redid the installation on a > Fedora machine: ./litex_setup.py --gcc=riscv...

On Fri, Nov 26, 2021 at 07:15:10AM -0800, enjoy-digital wrote: > For Verilator, I was hitting https://www.reddit.com/r/FPGA/comments/op24te/ > when_gccc_with_stdgnu14_and_a_lot_of_warning/ and so there that the issue was > fixed with 4.110...

moved to https://github.com/enjoy-digital/litex/wiki/CSR-Bus -- please check there for the actual content of the documentation (gls -- 03/04/2020)

Thanks @avpatel for the quick reply! I think the TL;DR version of my post above is that, given the `generic` defaults of: https://github.com/riscv-software-src/opensbi/blob/master/platform/generic/objects.mk#L25 , https://github.com/riscv-software-src/opensbi/blob/master/platform/generic/objects.mk#L33 , and https://github.com/riscv-software-src/opensbi/blob/master/platform/generic/objects.mk#L35 , the...

On Thu, Jan 04, 2024 at 05:34:26PM -0800, AndrewD wrote: > What is your trigger condition for litescope_cli: the aw channel > matching the full address? Yes. > Maybe add...

Here's what I get when I trigger on a combination of values and control signals: ``` litescope_cli --csv ./analyzer.csv --csr-csv ./csr.csv \ -v main_basesoc_rocket_mem_axi_aw_payload_addr 0x80000000 \ -r main_basesoc_rocket_mem_axi_aw_valid \ -r...

hmm, I always assumed multiple triggers on the same command line are AND-ed together, but maybe they're OR-ed instead, which would explain why I'm getting garbage in the address field...

For completeness, I ran: ``` ./litescope_cli --csv ./analyzer.csv --csr-csv ./csr.csv -v main_basesoc_rocket_mem_axi_aw_payload_addr 0x80000000 ``` without any additional (OR-ed or AND-ed) triggers, and got this:  The address is *not* `0x80000000`...