Suspected Project Import Problem or Compiler problem

Sysprogs forums Forums VisualGDB Suspected Project Import Problem or Compiler problem

This topic contains 14 replies, has 2 voices, and was last updated by  Miao Mico 4 days, 18 hours ago.

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #23307

    Miao Mico
    Participant

    My project is based on Keil v5.

    I import it into vs&visual gdb , but it can’t compile succeed .

    But it can work via Keil compiler .

    VGDB will show this error .

    But i can use the vs->right-click menu->go to definition to find it .

    I am very confused , please .

     

    Attachments:
    You must be logged in to view attached files.
    #23310

    Miao Mico
    Participant

    ADD INFO.

    My project is based on Standard Peripherals Library.

     

    #23319

    support
    Keymaster

    Hi,

    Most likely, your project does not enable the CRYP module in the configuration file. Please try searching for CRYP (case-sensitive, whole word) in the ST peripheral library folders. Most likely you will find a definition #ifdef-ed with a macro like STM32_CRYP_ENABLED. Then check your configuration file (typically stm32_*_config.h in the project directory) for similar definitions and uncomment/add the definition enabling the CRYP module.

    #23322

    Miao Mico
    Participant

    But why keil can use the project correctly ?

    It won’t show error message like vs&vGDB .

    #23324

    support
    Keymaster

    Hi,

    Most likely the Keil project is using a different configuration file.

    If you have 2 similar projects and would like to compare them, please consider enabling the preprocessor output in VisualGDB (VS Project Properties -> C/C++ -> Outputs) and Keil. This will expand all #include<> directives and the preprocessor macros, so you should be able to see where are various macros/variables defined and why the corresponding definition was not included in the other project.

    #23332

    Miao Mico
    Participant

    I thought you said preprocesser was what VisualGDB Project Properties -> MSbuild setting -> Preprocessor Macros list.

    What Keil correspondes is Option -> C/C++ -> Proprocesser Symbol -> Define lists

    So , i think it should’t be that fault , the preprocessor .

    Because the VisualGDB project is inported from the keil .

    if the ViusualGDB is imported correctly ,it should be the same preprocesser list.

    And now it is the same .

    And i have tried what you said the last time.

    • This reply was modified 1 week, 1 day ago by  Miao Mico.
    • This reply was modified 1 week, 1 day ago by  Miao Mico.
    #23335

    support
    Keymaster

    Hi,

    Depending on the mode you used for importing the project, the preprocessor macros might not have been imported automatically.

    If you could attach your keil project file (no source files are necessary), the screenshots of all the steps of the VisualGDB import wizard and the macro name that is set in the Keil project and not automatically imported into VisualGDB, we should be able to tell what is going on and update our importer accordingly.

    #23381

    Miao Mico
    Participant

    I’m so sorry about that.

    I can’t understand what you mean .

    I think the mode i used for importing my project is Automatically import a project in a different format -> Import an existing Keil Project -> Build using : Keil ARM Compiler -> My-Project-File.

    Is it right ?

    If not , please tell me again .

    Thanks.

    About the Keil project file .

     

    And i can consider and can provide the Keil Project file via email .

    And you can provide your e-mail address ?

    • This reply was modified 1 week ago by  Miao Mico.
    Attachments:
    You must be logged in to view attached files.
    #23384

    Miao Mico
    Participant

    Add the Keil project screenshot .

    Attachments:
    You must be logged in to view attached files.
    #23390

    support
    Keymaster

    Hi,

    The importing settings look correct, so the macros should get imported properly. Please send your project file via our support form and we will check what is going on.

    #23436

    Miao Mico
    Participant

    I have send the Test.uvprojx to support .

    Thanks .

    Waiting for your good news .

    #23443

    support
    Keymaster

    Thanks for the project file. We have rechecked the import and the macros got imported properly. If you believe some specific macro is not being imported, please let us know and attach the relevant screenshots.

    Attachments:
    You must be logged in to view attached files.
    #23471

    Miao Mico
    Participant

    Check my question again , please .

    And you can change the direction of thinking .

    Where will cause my problem ?

    And i succeed once through an the old version of VisualGDB .

    i can‘t remember which version and how to config .

    And the project succeed is missing .

    So blue .

     

    And your compiler is ARMCC or ARMCLANG ?

    I think yours is gcc .

    If I am wrong, please forgive me .

     

    #23472

    support
    Keymaster

    Unfortunately we are still not sure what you meant. The logic for importing the macros is the same for both compilers.

    If you are still trying to solve the original problem with the CRYP definition, please check the  stm32_*_config.h file as suggested earlier. Depending on your project configuration, you may need to enable the CRYP module on the Keil Packages page of VisualGDB Project Properties (available in the Custom edition or higher).

    If this is not what you are looking for, please let us know exactly the problem you are trying to solve.

    #23473

    Miao Mico
    Participant

    Thanks !

    Let me comb train of thought .

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic.