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
Last revisionBoth sides next revision
crosscompiler:deep_projects [2020/09/10 18:39] ursgrafcrosscompiler:deep_projects [2021/12/27 15:17] ursgraf
Line 20: Line 20:
 # programmeropts = none; # programmeropts = none;
 # imgfile = D:\temp\myFile.bin; # imgfile = D:\temp\myFile.bin;
-# imgformat = BIN; 
 # pl_file = ; # pl_file = ;
  
Line 70: Line 69:
 </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 = BIN;+
 </code> </code>
  
-==== PL Image file ==== +==== 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.+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> <code>
-  pl_file = "D:\temp\config.bit";+  pl_file = "I:\deep\lib\rsc\flink2.bit";
 </code> </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 ====
crosscompiler/deep_projects.txt · Last modified: 2022/12/20 15:56 by ursgraf