deep

a Cross Development Platform for Java

User Tools

Site Tools


crosscompiler:deep_projects

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
crosscompiler:deep_projects [2015/03/13 17:12] – [Setting Project Properties] ursgrafcrosscompiler:deep_projects [2022/12/20 15:56] (current) ursgraf
Line 1: Line 1:
 ====== Create and manage deep projects ====== ====== Create and manage deep projects ======
  
-When creating new projects all the necessary settings will be written automatically in a configuration file (''PROJECTNAME.deep'' in the root folder of the project). This file can also be manually edited to change project settings or to add more library files.+When creating new projects all the necessary settings will be written automatically in a configuration file (''PROJECTNAME.deep'' in the root folder of the project). This file can also be manually edited to change project settings.
  
 ===== The deep project file ===== ===== The deep project file =====
Line 16: Line 16:
  libpath = "I:\deep\lib";  libpath = "I:\deep\lib";
  boardtype = ntbMpc555HB;  boardtype = ntbMpc555HB;
- ostype = ntbSTS;+ ostype = sts_ppc;
  programmertype = ntbMpc555UsbBdi;  programmertype = ntbMpc555UsbBdi;
 +# programmeropts = none;
 +# imgfile = D:\temp\myFile.bin;
 +# pl_file = ;
  
 # enter names of rootclasses, e.g. # enter names of rootclasses, e.g.
Line 37: Line 40:
 <code> <code>
   libpath = "I:\deep\lib"; # network drive   libpath = "I:\deep\lib"; # network drive
-  libpath = "../ch.ntb.inf.deep.trglib","../ch.ntb.inf.junitTarget; # local+  libpath = "../org.deepjava.trglib","../ch.ntb.inf.junitTarget; # local
   libpath = "C:/Program Files/Java/jre6/lib/rt.jar","I:\deep\lib"; # jar file   libpath = "C:/Program Files/Java/jre6/lib/rt.jar","I:\deep\lib"; # jar file
   libpath = "I:\deep\lib","M:\EUser\runtime-EclipseApplication\Test"; # local project   libpath = "I:\deep\lib","M:\EUser\runtime-EclipseApplication\Test"; # local project
Line 46: Line 49:
 <code> <code>
   boardtype = ntbMpc555HB;   boardtype = ntbMpc555HB;
 +</code>
 +
 +==== Target operating system ====
 +Choose an operating system with
 +<code>
 +  ostype = sts_ppc;
 </code> </code>
  
 ==== Programmer ==== ==== Programmer ====
-The Programmer declaration is optional, if no programmer is given, deep will not automatically download the image to the target board.+The programmer declaration is optional, if no programmer is given, deep will not automatically download the image to the target board.
 <code> <code>
   programmertype = ntbMpc555UsbBdi;   programmertype = ntbMpc555UsbBdi;
 </code> </code>
  
-==== Target operating system ==== +==== Programmer Options ==== 
-Choose an operating system with+This options are used when the programmer is accessed trough a telnet connection, e.g. with OpenOCD.
 <code> <code>
-  ostype ntbSTS;+  programmeropts localhost_4444;
 </code> </code>
  
-==== Image file ==== +==== Image File ==== 
-It is possible to write an image file to disk. This might be useful for further processing or debugging. Currently only the binary image file format is supported.+It is possible to write an image file to disk. This might be useful for further processing or debugging.
 <code> <code>
-  imgfile = "D:\temp\myFile.bin"+  imgfile = "D:\myProject\myFile";
-  imgformat = binary;+
 </code> </code>
 +
 +==== PL Image File ====
 +If the target architecture contains a programmable logic block (PL), you can specify the bit-file with which the PL can be configured, e.g.
 +<code>
 +  pl_file = "I:\deep\lib\rsc\flink2.bit";
 +</code>
 +
 +==== Target Command Table File ====
 +When you specify this option, the launcher will create a file containing all methods together with their memory addresses of all classes which are commands.
 +<code>
 +  tctfile = "../ch.ntb.inf.junitTarget/tct/targetCommands.dtct";
 +</code>
 +This option is solely used for testing purposes.
  
 ==== Rootclasses ==== ==== Rootclasses ====
Line 74: Line 95:
  
  
----- 
- 
- 
- 
-===== Editing Run Configurations ===== 
-All the run configurations of all projects in a workspace can be edited with Properties - > Run/Debug Settings. \\ 
-{{.:runconfig2.png?300|}} 
-{{.:runconfig1.png?430|}} 
-With Run/Debug setting you can choose which run configuration of the chosen board you want to run. All the available run configuration (must be defined in the board description file) are listed. One of them can be chosen. 
- 
-===== Renaming Deep Projects ===== 
-Refactoring is a very powerful tool in the eclipse framework. You can rename a deep project by choosing a project in the package explorer and pressing Shift+Alt+R. The project together with its associated deep project file will be renamed. 
  
  
crosscompiler/deep_projects.1426263123.txt.gz · Last modified: 2016/02/25 13:33 (external edit)