Differences

This shows you the differences between two versions of the page.

--- resources:eval:user-guides:eval-adicup3029:tools:cces_user_guide [16 May 2017 18:30] – Andrew McLachlan
+++ 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:
-  - 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 add startup code and core components to a new project for the ADuCM3029
@@ Line 16: / Line 17: @@
   - How to configure the debug session for an ADuCM3029 application
   - How to start and stop debugging 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://www.youtube.com/playlist?list=PLiwaj4qabLWycR06TNf8eqSwX7qkDbSu_ | CrossCore Embedded Studio Videos ]]
+</WRAP>
+===== Workspace and Projects =====
 A CCES workspace is a folder (e.g. c:\Users\anon\cces\2.6.0) that contains project resources and metadata.
@@ Line 25: / 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.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-workspace.png |}}
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-workspace.png?500 |}}
+===== 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.  The following Packs are required to use the EVAL-ADICUP3029 along with the hardware examples and wireless connectivity
-===== How to install or upgrade the ADuCM302x Device Family Pack (DFP) for CCES =====
+  * ADuCM302x Device Family Pack (DFP)
+  * ARM CMSIS Pack
+\\
+{{analogTV>5588113421001}}
+\\
-CCES 2.6.0 does not comes with the ADuCM302x Device Family Pack (DFP) and ARM 4.5.0 CMSIS Pack file pre-installed.
+==== ADuCM302x Device Family Pack (DFP) ====
   * To install the ADuCM302x DFP:
-    * 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 )//. This may time a minute or two.
+  * Once opened, select //Check for Updates on Web ( blue arrows on the toolbar )//. This may time a minute or two.
-    * Choose //Analog Devices// and //ADuCM302x Series// in the Devices View.
+  * Choose //Analog Devices// and //ADuCM302x Series// in the Devices View.
-    * Select the //ADuCM302x CMSIS Pack// version (e.g. 1.0.4) from the Packs View.
+  * Select the //ADuCM302x CMSIS Pack// version (choose version 2.0.0 or higher) from the Packs View.
-    * Click the //Install// Action.
+  * Click the //Install// Action.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-perspective.png |}}
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-aducm302x-dfp-200.png |}}
 Alternatively, the ADuCM3029 Device Family Pack (DFP) files can be installed using a local download.
@@ Line 46: / 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's CMSIS-Pack installation directory (e.g. C:\Analog Devices\CrossCore Embedded Studio 2.6.0\ARM\packs\AnalogDevices).
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-import.png |}}
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-import-200.png |}}
+==== ARM CMSIS Pack ====
+  * To install the ARM 4.5.0 CMSIS Pack(or greater):
+  * 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.
+  * Choose //ARM// in the Devices View.
+  * Select the //Generic// and //ARM.CMSIS// from the Packs View, select version 4.5.0
+  * Click the //Install// Action.
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-arm-cmsis-200.png |}}
 ===== 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.
+{{analogTV>5588125388001}}
 {{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-project-new.png |}}
@@ Line 63: / Line 90: @@
 {{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-project-explorer.png |}}
-===== 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.
@@ Line 83: / Line 110: @@
   - Examples that you have saved to a local drive on your PC.
-  - Examples that come with the ADuCM3029 Device Family Pack (DFP).
+  - Examples that come with the Analog Devices Pack.
   - Examples which are in the ADICUP3029 GIT repository (most up to date content).
@@ Line 96: / Line 123: @@
 {{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-file-import.png |}}
-==== 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 are provided with the ADuCM3029 DFP and can be opened from the CMSIS Pack Manager Perspective Examples View.
+=== Opening CCES Examples using the CMSIS Pack Manager Perspective ===
   - Open CMSIS Pack Manager perspective by clicking "Open Perspective" icon on tool bar and selecting "CMSIS Pack Manager" in the Open Perspective window (or choose CMSIS Pack Manager perspective if already open).
@@ Line 105: / 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.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-example.png |}}
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-cmsis-pack-example-200.png |}}
-The CCES Examples Browser can also be used to open examples by Help | Browse Examples.
+=== Opening Examples using the CCES Example Browser ===
+  - 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.
+\\
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-example-browser.png |}}
+{{analogTV>5588123788001}}
+\\
 ==== How to Import Existing Projects from the GIT Repository ====
@@ Line 125: / Line 154: @@
   - Click //Next// and then //Finish//
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-clone.png |}}
+\\
+{{analogTV>5588103026001}}
-===== How to build projects for programming the ADuCM3029 =====
+\\
-  - Open the C perspective by clicking "Open Perspective" icon on tool bar and selecting C in the Open Perspective window (or choose the C perspective if already open).
-  - Right click on the project and select the //Build Project//.
-     * Or click the //Hammer// icon from the toolbar.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-project-build.png |}}
 ===== How to configure the Tools Settings used by an ADuCM3029 project =====
@@ Line 143: / Line 166: @@
 {{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-project-tools-settings.png |}}
+==== Enabling/Disabling Semihosting ====
+\\
+{{analogTV>5588123787001}}
+\\
+  - To enable/disable semi-hosting in your program, visit your project //Tools Settings//.
+  - Change the //semi-hosting support// option under //Linker | Libraries//:
+    * 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.
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-spec.png| }}
+===== How to build projects for programming the ADuCM3029 =====
+  - Open the C perspective by clicking "Open Perspective" icon on tool bar and selecting C in the Open Perspective window (or choose the C perspective if already open).
+  - Right click on the project and select the //Build Project//.
+     * Or click the //Hammer// icon from the toolbar.
+{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-project-build.png |}}
 ===== How to configure the debug session for an ADuCM3029 application =====
+\\
+{{analogTV>5588115358001}}
+\\
 You will need to create a launch configuration to debug your ADuCM3029 program.
@@ Line 160: / Line 213: @@
 {{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-configuration.png |}}
-======= 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.
 {{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-hw-limited.png |}}
 ===== How to start and stop debugging an ADuCM3029 application =====
   - 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 in the C Perspective, then you can launch the last Debug session by clicking the //Beetle// Debug button on the toolbar.
+  - If you are in the C Perspective, then you can launch the last Debug session by clicking the //Beetle// Debug button on the toolbar.{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-toolbar.png |}}
+  - You will be prompted to switch perspective to the Debug perspective. Click //Yes//. You can opt to not show this dialog again.{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-perspective.png |}}
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-toolbar.png |}}
+  - 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.{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-semi-hosting.png |}}
+  - To change the semihosting settings please see the section on "Enabling/Disabling Semihosting" above.
-  - 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.  Click on "//Allow Access//".{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-openocd-firewall.png |}}
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-perspective.png |}}
-  - 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.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-semi-hosting.png |}}
-  - To disable semi-hosting in your program, visit your project Tools Settings.
-  - Change the //semi-hosting support// option under //Linker | Libraries// to nosys.specs or None, depending on whether or not your program is currently using semi-hosting (e.g. printf).
-  - 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.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-spec.png| }}
-  - If this is the first time you have launched OpenOCD, the Windows Firewall may pop-up a window asking for access.  Click on "//Allow Access//".
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm360-openocd-firewall.png |}}
   - 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:<code>
@@ Line 215: / Line 250: @@
 Info : accepting 'gdb' connection on tcp/3333
 </code>
-  - Your program's execution is stopped automatically at the first breakpoint which is at the beginning of main() loop. You can use the debug functions and features of the CCES environment. (Such as stepping through, breakpoints, register reads, variable values, etc.)
+  - Your program's execution is stopped automatically at the first breakpoint which is at the beginning of main() loop. You can use the debug functions and features of the CCES environment. (Such as stepping through, breakpoints, register reads, variable values, etc.){{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debugging.png |}}
+  - To terminate a debug session, click on the red //Stop// button on the toolbar.{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-toolbar-stop.png |}}
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debugging.png |}}
+===== 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.
+  - Ensure that your program is built with semi-hosting disabled by visiting //Tools Settings | Linker | Libraries// and change //Semihosting support// to //nosys.specs// or //None//, depending on your application set-up.
+  - Rebuild your application.{{:resources:eval:user-guides:eval-adicup360:tools:360_no_sys.gif|}}
+  - Convert your application into Intel Hex (.hex) or Binary (.bin) format by visiting Tools Settings once more.
+  - Select the Build Steps tab.
+  - Add one of the following commands to the //Post-build steps | Command// entry box, depending on which file type you want.
+    * Intel Hex (.hex) file command:<code>arm-none-eabi-objcopy -O ihex ${ProjName} ${ProjName}.hex</code>
+    * Binary (.bin) file command:<code>arm-none-eabi-objcopy -O binary ${ProjName} ${ProjName}.bin</code>
+  - Rebuild your application.
-{{ :resources:eval:user-guides:eval-adicup3029:tools:eval-aducm3029-debug-toolbar-stop.png |}}
+{{:resources:eval:user-guides:eval-adicup360:tools:360_post_bin.gif|}}
 //End of Document//

Wiki

Analog Devices Wiki

Differences

Analog Devices Wiki

Differences

Page Tools