C-Block Coding Basics -- Recent Additions

QSPICE
1

I’ve created new documents that may be of interest to C-Block component developers:

  • C-Block Basics #4 — Revisits the Trunc() function, the QSpice simulation cycle, and more. Implements a simple comparator component example.

  • C-Block Basics #5 — Revisits the MaxExtStepSize() function, a QSpice “peculiarity,” and more. Implements a basic component with an internally generated clock.

I hope that you’ll find them useful. As always, please let me know if you find issues or have suggestions for improving the explanations or examples.

–robert

My GitHub QSpice repository is here.
The new documents are in the CBlock_Doc folder.

7 Likes
2

I’ve posted a couple of new documents in this unplanned C-Block component series:

  • C-Block Basics #6 – Connecting schematic bus wires to C-Block components with a focus on implementing “bit vectors” in non-Verilog code.

  • C-Block Basics #7 – Recent QSpice changes (new Display() function & Trunc() simplification). While mostly backwards compatible, there are “edge cases.”

You can find them in the CBlock_Doc folder of the main branch of my GitHub QSpice repository.

As always, I hope that you’ll find them useful. Please let me know if you find issues or have suggestions for improvements.

–robert

4 Likes
3

I’ve added a new document in the unplanned C-Block component series: C-Block Basics #8 – “Post-Processing Techniques.”

This one demonstrates techniques to:

  • Launch an external standalone program (*.exe) or batch command file (*.bat or *.cmd) from within a C-Block component.
  • Process multiple component instances and multi-step simulations.
  • Create a binary log file and convert it to a *.csv in post-processing.
  • Build file names and command line strings from user-supplied component attributes.
  • Code a standalone program (*.exe) and compile with the QSpice DMC compiler.

It’s available on the dev branch of my QSpice GitHub repository.

Hopefully, you’ll find the information useful. Please let me know if you find issues or have suggestions for improvements.

–robert

1 Like