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.

EVMC6678L Onboard Emulator in Linux

Hello Everyone, 

   I've been having some issues with connecting to my EVMC6678L's xds100 onboard emulator.  Since I was unable to connect to my board through CCS I began troubleshooting the connection with the command line utilities provided.  

 

The board comes with a CD that contains the original OS images.  These images can be programmed into NAND and NOR flash using the built in emulator.  I've successfully used the program_evm.js utility, in conjunction with the tools provided in the CCS installation to program the demo board.  However connecting to the device for debug/profiling sessions has not proved possible.

I've also tried using the dbgjtag utility that accompanies the CCS installation.  A .dat file was obtained from a windows xp system, and modified (according to the advice given in this post: http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/135560/488307.aspx#488307), and then used in an attempt to connect to the EVM.  Here's the output at the terminal:

 

 

./dbgjtag -f ./4863.ccBoard0.dat  -rv -S pathlength 

 

The [-d/-F] or [-X] options were not used.

This utility requires an emulator program or adapter file.

The board configuration file either did not name it at all,

or the named file was not found or lacked read permission.

 

The features of this utility are explained in the

[-h] option's brief help and the documentation.

I've attached the .dat file for your review.  
I previously had similar problems on a windows machine which were resolved in the following thread:
If someone could walk me through the setup/troubleshooting of the xds100 emulator, it would be greatly appreciated.
Thanks, 
-Brant

 

 

# config version=3.5

$ sepk

  pod_drvr=jioserdesusb.so

  pod_port=0

$ /

$ product

  title="Texas Instruments XDS100 USB"

  alias=TI_XDS100v1_USB

  name=FTDI_FT2232

$ /

$ ftdi_ft2232

  usb_vid=0x0403

  usb_pid=0xa6d0

  gpio_l0="TRSTn,Active_Low"

  gpio_l1="EMU_Pin_Enable,Active_Low"

  gpio_l2="EMU_Pin_0,Active_Low"

  gpio_l3="EMU_Pin_1,Active_Low"

  gpio_h0="SRSTn,Active_High"

  gpio_h1="SRSTn_In,Active_Low"

  gpio_h2="Power_Loss_Detect,Active_Low"

  gpio_h3="Power_Loss_Reset,Active_High"

$ /

$ uscif

  tdoedge=FALL

  jtagboot_mode=disable

  jtagboot_value=hiz

  powerboot_mode=disable

  powerboot_value=hiz

  tclk_program=SPECIFIC

  tclk_frequency=1.0

$ /

@ icepick_d family=icepick_d irbits=6 drbits=1 subpaths=9

  & dap type=debug address=9 default=no custom=no force=yes pseudo=no

    @ cs_dap_debugss family=cs_dap irbits=4 drbits=1 identify=0

  & subpath_7 type=debug address=8 default=no custom=no force=yes pseudo=no

    @ c66xx_7 family=tms320c66xx irbits=38 drbits=1

  & subpath_6 type=debug address=7 default=no custom=no force=yes pseudo=no

    @ c66xx_6 family=tms320c66xx irbits=38 drbits=1

  & subpath_5 type=debug address=6 default=no custom=no force=yes pseudo=no

    @ c66xx_5 family=tms320c66xx irbits=38 drbits=1

  & subpath_4 type=debug address=5 default=no custom=no force=yes pseudo=no

    @ c66xx_4 family=tms320c66xx irbits=38 drbits=1

  & subpath_3 type=debug address=4 default=no custom=no force=yes pseudo=no

    @ c66xx_3 family=tms320c66xx irbits=38 drbits=1

  & subpath_2 type=debug address=3 default=no custom=no force=yes pseudo=no

    @ c66xx_2 family=tms320c66xx irbits=38 drbits=1

  & subpath_1 type=debug address=2 default=no custom=no force=yes pseudo=no

    @ c66xx_1 family=tms320c66xx irbits=38 drbits=1

  & subpath_0 type=debug address=1 default=no custom=no force=yes pseudo=no

    @ c66xx_0 family=tms320c66xx irbits=38 drbits=1

  & /

# /

  • What version of the CCS you have? Make sure you select the emulation XDS100v1.

     

    Thanks,

    Arun.

  • Arun,

    I've gone through his CCS setup on Windows, and it's all ok.  I don't have a linux platform to try this on.

    When a target configuration is launched, CCS creates a ccBoard0.dat file. The problem on Windows was that the directory that this was supposed to go into was write protected. Can you search and see where this file was created on your linux install?

    Dan

     

  • Hi Guys, 

       I ran a find -name *.dat from my CCS installation directory.  Here's the output at the terminal:

    ./ccsv5/ccs_base_5.0.3.00028/dvt/RTA6/solutions/sessions/default/log.dat

    ./ccsv5/ccs_base_5.0.3.00028/dvt/platform/UIA_Prototype/BinFileA/sessions/default/log.dat

    ./ccsv5/ccs_base_5.0.3.00028/dvt/Tutorial/DVT GenericTrace(DGT)/Session/test/input/fire_30frames_5_Mbps.dat

    ./ccsv5/ccs_base_5.0.3.00028/dvt/ImageAnalyzer/examples/bayer/bayer720480_10of16_image.dat

    ./ccsv5/ccs_base_5.0.3.00028/dvt/ImageAnalyzer/examples/bayer/bayer720480_8of16_image.dat

    ./ccsv5/ccs_base_5.0.3.00028/scripting/examples/TestServer/loadDataFromFile.dat

    ./ccsv5/ccs_base_5.0.3.00028/common/targetdb/connections/defaultProperties.dat

    ./ccsv5/ccs_base_5.0.3.00028/common/targetdb/boarddat/multi-icepick.dat

    ./ccsv5/ccs_base_5.0.3.00028/common/targetdb/cpus/defaultProperties.dat

    ./ccsv5/ccs_base_5.0.3.00028/common/targetdb/routers/defaultProperties.dat

    ./ccsv5/ccs_base_5.0.3.00028/common/uscif/4863.ccBoard0.dat

    The last iterm is the .dat file that Dan generated for me from his windows machine.  So, it does not look like CCS is generating a .dat file to use for the emulator. Any thoughts as to why are greatly appreciated. 
    Thanks, 
    -Brant

     

  • I have my ccboard0.dat file in my home/<username>/.TI/<some number>

     

    Try with sudo access. I was not able to open the ccs to begin with. Once I used sudo access to open the ccs, it worked.

     

    Thanks,

    Arun.