• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 1020 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.

Question about testing jpeg decoder on TCI6630K2L EVM

Xuantian Li
Prodigy 160 points
Other Parts Discussed in Thread: TCI6630K2L, TMS320C6678

HI,

I am new to DSP and trying to use the jpeg decoder on the TCI6630K2L platform which combines up to two ARM® CortexTM-A15 MPCoreTM processors with four cores of TI's TMS320C66x high performance DSP. I just downloaded the code from

software-dl.ti.com/.../index_FDS.html

1. I wondered whether I can use this code directly, because the user guide just said it validated on TMS320C6678 EVM. If I cannot use this code on my device, how can I find a jpeg decoder or encoder to execute on it?

2. Do I need to use the same versions of SYS/BIOS, Bios IPC, XDC Tools, XDAIS Tools and TI Framework Components (FC) as the user guide showing. Is it not work if I used higher versions of these tools?

3. Can I compiler this code on ccs6.1.2, or I have to execute this jpeg decoder on ccs5?

Thank you very much,

Sincerely,

Xuantian

 

  • 0
    TI__Guru** 116100 points

    1. I wondered whether I can use this code directly, because the user guide just said it validated on TMS320C6678 EVM. If I cannot use this code on my device, how can I find a jpeg decoder or encoder to execute on it?

    You can run this on K2L EVM too as it has C66xx core like C6678.


    2. Do I need to use the same versions of SYS/BIOS, Bios IPC, XDC Tools, XDAIS Tools and TI Framework Components (FC) as the user guide showing. Is it not work if I used higher versions of these tools?

    Yes, you can use higher version also.


    3. Can I compiler this code on ccs6.1.2, or I have to execute this jpeg decoder on ccs5?

    Yes, you can use either CCSv5 or later (CCSv6.1.2)
  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 160 points
    Thank you for you help
  • 0 in reply to Xuantian Li
    TI__Guru* 81335 points

    ,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com). Please read all the links below my signature.

    We will get back to you on the above query shortly. Thank you for your patience.

    Thank you.

    PS: We strongly recommend you to create new e2e thread for your queries instead of following up on an old/closed e2e thread, new threads gets more attention than old threads and can provide link of old threads or information on the new post for clarity and faster response.

  • 0 in reply to Raja
    Prodigy 160 points
    Hi Raja,

    Can I ask a following questions? I can build the project successfully, but when I run it on my k2l device. I cannot achieve any results, and I also didn't get the error, either. The statue of device was running. Do I need to change the .cmd file? Could you give me some suggestion specifically?
    Is there a big different between c6678 and k2l? Thanks,

    Sincerely,
    Xuantian
  • 0 in reply to Xuantian Li
    TI__Guru** 116100 points
    Dear Xuantian,

    Can I ask a following questions? I can build the project successfully, but when I run it on my k2l device. I cannot achieve any results, and I also didn't get the error, either. The statue of device was running. Do I need to change the .cmd file? Could you give me some suggestion specifically?
    Is there a big different between c6678 and k2l? Thanks,

    Your code is not stopping at "main()" ?
    Its running directly after load the code on DSP core ?
    If its seems to be need to modify the *.cmd file.

    Can you please attach your *.cmd file ?
  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 160 points

    Hi Titus,

    I didn't change the JPEGDecApp.cmd totally. It is the default *.cmd file. Is it appropriate for my k2l?

    Fullscreen JPEGDecApp.txt Download 
    /******************************************************************************
            TEXAS INSTRUMENTS INCORPORATED PROPRIETARY INFORMATION           
                                                                             
   Property of Texas Instruments  
   For  Unrestricted  Internal  Use  Only 
   Unauthorized reproduction and/or distribution is strictly prohibited.  
   This product  is  protected  under  copyright  law  and  trade  secret law 
   as an unpublished work.  

   Created 2011, (C) Copyright 2011 Texas Instruments.  All rights reserved.
                                                           
   Filename         : JPEGDecApp.cmd

   Description      : Common linker command file for the DSP software 
   
   Project          : TMS320C6678

*********************************************************************************/


-stack    0x2000     /* Primary stack size   */
/* -heap     0x1f0f000    Heap area size       */
-c                   /* Use C linking conventions: auto-init vars at runtime */

MEMORY
{
	/*Don't change the len beyond this value*/
    DSPDATA        org = 0x80000000  len= 0x4000000
}

SECTIONS
{  
  	.const:JPEGIDEC_TI_dSect >	MSMCSRAM 
  	
  	.text:JPEGIDEC_TI_cSect	 >	MSMCSRAM
  
    /*external memory space for jpeg decoder for i/o buffers*/
    .input_buffer    >  DSPDATA
    .display_buffer  >  DSPDATA
    .ref_buffer      >  DSPDATA
    
	.intDataMem	: 	 >  L2SRAM
	.extDataMem	: 	 >  DSPDATA
	
	.text :          >  MSMCSRAM
    

     
    .far :        >  L2SRAM
	.alignconst   > (MSMCSRAM align(20h))	

    .stack :      >  L2SRAM
    .sysmem :     >  L2SRAM
    .data :       >  L2SRAM
    .bss :        >  L2SRAM
    .cinit :      >  L2SRAM
    .cio :        >  MSMCSRAM
    .pinit :      >  L2SRAM
    .const :      >  MSMCSRAM
    .switch :     >  MSMCSRAM 
    .bios	:     >  L2SRAM 
}

    Could you tell me how I can use the Testparams.cfg and Testvecs.cfg. Which parts I should modify? Thanks for your patient.

    Sincerely,

    Xuantian

  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 160 points
    Hi Titus,

    When I debug the code after built it, the code can stop at main(). But when I load and run it on DSP core, the program cannot enter the main(), and the status of the core is always running. Could you tell me how to deal with it?

    Thanks,

    Xuantian