Post Go back to editing

Using CLDP to program two ADSP-21364 on the same JTAG chain

I have two ADSP-21364 on the same JTAG chain.  The flash part is the same as in the eval board. I used to be able to program them in VisualDSP using the supplied device programmer and the flash programmer GUI but unsuccessful to do so using CLDP in CrossCore (with the Visual DSP device programmer DXE or Crosscore device programmer DXE). What are the steps required to accomplish this? I cannot find any formal documentation on how to use CLDP on a multi-chain JTAG configuration.

Parents
  • Hi,

    The CLDP utility supports the following command-line switch:

    -config [[path\]filename]
    This option supports complex targets consisting of more than one processor, or more than one device in the JTAG scan chain.Use the Target Configurator to create the file.

    Example: cldp -config myConfig.ini

    For more information please refer the below CCES help path:
    CrossCoreRegistered Embedded Studio 2.7.0 > Integrated Development Environment > Debugging Targets > Target Configurator > Platform Properties > Saving a Platform for Programming Devices

    You would need to create 2 different configuration files.One where the 1st chip is unknown(BYPASS) and the 2nd is the 21364. Then create a different config file that is the opposite and the 1st chip is the 21364 and the 2nd an unknown(BYPASS). Unfortunately right now we don't support writing to them both at the same time so it has to be done separately. We have an issue in our database to change this in a future release. Also note that the platforms used to create the config files should not be removed from the Configurator utility after because we use those platforms during the programming.

    Below is the example command-line that were used in CLDP.
    cldp.exe -config config1.ini -core 0 -driver w25q32bv_dpia.dxe -cmd prog -erase affected -format hex -file App1.ldr
    cldp.exe -config config2.ini -core 0 -driver w25q32bv_dpia.dxe -cmd prog -erase affected -format hex -file App2.ldr

    You can find the detailed information about Command line device programmer in the below CCES help path.
    CrossCoreRegistered Embedded Studio 2.7.0 > Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer

    For more information, please refer the below FAQ:
    FAQ: How do I program flash on my target board using CrossCore Embedded Studio?
    https://ez.analog.com/docs/DOC-2111

    Please refer the below CCES help path about Configuring a Scan Chain.
    CrossCoreRegistered Embedded Studio 2.7.0 > Integrated Development Environment > Debugging Targets > Target Configurator > Platform Properties > Configuring a Scan Chain

    Regards,

    Kader

Reply
  • Hi,

    The CLDP utility supports the following command-line switch:

    -config [[path\]filename]
    This option supports complex targets consisting of more than one processor, or more than one device in the JTAG scan chain.Use the Target Configurator to create the file.

    Example: cldp -config myConfig.ini

    For more information please refer the below CCES help path:
    CrossCoreRegistered Embedded Studio 2.7.0 > Integrated Development Environment > Debugging Targets > Target Configurator > Platform Properties > Saving a Platform for Programming Devices

    You would need to create 2 different configuration files.One where the 1st chip is unknown(BYPASS) and the 2nd is the 21364. Then create a different config file that is the opposite and the 1st chip is the 21364 and the 2nd an unknown(BYPASS). Unfortunately right now we don't support writing to them both at the same time so it has to be done separately. We have an issue in our database to change this in a future release. Also note that the platforms used to create the config files should not be removed from the Configurator utility after because we use those platforms during the programming.

    Below is the example command-line that were used in CLDP.
    cldp.exe -config config1.ini -core 0 -driver w25q32bv_dpia.dxe -cmd prog -erase affected -format hex -file App1.ldr
    cldp.exe -config config2.ini -core 0 -driver w25q32bv_dpia.dxe -cmd prog -erase affected -format hex -file App2.ldr

    You can find the detailed information about Command line device programmer in the below CCES help path.
    CrossCoreRegistered Embedded Studio 2.7.0 > Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer

    For more information, please refer the below FAQ:
    FAQ: How do I program flash on my target board using CrossCore Embedded Studio?
    https://ez.analog.com/docs/DOC-2111

    Please refer the below CCES help path about Configuring a Scan Chain.
    CrossCoreRegistered Embedded Studio 2.7.0 > Integrated Development Environment > Debugging Targets > Target Configurator > Platform Properties > Configuring a Scan Chain

    Regards,

    Kader

Children
  • Hi Kader,

    Thank you for the information. I had the same question and thanks to your answer I made it work. My follow-up question is in what file are these platforms saved? The .ini files only point to the platform names. I would like to be able to save the process of creating these platforms on different computers.

    Thanks again,

  • Hi,

    Platforms can be created using configurator utility.

    You can't simply transfer(copying) the config.ini file of the platform to different machines.For programming config.ini from CLDP on multiple machines, you need to generate that particular platform(config.ini) on each machine where the same config.ini should be used, because the platforms used to create the config files should not be removed from the Configurator utility of CCES in that machine.If the platform used to save the Target Configuration file is renamed or deleted, the file must be recreated.

    We recommend you to refer the below CCES help page for mre information.
    CrossCore® Embedded Studio 2.8.3 > Integrated Development Environment > Debugging Targets > Target Configurator > Platform Properties > Saving a Platform for Programming Devices

    Regards,
    Santha kumari.K

  • thanks Santha. I got it. it's not too bad to re-create these platforms on new computers. I just wanted to make sure I am not omitting any obviously simpler ways of doing it.