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.

Help connecting to EVMK2H Development Board

Hello, I am having trouble connecting to the TI ARM+DSP processor on the EVMK2H board. I am using a XDS560v2 STM USB emulator. I am able to use the SD560v2Cnfg utility and it successfully is able to find a Emulator. I am trying to run the "platform_test_evmk2h" project. I have setup the Target Configuration and ran the Test Connection Toot. Here is its output:

Test_Connection.txt
[Start: Spectrum Digital XDS560V2 STM USB Emulator_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\JOE~1.LIN\AppData\Local\TEXASI~1\
    CCS\ti\0\1\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'sd560v2u.out'.
Loaded FPGA Image: C:\ti\ccsv6\ccs_base\common\uscif\dtc_top.jbc
The library build date was 'Jul 27 2016'.
The library build time was '17:21:41'.
The library package version is '6.0.407.3'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '6' (0x00000006).
The controller has an insertion length of '0' (0x00000000).
The cable+pod has a version number of '8' (0x00000008).
The cable+pod has a capability number of '7423' (0x00001cff).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the Nano-TBC VHDL.
The link is a 560-class second-generation-560 cable.
The software is configured for Nano-TBC VHDL features.
The controller will be software reset via its registers.
The controller has a logic ONE on its EMU[0] input pin.
The controller has a logic ONE on its EMU[1] input pin.
The controller will use falling-edge timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '2' (0x0002).
The utility logic has not previously detected a power-loss.
The utility logic is not currently detecting a power-loss.
Loaded FPGA Image: C:\ti\ccsv6\ccs_base\common\uscif\dtc_top.jbc

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

  Test  Size   Coord      MHz    Flag  Result       Description
  ~~~~  ~~~~  ~~~~~~~  ~~~~~~~~  ~~~~  ~~~~~~~~~~~  ~~~~~~~~~~~~~~~~~~~
    1   none  - 01 00  500.0kHz   -    similar      isit internal clock
    2   none  - 01 09  570.3kHz   -    similar      isit internal clock
    3     64  - 01 00  500.0kHz   O    good value   measure path length
    4     16  - 01 00  500.0kHz   O    good value   auto step initial
    5     16  - 01 0D  601.6kHz   O    good value   auto step delta
    6     16  - 01 1C  718.8kHz   O    good value   auto step delta
    7     16  - 01 2E  859.4kHz   O    good value   auto step delta
    8     16  + 00 02  1.031MHz   O    good value   auto step delta
    9     16  + 00 0F  1.234MHz   O    good value   auto step delta
   10     16  + 00 1F  1.484MHz   O    good value   auto step delta
   11     16  + 00 32  1.781MHz   O    good value   auto step delta
   12     16  + 01 04  2.125MHz   O    good value   auto step delta
   13     16  + 01 11  2.531MHz   O    good value   auto step delta
   14     16  + 01 21  3.031MHz   O    good value   auto step delta
   15     16  + 01 34  3.625MHz   O    good value   auto step delta
   16     16  + 02 05  4.313MHz   O    good value   auto step delta
   17     16  + 02 13  5.188MHz   O    good value   auto step delta
   18     16  + 02 23  6.188MHz   O    good value   auto step delta
   19     16  + 02 37  7.438MHz   O    good value   auto step delta
   20     16  + 03 07  8.875MHz   O    good value   auto step delta
   21     16  + 03 15  10.63MHz   O    good value   auto step delta
   22     16  + 03 1E  11.75MHz  {O}   good value   auto step delta
   23     64  + 02 3E  7.875MHz   O    good value   auto power initial
   24     64  + 03 0E  9.750MHz   O    good value   auto power delta
   25     64  + 03 16  10.75MHz   O    good value   auto power delta
   26     64  + 03 1A  11.25MHz   O    good value   auto power delta
   27     64  + 03 1C  11.50MHz   O    good value   auto power delta
   28     64  + 03 1D  11.63MHz   O    good value   auto power delta
   29     64  + 03 1D  11.63MHz   O    good value   auto power delta
   30     64  + 03 13  10.38MHz  {O}   good value   auto margin initial

The first internal/external clock test resuts are:
The expect frequency was 500000Hz.
The actual frequency was 499110Hz.
The delta frequency was 890Hz.

The second internal/external clock test resuts are:
The expect frequency was 570312Hz.
The actual frequency was 569214Hz.
The delta frequency was 1098Hz.

In the scan-path tests:
The test length was 2048 bits.
The JTAG IR length was 6 bits.
The JTAG DR length was 1 bits.

The IR/DR scan-path tests used 30 frequencies.
The IR/DR scan-path tests used 500.0kHz as the initial frequency.
The IR/DR scan-path tests used 11.75MHz as the highest frequency.
The IR/DR scan-path tests used 10.38MHz as the final frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

The frequency of the JTAG TCLKR input is measured as 10.37MHz.

The frequency of the JTAG TCLKR input and TCLKO output signals are similar.
The target system likely uses the TCLKO output from the emulator PLL.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Spectrum Digital XDS560V2 STM USB Emulator_0]

I have the boot DIP Setting to 0010.

When I try to run the platform_test_evmk2h project I get the following reset error message:

If I change the boot DIP setting to 0001 I don't get this error message, BUT the program hangs at line 1114 platform_init().

Here is my project zipped up:

platform_test_evmk2h.zip

I have left the DIP setting to 0010 and tried removing the XCS200 but I get the same runtime error message about the processor in reset. The LCD on the board does say that it completing booting.

I am using the gel file "xtcievmk2x.gel" one DSP core 0.

Any ideas?

Thanks,

Joe

  • Hi Joe,

    I've forwarded this to the debug experts. Their feedback should be posted here.

    BR
    Tsvetolin Shulev
  • Joe,

    Whenever you are loading code over the emulator, we recommend that you set the EVM in No boot/Sleep Boot mode. whe you set the EVM to any other boot mode for example UART/SPI/NAND boot, the BOOT ROM initializes the device clocks and PSC which will interfere with your setup. Also, note that the EVM ships with Linux boot images (u-boot, linux kernel and Filesystem flashed on the NAND) so when you set the DIP switch to NAND boot, the Linux boot images will boot up and may put the DSP core in reset.

    processors.wiki.ti.com/.../EVMK2H_Hardware_Setup

    One way to check for this is to connect to the SOC UART/ BMC UART(FTDI USB port on EVM) using a mini USB cable and check the logs observed on the UART terminal. On the Host you can setup a serial terminal like Hyperterminal or Terterm and set the baudrate to 115.2kbps. When you boot in No boot mode, you should see no logs on the SOC serial terminal

    Regards,
    Rahul

    PS: If you are using Rev4 EVM then check if the boot mode is being displayed on the LCD and BOOT SUCCESS message as there is a power management issue due to the UCD firmware that can be fixed by updating the firmware.
  • Hello and thanks for helping me. I changed the DIP to No Boot mode and when I run the platform_test the program hangs at the platform_init() function. Here is the error:

    Here is my gel file config:

    Here is the text while I switch to Debug mode:

    Switch_to_Debug.txt
    C66xx_0: GEL Output: 
    Connecting Target...
    C66xx_0: GEL Output: TCI6638K2K GEL file Ver is 1.60000002 
    C66xx_0: GEL Output: Detected PLL bypass disabled: SECCTL[BYPASS] = 0x00000000
    C66xx_0: GEL Output: (3a) PLLCTL = 0x00000040
    C66xx_0: GEL Output: (3b) PLLCTL = 0x00000040
    C66xx_0: GEL Output: (3c) Delay...
    C66xx_0: GEL Output: (4)PLLM[PLLM] = 0x0000000F
    C66xx_0: GEL Output: MAINPLLCTL0 = 0x05000000
    C66xx_0: GEL Output: (5) MAINPLLCTL0 = 0x07000000
    C66xx_0: GEL Output: (5) MAINPLLCTL1 = 0x00000040
    C66xx_0: GEL Output: (6) MAINPLLCTL0 = 0x07000000
    C66xx_0: GEL Output: (7) SECCTL = 0x00090000
    C66xx_0: GEL Output: (8a) Delay...
    C66xx_0: GEL Output: PLL1_DIV3 = 0x00008002
    C66xx_0: GEL Output: PLL1_DIV4 = 0x00008004
    C66xx_0: GEL Output: PLL1_DIV7 = 0x00000000
    C66xx_0: GEL Output: (8d/e) Delay...
    C66xx_0: GEL Output: (10) Delay...
    C66xx_0: GEL Output: (12) Delay...
    C66xx_0: GEL Output: (13) SECCTL = 0x00090000
    C66xx_0: GEL Output: (Delay...
    C66xx_0: GEL Output: (Delay...
    C66xx_0: GEL Output: (14) PLLCTL = 0x00000041
    C66xx_0: GEL Output: PLL has been configured (CLKIN * PLLM / PLLD / PLLOD = PLLOUT):
    C66xx_0: GEL Output: PLL has been configured (122.879997 MHz * 16 / 1 / 2 = 983.039978 MHz)
    C66xx_0: GEL Output: Power on all PSC modules and DSP domains... 
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=2, md=9!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=17, md=25!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=17, md=26!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=18, md=27!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=19, md=28!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=19, md=29!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=30!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=31!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=32!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=33!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=21, md=34!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=22, md=35!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=22, md=36!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=23, md=37!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=23, md=38!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=39!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=40!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=41!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=42!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=43!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=44!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=45!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=46!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=26, md=47!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=27, md=48!
    C66xx_0: GEL Output: Power on all PSC modules and DSP domains... Done.
    C66xx_0: GEL Output: WARNING: SYSCLK is the input to the PA PLL.
    C66xx_0: GEL Output: Completed PA PLL Setup
    C66xx_0: GEL Output: PAPLLCTL0 - before: 0x0x098804C0	 after: 0x0x09080500
    C66xx_0: GEL Output: PAPLLCTL1 - before: 0x0x00000040	 after: 0x0x00002040
    C66xx_0: GEL Output: DDR begin
    C66xx_0: GEL Output: XMC setup complete.
    C66xx_0: GEL Output: DDR3 PLL (PLL2) Setup ... 
    C66xx_0: GEL Output: DDR3 PLL Setup complete, DDR3A clock now running at 666 MHz.
    C66xx_0: GEL Output: DDR3A initialization complete 
    C66xx_0: GEL Output: DDR3 PLL Setup ... 
    C66xx_0: GEL Output: DDR3 PLL Setup complete, DDR3B clock now running at 800MHz.
    C66xx_0: GEL Output: DDR3B initialization complete 
    C66xx_0: GEL Output: DDR done
    

    I hope this helps.

    Thank you for taking the time to help me, I really appreciate it.

    Joe

  • Joe,

    Your GEL output looks fine now. You can ignore the PSC timeout errors as they seem to be occuring from modules that are not enabled on this chip. The code seems to be hanging in the Serdes intialization and I am not sure if there is some additional step needed to resolve this issue. Let me try to reproduce this and also loop in a colleague who is more familiar with the Serdes initialization.

    Regards,

    Rahul
  • Joe,

    When you had the build error in a previous post, I discussed with our development team. The platform_test is obsolete, sorry for this. The suggested board test is using the board diagnostic processors.wiki.ti.com/.../Processor_SDK_RTOS_DIAG
    For K2H device, it is POST processors.wiki.ti.com/.../Processor_SDK_RTOS_POST

    Can you try if POST works for you? See the post.c:

    init_flags.phy = 0;
    acc_fail = 0;

    Another way to use platform_test is to set init_flags.phy = 0 before calling platform_init() to bypassing this serdes issue.

    Regards, Eric
  • Eric,

    HI, just some following up messages. I changed the platform_test_input.txt file so that it only ran the only the following: init_pll, init_ddr, init_ecc. It took a few minutes to finally get into the debugger, there are a lot of GEL statements. But once I am in the debugger I can run the test. Just letting you know. Quick question about the Compiling the Diagnostic Applications. Here are the instructions:

    1. cd <PDK>/packages/ti/board/diag
    2.make <BOARD>

    What do I type in for the <BOARD> and do I need the "<" and ">" ?

    Thanks for all you help and suggestions.
    Joe
  • Joe,

    I mentioned for K2H it is POST: processors.wiki.ti.com/.../Processor_SDK_RTOS_POST this link has the info how to build. BTW, the pre-built binary is available: pdk_k2hk_4_0_3\packages\ti\boot\post\evmk2h\bin

    Regards, Eric
  • Eric,

    HI, I have having some trouble running make in the Diag directory. From the output of make I get an cannot find directory error message because it is looking for a "evmK2HG" subdirectory of c:\ti\pdk_k2hk_4_0_3\packages\ti\board\ which at that directory there is only two directories: evmK2H and evenK2K. Now I should mention that the makefile for the Diag has the instruction to use the board evmK2HG when running make, such as "gmake buildtarget evmK2HG" which is strange because I'm not using the evmK2HG. I showed this to my co-worker and he asked me to verify that I have the right pdk and then asked me to start over and remove the pdk and try again.

    Any ideas?

    Thanks,
    Joe
  • Joe,

    I tried to build it and no issue, seem my attached log file.

    post_build.txt
    C:\ti\pdk_k2hk_4_0_3\packages>pdksetupenv.bat
    Optional parameter not configured : CG_XML_BIN_INSTALL_PATH
    REQUIRED for xdc release build
    Example: set CG_XML_BIN_INSTALL_PATH=C:/ti/cg_xml/bin
    Optional parameter not configured : DOXYGEN_INSTALL_PATH
    REQUIRED for xdc release build
    Example: set DOXYGEN_INSTALL_PATH=C:/ti/Doxygen/doxygen/1.5.1-p1/bin
    **************************************************************************
    Environment Configuration:
        LIMIT_SOCS                : k2h k2k
        LIMIT_BOARDS              : evmK2H evmK2K
        PDK_INSTALL_PATH          : /ti/PDK_K2~4/packages/
        C6X_GEN_INSTALL_PATH      : C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.
    1.0
        TOOLCHAIN_PATH_A15        : C:/ti_6_1_3/ccsv6/tools/compiler/gcc-arm-none-ea
    bi-4_9-2015q3
        TOOLCHAIN_PATH_A8         : C:/ti_6_1_3/ccsv6/tools/compiler/gcc-arm-none-ea
    bi-4_9-2015q3
        TOOLCHAIN_PATH_A9         : C:/ti_6_1_3/ccsv6/tools/compiler/gcc-arm-none-ea
    bi-4_9-2015q3
        TOOLCHAIN_PATH_M4         : C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-arm_15.1
    2.1.LTS
        FPULIB_PATH               : C:/ti_6_1_3/ccsv6/tools/compiler/gcc-arm-none-ea
    bi-4_9-2015q3/lib/gcc/arm-none-eabi/4.9.3/fpu
        CROSS_TOOL_PRFX           : arm-none-eabi-
        XDC_INSTALL_PATH          : C:/ti/xdctools_3_32_00_06_core
        BIOS_INSTALL_PATH         : C:/ti/bios_6_45_01_29
        IPC_INSTALL_PATH          : C:/ti/ipc_3_43_02_04
        EDMA3LLD_BIOS6_INSTALLDIR : C:/ti/edma3_lld_2_12_01_25
        NDK_INSTALL_PATH          : C:/ti/ndk_2_24_03_35
        IMGLIB_INSTALL_PATH       : C:/ti/imglib_c66x_3_1_1_0
        UIA_INSTALL_PATH          : C:/ti/uia_2_00_03_43
    **************************************************************************
    Changing to short name to support directory names containing spaces
    current directory: /ti/PDK_K2~4/packages/
    PDK BUILD ENVIRONMENT CONFIGURED
    **************************************************************************
    
    C:\ti\PDK_K2~4\packages>cd ti
    
    C:\ti\PDK_K2~4\packages\ti>cd boot
    
    C:\ti\PDK_K2~4\packages\ti\boot>cd post
    
    C:\ti\PDK_K2~4\packages\ti\boot\post>dir
     Volume in drive C is OSDisk
     Volume Serial Number is C027-5E3C
    
     Directory of C:\ti\PDK_K2~4\packages\ti\boot\post
    
    10/28/2016  01:03 PM    <DIR>          .
    10/28/2016  01:03 PM    <DIR>          ..
    10/28/2016  01:10 PM    <DIR>          evmk2h
    10/28/2016  01:10 PM    <DIR>          include
    10/28/2016  01:10 PM    <DIR>          src
                   0 File(s)              0 bytes
                   5 Dir(s)  15,627,714,560 bytes free
    
    C:\ti\PDK_K2~4\packages\ti\boot\post>dir
     Volume in drive C is OSDisk
     Volume Serial Number is C027-5E3C
    
     Directory of C:\ti\PDK_K2~4\packages\ti\boot\post
    
    10/28/2016  01:03 PM    <DIR>          .
    10/28/2016  01:03 PM    <DIR>          ..
    10/28/2016  01:10 PM    <DIR>          evmk2h
    10/28/2016  01:10 PM    <DIR>          include
    10/28/2016  01:10 PM    <DIR>          src
                   0 File(s)              0 bytes
                   5 Dir(s)  15,627,599,872 bytes free
    
    C:\ti\PDK_K2~4\packages\ti\boot\post>cd evmk2h
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h>dir
     Volume in drive C is OSDisk
     Volume Serial Number is C027-5E3C
    
     Directory of C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h
    
    10/28/2016  01:10 PM    <DIR>          .
    10/28/2016  01:10 PM    <DIR>          ..
    10/28/2016  01:16 PM    <DIR>          bin
    10/28/2016  01:10 PM    <DIR>          build
    10/04/2016  02:07 PM                32 macros.ini
    10/04/2016  02:07 PM             2,990 post.cmd
                   2 File(s)          3,022 bytes
                   4 Dir(s)  15,627,599,872 bytes free
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h>cd build
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h\build>dir
     Volume in drive C is OSDisk
     Volume Serial Number is C027-5E3C
    
     Directory of C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h\build
    
    10/28/2016  01:10 PM    <DIR>          .
    10/28/2016  01:10 PM    <DIR>          ..
    10/04/2016  02:07 PM             3,703 makefile
    10/04/2016  02:07 PM               274 objects.mk
    10/04/2016  02:07 PM             1,837 sources.mk
    10/28/2016  01:10 PM    <DIR>          src
    10/04/2016  02:07 PM               283 subdir_rules.mk
    10/04/2016  02:07 PM               314 subdir_vars.mk
                   5 File(s)          6,411 bytes
                   3 Dir(s)  15,627,599,872 bytes free
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h\build>gmake all
    gmake: Nothing to be done for `all'.
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h\build>gmake clean
    rm -f  "../bin/post_evmk2h.out"
    rm -f "src/c6678.pp" "src/cpdma.pp" "src/gmacsl.pp" "src/pa.pp" "src/post.pp" "s
    rc/psc.pp" "src/qm.pp"
    rm -f "src/c6678.obj" "src/cpdma.obj" "src/gmacsl.obj" "src/pa.obj" "src/post.ob
    j" "src/psc.obj" "src/qm.obj"
    Finished clean
    
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h\build>gmake all
    Building file: ../../../post/src/c6678.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/c6678.pp" --obj_directory="src"  "../../../post/src/c6678.c"
    Finished building: ../../../post/src/c6678.c
    
    Building file: ../../../post/src/cpdma.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/cpdma.pp" --obj_directory="src"  "../../../post/src/cpdma.c"
    Finished building: ../../../post/src/cpdma.c
    
    Building file: ../../../post/src/gmacsl.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/gmacsl.pp" --obj_directory="src"  "../../../post/src/gmacsl.c"
    Finished building: ../../../post/src/gmacsl.c
    
    Building file: ../../../post/src/pa.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/pa.pp" --obj_directory="src"  "../../../post/src/pa.c"
    Finished building: ../../../post/src/pa.c
    
    Building file: ../../../post/src/post.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/post.pp" --obj_directory="src"  "../../../post/src/post.c"
    Finished building: ../../../post/src/post.c
    
    Building file: ../../../post/src/psc.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/psc.pp" --obj_directory="src"  "../../../post/src/psc.c"
    Finished building: ../../../post/src/psc.c
    
    Building file: ../../../post/src/qm.c
    Invoking: C6000 Compiler
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --include_path="C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include
    " --include_path="/ti/PDK_K2~4/packages//ti/platform" --include_path="/ti/PDK_K2
    ~4/packages//" --include_path="../../../post/include" --define=SOC_K2H --display
    _error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="sr
    c/qm.pp" --obj_directory="src"  "../../../post/src/qm.c"
    Finished building: ../../../post/src/qm.c
    
    Building target: ../bin/post_evmk2h.out
    Invoking: C6000 Linker
    "C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6600 --abi=eab
    i -g --define=SOC_K2H --display_error_number --diag_warning=225 -z -m"../bin/pos
    t_evmk2h.map" -i"C:/ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/lib" -i"C:/
    ti_6_1_3/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include" -i"/ti/PDK_K2~4/packag
    es//ti/platform/evmk2h/platform_lib/lib/debug" -i"/ti/PDK_K2~4/packages//ti/csl/
    lib/k2h/c66/release" --reread_libs --warn_sections --xml_link_info="../bin/post_
    evmk2h_linkInfo.xml" --rom_model -o "../bin/post_evmk2h.out" "./src/c6678.obj" "
    ./src/cpdma.obj" "./src/gmacsl.obj" "./src/pa.obj" "./src/post.obj" "./src/psc.o
    bj" "./src/qm.obj" "../post.cmd"  -l"ti.platform.evmk2h.lite.lib" -l"ti.csl.ae66
    " -l"libc.a"
    <Linking>
    Finished building target: ../bin/post_evmk2h.out
    
    
    C:\ti\PDK_K2~4\packages\ti\boot\post\evmk2h\build>
     

    Regards, Eric

  • Eric,

    HI, well I managed to get the pre-built binary file to load and run. It would be nice that there was an already generated project file that I could load like the platform_test_evmk2h. I didn't have the UART connected, but in CCS6 it showed that it executed the .out file and it exited successfully. Are there any other projects that I could load and run?

    Thanks,
    Joe
  • Joe,

    Sorry, there is no CCS project for this that you can load and build. The board diagnostics are all makefile based.

    Regards, Eric