This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide [25 May 2017 18:11] – Stephen Kafka | resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide [08 Nov 2021 17:41] (current) – removed deprecated packs Brandon Bushey | ||
---|---|---|---|
Line 8: | Line 8: | ||
This page covers: | This page covers: | ||
- | - How to install or upgrade the ADuCM302x Device Family Pack (DFP) for CCES | + | - How to install or upgrade the Analog Devices Packs for CCES |
+ | - ADuCM302x Device Family Pack (DFP) | ||
- How to create a new project for the ADuCM3029 | - How to create a new project for the ADuCM3029 | ||
- How to add startup code and core components to a new project for the ADuCM3029 | - How to add startup code and core components to a new project for the ADuCM3029 | ||
Line 18: | Line 19: | ||
- How to create an Intel Hex (.hex) file from an ADuCM3029 application | - How to create an Intel Hex (.hex) file from an ADuCM3029 application | ||
- | ====== Workspace and Projects | + | <WRAP center round info 60%> |
+ | We have a playlist of **YOUTUBE VIDEOS** that can help you understand different functions and features of CrossCore Embedded Studio. [[https:// | ||
+ | </ | ||
+ | |||
+ | ===== Workspace and Projects ===== | ||
A CCES workspace is a folder (e.g. c: | A CCES workspace is a folder (e.g. c: | ||
Line 26: | Line 31: | ||
Each time you start CCES, you will be prompted for a workspace location. You can opt to default to a workspace directory by choosing to use a workspace directory as your default. You will not be prompted the next time you open CCES. | Each time you start CCES, you will be prompted for a workspace location. You can opt to default to a workspace directory by choosing to use a workspace directory as your default. You will not be prompted the next time you open CCES. | ||
- | {{ : | + | {{ : |
+ | |||
+ | ===== How to install or upgrade Packs for CCES ===== | ||
+ | |||
+ | CCES 2.6.0 does not comes with the Analog Device specific packs or the ARM CMSIS Pack file pre-installed. | ||
- | ===== How to install or upgrade the ADuCM302x Device Family Pack (DFP) for CCES ===== | + | * ADuCM302x Device Family Pack (DFP) |
+ | * ARM CMSIS Pack | ||
+ | \\ | ||
+ | {{analogTV> | ||
+ | \\ | ||
- | CCES 2.6.0 does not comes with the ADuCM302x Device Family Pack (DFP) and ARM CMSIS Pack file pre-installed. | + | ==== ADuCM302x Device Family Pack (DFP) ==== |
* To install the ADuCM302x DFP: | * To install the ADuCM302x DFP: | ||
Line 39: | Line 52: | ||
* Click the //Install// Action. | * Click the //Install// Action. | ||
- | {{ : | + | {{ : |
Alternatively, | Alternatively, | ||
Line 47: | Line 60: | ||
You will be prompted to accept a license agreement and, after agreeing to it, the CMSIS-Pack file will be installed into CrossCore Embedded Studio' | You will be prompted to accept a license agreement and, after agreeing to it, the CMSIS-Pack file will be installed into CrossCore Embedded Studio' | ||
- | {{ : | + | {{ : |
- | | + | ==== ARM CMSIS Pack ==== |
+ | |||
+ | | ||
* Switch to the CMSIS Pack Manager perspective by selecting //Window | Perspective | Open Perspective | Other... | CMSIS Pack Manager//. | * Switch to the CMSIS Pack Manager perspective by selecting //Window | Perspective | Open Perspective | Other... | CMSIS Pack Manager//. | ||
* Once opened, select //Check for Updates on Web ( blue arrows on the toolbar )//, if you have not already done so. | * Once opened, select //Check for Updates on Web ( blue arrows on the toolbar )//, if you have not already done so. | ||
* Choose //ARM// in the Devices View. | * Choose //ARM// in the Devices View. | ||
- | * Select the //Generic// and // | + | * Select the //Generic// and // |
* Click the //Install// Action. | * Click the //Install// Action. | ||
- | {{ : | + | {{ : |
===== How to create a new project for the ADuCM3029 ===== | ===== How to create a new project for the ADuCM3029 ===== | ||
A project for ADuCM3029 can be created using the New CrossCore Project Wizard. This wizard will guide you through the steps to create a new project. | A project for ADuCM3029 can be created using the New CrossCore Project Wizard. This wizard will guide you through the steps to create a new project. | ||
+ | |||
+ | {{analogTV> | ||
{{ : | {{ : | ||
Line 73: | Line 90: | ||
{{ : | {{ : | ||
- | ===== How to add startup code and core components to a new project for the ADuCM3029 | + | ==== How to add startup code and core components to a new project for the ADuCM3029 ==== |
An out-of-the-box ADuCM3029 project does not have startup code or a linker description file that maps code and data. It is necessary to add these components using the Run-time Environment (RTE) Configuration Editor. | An out-of-the-box ADuCM3029 project does not have startup code or a linker description file that maps code and data. It is necessary to add these components using the Run-time Environment (RTE) Configuration Editor. | ||
Line 93: | Line 110: | ||
- Examples that you have saved to a local drive on your PC. | - Examples that you have saved to a local drive on your PC. | ||
- | - Examples that come with the ADuCM3029 Device Family | + | - Examples that come with the Analog Devices |
- Examples which are in the ADICUP3029 GIT repository (most up to date content). | - Examples which are in the ADICUP3029 GIT repository (most up to date content). | ||
Line 106: | Line 123: | ||
{{ : | {{ : | ||
- | ==== How to Import Examples that come with the ADuCM3029 Device Family Pack (DFP) ==== | + | ==== How to Import Examples that come with the ADuCM3029 Device Family Pack (DFP) or Board Support Packs (BSP) ==== |
- | Examples | + | === Opening CCES Examples |
- Open CMSIS Pack Manager perspective by clicking "Open Perspective" | - Open CMSIS Pack Manager perspective by clicking "Open Perspective" | ||
Line 115: | Line 132: | ||
- A dialog will pop-up showing the location where the example will be copied to. Click //Copy// to copy and open the example project. | - A dialog will pop-up showing the location where the example will be copied to. Click //Copy// to copy and open the example project. | ||
- | {{ : | + | {{ : |
- | The CCES Examples | + | === Opening Examples using the CCES Example |
+ | - Launch the CCES Example Broswer by clicking on //Help --> Browse Examples// | ||
- Select ADuCM302x_DFP[x.y.z] in Product drop-down list, select the example and click Open example. Then the example will be copied to your workspace. | - Select ADuCM302x_DFP[x.y.z] in Product drop-down list, select the example and click Open example. Then the example will be copied to your workspace. | ||
- | + | \\ | |
- | {{ : | + | {{analogTV> |
+ | \\ | ||
==== How to Import Existing Projects from the GIT Repository ==== | ==== How to Import Existing Projects from the GIT Repository ==== | ||
Line 135: | Line 154: | ||
- Click //Next// and then //Finish// | - Click //Next// and then //Finish// | ||
- | {{ : | + | \\ |
- | + | {{analogTV> | |
- | ===== How to build projects for programming the ADuCM3029 ===== | + | \\ |
- | + | ||
- | - Open the C perspective by clicking "Open Perspective" | + | |
- | - Right click on the project and select the //Build Project// | + | |
- | * Or click the //Hammer// icon from the toolbar. | + | |
- | + | ||
- | {{ : | + | |
===== How to configure the Tools Settings used by an ADuCM3029 project ===== | ===== How to configure the Tools Settings used by an ADuCM3029 project ===== | ||
Line 153: | Line 166: | ||
{{ : | {{ : | ||
+ | |||
+ | ==== Enabling/ | ||
+ | |||
+ | \\ | ||
+ | {{analogTV> | ||
+ | \\ | ||
+ | |||
+ | - To enable/ | ||
+ | - Change the // | ||
+ | * Enable semi-hosting by selecting the **rdimon.specs** option. | ||
+ | * Use this option if using the debugger for things like printf() or other similar tools. | ||
+ | * Disable semi-hosting by selecting the **nosys.specs** or **None** options. | ||
+ | * Use this option for standalone embedded operation. | ||
+ | - After configuring your project, click Apply and/or OK. | ||
+ | - Right click on the project and select the //Build Project//. | ||
+ | * Or click the //Hammer// icon from the toolbar. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== How to build projects for programming the ADuCM3029 ===== | ||
+ | |||
+ | - Open the C perspective by clicking "Open Perspective" | ||
+ | - Right click on the project and select the //Build Project//. | ||
+ | * Or click the //Hammer// icon from the toolbar. | ||
+ | |||
+ | {{ : | ||
===== How to configure the debug session for an ADuCM3029 application ===== | ===== How to configure the debug session for an ADuCM3029 application ===== | ||
+ | |||
+ | \\ | ||
+ | {{analogTV> | ||
+ | \\ | ||
You will need to create a launch configuration to debug your ADuCM3029 program. | You will need to create a launch configuration to debug your ADuCM3029 program. | ||
Line 170: | Line 213: | ||
{{ : | {{ : | ||
- | ======= Hardware breakpoints are limited in your ADuCM3029 application | + | ==== Hardware breakpoints are limited in your ADuCM3029 application ==== |
- When you click Debug or Apply, you will be prompted with a dialog informing your the Hardware Breakpoints are limited. Click //Yes//. You can opt to not show this dialog again. | - When you click Debug or Apply, you will be prompted with a dialog informing your the Hardware Breakpoints are limited. Click //Yes//. You can opt to not show this dialog again. | ||
Line 180: | Line 223: | ||
- Ensure that you have connected your EVAL-ADICUP3029 board to your computer via the **USB** port (the micro USB connected closest to the DC barrel jack). | - Ensure that you have connected your EVAL-ADICUP3029 board to your computer via the **USB** port (the micro USB connected closest to the DC barrel jack). | ||
- If you are already in the Debug Configurations dialog, then click //Debug//. | - If you are already in the Debug Configurations dialog, then click //Debug//. | ||
- | - If you are in the C Perspective, | + | - If you are in the C Perspective, |
- | + | - You will be prompted to switch perspective to the Debug perspective. Click //Yes//. You can opt to not show this dialog again.{{ : | |
- | {{ : | + | - If your binary (program) was built with semi-hosting enabled, then CCES will warn you that you need to re-build the program when you want to run the program without a debugger attached.{{ : |
- | + | - To change | |
- | - You will be prompted to switch perspective to the Debug perspective. Click //Yes//. You can opt to not show this dialog again. | + | - If this is the first time you have launched OpenOCD, the Windows Firewall may pop-up a window asking for access. |
- | + | ||
- | {{ : | + | |
- | + | ||
- | - If your binary (program) was built with semi-hosting enabled, then CCES will warn you that you need to re-build the program when you want to run the program without a debugger attached. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | - To disable semi-hosting in your program, visit your project Tools Settings. | + | |
- | - Change | + | |
- | - After configuring your project, click Apply and/or OK. | + | |
- | - Right click on the project and select the //Build Project// | + | |
- | * Or click the //Hammer// icon from the toolbar. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | - If this is the first time you have launched OpenOCD, the Windows Firewall may pop-up a window asking for access. | + | |
- | + | ||
- | {{ : | + | |
- If everything goes fine, in the Console window, you will see a report without errors. | - If everything goes fine, in the Console window, you will see a report without errors. | ||
* As a reference, the full text should be similar to:< | * As a reference, the full text should be similar to:< | ||
Line 226: | Line 250: | ||
Info : accepting ' | Info : accepting ' | ||
</ | </ | ||
- | - Your program' | + | - Your program' |
+ | - To terminate a debug session, click on the red //Stop// button on the toolbar.{{ : | ||
- | {{ : | + | ===== How to create an Intel Hex (.hex) file or Binary (.bin) file for an ADuCM3029 application ===== |
- | + | ||
- | - To terminate a debug session, click on the red //Stop// button on the toolbar. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | ===== How to create an Intel Hex (.hex) file from an ADuCM3029 application ===== | + | |
- Ensure that your program is built with semi-hosting disabled by visiting //Tools Settings | Linker | Libraries// and change // | - Ensure that your program is built with semi-hosting disabled by visiting //Tools Settings | Linker | Libraries// and change // | ||
- | - Rebuild your application. | + | - Rebuild your application.{{: |
- | + | - Convert your application into Intel Hex (.hex) or Binary (.bin) format by visiting Tools Settings once more. | |
- | {{ : | + | |
- | + | ||
- | - Convert your application into Intel Hex (.hex) format by visiting Tools Settings once more. | + | |
- Select the Build Steps tab. | - Select the Build Steps tab. | ||
- | - Add the following | + | - Add one of the following |
+ | * Intel Hex (.hex) file command:< | ||
+ | * Binary (.bin) file command:< | ||
- Rebuild your application. | - Rebuild your application. | ||
- | {{ : | + | {{: |
//End of Document// | //End of Document// |