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/TMDSDOCK28035: TMDSDOCK28035

Part Number: TMDSDOCK28035
Other Parts Discussed in Thread: TMS320F28035, C2000WARE

Tool/software: Code Composer Studio

Hello TI people,
I am working on TMS320F28035 MCU. I am testing its max toggling freq. I have selected its internal oscillator and making it configuration to be 60 MHz system clock.
when i used RAM linker file, the toggle freq was 3.7MHz. when i used F28035 linker file (Flash one), the toggle freq was around 700KHz.
now i have 2 questions:
1- what is the relation between linker file and operating freq and how to overcome its effect?
2- max toggling Freq is 15MHz as stated in reference manual,  so why 3.7 MHz is achieved when using RAM Linker file?

Best regards
Hosam

  • Hi Hosam,

    Are you simply toggling a GPIO and measuring it's frequency?

    For #1, I think what you're experiencing is the difference between code running from RAM vs. Flash. When using the flash linker command file make sure you copy code to RAM, memcpy() function.

    For #2, how are you going about toggling the GPIO? Maybe there is some overhead? Also, remember that when toggling a GPIO you will experience half the actual frequency if probed using an oscilloscope. i.e. need cycles to toggle the GPIO on and cycles to toggle the GPIO off.

    Best,
    Kevin
  • Hi Kevin,
    Thanks for your response.
    — for toggling, am just using this line GpioDataRegs.GPBTOGGLE.bit.GPIO34 = 1;
    Inside endless loop. As u see no overhead cycles. Now u can eliminate this possibility. The question remains the toggle freq should be 60MHz as stated in data sheet but it is just 3.7MHz?!!!

    — I didn’t write any linker script, I just used Ti files.
    Even using flash file, it means the code will be uploaded for permanent use but when the MCU start working, it copies its code into RAM for execution. So In both cases the code will be executed from RAM.

    How can Ti fix this issue?

    Thanks
    Hosam
  • Hi Hosam,

    The MAX toggle frequency specification is 15 MHz, not 60 MHz:

    You may be witnessing a 3.7MHz frequency when probing the signal because of the clock cycles it takes to iterate through the for loop and execute the GpioDataRegs.GPBTOGGLE.bit.GPIO34 = 1 line of code again. This is creating some additional overhead.

    Are you using a C2000ware linker command file for flash? If so which one? I still imagine the Flash/RAM configuration is showing different results because of a copy to and run from RAM issue.

    Best,

    Kevin

  • Hi Kevin
    - for toggling freq is 15 as I stated in my first post not 60 in the second one. Sorry for the typo.

    - for linker files, yes am using c2000 ware whose name is F28035.cmd

    Btw when using another file, it gives “ this program is not fit memory region”
    Yes this error can be solved by altering linker file memory region but I don’t like playing with linkers.

    If u tested with better response using flash files, pls attach this file thanks Regards
    Hosam
  • Hi Kevin 
    Am waiting for your response thanks.

    best,
    Hosam

  • Hi Hosam,

    Sorry for the delay. Could you try adding the below line of code somewhere within Main()? I think the issue roots from code not running from RAM.

        // We must also copy required user interface functions to RAM. 
        MemCopy(&RamfuncsLoadStart, &RamfuncsLoadEnd, &RamfuncsRunStart);

    For some good information on Linker command files see this read: http://software-dl.ti.com/ccs/esd/documents/sdto_cgt_Linker-Command-File-Primer.html#introduction

    Best,

    Kevin

  • Hello, Kevin 
    Thanks for your response. The same issue remains. could u send the full simple code u testes with flash linker. 

    Regards 
    Hosam

  • Hi Hosam,

    I haven't tested or generated any code for this yet. I'll try to send something by the end of today.

    Best,
    Kevin
  • Hi Hosam,

    I was able to get the function copied/running from RAM, but I kept getting into an ILLEGAL_ISR. There must be something I'm missing too.

    You can use the attached files for guidance, but something is still missing (make .txt a .cmd file).

    2703.Example_2803xGpioToggle.c
    //###########################################################################
    //
    // FILE:    Example_2803xGpioSetup.c
    //
    // TITLE:   GPIO Toggle Test example
    //
    //! \addtogroup f2803x_example_list
    //! <h1>GPIO Toggle Test (gpio_toggle)</h1>
    //!
    //!  \note ALL OF THE I/O'S TOGGLE IN THIS PROGRAM.  MAKE SURE
    //!  THIS WILL NOT DAMAGE YOUR HARDWARE BEFORE RUNNING THIS
    //!  EXAMPLE.
    //!
    //!  Three different examples are included. Select the example
    //!  (data, set/clear or toggle) to execute before compiling using
    //!  the macros found at the top of the code.
    //!
    //!  Each example toggles all the GPIOs in a different way, the first
    //!  through writing values to the GPIO DATA registers, the second through
    //!  the SET/CLEAR registers and finally the last through the TOGGLE register
    //!
    //!  The pins can be observed using Oscilloscope.
    //
    //###########################################################################
    // $TI Release: F2803x Support Library v2.01.00.00 $
    // $Release Date: Thu Oct 18 15:46:42 CDT 2018 $
    // $Copyright:
    // Copyright (C) 2009-2018 Texas Instruments Incorporated - http://www.ti.com/
    //
    // Redistribution and use in source and binary forms, with or without 
    // modification, are permitted provided that the following conditions 
    // are met:
    // 
    //   Redistributions of source code must retain the above copyright 
    //   notice, this list of conditions and the following disclaimer.
    // 
    //   Redistributions in binary form must reproduce the above copyright
    //   notice, this list of conditions and the following disclaimer in the 
    //   documentation and/or other materials provided with the   
    //   distribution.
    // 
    //   Neither the name of Texas Instruments Incorporated nor the names of
    //   its contributors may be used to endorse or promote products derived
    //   from this software without specific prior written permission.
    // 
    // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
    // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
    // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 
    // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 
    // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
    // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
    // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 
    // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    // $
    //###########################################################################
    
    //
    // Included Files
    //
    #include "DSP28x_Project.h"     // Device Headerfile and Examples Include File
    
    #define FLASH 1
    
    extern Uint16 RamfuncsLoadStart;
    extern Uint16 RamfuncsLoadEnd;
    extern Uint16 RamfuncsRunStart;
    
    //
    // Function Prototype
    //
    void Gpio_select(void);
    void Example_MemCopy(Uint16 *SourceAddr, Uint16* SourceEndAddr, Uint16* DestAddr);
    void gpio_toggle(void);
    
    //
    // Main
    //
    void main(void)
    {
        //
        // Step 1. Initialize System Control:
        // PLL, WatchDog, enable Peripheral Clocks
        // This example function is found in the DSP2803x_SysCtrl.c file.
        //
        InitSysCtrl();
    
    #if FLASH
        // We must also copy required user interface functions to RAM.
        Example_MemCopy(&RamfuncsLoadStart, &RamfuncsLoadEnd, &RamfuncsRunStart);
    //    MemCopy(&RamfuncsLoadStart, &RamfuncsLoadEnd, &RamfuncsRunStart);
    #endif
    
        //
        // Step 2. Initialize GPIO:
        // This example function is found in the DSP2803x_Gpio.c file and
        // illustrates how to set the GPIO to it's default state.
        //
        // InitGpio();  // Skipped for this example
    
        //
        // For this example use the following configuration:
        //
        Gpio_select();
    
        //
        // Step 3. Clear all interrupts and initialize PIE vector table:
        // Disable CPU interrupts
        //
        DINT;
    
        //
        // Initialize PIE control registers to their default state.
        // The default state is all PIE interrupts disabled and flags
        // are cleared.
        // This function is found in the DSP2803x_PieCtrl.c file.
        //
        InitPieCtrl();
    
        //
        // Disable CPU interrupts and clear all CPU interrupt flags:
        //
        IER = 0x0000;
        IFR = 0x0000;
    
        //
        // Initialize the PIE vector table with pointers to the shell Interrupt
        // Service Routines (ISR).
        // This will populate the entire table, even if the interrupt
        // is not used in this example.  This is useful for debug purposes.
        // The shell ISR routines are found in DSP2803x_DefaultIsr.c.
        // This function is found in DSP2803x_PieVect.c.
        //
        InitPieVectTable();
    
        //
        // Step 4. Initialize all the Device Peripherals:
        // Not required for this example
        //
        
        //
        // Step 5. User specific code:
        //
    
        gpio_toggle();
    
    }
    
    //
    // Gpio_select - Sets the gpios functionality
    //
    void 
    Gpio_select(void)
    {
        EALLOW;
        GpioCtrlRegs.GPAMUX1.all = 0x00000000;  // All GPIO
        GpioCtrlRegs.GPAMUX2.all = 0x00000000;  // All GPIO
        GpioCtrlRegs.GPAMUX1.all = 0x00000000;  // All GPIO
        GpioCtrlRegs.GPADIR.all = 0xFFFFFFFF;   // All outputs
        GpioCtrlRegs.GPBDIR.all = 0xFFFFFFFF;   // All outputs
        EDIS;
    }
    
    #pragma CODE_SECTION(gpio_toggle, "ramfuncs");
    void gpio_toggle(void)
    {
        for(;;)
        {
            GpioDataRegs.GPBTOGGLE.bit.GPIO34 = 1;
        }
    }
    
    /*------------------------------------------------------------------
      Simple memory copy routine to move code out of flash into SARAM
    -----------------------------------------------------------------*/
    void Example_MemCopy(Uint16 *SourceAddr, Uint16* SourceEndAddr, Uint16* DestAddr)
    {
        while(SourceAddr < SourceEndAddr)
        {
           *DestAddr++ = *SourceAddr++;
        }
        return;
    }
    
    //
    // End of File
    //
    
    

    F28035 - Copy.txt
    /*
    // TI File $Revision: /main/4 $
    // Checkin $Date: November 9, 2009   15:09:12 $
    //###########################################################################
    //
    // FILE:	F2808.cmd
    //
    // TITLE:	Linker Command File For F2808 Device
    //
    //###########################################################################
    // $TI Release: F2803x Support Library v2.01.00.00 $
    // $Release Date: Thu Oct 18 15:46:42 CDT 2018 $
    // $Copyright:
    // Copyright (C) 2009-2018 Texas Instruments Incorporated - http://www.ti.com/
    //
    // Redistribution and use in source and binary forms, with or without 
    // modification, are permitted provided that the following conditions 
    // are met:
    // 
    //   Redistributions of source code must retain the above copyright 
    //   notice, this list of conditions and the following disclaimer.
    // 
    //   Redistributions in binary form must reproduce the above copyright
    //   notice, this list of conditions and the following disclaimer in the 
    //   documentation and/or other materials provided with the   
    //   distribution.
    // 
    //   Neither the name of Texas Instruments Incorporated nor the names of
    //   its contributors may be used to endorse or promote products derived
    //   from this software without specific prior written permission.
    // 
    // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 
    // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
    // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
    // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 
    // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 
    // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
    // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
    // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
    // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 
    // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    // $
    //###########################################################################
    */
    
    /* ======================================================
    // For Code Composer Studio V2.2 and later
    // ---------------------------------------
    // In addition to this memory linker command file,
    // add the header linker command file directly to the project.
    // The header linker command file is required to link the
    // peripheral structures to the proper locations within
    // the memory map.
    //
    // The header linker files are found in <base>\DSP2803x_Headers\cmd
    //
    // For BIOS applications add:      DSP2803x_Headers_BIOS.cmd
    // For nonBIOS applications add:   DSP2803x_Headers_nonBIOS.cmd
    ========================================================= */
    
    /* ======================================================
    // For Code Composer Studio prior to V2.2
    // --------------------------------------
    // 1) Use one of the following -l statements to include the
    // header linker command file in the project. The header linker
    // file is required to link the peripheral structures to the proper
    // locations within the memory map                                    */
    
    /* Uncomment this line to include file only for non-BIOS applications */
    /* -l DSP2803x_Headers_nonBIOS.cmd */
    
    /* Uncomment this line to include file only for BIOS applications */
    /* -l DSP2803x_Headers_BIOS.cmd */
    
    /* 2) In your project add the path to <base>\DSP2803x_headers\cmd to the
       library search path under project->build options, linker tab,
       library search path (-i).
    /*========================================================= */
    
    /* Define the memory block start/length for the F28035
       PAGE 0 will be used to organize program sections
       PAGE 1 will be used to organize data sections
    
       Notes:
             Memory blocks on F2803x are uniform (ie same
             physical memory) in both PAGE 0 and PAGE 1.
             That is the same memory region should not be
             defined for both PAGE 0 and PAGE 1.
             Doing so will result in corruption of program
             and/or data.
    
             L0 memory block is mirrored - that is
             it can be accessed in high memory or low memory.
             For simplicity only one instance is used in this
             linker file.
    
             Contiguous SARAM memory blocks or flash sectors can be
             be combined if required to create a larger memory block.
    */
    
    MEMORY
    {
    PAGE 0:    /* Program Memory */
               /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE1 for data allocation */
       RAML0       : origin = 0x008000, length = 0x000800     /* on-chip RAM block L0 */
       RAML1       : origin = 0x008800, length = 0x000400     /* on-chip RAM block L1 */
       OTP         : origin = 0x3D7800, length = 0x000400     /* on-chip OTP */
       FLASHH      : origin = 0x3E8000, length = 0x002000     /* on-chip FLASH */
       FLASHG      : origin = 0x3EA000, length = 0x002000     /* on-chip FLASH */
       FLASHF      : origin = 0x3EC000, length = 0x002000     /* on-chip FLASH */
       FLASHE      : origin = 0x3EE000, length = 0x002000     /* on-chip FLASH */
       FLASHD      : origin = 0x3F0000, length = 0x002000     /* on-chip FLASH */
       FLASHC      : origin = 0x3F2000, length = 0x002000     /* on-chip FLASH */
       FLASHA      : origin = 0x3F6000, length = 0x001F80     /* on-chip FLASH */
       CSM_RSVD    : origin = 0x3F7F80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
       BEGIN       : origin = 0x3F7FF6, length = 0x000002     /* Part of FLASHA.  Used for "boot to Flash" bootloader mode. */
       CSM_PWL_P0  : origin = 0x3F7FF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA */
    
       IQTABLES    : origin = 0x3FE000, length = 0x000B50     /* IQ Math Tables in Boot ROM */
       IQTABLES2   : origin = 0x3FEB50, length = 0x00008C     /* IQ Math Tables in Boot ROM */
       IQTABLES3   : origin = 0x3FEBDC, length = 0x0000AA	  /* IQ Math Tables in Boot ROM */
    
       ROM         : origin = 0x3FF27C, length = 0x000D44     /* Boot ROM */
       RESET       : origin = 0x3FFFC0, length = 0x000002     /* part of boot ROM  */
       VECTORS     : origin = 0x3FFFC2, length = 0x00003E     /* part of boot ROM  */
    
    PAGE 1 :   /* Data Memory */
               /* Memory (RAM/FLASH/OTP) blocks can be moved to PAGE0 for program allocation */
               /* Registers remain on PAGE1                                                  */
       BOOT_RSVD   : origin = 0x000000, length = 0x000050     /* Part of M0, BOOT rom will use this for stack */
       RAMM0       : origin = 0x000050, length = 0x0003B0     /* on-chip RAM block M0 */
       RAMM1       : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
       RAML2       : origin = 0x008C00, length = 0x000400     /* on-chip RAM block L2 */
       RAML3       : origin = 0x009000, length = 0x001000     /* on-chip RAM block L3 */
       FLASHB      : origin = 0x3F4000, length = 0x002000     /* on-chip FLASH */
    
    }
    
    /* Allocate sections to memory blocks.
       Note:
             codestart user defined section in DSP28_CodeStartBranch.asm used to redirect code
                       execution when booting to flash
             ramfuncs  user defined section to store functions that will be copied from Flash into RAM
    */
    
    SECTIONS
    {
    
       /* Allocate program areas: */
       .cinit              : > FLASHA      PAGE = 0
       .pinit              : > FLASHA,     PAGE = 0
       .text               : > FLASHA      PAGE = 0
       codestart           : > BEGIN       PAGE = 0
       /*ramfuncs            : LOAD = FLASHD, */
       ramfuncs            : LOAD = FLASHD,
                             /*RUN = RAML0,*/
                             RUN = RAML1,
                             LOAD_START(_RamfuncsLoadStart),
                             LOAD_SIZE(_RamfuncsLoadEnd),
                             RUN_START(_RamfuncsRunStart),
                             PAGE = 0
    
       csmpasswds          : > CSM_PWL_P0  PAGE = 0
       csm_rsvd            : > CSM_RSVD    PAGE = 0
    
       /* Allocate uninitalized data sections: */
       .stack              : > RAMM0       PAGE = 1
       .ebss               : > RAML2       PAGE = 1
       .esysmem            : > RAML2       PAGE = 1
    
       /* Initalized sections go in Flash */
       /* For SDFlash to program these, they must be allocated to page 0 */
       .econst             : > FLASHA      PAGE = 0
       .switch             : > FLASHA      PAGE = 0
    
       /* Allocate IQ math areas: */
       IQmath              : > FLASHA      PAGE = 0            /* Math Code */
       IQmathTables        : > IQTABLES,   PAGE = 0, TYPE = NOLOAD
    
      /* Uncomment the section below if calling the IQNexp() or IQexp()
          functions from the IQMath.lib library in order to utilize the
          relevant IQ Math table in Boot ROM (This saves space and Boot ROM
          is 1 wait-state). If this section is not uncommented, IQmathTables2
          will be loaded into other memory (SARAM, Flash, etc.) and will take
          up space, but 0 wait-state is possible.
       */
       /*
       IQmathTables2    : > IQTABLES2, PAGE = 0, TYPE = NOLOAD
       {
    
                  IQmath.lib<IQNexpTable.obj> (IQmathTablesRam)
    
       }
       */
        /* Uncomment the section below if calling the IQNasin() or IQasin()
           functions from the IQMath.lib library in order to utilize the
           relevant IQ Math table in Boot ROM (This saves space and Boot ROM
           is 1 wait-state). If this section is not uncommented, IQmathTables2
           will be loaded into other memory (SARAM, Flash, etc.) and will take
           up space, but 0 wait-state is possible.
        */
        /*
        IQmathTables3    : > IQTABLES3, PAGE = 0, TYPE = NOLOAD
        {
    
                   IQmath.lib<IQNasinTable.obj> (IQmathTablesRam)
    
        }
        */
    
       /* .reset is a standard section used by the compiler.  It contains the */
       /* the address of the start of _c_int00 for C Code.   /*
       /* When using the boot ROM this section and the CPU vector */
       /* table is not needed.  Thus the default type is set here to  */
       /* DSECT  */
       .reset              : > RESET,      PAGE = 0, TYPE = DSECT
       vectors             : > VECTORS     PAGE = 0, TYPE = DSECT
    
    }
    
    /*
    //===========================================================================
    // End of file.
    //===========================================================================
    */
    
    

    Reviewing this appnote may help find what's missing:

    http://www.ti.com/lit/spra958

    Best,

    Kevin