After discussion with Stephan Ahrends,NI, at the LV EAT handson course in Munich I have following questions:
1. How to proceed to create a new Target for a new OS, in my case PowerPC PPc750 running Lynx?
1.1 I used the wizzard "Create Embedded Target ..." to create a new entry for Lynx OS successfully.
1.2 Next I copied the target cmd565 from ecos to the lyynx directory.
1.3 Then I tried to created a new target from lynx\cmd565.
I got an error that some file could not be moved since they were missing.
But I got a new directory lynx\ppc750, and after restart of LabVIEW is was visible in the target secetion.
1.4 I deleted the lynx\cmd565 target from the lynx directory since it was used only a template. I also deleted the directory
lynx\pp750\rom since it is a relict from the template. I guess I can remove some more file: Which?
2. Integrating the Tool Chain?
2.1 lynx\TargetOptions.ini: Rename the section [ECOS Device] to [Lynx Device]. Later to be modified for TCP/IP download and debugging.
2.2 lynx\lynx_LEP_TargetPlugin:
2.2.1 Save *_ecos_*.ctl to *_lynx_*.ctl and delete the previous since the are a relict from the template.
2.2.2 Modifiy all Plugin-VIs according to the needs for Lynx. Not yet done!
2.3 lynx\build: We have several targets all running Lynx. I think I have to prepare different makefiles for all targets which are called from the plugin-VIs.
3. Integrating the specific target
Since our Lynx OS is not a cross compiled embedded system I have to do something different than it is done in the template.
3.1 lynx\ppc750\TargetOption.ini: Rename the section [Axiom CMD565, eCos RAM Image] to [PPC750, Lynx]. Later to be modified for TCP/IP download and debugging.
3.2 lynx\ppc750: I guess *.xml are generated by other tools and need no manual modifications.
3.3 lynx\ppc750\LEPPlugins.ini: Replace ecos with lynx and cmd565 with ppc750.
3.3 Rename lynx\ecos_cmd565_LEP_TargetPlugin to lynx\lynx_ppc750_LEP_TargetPlugin.
3.4 lynx\lynx_ppc750_LEP_TargetPlugin: Rename LEP_ecos_cmd565_*.vi to LEP_lynx_ppc750_*.vi
4. Repair the VI-Hierarchy
4.1 Open the Plugin-VIs and repair the links to the renamed VIs.
4.2 Rename ecos to lynx and cmd565 to ppc750.
4.3 Relink VI types for call by reference to the VI in the Lynx directory.
5. Modify the VIs to the Lynx requirements.
6. Porting the LV Runtime
So far I finished with points 1 to 4 and all menue items, except Build, Run and Debug, are working in principle.
I think the next step is to compile the LabVIEW Runtime Libraries, point 6, to find out which commands and options have to be set in point 5 to integrate the tool chain for Lynx OS.
Holger
