Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
/ fli_jtag Public archive

Connect to your ModelSim/QuestaSim simulation via JTAG! GDB <-TCP-> OpenOCD <-remote bitbang-> fli_jtag <-FLI-> VSIM

Notifications You must be signed in to change notification settings

NikLeberg/fli_jtag

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Warning

This repository has been superseeded by my own NikLeberg/cosim_jtag which combines this FLI approach with VHPIDIRECT. The code here is perfectly fine and still works with ModelSim/QuestaSim. It won't get any updates or new features though.

fli_jtag

Connect to your ModelSim / QuestaSim simulation via JTAG!

Got tired of looking at those pesky waveforms while ultimately debugging your VHDL softcore in simulation? Ever wished you could just use the glory that is the gnu debugger GDB without actually having to use any real hardware? Well here is your answer. With the magic that is FLI, we can interface from the GHDL simulation to other software.

FLI or MTI FLI stands for Model Technology Incorporated - Foreign Language Interface.

The communication channel from gdb to your softcore roughly looks like this:

+-----+     +---------+     +------------+     +--------------+     +---------------------+
| GDB | <-> | OpenOCD | <-> | fli_jtag.c | <-> | fli_jtag.vhd | <-> | JTAG TAP / softcore |
+-----+  :  +---------+  :  +------------+  :  +--------------+  :  +---------------------+
        TCP         UNIX socket            FLI                  JTAG

[        outside VSIM <<] [>> inside VSIM                                                 ]

This repository contains a simple VHDL entity fli_jtag with a corresponding C-API that exposes a named UNIX socket. The VHDL entity can be used wherever you want to drive the typical tdo, tck, tms and tdi JTAG signals. During simulation a named UNIX socket is created to which OpenOCD can connect via the lovely remote bitbanging protocol. GDB can then connect to OpenOCD as usual and off you go!

Getting started

The following assumes prior knowledge about the general use of vsim, openocd and gdb. For a more complete example see test subfolder. Especially examine the run.sh script that brings it all together.

First, instantiate the fli_jtag entity in your design (probably an testbench) and drive your JTAG TAP with its signals.

  -- example:
  fli_jtag_inst : entity work.fli_jtag
    port map (
      clk => clk,
      tdo => con_jtag_tdo,
      tck => con_jtag_tck,
      tms => con_jtag_tms,
      tdi => con_jtag_tdi,
      trst => open,
      srst => open
    );

Next, analyze and elaborate the VHDL design files as usual.

vcom fli_jtag.vhd

Compile the C interface into a shared library.

gcc -shared -fPIC -o fli_jtag.so -I$MODEL_TECH/../include fli_jtag.c

Everything is now compiled and ready to simulate. Assuming you have a toplevel entity named top, run it and additionally load the shared library with the additional foreign switch.

vsim -c top -foreign "fli_jtag_init fli_jtag.so" -do "run -all"

While the simulation is running, a named UNIX socked is created in /tmp/fli_jtag.sock. Connect to that socket with OpenOCD by selecting the remote_bitbang adapter in your config files.

adapter driver remote_bitbang
remote_bitbang_port 0
remote_bitbang_host /tmp/fli_jtag.sock

<other config lines for jtag tap(s) and target(s)>
openocd -f openocd.cfg

Compared to running on a real target a simulated JTAG connection can be quite slow. So OpenOCD might complain about timeouts. You can increase the timeout for commands with the following in the config:

riscv set_reset_timeout_sec 120
riscv set_command_timeout_sec 120

If everything has been successful so far, OpenOCD should print out something like this:

[...]
Info : Initializing remote_bitbang driver
Info : Connecting to unix socket /tmp/fli_jtag.sock
Info : remote_bitbang driver initialized
[...]
Info : JTAG tap: riscv.cpu tap/device found: 0x00000003 (mfg: 0x001 (AMD), part: 0x0000, ver: 0x0)
[...]
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40901103
Info : starting gdb server for riscv.cpu on 3333

All that's left to do is start up gdb and debug away:

gdb-multiarch -ex 'target extended-remote localhost:3333'

Links

Further Documentation

Similar Projects:

License

MIT © N. Leuenberger.

About

Connect to your ModelSim/QuestaSim simulation via JTAG! GDB <-TCP-> OpenOCD <-remote bitbang-> fli_jtag <-FLI-> VSIM

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published