• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 1040 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.

CCS/EK-TM4C123GXL: airmouse Example Code for Sensor Hub not compiling, airmouse.out not found

Kala Mccomb
Prodigy 100 points
Part Number: EK-TM4C123GXL

Tool/software: Code Composer Studio

Hey,

So I've just switched over to the Tiva C series TM4C123GXL, and I have made sure to update CCS to v7 and have the Sensor Hub BoosterPack, however when I tried to run the airmouse example code, I got an error message. (Image Attached below).

When I followed the setup steps, I did get LM Flash Programmer to run airmouse with little issue, but nothing is making it run from ccs, the version found in Resource Explorer.

I really just need to know that I can get ccs to debug a program with position control because I'm going to try to build a 2-wheeled balancing bot for a final project for school.

Thanks,

Kala

  • 0
    TI__Guru 72500 points

    Hi Kala,

    Welcome to the forum.

    Earlier in the console output, you will see the names of the functions that cannot be found. That may give a hint as to what libraries it could not find. I am guessing that your linker file search path may be pointing to a different version of TivaWare than the one you have installed. Open the build settings by right clicking on the "airmouse" project in the project explorer window and select "Show Build Settings...". Then expand the topics on the left:  Build->ARM Linker->File Search Path. Check the paths used for the three libraries. (use the little box with three dots to see the actual path) If they are incorrect, you can edit them, or add the correct path.

  • 0 in reply to Bob Crosby
    Prodigy 100 points

    Hey Bob,

    So I checked the File Search Path for the libraries and when I couldn't find any errors in the path I did uninstall ccs and all other support files and then reinstalled them. I checked the File Search again and they were at the same locations, I also check one of the other sensor examples, the light_isl29023 example and had no trouble running it, or checking the terminal outputs. I checked the File Search for its libraries and they had the same path, with the exception of usblib.lib which the light sensor doesn't include.

    Do you have any other ideas?

    Thanks for your help,

    Kala

  • 0 in reply to Kala Mccomb
    Guru 117855 points

    Feel your pain! Simple outsider - with an idea - which (often) has succeeded.

    We cannot tell if you have attempted to "Create your OWN Project."    Most always - when such is attempted - poster's arrive here - w/ failed results - very similar to yours!     Now you report success w/"light_isl29023" - which you note as an example.     Might that also be a, "Vendor Provided Project" - thus beyond (just) an example?

    Even though you've "checked various search paths" - the IDE is SO Complex - it is "difficult" (if not highly unlikely) to "Check everything."     And this is the value of ONLY employing a  'Vendor Provided Project' - where ALL of those arcane details - have been managed FOR YOU!

    I would suggest that you "Reconfirm that your "light_" project indeed still works - and then gradually - and systematically - paste in individual segments of the code from your "desired, Airmouse project."    Do this gradually (code segment by segment) - always checking to insure that dreaded "errors" - have not arrived.     (the justification for "gradually" is in keeping w/ "KISS" - small, measurable steps - FAR better "Test for Errors" - so that you may deal w/them  (Early/Immediately) while they are STILL SMALL!      (and far more manageable.)

    Bob noted his departure - I've attempted to provide a "successful path."     (I could "use" your "2 wheeled balancing bot - especially when "Pulled over.")     You might extend that bot's capability to, "Walking correctly -  along a straight line - too."     Bon chance...

  • 0 in reply to Kala Mccomb
    TI__Guru 72500 points
    Hi Kala,
    If you scroll back in the output, the linker should tell you the names of the unresolved symbols. From that we might be able to know which library they should be in.
  • 0 in reply to Bob Crosby
    Prodigy 100 points

    Hey Bob,

    It's been awhile, but I've been troubleshooting and taking the code apart and can give you more information. Also, I updated to ccs v8.

    So, I did what you asked and checked the debugger for which connection wasn't linking and found that it was the complementary filter, comp_dcm.c. I checked the other example, compdcm_mpu9150, that used this file and found it doesn't work either. I rebuilt compdcm_mpu9150, as it was simpler,  in a new ccs project, linking and copying all the files exactly, then I took out everything but the calls and put a main(void) with an infinite while loop.

    When I debugged just that, everything linked fine, including comp_dcm.c. I then started adding back the parts and found that, still with just main(void) while(1), the functions MPU9150AppErrorHandler, MPU9150AppI2CWait, and ConfigureUART would cause it to not build. Also ROM_ statements in it showed an error when I just grabbed comp_dcm.c and compiled it on it's own. I've attached a picture of the error log and, well everything when just debugging  compdcm_mpu9150 with just main(void) while(1).

    Thanks,

    Kala

    Also, sorry if I'm doing something dumb, I've mostly programmed the MSP430 in C and assembly. 

  • 0 in reply to Kala Mccomb
    TI__Guru*** 135355 points

    Hello Kala,

    Do you have the driverlib rom.h included in your project? That is needed to use the ROM TivaWare API's.

    #include "driverlib/rom.h"

  • 0 in reply to Ralph Jacobi
    TI__Guru 72500 points
    We have not heard back from you so I assume Ralph's last response helped you resolve your problem. If not, please reply or start a new thread.
  • 0 in reply to Bob Crosby
    Prodigy 100 points

    Hello Bob,

    Sorry, I had actually been composing a reply and log but I got slammed with work and it slipped my mind,

    The solution wasn't a missing rom.h file, as it was directly an example, though myself and a few others working with the Tiva C have found that deleting ROM_ from certain older codes has run the code. It turned out that what I missed was recompiling the libraries. What I had to do was import the library files into CCS and build them, This updated the compiler and then I could link to the updated version in my work space. 

    I honestly missed that step somewhere and hadn't used example code before to know. 

    I thank everyone that gave me someone to talk to while working on it though,

    Kala