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.

CCS/TMS320F28335: TMS320F28335

Part Number: TMS320F28335
Other Parts Discussed in Thread: SFRA, CONTROLSUITE

Tool/software: Code Composer Studio

Hello

what is the approach for testing ccs code in offline (without connected to power)? I have a matlab background, especially in simulink, it is possible to observe output on the scope at an interesting point. 

so how can i test the ccs code of my control if it fits my objective before connected to the sensor and driver circuit?  thanks 

  • Hi,

    Here is a E2E thread on the usage of external mode feature in Matlab:
    e2e.ti.com/.../769087

    Regards,
    Veena
  • I have connected the ADC to sensor OUT put. how ever the variabls in the expression ware still not vary. Is the follwing warnings be the cause? some of the memeory error were solved as follwing your direction in the previous. however, the below could not fix.


    PAGE 1 :
    /* BOOT_RSVD is used by the boot ROM for stack. */
    /* This section is only reserved to keep the BOOT ROM from */
    /* corrupting this area during the debug process */

    BOOT_RSVD : origin = 0x000002, length = 0x00004E /* Part of M0, BOOT rom will use this for stack */
    RAMM1 : origin = 0x000400, length = 0x000400 /* on-chip RAM block M1 */
    RAML4 : origin = 0x00C000, length = 0x001000
    RAML5 : origin = 0x00D000, length = 0x001000
    RAML6 : origin = 0x00E000, length = 0x001000
    RAML7 : origin = 0x00F000, length = 0x001000
    ZONE7B : origin = 0x20FC00, length = 0x001000 /*0x20FC00 0XINTF zone 7 - data space */
    }



    SECTIONS
    {
    . . .
    codestart : > BEGIN, PAGE = 0


    #ifdef __TI_COMPILER_VERSION__
    #if __TI_COMPILER_VERSION__ >= 15009000
    .TI.ramfunc : {} > RAML0, PAGE = 0
    #else
    ramfuncs : > RAML0, PAGE = 0
    #endif
    #endif

    .cntlcoeff : > RAML6, PAGE = 1
    .cntlar : > RAML7, PAGE = 1
    .SFRA_F_Data : > RAML7, PAGE = 1
    . . .
    }
    .

    warning
    warning #10247-D: creating output section "PartIdRegsFile" without a SECTIONS specification
    warning #10247-D: creating output section "ramfuncs" without a SECTIONS specification
    warning #10247-D: creating output section "cntlcoeff " without a SECTIONS specification
    warning #10247-D: creating output section "cntlar" without a SECTIONS specification
    warning #10247-D: creating output section "SFRA_F_Data" without a SECTIONS specification
    warning #10063-D: entry-point symbol other than "_c_int00" specified: "code_start"



    how can i fix these warng? would apprciate some guide for this problem. thank you
  • Hi,

    Please update your linker command file to include the sections mentioned in the warnings. I see sections .cntlcoeff, .cntlar present in the cmd file file. Probably, in your source code where you define those sections, "." may not be present. Please keep the names consistent in both yor source code and linker command file.

    Regards,
    Veena
  • Yes , you are right, I do not use dot '.' in pragma section. i define as follows:

    // FILTER EXTRACTION
    #pragma DATA_SECTION(cntl2p2z_BPFICF_vars,"cntlar")
    #pragma DATA_SECTION(cntl2p2z_BPFICF_coeff,"cntlcoeff")
    CNTL_2P2Z_F_VARS cntl2p2z_BPFICF_vars;
    CNTL_2P2Z_F_COEFFS cntl2p2z_BPFICF_coeff;



    one thing i want to tell you that i use

    '28335_RAM_lnk.cmd' file in the project folder

    in c2000 linker -> file serch path
    C:\ti\controlSUITE\..\DSP2833x_Headers_nonBIOS.cmd



    project -> linker command file : 28335_RAM_lnk.cmd

    Is these two files should be the same i.e. either '28335_RAM_lnk.cmd' or 'DSP2833x_Headers_nonBIOS.cmd'?


    and finally I tried to add dot '.' in my code as shown below
    ...
    #pragma DATA_SECTION(cntl2p2z_BPFICF_vars,".cntlar")
    ...


    but nothing was changed . I tried to search how to 'update linker command file to include the sections ' Could you tell me the steps please. thanks
  • Hi,

    The cmd files '28335_RAM_lnk.cmd' or 'DSP2833x_Headers_nonBIOS.cmd' are different and both must be included in your project. DSP2833x_Headers_nonBIOS.cmd is used by the the header files which defines the register structs and we not expect any update to this file by users. 28335_RAM_lnk.cmd is more like a sample linker command file that can be modified as per application need.

    After updating the section name to .cntlar, do you still get the warning "creating output section "cntlar" without a SECTIONS specification"?? That is weird. Can you check if the the build has picked that change? You could also do Rebuild project

    Regards,
    Veena