I am using the FreeRTOS port for the Renesas RX62N Microcontroller,
FreeRTOS V7.4.2
compiler = Renesas RX Family V.1.02.01.000
IDE = HEW4 V4.09.00.007
HW = Renesas Development Kit YRDKRX62N
I have built the Blinky project and I am getting the following errors.
Yes - the dependency scanner is eccentric. By default it ignores the preprocessor directives and tries to includes files from all the FreeRTOS ports. You can ignore these warnings (I think the documentation page for the official demo says as much) because they are not compile or linker errors - you should find the code compiles and links without any problems.
Also, if you dig deep enough into the IDE options you will find an option that requests the dependency scanner includes processing of the pre-processor directives, selecting that option makes it much quieter.
In your reply are you refering to when an #include is made within a #ifdef of #ifndef statement, i.e. as in portable.h
I have temporarily modified code so no header files are included in this way. However I still get the errors.
The first error (DC306), seems to be associated with the following lines in port.c
In future it would be helpful if you could post the error text, rather than just the error number, so I don’t have to look it up. In this case it appears to just be “syntax error”.
Can you post the definitions of configMAX_SYSCALL_INTERRUPT_PRIORITY and configKERNEL_INTERRUPT_PRIORITY. They should be in FreeRTOSConfig.h.
I am using the same compiler version. This is the output I get when I build the HEW project located in FreeRTOS/Demo/RX600_RX62N-RDK_Renesas (unmodified, so with the same configKERNEL_INTERRUPT_PRIORITY and configMAX_SYSCALL_INTERRUPT_PRIORITY settings as you:
The DC306 syntax error, is displayed for the “Blinky” build.
I think the output you have shown is for the “Debug” build, if possible can you try again using the “Blinky” build
Note: Blinky build also throws up a L3100 (F) Section address overflow out of range : “L” but this can be rectified by adding the “L” section using the RX standard toolchain.
Note: Blinky build also throws up a L3100 (F) Section address overflow out of range : “L” but this can be rectified by adding the “L” section using the RX standard toolchain.
Confirm I can replicate that, and fixed it by adding in the L* section. I then get:
Going to the options dialogue, standard library tab, standard library category, and selecting “match.h” in the category window (so the selections match those used by the debug build configuration) fixed that.
After that my output from the build is as per my previous post.