• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 21 subscribers
  • Views 1610 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

MDK 5.01 does not support ST.NXP peripherals lib

nini nini

MDK 5 have a big problem and bug that you can not use ST,NXP or non-KEIL peripheral drivers for cortex M devices,or if you do not use keil soft packs for using non-Keil drivers then you can not work with keil middlewares ,because they are dependent on keil drivers and driver layer is not independent.

I think these modification must be done in future:

- allows us to use user selected driver(Keil or ST or custom driver)
- middle wares should have a driver api functions that make them independent from other parts and can work with keil or ST or ... driver

- we can add ST driver lib as a software pack to keil.

I hope keil understand user needs and do it in future,Our codes for STM32 are dependent on ST peripheral driver and ST lib is very perfect and professional.but keil drivers for STM32 are not perfect and complete and keil must use vendors provided drivers because vendor drivers are better and perfect , keil have no time to write huge number of drivers for many cortex m devices.

Parents
  • 0 in reply to A K

    Hi

    I am also using STM32Fx products. The software packs are a step forward in making it easier for programmers looking forward - positive. uVision 5 is good as far I am concerned.

    The problems with ARM MDK5 for users are:
    1 The majority of the example programs are still in uVision 4 and are not utilizing software packs.
    2 A vendor knows its peripherals the best and therefore programmers will prefer using its peripheral firmware - hopefully all CMSIS compliant.
    3 It is clear that many programmers at this stage are struggling with the uVision 5 and vendor peripheral specific firmware integration in a project. In a RTX project the problem seems to be worse. Try retargetting for an example. Went through documentation, examples (all MDK 4 and lower and there is the problem) File dependencies seems to be problematic - can you clear this up?

    I hope that somebody at KEIL is reading this:

    Please supply documented simple example projects to your customers addressing the problems stated above. The current example projects for MDK 5 does not address these problems.

    Please include examples for RTOS and non RTOS applications.

    Using printf for debugging purposes (retargetting)is an easy way for debugging and should be covered in the examples please (STM32FxDISCOVERY boards?).

    I see I am not alone in this. If there are documentation in MDK 5 context available which I am not aware off, can somebody please point me to the solution. Looking forward to the solution.

    Thanks

    Matze

Reply
  • 0 in reply to A K

    Hi

    I am also using STM32Fx products. The software packs are a step forward in making it easier for programmers looking forward - positive. uVision 5 is good as far I am concerned.

    The problems with ARM MDK5 for users are:
    1 The majority of the example programs are still in uVision 4 and are not utilizing software packs.
    2 A vendor knows its peripherals the best and therefore programmers will prefer using its peripheral firmware - hopefully all CMSIS compliant.
    3 It is clear that many programmers at this stage are struggling with the uVision 5 and vendor peripheral specific firmware integration in a project. In a RTX project the problem seems to be worse. Try retargetting for an example. Went through documentation, examples (all MDK 4 and lower and there is the problem) File dependencies seems to be problematic - can you clear this up?

    I hope that somebody at KEIL is reading this:

    Please supply documented simple example projects to your customers addressing the problems stated above. The current example projects for MDK 5 does not address these problems.

    Please include examples for RTOS and non RTOS applications.

    Using printf for debugging purposes (retargetting)is an easy way for debugging and should be covered in the examples please (STM32FxDISCOVERY boards?).

    I see I am not alone in this. If there are documentation in MDK 5 context available which I am not aware off, can somebody please point me to the solution. Looking forward to the solution.

    Thanks

    Matze

Children
No data