• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 3150 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/TM4C129ENCPDT: Type #10247-D creating output section ".vtable" without a SECTIONS specification

M Syd Ahmed
Expert 1035 points
Part Number: TM4C129ENCPDT

Tool/software: TI-RTOS

Hello friends,

 I downloaded IR Remote code from , I made some changes for working in Tiva ware, Here is my project zip file 4682.uartecho_EK_TM4C129EXL_TI_TivaTM4C129ENCPDT.zip  

 When I try to build this code it make a warning as

           Type #10247-D creating output section ".vtable" without a SECTIONS specification   

 Can anyone help me to get off this warning

  • 0
    TI__Guru**** 190806 points
    Hi,

    What the linker warning is saying is that the section .vtable is being created but the linker command file does not have a SECTIONS specification to tell it where to allocate it. So the first thing is to check your .cmd file to see if the .vtable is properly allocated. Note that the .cmd file name in TivaWare is of the format "<example>_ccs.cmd". Since you are porting the project from LM to TM4C, this could be the area to first investigate. If you go to CCS Resource Explorer there are various TI-RTOS based TM4C examples you can import for reference on the .cmd file. TivaWare package also has various non RTOS based examples. I will like to suggest when possible it would be easier to use an existing project from the TivaWare build and add or remove files as needed. This would have the project environment setup as needed by the different libraries.
  • 0 in reply to Charles Tsai
    Expert 1035 points
    Hello Tsai,
    here are the things I did,

    1. Import uartecho project from resource explorer.
    2.removed uartecho.c file and added remote.c, remote.h, irdemo.c files from given zip file.
    3. added #include "utils/uartstdio.c" and changed uartstdioinit to uartstidoconfig.

    Still am getting error
  • 0 in reply to M Syd Ahmed
    Guru 117855 points
    You first noted a "warning" - now you report an "error!"

    Usually code will run w/"warnings" - and your ability to troubleshoot is greatly aided w/such capability... (i.e. you may compartmentalize your code - test/verify by code block - and this may enable you to "clear" the warning...)
  • 0 in reply to cb1_mobile
    Expert 1035 points
    Sorry, its an warning only. but code was not running it gets exiting even without reaching main().
  • 0 in reply to cb1_mobile
    Expert 1035 points
    Am thinking there is something which is undefined or something leading to this warning. But I dont know which is missing. Am a newbie to RTOS. I have attached my project zip file in post. If possible, can you go through the project and point me the mistake.
  • 0
    Expert 1035 points

    uartecho_EK_TM4C129EXL_TI_TivaTM4C129ENCPDT.rar

    My updated project zip file. Still warning is there.

  • 0 in reply to M Syd Ahmed
    TI__Guru**** 190806 points
    Hi,
    When you compile just the uartecho did you get any warning? I import the uartecho from CCS7.1 resource explorer and do not see any warnings. I'm having some problem to even compile your project at the moment.
  • 0 in reply to Charles Tsai
    TI__Guru 72500 points

    The section .vtable is for a copy of the vector table that is used by the driver library functions in interrupt.c. This table needs to be in RAM. Since it is not used in the uartecho project you started with, it is not in the EK_TM4C1294XL.cmd file.  Just adding a line to the sections part of the link command file will get rid of the warning and properly place the .vtable section in RAM.

    SECTIONS
{
    .text   :   > FLASH
    .const  :   > FLASH
    .cinit  :   > FLASH
    .pinit  :   > FLASH
    .init_array : > FLASH

    .data   :   > SRAM
    .bss    :   > SRAM
    .sysmem :   > SRAM
    .stack  :   > SRAM
    .vtable :   > SRAM
}

    I noticed some other things that need attention. In IR_Demo.c, lines 100-101 the code specifies a 16MHz crystal. The EK_TM4C1294XL uses a 25MHz crystal. Also in the file remote.c on line 59 you call the function SysCtlClockGet(); This function is for the TM4C123 and not valid for the TM4C1294 device. You can hard code this based on your operating frequency or use the value returned when you initialize the system clock.

    Other than the .vtable section, your problems are that the IR demo was written for a TM4C123 device and you need to be careful of the clock settings to change it to the TM4C1294.

  • 0 in reply to Bob Crosby
    Expert 1035 points
    We removed interrupt function and replace it with gpio interrupt. now its working fine, will get back any other error occur. thanks for the help.