Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| resources:tools-software:crosscore:cces:getting-started:app [26 Aug 2019 18:00] – Steven MacDiarmid | resources:tools-software:crosscore:cces:getting-started:app [27 Aug 2019 15:54] – Steven MacDiarmid | ||
|---|---|---|---|
| Line 59: | Line 59: | ||
| * [[resources: | * [[resources: | ||
| * [[resources: | * [[resources: | ||
| - | * [[resources: | + | * [[resources: |
| After creating your boot image, please return to this page and continue from [[#Step 2: Write Application to Flash Memory|Step 2]] below. | After creating your boot image, please return to this page and continue from [[#Step 2: Write Application to Flash Memory|Step 2]] below. | ||
| Line 73: | Line 73: | ||
| <note tip>This example uses the ICE-1000 emulator so this switch is set to **ICE-1000**. Consult CCES On-Line Help for CLDP settings appropriate for your configuration.</ | <note tip>This example uses the ICE-1000 emulator so this switch is set to **ICE-1000**. Consult CCES On-Line Help for CLDP settings appropriate for your configuration.</ | ||
| + | |||
| + | **-core** the core used to run the flash memory driver. | ||
| + | |||
| + | <note important> | ||
| **-driver**: | **-driver**: | ||
| Line 93: | Line 97: | ||
| | | ||
| <code bash> | <code bash> | ||
| - | cldp -proc ADSP-SC573 -emu ICE-1000 -driver "< | + | cldp -proc ADSP-SC573 -emu ICE-1000 |
| </ | </ | ||
| <note important>//< | <note important>//< | ||
| - | =====Automatically Flash Device | + | === Method 1: Use Command-Line |
| - | CCES can be configured | + | 1. Open a Command Prompt and navigate |
| - | - In **Project Explorer** view, right-click **CCES Example** project name and select **Properties…** | + | |
| - | - On **C/%%C++%% Build Settings** page, select **Build Steps** | + | |
| - | - Under **Post-build steps**, populate **Command** field with appropriate command line (see //Figure 5//). | + | |
| - | + | ||
| - | <note warning> | + | |
| - | {{:resources: | + | 2. Run the flash driver using the appropriate command line from above and tailoring as required: |
| + | * Our blink example targets the ADSP-SC589 heterogeneous processor so we must specify **-core 1** | ||
| + | * Ensure the path to the **-driver** file correctly points to the core 1 '' | ||
| + | * Ensure the **-path** parameter points to the '' | ||
| - | //Figure 5: CLDP Command Line in Project Settings Build Steps Window// | + | {{:resources: |
| - | The successful **. . . . . . done** message | + | //Figure 1: Flashing device directly with cldp.exe// |
| + | |||
| + | The successful **. . . . . . done** message indicates device programming is complete and the application is now stored in the flash memory. To verify the application boots properly without CCES, close CCES and verify the boot selector switch (SW1) on the board is in Position 1 to boot from SPI flash. If the board’s power is cycled or reset button pushed, the LED blink application will boot from flash memory should behave as it did during debug. | ||
| + | |||
| + | === Method 2: Configure CCES to Automatically Trigger cldp.exe on Successful Build === | ||
| + | |||
| + | CCES can be configured to automatically call **cldp.exe** at the end of the build process: | ||
| + | 1. In **Project Explorer** view, right-click any of the projects and select **Properties…** | ||
| + | 2. On **C/%%C++%% Build Settings** page, select **Build Steps** | ||
| + | 3. Under **Post-build steps**, populate **Command** field with appropriate command line (see //Figure 5//). | ||
| + | |||
| + | <note warning> | ||
| - | {{: | + | {{: |
| - | // | + | // |
| ---- | ---- | ||
| {{navigation CCES Getting Started# | {{navigation CCES Getting Started# | ||
resources/tools-software/crosscore/cces/getting-started/app.txt · Last modified: 27 Aug 2019 16:54 by Steven MacDiarmid