A good way to retrieve information of what is happening in our SystemC simulations is to generate a log file with the information that we need (module name, simulation time, what phase is going on, etc.).
The most elegant and easy way to do that is to create a special class for that task, that the other modules in the simulation can use to send their information and to be stores in disk. This can be achieved designing a singleton type class. This design pattern restricts the instantiation of a class to one single object. In our case, it will cause that all modules use the same object and log file.
Continue reading A class to Log them all
Today I tell you how to create a project in eclipse for work with TLM-2 and SystemC, it’s very easy!
Continue reading How to configure Eclipse to use TLM-2.0
TLM-2 lists modeling 3 different modes (called Coding Styles in official documents): untimed, Loosely-timed and Approximately-timed. Each serves a specific purpose, and to model different types of systems. We must also take into account the cost of each simulation mode (untimed less expensive, Approximatelly-timed more expensive).
I start this blog with the intention to talk, discuss, inform, learn about the SystemC-TLM-2.0 world.