Skip to main content
Marco Franco
Associate
March 16, 2018
Solved

CUBEMX 4.25 error with keil 5

  • March 16, 2018
  • 4 replies
  • 1318 views
Posted on March 16, 2018 at 09:07

I generated a project with cube mx version 4.25 and I have the attached error in

Keil Microvision 5.

The project is a simple example of STM32f091 (all default)

I get the same error in all the projects

Thanks for help
    This topic has been closed for replies.
    Best answer by Marco Franco
    Posted on April 13, 2018 at 10:33

    Keil solved the problem in version 5.25.

    Thanks

    4 replies

    Tilen MAJERLE
    ST Employee
    March 19, 2018
    Posted on March 19, 2018 at 11:30

    Hello

    mfranco

    ‌,

    This is not CubeMX error with export. You don't have DFP drivers for Keil to be able to work with STM32F0 family. On the window behind your message (referring to image), findSTMicroelectronics on left side and then on right one, install STM32F0 package.

    Best regards,

    Tilen

    Andrew Neil
    Super User
    March 19, 2018
    Posted on March 19, 2018 at 13:21

    If you use Alt+Print-Screen, it will just capture the current dialogue - rather than your entire screen.

    Attaching the screenshot is not so helpful - as we can't see it in context.

    Just paste it into the post - where we can see it:

    0690X0000060AAKQA2.png

    Did you not just try pressing the 'Install' button ?

    A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
    Marco Franco
    Associate
    March 21, 2018
    Posted on March 21, 2018 at 08:44

    Thanks

    Majerle.Tilen

    , DFP drivers are installed but every time I edit a project on cube mx I have to redo the procedure of selecting the micro asyou advises (not automatically). I have uninstalled and reinstalled both keil and cube and I have not solved the problem. I have performed a new installation of both in another pc and I always have the same error.

    Thanks for your help

    Marco Franco
    Marco FrancoAuthorBest answer
    Associate
    April 13, 2018
    Posted on April 13, 2018 at 10:33

    Keil solved the problem in version 5.25.

    Thanks