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

Using RTC in new MDK uVision5

Hello,
I'm trying use new uVision5 and i don't know where is pariphery library for RTC and how it use. Can anyone help me with this?

Thank You
Jan

Parents Reply Children
  • Why do you think that?

    "Without this files is unusable"

    Nonsense - a competent programmer could write it all from scratch from the Datasheet, These libraries are purely a convenience to save you the effort.

    " must download files from STM site "

    Exactly - they are provided as source; you can build them using whatever tools you like.

  • I don't have time for write over 10 000 rows for only initialize periphery. If i write all initialize functions for used periphery i have 160 years... Without support this libraries i go install older version where i can programming my own code 10 minutes after create new project and initialize all needed peripherials.
    This new solution is one step forward and two steps back :-(

  • This new solution is one step forward and two steps back :-(

    Why are you even looking at embedded? It is obvious that you are not capable of doing it.

  • 10000 lines and 160 years. I must be many times older than Merlin or Gandalf if we assume the code I have written have grown at only 62 lines/year. And I have programmed quite a number of chips without any manufacturer library to allow me to assign to lots and lots of structs and then call helper functions.

  • What do you mean, "new solution"?

    As far as the ST libraries are concerned, there is no difference - you get the source code from ST, and you include it in your project.

    Simples.

  • I know, that after version 4.12 was ST library diferent from definitions used in keil libraries. It could be in version 5 corrected, but ST libraries are not included in Keil as previously. I have worry, that downloaded ST library from their site will not be corrsepond as previously. In examples for LED "blinky" without RTOS is not included any STM library for driving GPIOs and initialize RCC. Because im saying "new soultion", there is used any other way for driving GPIOs. I think it is more difficult as before. I know, that project manager contains any features for initialize serial periphery. In this cause must contain all periphery as ST library. I mean, now are any periphery in project wizard and others periphery must be initialized from external ST library.

  • "after version 4.12 was ST library diferent from definitions used in keil libraries"

    And look at the trouble that caused!

    "It could be in version 5 corrected"

    I think it has been corrected - by keeping the silicon vendor's code separate from Keil's own stuff, there is no longer any risk of Keil's stuff getting clogged-up with out-of-date silicon vendor code.

    This seems like the most practical solution to me.

    Think about it: there are dozens (hundreds?) of silicon vendors, each with their own support libraries - it's impractical for a compiler vendor to try to keep up with all the different releases & revisions of all that 3rd-party stuff!

    Maybe this is the idea of the new "packs" approach - so that the silicon vendors can take ownership of the specific support for their particular product(s)...?