パートナー Strategic Test パートナー Atollic
2.memory viewからメモリーを読み込むことができない
2.memory viewからメモリーを読み込むことができない
If it seems that only the ‘traditional’ rendering is OK and that you otherwise get “Target request failed: Unable red memory”, you need to change the table rendering preferences for the view to manually read the memory.The reason for this is because, by default, for performance reasons, the debugger tries to preload data from memory before and after the visible memory region for all renderings. This is not done in the traditional rendering.
This results in the debugger trying to read the memory before 0x20000000, which it can’t' and after this error it won't read anything else.
However, you can change this behavior by clicking the small downward arrow located in the top right corner of the memory view, next to the minimize and maximize view buttons.
Select Table rendering preferences and switch to manual memory loading mode instead of automatic.
1.address や 変数のdata valuesを素早く見つける方法
1.address や 変数のdata valuesを素早く見つける方法
Open the view called "Expressions" by navigating to:"MyVar" gives the value
8.TrueSTUDIO内でのタスクとは？
8.TrueSTUDIO内でのタスクとは？
Task Markers
Task markers are a very convenient way to add items to the TrueSTUDIO® task list. A task marker is generated when the string TODO is found in a comment in the source code. On deletion of the TODO comment, the task marker is also deleted.
You can customize the keywords which begin task markers in the preferences that you find by selecting Windows -> Preferences -> C/C++ -> Task Tags.
The coloring and format of the Task markers are set in Windows -> Preferences ->C/C++ -> Editor -> Syntax Coloring. There you select the comments element and there you find tag-tasks.
These two settings are stored in the workspace and can be exported together with other preferences to other workspaces from Files -> Export -> Preferences and imported by selecting Files -> Import -> Preferences.
The task markers can be viewed in the task-view that is opened with Widows -> Show View -> Tasks. This view has a configuration that can be set so that some tasks are filtered out or highlighted.
If you select one or more task markers in this view, you can copy them and past them into a spreadsheet, such as Excel.
Task markers are normally auto-detected by the indexer but can also be added manually to a position in the file or as unassociated task markers.
The manually added task markers can be flagged as finished. The automatic ones are deleted just by deleting the text.
The task markers are associated with files and thus not exported when the file is exported.
They can be used to create Tasks in the Bug Database Client in TrueSTUDIO®. Just right-click the task marker and select New task from Marker… and then select what repository to store it in. If you don’t have any repository, it can always be stored locally.
These tasks are not the same as task markers and they can be viewed in the Task-list-view (not the same view as the Tasks-view). If you store them locally and want to export these new tasks into other project, you can select to export them by right-clicking them in the Task-list-View.
7.プロジェクトをコンピューターまたはワークスペースを越えて動かすには？
7.プロジェクトをコンピューターまたはワークスペースを越えて動かすには？
Atollic TrueSTUDIO® provides a very handy way of moving a project, by first exporting the project to an archive file, that later can be imported into another TrueSTUDIO® installation or workspace.This information applies to projects which do not have linked resources. Linked resources are resources such as files and folders that are not located somewhere else on storage media, other than the project workspace currently being used. Linked resources are pointed to so that they will be found when required. For example, older projects distributed by ST Microelectronics® use this technique to point resource from their Standard Peripheral Library, which is not included within the workspace of their examples. Use the following procedure for Importing and Exporting projects that have been built by hand or have been generated by the TrueSTUDIO® Project Wizard.
See the note at the end of the article for how to deal with projects that contain linked resources.
Note on debug configurations! The debug configuration for a project is by default stored in the workspace metadata. To include the debug configuration when exporting a project, please perform the following steps:
• Select the project in the "Project Explorer" view.
• Select the "Project->Properties" menu.
• Select Run/Debug Settings.
• Select the configuration and click "Edit".
• Select "Save as->Shared file:" in the "Common" tab.
• Click "Ok".
A new file, "my_config_name.launch", is now added to the project.
To export a project to an archive file, please perform the following steps:
• Select the "File->Export" menu.
• Select "General->Archive File".
• Click "Next".
• Select the project(s) that should be exported (all files in the project will be included by default).
• Select destination and name for the archive.
• Click "Finish".
The exported project (in the form of an archive file) can now be imported into another TrueSTUDIO installation or workspace, by using the corresponding import function.
To import a project from an archive file, please perform the following steps:
• Select the "File->Import" menu.
• Select "General->Existing Projects into Workspace".
• Click "Next".
• Select "Select archive file:" and browse to the archive containing the project(s).
• Select the project(s) that should be imported from the archive.
• Click "Finish".
Note on linked resources! When a project contains linked resources, the Export Wizard tries to resolve all paths so that the linked resources will be found after importing into another environment. This is done by creating relative paths that use the information at time of Export that tells the IDE where the resources are located. This information depends on the location of the linked resources relative to the project Workspace at time of Export. When the exported project is imported into a new location, there is no guarantee that this relative relationship will be preserved. In general, it is not.
The relative paths that were created during Export can be inspected by highlighting the project in the Project Explorer window, right-clicking, selecting "Properties -> C/C++ build-> Settings -> Tools Settings -> Compiler -> Directories". These settings can be edited to point to the linked resources when they are located in a different relative path to the new project Workspace location.
6.TrueSTUDIOで外部ツールを起動したいのですが？
6.TrueSTUDIOで外部ツールを起動したいのですが？
First you need to enable the external tool button.
To do this, do the following procedure:
Select Windows -> Customize Perspective…
Select the Tool Bar Visibility tab and check Launch -> External Tools and in the Menu Visibility tab make sure that External Tools is checked.
You should now have a toolbar button available for launching external tools/programs.
To configure an external tool/program you can click the Runt External Tool button (It is the green Play icon with a red suitcase below).
Select External Tools Configuration to open up the Create, manage and run configurations panel.
Click the icon in the top left corner to create a new Launch configuration for some program. Here you can not only add a specific program, but you can also pass different arguments and variables to the chose program at launch time.
In addition it is possible to specify different options for the behavior when the application is launched. For instance you can specify a build before launch, refresh after launch.