ROM_SysCtlDelay declared implicitly/unresolved symbol

ROM_Jamie

I decided I would modify the blinky project (dk-tm4c129x) because I'll likely want to make some LED error codes in the future. Blinky uses the LEDs differently than I am used to, avoiding calls to ROM_SysCtlPeripheralEnable, ROM_GPIOPinTypeGPIOOutput, GPIOPinWrite and ROM_SysCtlDelay.

I decided as practice I would try to transform blinky to use these as opposed to writing directly as it was.

Unfortunately I've been held up immediately and I can't figure out why I'm getting this unresolved symbol error.

My first change was to replace the for loops with ROM_SysCtlDelay's.

#include <stdint.h>
#include "driverlib/rom.h"
#include "inc/tm4c129xnczad.h"

//*****************************************************************************
//
//! \addtogroup example_list
//! <h1>Blinky (blinky)</h1>
//!
//! A very simple example that blinks the on-board LED.
//
//*****************************************************************************

//*****************************************************************************
//
// Blink the on-board LED.
//
//*****************************************************************************
int
main(void)
{
    volatile uint32_t ui32Loop;

    //
    // Enable the GPIO port that is used for the on-board LED.
    //
    SYSCTL_RCGCGPIO_R = SYSCTL_RCGCGPIO_R14;

    //
    // Do a dummy read to insert a few cycles after enabling the peripheral.
    //
    ui32Loop = SYSCTL_RCGCGPIO_R;

    //
    // Enable the GPIO pin for the LED (PQ7).  Set the direction as output, and
    // enable the GPIO pin for digital function.
    //
    GPIO_PORTQ_DIR_R = 0x80;
    GPIO_PORTQ_DEN_R = 0x80;

    //
    // Loop forever.
    //
    while(1)
    {
        //
        // Turn on the LED.
        //
        GPIO_PORTQ_DATA_R |= 0x80;

        //
        // Delay for a bit.
        //
        //for(ui32Loop = 0; ui32Loop < 200000; ui32Loop++)
       // {
       // }
        ROM_SysCtlDelay(200000);

        //
        // Turn off the LED.
        //
        GPIO_PORTQ_DATA_R &= ~(0x80);

        //
        // Delay for a bit.
        //
        for(ui32Loop = 0; ui32Loop < 200000; ui32Loop++)
        {
        }
    }
}

If I click f3 on "driverlib/rom.h" it takes me to the header, searching the header I'm able to find ROM_SysCtlDelay which should be defined if TARGET_IS_TM4C129_RA1 (which is defined in my compile time flags)

This one just doesn't make any sense to me. Any ideas?

over 11 years ago

0 Randy Ott over 11 years ago

Intellectual 750 points

You need to include driverlib.lib in the linker options area for the project properties.

Randy Ott

0 ROM_Jamie over 11 years ago in reply to Randy Ott

Intellectual 810 points

Good thought. I included the driverlib.lib. Unfortunately it hasn't solved the problem.

0 Randy Ott over 11 years ago in reply to ROM_Jamie

Intellectual 750 points

Did you include the complete path to the library?

"${SW_ROOT}/driverlib/ccs/Debug/driverlib.lib"

Also, a project rebuild might be required.

Randy Ott

0 ROM_Jamie over 11 years ago in reply to Randy Ott

Intellectual 810 points

I tried including the path as you wrote above, I also tried browsing to the driverlib.lib file to make sure it was getting the right path. Am I adding it in the wrong place? I've put it under

Properties -> CCS Build -> ARM Linker -> File Search Path -> Include library file or command file as input

Rebuild didn't help.

0 Randy Ott over 11 years ago in reply to ROM_Jamie

Intellectual 750 points

That's where it goes.

I might suggest that you add #include "driverlib/rom_map.h" to your source file and call "MAP_SysCtlDelay()" instead of the "ROM_" version. See if this resolves the link.

Randy Ott

0 ROM_Jamie over 11 years ago in reply to Randy Ott

Intellectual 810 points

To cloud this issue more. I re-imported the blinky project, added my blinky.c changes and was able to compile the project without issue. I didn't even include the driverlib.lib file. Chalk up another bizarre error in CCS on Ubuntu.

Thanks for your help anyway, Randy.

0 INTEGRIS Dexter over 11 years ago in reply to ROM_Jamie

Intellectual 905 points

Blinky is designed and intended as a starting point for those that DO NOT want to use the TivaWare functions calls (including the ROM calls). Particularly prior to TivaWare DriverLib being BSD licensed this was a bigger issue.

If you want to use the TivaWare API's the best bet is to start with any other project. "hello" is usually a good one as it is very simple and minimal.

0 ROM_Jamie over 11 years ago in reply to INTEGRIS Dexter

Intellectual 810 points

Dexter, the point of the exercise was to get practice with both forms of writing. I wanted to make sure I understood both well enough that I could replace the direct writes with function calls. My next undertaking will be to find a project where I will replace the function calls with direct writes.

In any case I now have code written to use the LED whichever way makes sense in my projects.

Arm-based microcontrollers

Arm-based microcontrollers forum

ROM_SysCtlDelay declared implicitly/unresolved symbol