Wiki

Analog Devices Wiki

English
English
简体中文
简体中文
日本語
日本語
Руccкий
Руccкий

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
resources:tools-software:crosscore:cces:getting-started:app [27 Aug 2019 15:54] – Steven MacDiarmidresources:tools-software:crosscore:cces:getting-started:app [27 Aug 2019 16:51] – Steven MacDiarmid
Line 64: Line 64:
  
 =====Step 2: Write Application to Flash Memory===== =====Step 2: Write Application to Flash Memory=====
-With the LDR file generated, the final step is to write your application to your device's SPI flash memory. This is handled via the Command Line Device Programmer (cldp.exe) utility. Again, we will use the [[blink example]] project created previously for the ADSP-SC573 EZ-KIT.+With the LDR file generated, the final step is to write your application to your device's SPI flash memory. This is handled via the Command Line Device Programmer (cldp.exe) utility. Again, we will use the [[resources:tools-software:crosscore:cces:getting-started:led-blink-app:sc573-blink|blink example]] project created previously for the ADSP-SC573 EZ-KIT.
  
 Just as the JTAG interface does not directly access DDR memory when downloading the DXE during debug, the CLDP does not interact directly with the board's flash memory. Instead, it uses the processor to load a host driver to communicate with flash, then passes the LDR image via JTAG so the processor can write it by issuing the proper commands to the flash. To coordinate this, **cldp.exe** needs several command-line switches and arguments to initialize the JTAG programmer, load the flash driver to the processor, then load the LDR image to the EZ-Kit's memory, as follows: Just as the JTAG interface does not directly access DDR memory when downloading the DXE during debug, the CLDP does not interact directly with the board's flash memory. Instead, it uses the processor to load a host driver to communicate with flash, then passes the LDR image via JTAG so the processor can write it by issuing the proper commands to the flash. To coordinate this, **cldp.exe** needs several command-line switches and arguments to initialize the JTAG programmer, load the flash driver to the processor, then load the LDR image to the EZ-Kit's memory, as follows:
Line 72: Line 72:
 **-emu**: emulator driver (**-1000** or **-2000**) for the active debug session. Needed to send LDR image to processor **-emu**: emulator driver (**-1000** or **-2000**) for the active debug session. Needed to send LDR image to processor
  
-<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>+<note tip>This example uses the ICE-2000 emulator so this switch is set to **ICE-2000**. Consult CCES On-Line Help for CLDP settings appropriate for your configuration.</note>
  
 **-core** the core used to run the flash memory driver. **-core** the core used to run the flash memory driver.
  
-<note important>For heterogeneous processors containing ARM and SHARC+ cores, **core 1 must run the flash memory driver**.</note>+<note important>For processors containing ARM and SHARC+ cores, **core 1 must run the flash memory driver**.</note>
  
 **-driver**: flash memory device driver (included with the Board Support Package installation) the processor uses to work with the board's flash device **-driver**: flash memory device driver (included with the Board Support Package installation) the processor uses to work with the board's flash device
Line 124: Line 124:
 3. Under **Post-build steps**, populate **Command** field with appropriate command line (see //Figure 5//). 3. Under **Post-build steps**, populate **Command** field with appropriate command line (see //Figure 5//).
      
-  <note warning>Do //not// copy and paste the command line from above as formatting differences will cause cldp.exe to fail.</note>+<note warning>Do //not// copy and paste the command line from above as formatting differences will cause cldp.exe to fail.</note>
  
 {{:resources:tools-software:crosscore:cces:getting-started:08_postbuild_configuration.gif|}} {{:resources:tools-software:crosscore:cces:getting-started:08_postbuild_configuration.gif|}}
resources/tools-software/crosscore/cces/getting-started/app.txt · Last modified: 27 Aug 2019 16:54 by Steven MacDiarmid

Page Tools