• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 18 subscribers
  • Views 2498 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

STM32CubeMX invalaid number of arguments

Márton Dankó

Hi,

I downloaded from the stm home page the cube mx and installed it, then I downloaded with it the stm cube for stm32f4 version 1.8.0. When I want to ad to the project the cubemx framework/system, I will get this in a command line:

STM32CubeMX Launcher V1.0.0.1
Copyright (C) 2015 ARM Ltd and ARM Germany GmbH. All rights reserved.

*** Error: invalid number of arguments
    Usage: CubeMxLauncher
           CubeMxLauncher Device_name UV_Project_file Device_Family_Pack_Path

CubeMXLauncher termiates with error code 3
Enter any key to close.


How can I solve it? Or why I get this error?

Note: at "Manage runtime environment" after pressing "OK" button, it will print a window, with a "notice" which say they will be generate a few file ect, I press there yes button after that, I get this error.

Parents
  • 0

    Thank you for bringing this problem to our attention.

    Do you have any space characters in your project or MDK-ARM installation path names?

    What is the version of MDK-ARM you are using? This issue should have been fixed in MDK 5.16a/uVision 5.16.1.0.

    If you still see the problem with uVision 5.16.1.0 we would need more information about your project setup.
    - MDK-Core installation directory
    - Pack Folder location
    - Device being selected
    - Project Folder location

    we will be assuming MDK-ARM 5.16a and Keil.STM32F4xx_DFP.2.6.0.pack are used.

    Best regards,

    Joachim

Reply
  • 0

    Thank you for bringing this problem to our attention.

    Do you have any space characters in your project or MDK-ARM installation path names?

    What is the version of MDK-ARM you are using? This issue should have been fixed in MDK 5.16a/uVision 5.16.1.0.

    If you still see the problem with uVision 5.16.1.0 we would need more information about your project setup.
    - MDK-Core installation directory
    - Pack Folder location
    - Device being selected
    - Project Folder location

    we will be assuming MDK-ARM 5.16a and Keil.STM32F4xx_DFP.2.6.0.pack are used.

    Best regards,

    Joachim

Children