• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 961 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

STR71x.LIB

Simon Hodgson

I'm trying to develop and application that uses both the ARTX and the STR71x library.

I've added both to my project, when I run it, the program jumps from os_sys_init to SWIHandler in STR71x.s (which is undefined so it ends up in an endless loop)

I can change the options in STR71x.s to enable 'EIC' but when I do that the project won't build as I appear to be missing a load of xxxxxxxHandler functions.

I've added 71x_it.c to the project, but this doesn't seem to make any difference.

Maybe I've got the wrong version of a file somewhere, but I'm very confused, it seems very hard to get a simple program up and running!

Thanks for you help


Simon

Parents
  • 0 in reply to Keil Software Support Intl.

    Rienhard;
    We too are having problems integrating RTL into our project. We can run the Blinky example or we can can run the interrupt examples but we cannot run RTL with the interrupt routines. We have used the STR71x.s start-up or startup.s with results
    similar to Simon.

    Is there example code with RTL and interrupts?

    We link the STR71x.LIB files defined in the RV30\LIB\ST\STR71x folder. To quote the text, 'STR71xR.LIB: (Release Version) ST specific interrupt handling without debug variables. The Keil RTX does not work with ST interrupt handling, therefore, do not use this library with Keil RTX.
    This implies that we use the STR71x.lib files but does not state this directly.

    Is there a place or places in the manuals defining libs versus startup files such that we do not get the name space errors.

    As Rene writes, we are sure we are using the wrong mix of Libs and startup files or we are missing some other vector definition files but we are unable to determine our next attempts.

    Comparing code on the many different versions of startup leads us to believe we may be using the wrong files.

    Does the Ver 3.02 mentioned in other threads address these problems? Should we chuck the STR interrupt handler routines and attempt to roll our own?
    It appears our problems center around the SWI handler during initialization.
    Our most recent problems are the same endless loops of Simon's code during the call to os_sys_init (init). We never enter the init rountine, instead we branch to start of main.
    Any direction you can give us will be appreciated.

Reply
  • 0 in reply to Keil Software Support Intl.

    Rienhard;
    We too are having problems integrating RTL into our project. We can run the Blinky example or we can can run the interrupt examples but we cannot run RTL with the interrupt routines. We have used the STR71x.s start-up or startup.s with results
    similar to Simon.

    Is there example code with RTL and interrupts?

    We link the STR71x.LIB files defined in the RV30\LIB\ST\STR71x folder. To quote the text, 'STR71xR.LIB: (Release Version) ST specific interrupt handling without debug variables. The Keil RTX does not work with ST interrupt handling, therefore, do not use this library with Keil RTX.
    This implies that we use the STR71x.lib files but does not state this directly.

    Is there a place or places in the manuals defining libs versus startup files such that we do not get the name space errors.

    As Rene writes, we are sure we are using the wrong mix of Libs and startup files or we are missing some other vector definition files but we are unable to determine our next attempts.

    Comparing code on the many different versions of startup leads us to believe we may be using the wrong files.

    Does the Ver 3.02 mentioned in other threads address these problems? Should we chuck the STR interrupt handler routines and attempt to roll our own?
    It appears our problems center around the SWI handler during initialization.
    Our most recent problems are the same endless loops of Simon's code during the call to os_sys_init (init). We never enter the init rountine, instead we branch to start of main.
    Any direction you can give us will be appreciated.

Children
No data