[Miao Mico]

I think i find the problem .

The STDPeriph Lib’s .h files are not been included .

And i checked the keil project file and the imported MCU.xml .

The VGDB imported correctly .

But Keil can find the .h along the tree included .

 

Attachments:

You must be logged in to view attached files.

[Miao Mico]

Thanks !

Let me comb train of thought .

[Miao Mico]

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 .

 

[Miao Mico]

I have send the Test.uvprojx to support .

Thanks .

Waiting for your good news .

[Miao Mico]

Add the Keil project screenshot .

Attachments:

You must be logged in to view attached files.

[Miao Mico]

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 6 years, 3 months ago by Miao Mico.

Attachments:

You must be logged in to view attached files.

[Miao Mico]

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 6 years, 3 months ago by Miao Mico.
• This reply was modified 6 years, 3 months ago by Miao Mico.

[Miao Mico]

But why keil can use the project correctly ?

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

[Miao Mico]

ADD INFO.

My project is based on Standard Peripherals Library.

 

[Miao Mico]

https://visualgdb.com/tutorials/arm/attach/

 

I find the SVD file you reffered ,and i can’t find cases about CFSR in that file.

AND i find the compiler you choose is ARM-EABI,not ARMCC ,in the above web page .

THEN i think the solution the above web page refered may not fit to me .

HOW CAN I DO ?

Thank you in advance .

• This reply was modified 6 years, 4 months ago by Miao Mico.

Attachments:

You must be logged in to view attached files.

[Miao Mico]

AND

How to add the up to data ARMCLANG compiler (v6.11) downloaded via ARM official website into VISUAL GDB while the KEIL ARMCLANG vision is v6.10.1 ?

CAN THE VISUAL GDB  SUPPORT THE UP TO DATA COMPILER NOW?

 

According to the STEP to reproduce that phenomenon Preprocesser Macros add ‘$$com.sysprogs.bspoptions.primary.memorys$$_layout;’  .

You know the STM32CubeMX ?

I use it to generate the keil project .

Whether function i choose to enable,changes the setting on STM32CubeMX ,the Keil project it generates will cause the problem,when i import it into Visual GDB .

 

You can try it . If the conditions differ from mine, i will send the whole file about the project .

Attachments:

You must be logged in to view attached files.

[Miao Mico]

but why i can’t find the CFSR via the Hardware Registers ?

My chip is STM32F407ZG.

Any Visual Gdb settings not correct?

By the way , my setting is default.

Attachments:

You must be logged in to view attached files.

[Miao Mico]

ADD INFO.

 

It can’t work via DEBUG : Program and Start Without Debuging .

BUT can work via DEBUG : Start Debugging With Gdb .

 

I will try what you just directed.

[Miao Mico]

 

THE SECOND QUESTION.

 

This may be a silly question,too.

 

I can’t load the programs compiled by KEIL ARMCLANG(V6.10.1) via VS2017 DEBUG mode CORRECTLY .

AND the KEIL ARMCC is work perfectly.

I got this conclusion from my discovery board not working, while my program focus it float shine.

BUT the GDBSever show it load success.

I feel very confused about this.

I think the code should be no problem, because the Initialize GPIO part code is generated by STM32CUBEMX5.0 .

 

FOR THIS.

I want to know the difference between RELEASE MODE and DEBUG MODE .

Is it just differ from Optimization Grades?

Want to understand how it works,please.

• This reply was modified 6 years, 4 months ago by Miao Mico.

[Miao Mico]

AND I want to know how to ENABLE the Regular VC ++ IntelliSence as default.i can’t use the clang very well.

I am so sorry about this.

[Author]

Posts