• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 82 subscribers
  • Views 1530 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.

RTOS/TMS320F28335: How do I access GPIO using TIRTOS (SYSBIOS)?

Frank Pernice90
Prodigy 235 points

Part Number: TMS320F28335
Other Parts Discussed in Thread: C2000WARE,

Tool/software: TI-RTOS

I'm currently trying to learn how to use SYS/BIOS 6.70.00.21. 

I'd like to simply blink an LED or perform some other simple I/O operation. I cannot seem to figure out how to do so and I'd appreciate some help. In reading the user guide, section E1 mentions the "GIO Drivers" but indicates that they are deprecated. I do not see any sort of replacement mentioned in that guide. Should I be using a different version of TI-RTOS? I was told in another post that the C28335 does not have TI-RTOS and that SYS/BIOS is what I ought to be using (If I'm mistaken, please let me know). Thanks

  • 0
    TI__Guru 54445 points
    Hi Frank,

    You're correct that the TI-RTOS drivers are not supported for F28335. Instead you can use the F28335 code from C2000Ware in your SYS/BIOS projects to interact with the peripherals. You can use the C2000Ware examples to guide you through which files and include paths you need to add to your SYS/BIOS project to enable it to use the C2000Ware header files and then you can write to the GPIO registers like you normally would (e.g. GpioDataRegs.GPATOGGLE.bit.GPIO3 = 1).

    Whitney
  • 0 in reply to Whitney Dewey
    Prodigy 235 points

    Hi Whitney,

    In that case, might I direct you to my previous question?

    I thought I was on the right track by disregarding C2000Ware, but apparently I still need it. So Now I'm back at square one. 

    Perhaps you could then walk me through an example of setting up an LED to blink on a SYS/BIOS timer? 

  • 0 in reply to Frank Pernice90
    TI__Guru 54445 points
    Yes, you'll still need C2000Ware.

    I took a look at your other post and it looks like you had most of the pieces in your project already--your #include and linking paths looked good at least. I suspect that you'll want to use a flash cmd file instead of a RAM one so you'll have plenty of room for SYS/BIOS and hopefully that will clear up some of those linker errors. You'll also need to add the DSP2833x_GlobalVariableDefs.c file to your project and #include DSP28x_Project.h. Then you should be able to use GpioCtrlRegs and GpioDataRegs to get the GPIO registers configured.

    Please give it another try and let me know if you run into any more errors.

    processors.wiki.ti.com/.../BIOS_for_the_28x

    Whitney
  • 0 in reply to Whitney Dewey
    Prodigy 235 points

    Thanks for the response Whitney. I believe I've done all the above and I'm still having problems. See the log output below. I've also attached the project (C2000ware files are linked, so your paths may be different). I've used the attached linker command file (rather than the RAM linker command file I was using before). I renamed it as a text file so I could upload it here.

    Fullscreen F28335.cmd.txt Download 
    /*
// TI File $Revision: /main/10 $
// Checkin $Date: July 9, 2008   13:43:56 $
//###########################################################################
//
// FILE:	F28335.cmd
//
// TITLE:	Linker Command File For F28335 Device
//
//###########################################################################
// $TI Release: F2833x Support Library v2.00.00.00 $
// $Release Date: Sun Mar 25 13:25:02 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>\headers\cmd
//   
// For BIOS applications add:      DSP2833x_Headers_BIOS.cmd
// For nonBIOS applications add:   DSP2833x_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 DSP2833x_Headers_nonBIOS.cmd */

/* Uncomment this line to include file only for BIOS applications */
/* -l DSP2833x_Headers_BIOS.cmd */

/* 2) In your project add the path to <base>\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 F28335  
   PAGE 0 will be used to organize program sections
   PAGE 1 will be used to organize data sections

    Notes: 
          Memory blocks on F28335 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/L1/L2 and L3 memory blocks are mirrored - that is
          they can be accessed in high memory or low memory.
          For simplicity only one instance is used in this
          linker file. 
          
          Contiguous SARAM memory blocks can 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 */

   ZONE0       : origin = 0x004000, length = 0x001000     /* XINTF zone 0 */
   RAML0       : origin = 0x008000, length = 0x001000     /* on-chip RAM block L0 */
   RAML1       : origin = 0x009000, length = 0x001000     /* on-chip RAM block L1 */
   RAML2       : origin = 0x00A000, length = 0x001000     /* on-chip RAM block L2 */
   RAML3       : origin = 0x00B000, length = 0x001000     /* on-chip RAM block L3 */
   ZONE6       : origin = 0x0100000, length = 0x100000    /* XINTF zone 6 */ 
   ZONE7A      : origin = 0x0200000, length = 0x00FC00    /* XINTF zone 7 - program space */ 
   FLASHH      : origin = 0x300000, length = 0x008000     /* on-chip FLASH */
   FLASHG      : origin = 0x308000, length = 0x008000     /* on-chip FLASH */
   FLASHF      : origin = 0x310000, length = 0x008000     /* on-chip FLASH */
   FLASHE      : origin = 0x318000, length = 0x008000     /* on-chip FLASH */
   FLASHD      : origin = 0x320000, length = 0x008000     /* on-chip FLASH */
   FLASHC      : origin = 0x328000, length = 0x008000     /* on-chip FLASH */
   FLASHA      : origin = 0x338000, length = 0x007F80     /* on-chip FLASH */
   CSM_RSVD    : origin = 0x33FF80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
   BEGIN       : origin = 0x33FFF6, length = 0x000002     /* Part of FLASHA.  Used for "boot to Flash" bootloader mode. */
   CSM_PWL     : origin = 0x33FFF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA */
   OTP         : origin = 0x380400, length = 0x000400     /* on-chip OTP */
   ADC_CAL     : origin = 0x380080, length = 0x000009     /* ADC_cal function in Reserved memory */
   
   IQTABLES    : origin = 0x3FE000, length = 0x000b50     /* IQ Math Tables in Boot ROM */
   IQTABLES2   : origin = 0x3FEB50, length = 0x00008c     /* IQ Math Tables in Boot ROM */  
   FPUTABLES   : origin = 0x3FEBDC, length = 0x0006A0     /* FPU 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 */
   RAML4       : origin = 0x00C000, length = 0x001000     /* on-chip RAM block L1 */
   RAML5       : origin = 0x00D000, length = 0x001000     /* on-chip RAM block L1 */
   RAML6       : origin = 0x00E000, length = 0x001000     /* on-chip RAM block L1 */
   RAML7       : origin = 0x00F000, length = 0x001000     /* on-chip RAM block L1 */
   ZONE7B      : origin = 0x20FC00, length = 0x000400     /* XINTF zone 7 - data space */
   FLASHB      : origin = 0x330000, length = 0x008000     /* 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, 
                         RUN = RAML0, 
                         LOAD_START(_RamfuncsLoadStart),
                         LOAD_END(_RamfuncsLoadEnd),
                         RUN_START(_RamfuncsRunStart),
                         LOAD_SIZE(_RamfuncsLoadSize),
                         PAGE = 0

   csmpasswds          : > CSM_PWL     PAGE = 0
   csm_rsvd            : > CSM_RSVD    PAGE = 0
   
   /* Allocate uninitalized data sections: */
   .stack              : > RAMM1       PAGE = 1
   .ebss               : > RAML4       PAGE = 1
   .esysmem            : > RAMM1       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              : > FLASHC      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)
   
   }
   */
   
   FPUmathTables    : > FPUTABLES, PAGE = 0, TYPE = NOLOAD 
         
   /* Allocate DMA-accessible RAM sections: */
   DMARAML4         : > RAML4,     PAGE = 1
   DMARAML5         : > RAML5,     PAGE = 1
   DMARAML6         : > RAML6,     PAGE = 1
   DMARAML7         : > RAML7,     PAGE = 1
   
   /* Allocate 0x400 of XINTF Zone 7 to storing data */
   ZONE7DATA        : > ZONE7B,    PAGE = 1

   /* .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
   
   /* Allocate ADC_cal function (pre-programmed by factory into TI reserved memory) */
   .adc_cal     : load = ADC_CAL,   PAGE = 0, TYPE = NOLOAD

}

/*
//===========================================================================
// End of file.
//===========================================================================
*/
    many-hours.zip

    **** Build of configuration Debug for project many-hours ****

"C:\\ti\\ccsv8\\utils\\bin\\gmake" -k -j 8 all -O 
 
making ../src/sysbios/sysbios.a28FP ...
gmake[1]: Nothing to be done for 'all'.
Building file: "../main.c"
Invoking: C2000 Compiler
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/bin/cl2000" -v28 -ml -mt --float_support=fpu32 --include_path="C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/include" --include_path="C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/include" --include_path="C:/Users/fpernice/workspace_v8/many-hours" --include_path="C:/ti/bios_6_70_00_21/packages/ti/posix/ccs" --include_path="C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/include" -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="main.d_raw" --cmd_file="configPkg/compiler.opt" "../main.c"
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/include/DSP2833x_Device.h", line 123: warning #303-D: typedef name has already been declared (with same type)
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/include/DSP2833x_Device.h", line 124: warning #303-D: typedef name has already been declared (with same type)
Finished building: "../main.c"
 
Building file: "C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/source/DSP2833x_GlobalVariableDefs.c"
Invoking: C2000 Compiler
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/bin/cl2000" -v28 -ml -mt --float_support=fpu32 --include_path="C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/include" --include_path="C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/include" --include_path="C:/Users/fpernice/workspace_v8/many-hours" --include_path="C:/ti/bios_6_70_00_21/packages/ti/posix/ccs" --include_path="C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/include" -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="DSP2833x_GlobalVariableDefs.d_raw" --cmd_file="configPkg/compiler.opt" "C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/source/DSP2833x_GlobalVariableDefs.c"
Finished building: "C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/source/DSP2833x_GlobalVariableDefs.c"
 
making ../src/sysbios/sysbios.a28FP ...
gmake[2]: Nothing to be done for 'all'.
Building target: "many-hours.out"
Invoking: C2000 Linker
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/bin/cl2000" -v28 -ml -mt --float_support=fpu32 -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on -z -m"many-hours.map" --stack_size=0x300 --warn_sections -i"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/headers/cmd" -i"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/lib" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.1.LTS/include" --reread_libs --diag_wrap=off --display_error_number --xml_link_info="many-hours_linkInfo.xml" --entry_point=code_start --rom_model -o "many-hours.out" "./DSP2833x_ADC_cal.obj" "./DSP2833x_CodeStartBranch.obj" "./DSP2833x_GlobalVariableDefs.obj" "./DSP2833x_Gpio.obj" "./DSP2833x_SysCtrl.obj" "./DSP2833x_usDelay.obj" "./main.obj" "../TMS320F28335.cmd" -l"configPkg/linker.cmd" -lrts2800_fpu32.lib -lF28335.cmd -lDSP2833x_Headers_BIOS.cmd 
<Linking>
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 115: error #10264: FLASHH memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 116: error #10264: FLASHG memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 117: error #10264: FLASHF memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 118: error #10264: FLASHE memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 119: error #10264: FLASHD memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 120: error #10264: FLASHC memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 121: error #10264: FLASHA memory range overlaps existing memory range FLASH
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 122: error #10263: CSM_RSVD memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 122: error #10264: CSM_RSVD memory range overlaps existing memory range CSM_RSVD
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 123: error #10263: BEGIN memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 123: error #10264: BEGIN memory range overlaps existing memory range BEGIN
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 124: error #10263: CSM_PWL memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 124: error #10264: CSM_PWL memory range overlaps existing memory range CSM_PWL
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 125: error #10263: OTP memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 125: error #10264: OTP memory range overlaps existing memory range OTP
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 126: error #10263: ADC_CAL memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 126: error #10264: ADC_CAL memory range overlaps existing memory range ADC_CAL
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 128: error #10263: IQTABLES memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 128: error #10264: IQTABLES memory range overlaps existing memory range IQTABLES
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 129: error #10263: IQTABLES2 memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 129: error #10264: IQTABLES2 memory range overlaps existing memory range IQTABLES2
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 130: error #10263: FPUTABLES memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 130: error #10264: FPUTABLES memory range overlaps existing memory range FPUTABLES
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 131: error #10263: ROM memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 131: error #10264: ROM memory range overlaps existing memory range ROM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 132: error #10263: RESET memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 132: error #10264: RESET memory range overlaps existing memory range RESET
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 133: error #10263: VECTORS memory range has already been specified
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 133: error #10264: VECTORS memory range overlaps existing memory range VECTORS
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 139: error #10264: BOOT_RSVD memory range overlaps existing memory range M01SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 140: error #10264: RAMM0 memory range overlaps existing memory range M01SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 141: error #10264: RAMM1 memory range overlaps existing memory range M01SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 142: error #10264: RAML4 memory range overlaps existing memory range L07SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 143: error #10264: RAML5 memory range overlaps existing memory range L07SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 144: error #10264: RAML6 memory range overlaps existing memory range L07SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 145: error #10264: RAML7 memory range overlaps existing memory range L07SARAM
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 167: warning #10190-D: absolute symbol "_RamfuncsLoadStart" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 168: warning #10190-D: absolute symbol "_RamfuncsLoadEnd" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 169: warning #10190-D: absolute symbol "_RamfuncsRunStart" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 170: warning #10190-D: absolute symbol "_RamfuncsLoadSize" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 167: warning #10190-D: absolute symbol "_RamfuncsLoadStart" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 168: warning #10190-D: absolute symbol "_RamfuncsLoadEnd" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 169: warning #10190-D: absolute symbol "_RamfuncsRunStart" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 170: warning #10190-D: absolute symbol "_RamfuncsLoadSize" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 167: warning #10190-D: absolute symbol "_RamfuncsLoadStart" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 168: warning #10190-D: absolute symbol "_RamfuncsLoadEnd" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 169: warning #10190-D: absolute symbol "_RamfuncsRunStart" being redefined
"C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2833x/common/cmd/F28335.cmd", line 170: warning #10190-D: absolute symbol "_RamfuncsLoadSize" being redefined
warning #10063-D: entry-point symbol other than "_c_int00" specified:  "code_start"
error #10010: errors encountered during linking; "many-hours.out" not built
 
>> Compilation failure
makefile:149: recipe for target 'many-hours.out' failed
gmake[1]: *** [many-hours.out] Error 1
makefile:145: recipe for target 'all' failed
gmake: *** [all] Error 2

**** Build Finished ****

    I've also attached my linker and compiler search paths and my project structure thusfar. I basically made a new (typical) SYS/BIOS project, then tried to "copy" the 2833xGPIOSetup project. I had to start from scratch because I deleted my original project.

  • 0 in reply to Frank Pernice90
    TI__Guru 54445 points

    You have two conflicting linker command files, TMS320F28335.cmd and F28335.cmd,  which is why you're seeing the "memory range has already been specified" message. Remove the F28335.cmd one from your linking options.

    Whitney

  • 0 in reply to Whitney Dewey
    Prodigy 235 points
    Perfect, that seemed to have fixed it. I can reference GPIO peripherals with no issue now. Thanks