|Non-Confidential||PDF version||ARM DUI0446W|
|Home > Writing OS Awareness for DS-5 Debugger > Creating an OS awareness extension|
The debugger searches for OS awareness extensions in its configuration database. All files pertaining to a particular extension must be located in a folder or at the root of a Java Archive (JAR) file in the configuration database
<some folder> /mydb /OS
<some folder> /mydb /OS /myos /extension.xml /messages.properties
messages_<language code>_<country code>.properties,
<?xml version="1.0" encoding="UTF-8"?> <os id="myos" version="5.15" xmlns="http://www.arm.com/os_extension"> <name>myos.title</name> <description>myos.desc</description> <provider><!-- todo --></provider> </os>
oselement refers to the API version, which is aligned with the version of DS-5 that the API was made public with. You must set the version attribute to the DS-5 version that the OS awareness extension was developed in, or the lowest version that it was tested with. The debugger does not display any extensions that require a higher version number. However, as the API is backwards compatible, the debugger displays extensions with earlier API versions. The earliest API version was 5.15.
myos.title=My OS myos.desc=This is My OS. myos.help=Displays information about My OS.
myos.helpstring is only visible from the debugger's command line interface, for instance, when typing help myos once connected.