CCSv5 installation on TMS320C6657

When you click on "reply", you will see a link on the right bottom corner "use rich formatting". Click on that, then you will see the little paper clip icon to attach your screen shots.

Were you using the app center to install the new emulation? 

Danish

8475.install_logs.zip

Hi,

Something seems to be preventing the installer from writing a file. I'm unable to tell what that is. Could you please reboot the machine before doing the following:

Exit out of CCS completely

Start a cmd prompt as Admin

cd to the downloads folder

Run this command from the command prompt:

ti_emupack_setup_6.0.407.3_win_32.exe" arguments --mode unattended --ccs true  --prefix c:/ti/ccsv6 --eclipseprefix  C:/ti/ccsv6/eclipse         --enable-components c6000,arm,xds100,xds560

Please note, that's one command. Also, those are double dashes before mode, ccs, prefix, eclipseprefix and enable-components.

You also need to modify the ccsv6\eclipse\ccs_config.xml file to change all instances of "feature registered" to "feature installed"

Please let me know if you run into any problems.

Thanks

Danish

Peter Laurie said:

C66xx_0: File Loader: Data verification failed at address 0x00000020 Please verify target memory and memory map.

Valid memory regions for loading programs on a TMDSEVM6657LS are either:

- 1 Mbyte of Multicore Shared Memory (MSM) at addresses 0x0c000000 - 0x0c1fffff

- 512 Mbyte of  DDR3 at addresses 0x80000000 - 0x9fffffff

If you place the following in linker command file, e.g. named C6657.cmd, in the CCS project it will place the program in Multicore Shared Memory which should allow the program to load:

MEMORY
{
    SHRAM:          o = 0x0C000000 l = 0x00100000   /* 1MB Multicore shared Memmory */
}

SECTIONS
{
    .text          >  SHRAM
    .stack         >  SHRAM
    .bss           >  SHRAM
    .cio           >  SHRAM
    .const         >  SHRAM
    .data          >  SHRAM
    .switch        >  SHRAM
    .sysmem        >  SHRAM
    .far           >  SHRAM
    .args          >  SHRAM
    .ppinfo        >  SHRAM
    .ppdata        >  SHRAM

    /* COFF sections */
    .pinit         >  SHRAM
    .cinit         >  SHRAM

    /* EABI sections */
    .binit         >  SHRAM
    .init_array    >  SHRAM
    .neardata      >  SHRAM
    .fardata       >  SHRAM
    .rodata        >  SHRAM
    .c6xabi.exidx  >  SHRAM
    .c6xabi.extab  >  SHRAM
}

I based the above from the CCS 6.1.3 supplied C6678_unified.cmd example. Note:

1) I don't have a TMDSEVM6657LS, so haven't been able to actually test that the resulting program will run.

2) I used the Multicore Shared Memory (MSM), rather than the larger DDR3, since the MSM is on-chip and doesn't require any configuration. To load a program into DDR3 the DDR3 external memory interface must be configured, either a CCS GEL script or a bootloader on the C6657.

Peter Laurie said:

I say 'seems to' because I don't see where 'Hello world' has been printed to the screen

Some things which can cause the output of printf to not be displayed in CCS:

1) Insufficient heap space. E.g. Using a C66xx device with the Heap Size set to 0x100 bytes printf fails to display any output, but with the Heap Size set to 0x200 bytes printf displayed output in the CCS CIO console. The Heap Size is set in the CCS project properties CCS Build -> C6000 Linker -> Basic Options -> Heap Size for C/C++ dynamic memory allocation (--heap_size, -heap)

2) If CIO is not enabled in CCS. This is set in the CCS project properties Debug -> Program/Memory Load Options -> Enable CIO function use (requires setting a breakpoint). This should be enabled by default when a new project is created.

3) CIO is line buffered, so output is only displayed when there is a '\n' in the output.

See Tips for using printf and CIO System Call Protocol for more information on how CIO is used in the CCS debugger and run time library to handle printf and related functions.

Peter Laurie said:

In the meantime, I understand that the linker file I need is available in
ti_emupack_keystone1_setup_1.0.9.1
How should I run that?

Also, the contents of ti_emupack_keystone1_setup_1.0.9.1 didn't contain any extra files over-and-above a CCS 6.1.3 installation which already had Keystone1 1.0.10.0 com.ti.emulation.keystone1.win32.feature.group installed.

Peter Laurie said:

I have Stack set to 0x160

Running the call_graph utility, as described in Finding out static stack usage, reported that the "hello world" program using printf() requires 1480 bytes of stack. Note that I didn't attempt to remove all the warnings about indirect function calls, and so the worst case stack usage may be higher.

Therefore, suggest you increase the stack size.

With the stack size set to 1480 and the heap to 0x320 printf("Hello World!\n") produced output in the CCS CIO console.