TRACE32 RISC-V Demo Directory Consolidation


The embedded tools company
Consolidation of the TRACE32 demo directory for RISC-V: ~~/demo/riscv
How to Adjust File References
TRACE32 Software Update



 

Consolidation of the TRACE32 demo directory for RISC-V: ~~/demo/riscv


For a simplified usage, the 32-bit and 64-bit directories of the individual TRACE32 RISC-V flash and OS awareness demos have been consolidated. The consolidation was enabled by enhancements in TRACE32's flash and OS awareness handling. It is thus now no longer necessary to distinguish between 32-bit or 64-bit RISC-V architectures when referencing flash or OS awareness files.

The changes made to the respective ~~/demo/riscv directories require existing users of the flash and OS awareness functionality to adjust their custom scripts to be compatible again. Check section "How to Adjust File References" for the details.

Existing RISC-V demo directories will either be outdated when updating via a TRACE32 interim version or no longer available in installations obtained via the TRACE32 Updater or Installer. To avoid issues, check the information about TRACE32 updates containing the new demo structure described in "TRACE32 Software Update".

Because of their new format, the new flash and OS awareness files are no longer compatible with TRACE32 software versions prior to N.2021.08.000138391. However, old flash and OS awareness files of previous TRACE32 versions will continue to work with new TRACE32 software.

Available Since

Interim/Nightly release: N.2021.08.000138391

The rollout of the consolidated TRACE32 demo directories for the RISC-V architecture started on 13th August 2021 with software version N.2021.08.000138391.

DVD release: 09/2021

The first DVD release that contains the consolidated TRACE32 demo directories for the RISC-V architecture is 09/2021.

Major Changes

  • ~~/demo/riscv/flash/<*>_rv32 and ~~/demo/riscv/flash/<*>_rv64 are consolidated into ~~/demo/riscv/flash/<*>
  • ~~/demo/riscv/kernel/<*>/rv32 and ~~/demo/riscv/kernel/<*>/rv64 are consolidated into ~~/demo/riscv/kernel/<*>
 

How to Adjust File References


This text uses the ~~/ notation where the two tildes are interpreted by PowerView as the TRACE32 system directory, also known as the installation directory. Lauterbach recommends the usage of ~~/ in custom scripts to be independent from a particular installation or host operating system.

However, users should be aware that the mentioned directories might also be referenced differently in their scripts, e.g. via absolute or relative paths.

~~/demo/riscv/kernel

The files for the OS awareness have been consolidated and now contain all relevant files for all RISC-V architecture variants which were previously supported for the respective OS.

In previous versions of TRACE32, the OS awareness files were split into different sub-directories, dependent on their architecture. Files for 32-bit chips were stored in ~~/demo/riscv/kernel/<*>/rv32 and files for 64-bit in ~~/demo/riscv/kernel/<*>/rv64. With this differentiation no longer necessary, users have to adjust the file paths in custom scripts to the new universal file path as follows: Exchange ~~/demo/riscv/kernel/<*>/rv32 or ~~/demo/riscv/kernel/<*>/rv64 with ~~/demo/riscv/kernel/<*>
where <*> is the chosen OS

~~/demo/riscv/flash

The binary files containing the flash algorithms have been consolidated and now contain binaries for all RISC-V architecture variants which were previously supported for the particular flash chip.

In previous versions of TRACE32, the flash files were split into different sub-directories, dependent on their architecture. Files for 32-bit chips were stored in ~~/demo/riscv/flash/<*>_rv32 and files for 64-bit in ~~/demo/riscv/flash/<*>_rv64. With this differentiation no longer necessary, users have to adjust the file paths in custom scripts to the new universal file path as follows: Exchange ~~/demo/riscv/flash/<*>_rv32 or ~~/demo/riscv/flash/<*>_rv64 with ~~/demo/riscv/flash/<*>
where <*> is the flash word size

 

TRACE32 Software Update


The required changes for the consolidation will lead to restructuring or renaming of certain directories or files. Because of that, the demo directories might end up in an inconsistent or conflicted state if a TRACE32 software update is not applied correctly. Two update methods need to be distinguished.

TRACE32 Updater

The preferred method for updating an existing TRACE32 installation to the demo directory changes is with an update via the TRACE32 Updater, version 09/2021 or later. The TRACE32 Updater will automatically backup the user installation (including local modifications) and afterwards replace the old demo directory with the new one to achieve a consistent installation.

Interim/Nightly Updates

If a user receives an interim update, it is advised to first use the TRACE32 Updater for the DVD release 09/2021 or later which will clean up the existing installation. If that is not possible, users should first backup and then delete or rename the affected directories to be able to achieve a consistent installation and avoid unintended merging of the old and new directories. Afterwards, the interim update can be applied by following the usual interim update instructions.





Copyright © 2021 Lauterbach GmbH, Altlaufstr.40, 85635 Höhenkirchen-Siegertsbrunn, Germany   Impressum     Privacy Policy
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 13-Aug-2021