Changes between Version 2 and Version 3 of ppc_prog_overview/EDK_prog


Ignore:
Timestamp:
Aug 3, 2006, 2:01:43 PM (18 years ago)
Author:
sgupta
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ppc_prog_overview/EDK_prog

    v2 v3  
    1313It is assumed that the user has already successfully generated the hardware system in XPS. Before building a software application project, it’s important to set up the Operating System and drivers such that all required API are included during compilation. This can be done through direct modification of the system MSS file (requires familiarity with the MSS format and a good read of the software platform specification manual), or through tweaking settings in the “Software Platform Settings” User Interface. “Software Platform Settings” (SPS) is available in the “Software” drop-down in XPS.[[BR]][[BR]] 
    1414There exist 4 tabs for setting up the system in SPS. “'''Software Platform''',” “'''OS and Libraries''',” “'''Drivers''',” and “'''Interrupt Handlers'''.” In “'''Software Platform''',” the user can specify the processor settings, the Operating System to use, and extended built in libraries. All operating systems support the extended built in libraries. The user may select these to fit their functionality requirements (such as lwip for networking or xilfatfs for using Compact Flash and the SystemACE controller on WARP) – if the functionality is not required, it’s best to leave the library out in order to reduce the operating system memory footprint. The extended library API documentation is available in the “OS and Libraries Document Collection” It should be located under the EDK installation directory: '''$EDK\doc\oslib_rm.pdf'''.[[BR]][[BR]]
    15 The “'''OS and Libraries'''” tab in SPS gives the user a host of modifiable parameters based on the chosen operating system. Here, the user can specify the peripheral to use for standard I/O – for warp this should be the RS232 serial peripheral. This will allow the WARP to display prints to a mini-terminal (such as TeraTerm Pro) by simply calling the print( ) function in C. If any extended libraries were included, they can be modified in this tab as well. Information on all the modifiable parameters (available for standalone and xilkernel operating systems only), is also located in '''$EDK\doc\oslib_rm.pdf.'''[[BR]][[BR]]
     15The “'''OS and Libraries'''” tab in SPS gives the user a host of modifiable parameters based on the chosen operating system. Here, the user can specify the peripheral to use for standard I/O – for warp this should be the RS232 serial peripheral. This will allow the WARP to display prints to a mini-terminal (such as !TeraTerm Pro) by simply calling the print( ) function in C. If any extended libraries were included, they can be modified in this tab as well. Information on all the modifiable parameters (available for standalone and xilkernel operating systems only), is also located in '''$EDK\doc\oslib_rm.pdf.'''[[BR]][[BR]]
    1616The third tab is “'''Drivers'''.” The parameters here typically do not need to be changed. Bringing an EDK-compliant peripheral into XPS will automatically update the MSS to include the most up-to-date driver associated with it. If a deprecated driver is required, however, it can be selected here.[[BR]][[BR]]
    1717The final tab is “'''Interrupt Handlers'''.” The user can give specify the function names to be called with an associated peripheral’s interrupt. It is important to note, that for interrupts to appear here, they must be tied in hardware first correctly. Secondarily, it is not required (but convenient) to place the handler names here – an alternative to doing so, is to use the intc API (for standalone OS, documentation located in: '''$EDK\doc\xilinx_drivers_api_toc.htm'''), or the xilkernel API (located in '''$EDK\doc\oslib_rm.pdf'''). [[BR]][[BR]]