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

Integration with TerosHDL #2

Open
qarlosalberto opened this issue Jul 12, 2021 · 1 comment
Open

Integration with TerosHDL #2

qarlosalberto opened this issue Jul 12, 2021 · 1 comment

Comments

@qarlosalberto
Copy link

It would be possible to create a command to open a file. So we could call it from TerosHDL similar to:

vscode.commands.executeCommand('impulse.open_wave', '/path/to/waveform.vcd');

Now we support only GTKwave, but if you add the command we could support Impulse.

sample

@thomasAtToem
Copy link
Member

Hi Carlos,

good point!

I had a look and I assume it should be working with the

vscode.openWith - Opens the provided resource with a specific editor.

resource - Resource to open
viewId - Custom editor view id or 'default' to use VS Code's default editor
columnOrOptions - (optional) Either the column in which to open or editor options, see vscode.TextDocumentShowOptions
(returns) - no result

The viewId =
de.toem.impulse.editor.records

It might be interesting to connect a 'life' simulation output.

impulse has mechanisms (not in vscode yet) to connect to streams, pipes, databases, ....

Which simulators do you support - and output formats ?

https://toem.de/index.php/products/impulse-hdl currently supports FST, FSDB and WLF.

In previous discussions (some time ago), we had the request to navigate from a signal in the waveform viewer (position ?) to an rtl editor position (that is responsible for the signal).
We could define an interface for this purpose (with signal name and position as parameters) if you are interested - not sure how this works out on your side.

Maybe there are other interesting interactions !?! - (Breakpoints, Tasks)

thanks,

thomas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants