Eclipse Community Forums: Newcomers » Problems tab disagreeing with Console tab

Help

Home

Home » Newcomers » Newcomers » Problems tab disagreeing with Console tab

Show: Today's Messages :: Show Polls :: Message Navigator

Problems tab disagreeing with Console tab [message #1577304]

Wed, 21 January 2015 20:40

Michael Brooks

Messages: 5
Registered: January 2015

Junior Member

I'm not sure whether this is an Eclipse issue or a CDT issue or a combination of both. Most likely it's a user issue. Wink

I have just built a project. The console output is very clean, as follows.

Quote:

20:56:16 **** Build of configuration Default for project STM32-H152_blink_RAM ****
make all
.compiling
arm-none-eabi-gcc -Wall -fno-common -c -g -mcpu=cortex-m3 -mthumb -g -O0 -I./ -I./lib/ -I./lib/inc/ -I./lib/inc/../../ -DTRACE_LEVEL=4 -o obj/main.o main.c
arm-none-eabi-gcc -Wall -fno-common -c -g -mcpu=cortex-m3 -mthumb -g -O0 -I./ -I./lib/ -I./lib/inc/ -I./lib/inc/../../ -DTRACE_LEVEL=4 -o obj/system_stm32f10x.o system_stm32f10x.c
arm-none-eabi-gcc -Wall -fno-common -c -g -mcpu=cortex-m3 -mthumb -g -O0 -I./ -I./lib/ -I./lib/inc/ -I./lib/inc/../../ -DTRACE_LEVEL=4 -o obj/stm32f10x_it.o stm32f10x_it.c
.compiling libraries
arm-none-eabi-gcc -Wall -fno-common -c -g -mcpu=cortex-m3 -mthumb -g -O0 -I./ -I./lib/ -I./lib/inc/ -I./lib/inc/../../ -DTRACE_LEVEL=4 -o obj/stm32f10x_gpio.o ./lib/src/stm32f10x_gpio.c
arm-none-eabi-gcc -Wall -fno-common -c -g -mcpu=cortex-m3 -mthumb -g -O0 -I./ -I./lib/ -I./lib/inc/ -I./lib/inc/../../ -DTRACE_LEVEL=4 -o obj/stm32f10x_rcc.o ./lib/src/stm32f10x_rcc.c
.assembling
arm-none-eabi-as -g -mapcs-32 -o obj/startup_stm32f10x_md.o ./lib/startup_stm32f10x_md.s
..linking
arm-none-eabi-ld -g -v -nostartfiles -Map ./main.map -T./lib/stm32_ram.ld -o ./main.out obj/main.o obj/system_stm32f10x.o obj/stm32f10x_gpio.o obj/stm32f10x_rcc.o obj/stm32f10x_it.o obj/startup_stm32f10x_md.o libgcc.a
GNU ld (GNU Binutils) 2.20.1.20100303
arm-none-eabi-objcopy -O binary ./main.out ./main.bin
...completed.

20:56:18 Build Finished (took 1s.797ms)

As you can see, it has completed the build and has produced a main.out file. But the Problems tab lists 24 errors. Actual errors; not warnings. See below.

Quote:

Description Resource Path Location Type
Type 'GPIO_Pin_12' could not be resolved main.c /STM32-H152_blink_RAM line 63 Semantic Error
Type 'GPIOC' could not be resolved main.c /STM32-H152_blink_RAM line 66 Semantic Error
Type 'GPIOC' could not be resolved main.c /STM32-H152_blink_RAM line 76 Semantic Error
Type 'GPIOC' could not be resolved main.c /STM32-H152_blink_RAM line 82 Semantic Error
Type 'RCC_APB2Periph_GPIOC' could not be resolved main.c /STM32-H152_blink_RAM line 60 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 93 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 353 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 354 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 355 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 356 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 357 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 358 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 359 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 360 Semantic Error
Type 'uint16_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 361 Semantic Error
Type 'uint32_t' could not be resolved main.c /STM32-H152_blink_RAM line 50 Semantic Error
Type 'uint32_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 364 Semantic Error
Type 'uint32_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 366 Semantic Error
Type 'uint8_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 353 Semantic Error
Type 'uint8_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 355 Semantic Error
Type 'uint8_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 362 Semantic Error
Type 'uint8_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 362 Semantic Error
Type 'uint8_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 365 Semantic Error
Type 'uint8_t' could not be resolved stm32f10x_gpio.h /STM32-H152_blink_RAM/lib/inc line 365 Semantic Error

How can this be? In all my decades as a software developer I have never encountered a situation whereby errors are reported but an object file is still generated. The only exception to that statement is in Visual Studio if Intellisense is out of sync with the compiler - in that case Intellisense will report errors but the compiler will happily build. Might something like that be happening here?

The thing that makes me doubt the above hypothesis is the fact that I have been unable to debug this .out file. I have seemingly managed to get it loaded into my development board via the hardware debugger and I can get GDB up and running in Eclipse and when I issue the GDB commands to list program source lines it responds correctly, but whenever I try to query what's happening in the running program it keeps saying that it lacks a symbol table. That leads me to suspect that the .out file is corrupt, which would hardly be surprising if it has been generated in spite of compiler errors.

Michael

Report message to a moderator

Re: Problems tab disagreeing with Console tab [message #1579282 is a reply to message #1577304]

Thu, 22 January 2015 22:38

Michael Brooks

Messages: 5
Registered: January 2015

Junior Member

I can't believe that there have been nearly 600 views of this issue and no one has any idea what is going on. Somebody surely must understand where the Problems tab gets its information from?

Report message to a moderator

Re: Problems tab disagreeing with Console tab [message #1580127 is a reply to message #1579282]

Fri, 23 January 2015 09:52

Tauno Voipio

Messages: 742
Registered: August 2014

Senior Member

Michael Brooks wrote on Fri, 23 January 2015 00:38

I can't believe that there have been nearly 600 views of this issue and no one has any idea what is going on. Somebody surely must understand where the Problems tab gets its information from?

A) This question applies better to the CDT forum.

B) You are making a cross-compilation. The compiler finds your toolkit, but the CDT indexer does not have a clue on what is going on.

Please open the project properties on C/C++ development, and correct the include file paths according to your toolset. You have to get rid of the native compiler includes and add the cross-compiler includes.

The procedure is described in the CDT documentation.

For more detailed instructions, information about your operating system and cross-compiler toolkit are needed.

--

Tauno Voipio

Report message to a moderator

Re: Problems tab disagreeing with Console tab [message #1586324 is a reply to message #1580127]

Mon, 26 January 2015 20:01

Michael Brooks

Messages: 5
Registered: January 2015

Junior Member

Thanks Tauno - that's exactly what I needed. The default include paths for the project were more or less correct but they were purely relative paths (contrary to the warning at the bottom of the edit dialog). I have prepended the appropriate variables to the paths and the GPIO types are now resolving. So basically this is just like when Visual Studio gets its Intellisense paths out of sync with the compiler's paths.

Regards,
Michael

Report message to a moderator

Re: Problems tab disagreeing with Console tab [message #1588222 is a reply to message #1580127]

Tue, 27 January 2015 20:35

Michael Brooks

Messages: 5
Registered: January 2015

Junior Member

Incidentally, when you say "the CDT documentation", what document are you referring to? I have browsed the page "cdt/documentation.php" on the eclipse website and none of the links there appear to be what I'm looking for - i.e. a reference document for the CDT. Instead I see articles, webinars, overviews, FAQs, etc. No straightforward "Eclipse CDT Reference", which strikes me as odd because it's what I would imagine most people would want to refer to first.
If there's a specific document that you think I should refer to I'd be grateful if you could point me in the right direction.

Cheers,
Michael

Report message to a moderator