Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cxxsim: random garbage in memory traces #565

Closed
cestrauss opened this issue Dec 19, 2020 · 8 comments
Closed

cxxsim: random garbage in memory traces #565

cestrauss opened this issue Dec 19, 2020 · 8 comments
Labels
bug simulator:cxxsim upstream

Comments

@cestrauss
Copy link

Consider:

from nmigen import Module, Memory
from nmigen.sim import Simulator

m = Module()
mem = Memory(width=64, depth=8)
rdport = mem.read_port()
m.submodules.rdport = rdport


def process():
    yield


for engine in ["pysim", "cxxsim"]:
    sim = Simulator(m, engine=engine)
    sim.add_clock(1e-6)
    sim.add_sync_process(process)
    with sim.write_vcd(f"bug18.{engine}.vcd"):
        sim.run()

The CXXSim VCD file shows some strange behavior:

  1. rdport sub-module is absent
  2. The top module has some mem[<i>][63:0] signals that appear to contain random garbage.
@whitequark
Copy link
Member

1. rdport sub-module is absent

This is expected; rdport does not exist in synthesis. If there will be a change related to rdport, it will be to remove it from pysim vcd files as well.

2. The top module has some mem[<i>][63:0] signals that appear to contain random garbage.

Will look into this.

@whitequark
Copy link
Member

Confirmed random garbage; looks ASCII to me, so probably uninitialized memory of some sort?
Screenshot_20201220_090936

@whitequark
Copy link
Member

This is a problem with the way the simulation is reset. It is not entirely trivial to fix.

@whitequark
Copy link
Member

This is fixed by YosysHQ/yosys#2495.

@whitequark whitequark mentioned this issue Dec 20, 2020
Open
15 tasks
@cestrauss
Copy link
Author

Just to confirm that I've tried the above Yosys branch, and it does seem to fix the random garbage.
Also, I checked that the VCD traces of the memory array do reflect the values written through a write port.
For instance:

from nmigen import Module, Memory
from nmigen.sim import Simulator

m = Module()
mem = Memory(width=64, depth=8)
wrport = mem.write_port()
rdport = mem.read_port()
m.submodules.rdport = rdport
m.submodules.wrport = wrport


def process():
    yield wrport.en.eq(1)
    yield wrport.data.eq(0x5432123412345678)
    yield
    yield


sim = Simulator(m, engine="cxxsim")
sim.add_clock(1e-6)
sim.add_sync_process(process)
with sim.write_vcd("bug27.vcd"):
    sim.run()

In the VCD trace, mem[0][63:0] does reflect the written value, while the others do remain zeroed.

Not all is well, though. The branch seems to introduce a regression.
Code:

from nmigen import Module, Signal
from nmigen.sim import Simulator


m = Module()
s = Signal()
m.d.sync += s.eq(1)


def process():
    yield


sim = Simulator(m, engine="cxxsim")
sim.add_clock(1e-6)
sim.add_sync_process(process)
sim.run()

Result:

$ python bug26.py
/home/cstrauss/src/nmigen/nmigen/sim/cxxsim.py:198: YosysWarning: The `-Og` option has been removed. Use `-g3` instead for complete design coverage regardless of optimization level.
  cxx_source, name_map = cxxrtl.convert_fragment(fragment)
sim.cc: In constructor ‘cxxrtl_design::p_top::p_top(cxxrtl::adopt, cxxrtl_design::p_top)’:
sim.cc:55:2: error: expected identifier before ‘{’ token
  {
  ^
Traceback (most recent call last):
  File "/usr/lib/python3.7/distutils/unixccompiler.py", line 118, in _compile
    extra_postargs)
  File "/usr/lib/python3.7/distutils/ccompiler.py", line 909, in spawn
    spawn(cmd, dry_run=self.dry_run)
  File "/usr/lib/python3.7/distutils/spawn.py", line 36, in spawn
    _spawn_posix(cmd, search_path, dry_run=dry_run)
  File "/usr/lib/python3.7/distutils/spawn.py", line 159, in _spawn_posix
    % (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'x86_64-linux-gnu-gcc' failed with exit status 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "bug26.py", line 14, in <module>
    sim = Simulator(m, engine="cxxsim")
  File "/home/cstrauss/src/nmigen/nmigen/sim/core.py", line 70, in __init__
    self._engine   = engine(self._fragment)
  File "/home/cstrauss/src/nmigen/nmigen/sim/cxxsim.py", line 210, in __init__
    output_name="sim"
  File "/home/cstrauss/src/nmigen/nmigen/_toolchain/cxx.py", line 51, in build_cxx
    cc_driver.compile(cxx_filenames)
  File "/usr/lib/python3.7/distutils/ccompiler.py", line 574, in compile
    self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
  File "/usr/lib/python3.7/distutils/unixccompiler.py", line 120, in _compile
    raise CompileError(msg)
distutils.errors.CompileError: command 'x86_64-linux-gnu-gcc' failed with exit status 1

@whitequark
Copy link
Member

The branch seems to introduce a regression.

This regression is something that will be fixed by the changes I will apply before merging. Nevertheless, I wasn't aware of it, so thanks anyway!

@whitequark
Copy link
Member

This is fixed by YosysHQ/yosys#2495.

That PR has been superseded by YosysHQ/yosys#3105.

@whitequark
Copy link
Member

Fixed upstream, with no Amaranth-specific changes needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug simulator:cxxsim upstream
Milestone
No milestone
Development

No branches or pull requests
2 participants
@whitequark @cestrauss