Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| resources:tools-software:crosscore:cces:getting-started:bsp [01 Oct 2018 20:00] – [System.svc] Chad Wentworth | resources:tools-software:crosscore:cces:getting-started:bsp [07 Nov 2018 16:38] – [Power On Self Test] Chad Wentworth | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| =====Power On Self Test===== | =====Power On Self Test===== | ||
| In order to ship our EZ-KITs to customers we need to verify that they are working properly. The Power On Self Test is one of the ways we ensure that our EZ-KITs function correctly. The Power On Self Test includes many of the drivers and services available for that particular processor since it has to test all components of the board. This is often the goto example for customers looking for sample code for a particular peripheral. | In order to ship our EZ-KITs to customers we need to verify that they are working properly. The Power On Self Test is one of the ways we ensure that our EZ-KITs function correctly. The Power On Self Test includes many of the drivers and services available for that particular processor since it has to test all components of the board. This is often the goto example for customers looking for sample code for a particular peripheral. | ||
| - | |||
| - | =====System Configuration File (system.svc)===== | ||
| - | Every CCES project contains a system configuration file. The file is the IDE's interface for adding to and managing pre-written software components in a project' | ||
| - | |||
| - | {{: | ||
| - | |||
| - | The **System Configuration Overview** window lists all the installed add-ins that you selected when creating the project. Here, you can also add more add-ins, remove them, or upgrade them if your application was created with an older version of the add-ins. In CCES, **Add-Ins** are additional tools that allow for things such as code generation to facilitate your code development process. If you create a new project using the default selections, you will have two or three default add-ins – **Analog Devices’ MCAPI** (only available for multi-core processors), | ||
| - | |||
| - | **Analog Devices’ MCAPI add-in** - provides Analog Devices’ implementation of Multicore Association’s Multicore Communications API (MCAPI™). Documentation can be found in //CCES Online Help under CrossCore® Embedded Studio 2.3.0 -> System Run-Time Documentation -> Multicore Communications API (MCAPI) Specification// | ||
| - | |||
| - | **Startup Code/LDF add-in** - automatically generates the necessary startup code for the processor. This code is executed before the application’s main function to perform required processor initialization based on user input. The GUI available via the configuration tab allows the user to select Cache and Memory Protection, configure how memory is initialized, | ||
| - | |||
| - | **Pin Multiplexing add-in** - provides a GUI to configure pin usage to support the various peripheral interface combinations (SPI, SMC, CAN, TWI, etc.) available on the target processor. The GUI provides all the information necessary to properly configure general-purpose ports on the processor to support the required peripherals and identify/ | ||
| - | |||
| - | To install additional add-ins, click Add… and the selection window will appear: | ||
| - | |||
| - | {{: | ||
| - | |||
| - | There are also add-ins for the various system services (e.g., RTC and GPIO) and device drivers (for supported peripherals such as PPI, SPI, SPORT, etc.). | ||
| ---- | ---- | ||
| - | Next Topic: [[resources: | + | {{navigation CCES Getting Started# |
resources/tools-software/crosscore/cces/getting-started/bsp.txt · Last modified: 07 Nov 2018 16:40 by Chad Wentworth