4 Migrating from Simics 6

4.1 Introduction

This chapter describes issues related to migrating to Simics 7 from Simics 6. For information about what is new in Simics 7, read the product release notes.

4.2 Launching Simics

When launching Simics 5 or 6 on Linux, the shell script file $HOME/.simics-5.sh was sourced if it existed. In Simics 7 this is no longer done.

4.3 DML migration

When migrating to Simics API 7 from Simics API 6, there are a few differences that may need to be addressed for DML code or modules. It is important to note that the migration to the Simics 7 API can be performed gradually. A single module in a large system can be migrated individually and each feature to be migrated can be migrated individually.

A comprehensive description of migration concerns and a process for migration is documented in Appendix C of the Device Modeling Language 1.4 Reference Manual . The section below provides a brief list and brief description of some items to be addressed in the migration.

• The transaction interface was introduced in API 6, and will eventually replace the io_memory interface. In API 7, bank objects will by default implement the transaction interface.
• Log statements in shared methods now log on the nearest enclosing configuration object like non-shared methods. A common example of this is that logs from certain register/field templates which appeared on the device objects in API 6 will instead appear on the bank objects in API 7.
• The common error of mixing up log level and log group in log statements gives a warning in Simics API 7.

For migrating DML 1.2 code, please refer to Appendix B of the Device Modeling Language 1.4 Reference Manual .