This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| crosscompiler:deep_projects [2015/03/13 17:12] – [Editing Run Configurations] ursgraf | crosscompiler: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 ('' | + | When creating new projects all the necessary settings will be written automatically in a configuration file ('' |
| ===== The deep project file ===== | ===== The deep project file ===== | ||
| Line 16: | Line 16: | ||
| libpath = " | libpath = " | ||
| boardtype = ntbMpc555HB; | boardtype = ntbMpc555HB; | ||
| - | ostype = ntbSTS; | + | ostype = sts_ppc; |
| programmertype = ntbMpc555UsbBdi; | programmertype = ntbMpc555UsbBdi; | ||
| + | # | ||
| + | # imgfile = D: | ||
| + | # pl_file = ; | ||
| # enter names of rootclasses, | # enter names of rootclasses, | ||
| Line 37: | Line 40: | ||
| < | < | ||
| libpath = " | libpath = " | ||
| - | libpath = "../ch.ntb.inf.deep.trglib"," | + | libpath = "../org.deepjava.trglib"," |
| libpath = " | libpath = " | ||
| libpath = " | libpath = " | ||
| Line 46: | Line 49: | ||
| < | < | ||
| boardtype = ntbMpc555HB; | boardtype = ntbMpc555HB; | ||
| + | </ | ||
| + | |||
| + | ==== Target operating system ==== | ||
| + | Choose an operating system with | ||
| + | < | ||
| + | ostype = sts_ppc; | ||
| </ | </ | ||
| ==== Programmer ==== | ==== Programmer ==== | ||
| - | The Programmer | + | The programmer |
| < | < | ||
| programmertype = ntbMpc555UsbBdi; | programmertype = ntbMpc555UsbBdi; | ||
| </ | </ | ||
| - | ==== Target operating system | + | ==== Programmer Options |
| - | Choose an operating system | + | This options are used when the programmer is accessed trough a telnet connection, e.g. with OpenOCD. |
| < | < | ||
| - | | + | |
| </ | </ | ||
| - | ==== 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. |
| < | < | ||
| - | imgfile = "D:\temp\myFile.bin"; | + | imgfile = "D:\myProject\myFile"; |
| - | imgformat = binary; | + | |
| </ | </ | ||
| + | |||
| + | ==== 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. | ||
| + | < | ||
| + | pl_file = " | ||
| + | </ | ||
| + | |||
| + | ==== 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. | ||
| + | < | ||
| + | tctfile = " | ||
| + | </ | ||
| + | This option is solely used for testing purposes. | ||
| ==== Rootclasses ==== | ==== Rootclasses ==== | ||
| Line 74: | Line 95: | ||
| - | ---- | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | ===== 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. | ||