• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 3569 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Problem with calling functions from ROM

Roberts Trops
Prodigy 30 points

Hello.

I have writen small code but I am unable to perform function calls from ROM due to errors I get when attempting to compile the project.

I am using CCS 5.2.1 , Win 7 OS and stellaris launchpad with LM4F120H5QR MCU. 

This is what I am getting:

At the top of the main.c file I have included rom.h as it should be: #include "driverlib/rom.h" and in project properties added predefined symbol "TARGET_IS_BLIZZARD_RA1"

I have done so tried to include rom.h seperatly in project and tested other functions from driver libarary which work fine.

So I get linking error saying that compiler can't find ROM function declaration of the ROM_SysCtlClockSet function I use and if I add other ROM functions they do not work either.

I will appreciate any constructive advise.

  • 0
    Guru 117855 points

    Always a challenge when "constructive advice" specified...

    Don't know/use your CCS - but am hopeful this will assist...  (extract from our paid, IAR - especially note, "PART_LX4F...")   While rom.h does not specifically reference MCU by part number - suspect  "PART_" may be worthwhile addition...

  • 0 in reply to cb1_mobile
    Prodigy 30 points

    Thank you, but unfortunately adding this symbol did not help.  

    So the current predefined symbols in my project are these:

    Included library's :

  • 0
    Guru 92251 points

    Roberts Trops said:
    At the top of the main.c file I have included rom.h as it should be: #include "driverlib/rom.h" and in project properties added predefined symbol "TARGET_IS_BLIZZARD_RA1"

    That should be sufficient to define the macro ROM_SysCtlClockSet in driverlib/rom.h which calls the function in ROM.

    Roberts Trops said:
    So I get linking error saying that compiler can't find ROM function declaration of the ROM_SysCtlClockSet function I use and if I add other ROM functions they do not work either.

    The other indication of the problem is that the compiler is warning about ROM_SysCtlClockSet being a "function declared implicitly".
    Roberts Trops said:
    I will appreciate any constructive advise
    From the information posted so far I can't see what the problem is. In CCS can you perform "Rebuild project" and then post the complete build output, so can see the compiler and linker command lines.

     

  • 0
    Guru 47900 points

    These type issues always frustrate - appear to have no basis.  (we feel your pain)

    Being "out of my league" re: CCS - perhaps a general "attack" may yield benefit:

    a) Is this your own, custom project?  Most always - these are fraught w/peril - all too often cause this type issue.  If this is your case - suggest that you switch to one of the simpler, "ready-made" projects.  (ideally one which your preview reveals to include ROM calls)  Suggest this as these are exhaustively tested - and all "nooks/crannies" are usually covered by the factory.  Far safer! 

    b) When this "ready made" project compiles - then runs successfully - suggest that you "screen-cap" each/every of the critical set-up/config listings - especially those which involve your MCU, MCU Rev, and any/all references to driverlib and related.  Hundreds of posts - this/other forums - show that this method pays off.

    c) Your plight caused me to look @ my driverlib - and I note both rom.h and rom_map.h present w/in driverlib.  Have you checked to confirm that indeed these files are present - and that they are in "good shape?"  (we can open/read both via notepad)  Suppose that it is possible that rom.h has someway/somehow been "lost" or corrupted.  Check also for rom_map.h - I had never noted this file in the past - cannot swear that it's needed...

    d) Unless my (c) above proves "lucky guess" - hard to believe that "only" rom.h is mishandled.  Suspect that other files w/in driverlib may be similarly effected - and have just not "bubbled up" for you yet...

    Kindly try - report - I am betting this is "custom project" issue - and factory set-up clearly is far safer...

  • 0 in reply to cb1
    Prodigy 30 points

    Problem is solved!!!

    I was reading your comments and going through my project when it hit me. Why did I not think of this earlier? I checked if the rom.h file contains the definition of the target I am referring to and vuola. The reference to TARGET_IS_BLIZZARD_RA1 wasn't going anywhere because the rom.h file did not have definition for it. Apparently I have somehow downloaded outdated or modified version of StellarisWare examples which contain all the necessary project files but they are not all compatible with my target device. I downloaded up-to-date version of StellarisWare with the "right'' files then copied the contents of up-to-date rom.h file overwriting rom.h that I had in my project and done, no errors, everything runs fine. Just had to clear the head for one day to solve this mystery.

    Thank you everyone for helping me you gave me the idea to look in the right place. I really appreciate it. 

  • 0 in reply to Roberts Trops
    Guru 47900 points

    Glad you persisted - "got it!"  Always satisfying. 

    Surely "everyone" - and this reporter - thank you...

    Do note - my earlier report - which did not find MCU ID w/in, "rom.h" - but clearly, "TARGET_IS_BLIZZARD_RA1" resides there - your system - now!  Good job!