• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 22 subscribers
  • Views 1399 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM Libraries Documentation

Brian Ingwersen

Hi,

Before I go into my issues (which being an old hardware fart are many), let me confess that its been more then 10 years since I have had to play in the firmware park. I'm a hardcore hardware guy, but I have been put in the position of needing to write some firmware for one of my projects.

Now here's my problem (or issue).. I can't find any published information regarding the Keil implementation of the included libraries. Keil has lots of information about the compiler, linkers, and the such, but nothing about the libraries. I have been trolling the include files for the last two weeks just to get and idea of whats supported and how its called; now that's not a big deal, except it seems like the hard way of doing things. As Keil is a "professional" product I'm assuming that they have properly document libraries with specific implementation details; where are they?

As an example, fmod() in the Math libs., the definition in the Math.h file is perfect no problems, but why can't I find any information in the Keil documentation about this function? Am I missing something basic, or is Keils documentation of libraries really this poor?

Any help or insights from other users would be greatly appreciated.

Thanks
Brian Ingwersen

Parents
  • 0 in reply to Brian Ingwersen

    > what I really want them to publish is the impact that those
    > functions has on the systems environment.
    > [...]
    > In debugging an application its really important to know what
    > registers and resources a function touches.

    That is covered by another standard :-) On the infocenter, look for
    the AAPCS (ARM Architecture Procedure Call Standard). Among many other
    things, it defines the ways in which functions may use processor
    registers and stack. Somehow I've got the feeling that this doesn't
    make you any happier...

    Any description going into more detail would lock a vendor into never
    changing that function ever again since every change would break
    hundreds of applications relying on previous behavior.

    > I really need to quit being lazy and just deal with whats is
    > available or create my own functions.

    In most cases the former is probably your best option.

    Regards
    Marcus

Reply
  • 0 in reply to Brian Ingwersen

    > what I really want them to publish is the impact that those
    > functions has on the systems environment.
    > [...]
    > In debugging an application its really important to know what
    > registers and resources a function touches.

    That is covered by another standard :-) On the infocenter, look for
    the AAPCS (ARM Architecture Procedure Call Standard). Among many other
    things, it defines the ways in which functions may use processor
    registers and stack. Somehow I've got the feeling that this doesn't
    make you any happier...

    Any description going into more detail would lock a vendor into never
    changing that function ever again since every change would break
    hundreds of applications relying on previous behavior.

    > I really need to quit being lazy and just deal with whats is
    > available or create my own functions.

    In most cases the former is probably your best option.

    Regards
    Marcus

Children
No data