• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 828 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSV5: Cannot Change Target from XDS560v2 Emulator to Simulator, or Vice Versa

Bernard Oliver
Expert 1020 points

Hi,

My 6678 EVM with XDS560v2 Mezzanine emulator (TMDXEVM6678LE) has finally turned up. Very nice bit of kit, and great value for the money. 

However, I am unable to change the target for even the simplest programs (e.g. hello world) from the EVM to the simulator, or vice versa.

When I create a new project (e.g. New CCS Project using the SYS/BIOS Empty Example Template)  specifying the simulator as target, it debugs OK under the simulator, and when I create the identical project except for specifying the emulator as target, that debugs OK on the EVM.    (During the project creation process I specify the target in 2 locations: a) in the .ccxml file, and b) in the final form presented by the New CSS Project wizard at the "RTSC Platform" prompt where I choose "ti.platforms.evm6678" for the emulator or "ti.sdo.ipc.examples.platforms.evm6678.core0" for the simulator.

I then edit the project that debugs on the simulator to specify the emulator as target by:

a) editing the .ccxml file  to specify the emulator as target,

b) manually changing the "RTSC platform" parameter specified at Properties/XDCtools/Basic Options from "ti.sdo.ipc.examples.platforms.evm6678.core0" to "ti.platforms.evm6678"

c) clean and rebuild.  The debug window then reports "Blackhawk XDS560v2-USB Mezzanine Emulator_0/C66xx_0 (Disconnected : Unknown)", and ditto for the other cores. If I then right click/Connect Target, I get "No source available for "0x20b002a8"

I have followed the equivalent process to change the project working on the emulator to the simulator, and debug reports: "0x00800000 (no symbols defined of 0x00800000)" for each core.

I have attempted deleting the .ccxml file and creating a new one specifying the other target, but it makes no difference.   (I am also suspicious of the final form in the "New CSS Project " wizard where it gives me the following options for "RTSC Platform"   This step is not in the tutorial/videos, and it seems odd that I have to use an Item from an example in the IPC package:

  • ti.platforms.evm6670
  • ti.platforms.evm6678
  • ti.platforms.simTCI6608
  • ti.platforms.simTCI6616
  • ti.sdo.ipc.examples.platforms.evm6670.core0,
  • ti.sdo.ipc.examples.platforms.evm6678.core0
  • xdc.platform.generic)

What am I doing wrong? 

Regards,

Bernard

 

  • 0
    Expert 1020 points

    I have worked out that I should be using simTCI6608, but the problem remains.

    Bernard

  • 0 in reply to Bernard Oliver
    TI__Guru**** 162305 points

    Bernard,

    Changing the connection in your target configuration (ccxml) file will cause it to be regenerated so it should be fine.  When changing to the EVM from the sim I would check to make sure that it has the GEL initialization file specified for each core.  You can see by clicking on the advanced tab when the ccxml file is open and then click on each core and see if something is specified for the initialization script.  Other than that I would think that your ccxml file is fine.

    I may need to move this into the BIOS forum to see if there are any tricks to changing RTSC platforms.

    John

  • 0 in reply to JohnS
    TI__Intellectual 1270 points

    Hi, what's happening is that immediately after you "Connect to Target" it goes to an uninitialized state. There is no program in the memory for neither the simulator nor the emulator.  Only after you "Load Program" does the program get placed into memory.

     

    You don't need to change the platforms (6678/6678.core0/sim6670) -- they simply specify the memory layout so that the compiler can bring in the appropriate libraries and place sections in the right places.

     

    I think if you follow the procedure:

    Launch Target Configuration (Emulator or Simulator) -> Connect to Target (Emulator only) -> Load Program -> Resume

    then you should be fine.  You must terminate the session and restart when you are switching from a simulator to an emulator.

     

    Hope that helps

  • 0 in reply to Tim Wentz
    Expert 1020 points

    Thanks guys, that works

     

    Regards,

    Bernard