halherta wrote on Friday, June 08, 2012:
I recently purchased the RX62N version of the “Using the FreeRTOS Real Time Kernel - A Practical Guide” textbook and downloaded the book examples from the site. after unzipping the file I opened the workspace containing all the examples. When building any example I get the following output:
Phase RX C/C++ Compiler starting
C:\WorkSpace\source-code-for-RX62N-examples\Examples\Example001\main.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\demo_code\basic_io.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\demo_code\tick_timer_setup.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\list.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\portable\MemMang\heap_2.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\portable\Renesas\RX600\port.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\queue.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\tasks.c
C:\WorkSpace\source-code-for-RX62N-examples\RenesasCode\application_entry_and_vector_table.c
C:\WorkSpace\source-code-for-RX62N-examples\FreeRTOS_Source\portable\Renesas\RX600\port.c(255) : A2029 (E) Invalid description in #pragma inline_asm function
C:\WorkSpace\source-code-for-RX62N-examples\RenesasCode\lowsrc.c
C:\WorkSpace\source-code-for-RX62N-examples\RenesasCode\application_entry_and_vector_table.c(55) : C5167 (W) Argument of type "unsigned long" is incompatible with parameter of type "void *"
Phase RX C/C++ Compiler finished
Phase RX Assembler starting
C:\WorkSpace\source-code-for-RX62N-examples\RenesasCode\lowlvl.src
Phase RX Assembler finished
Phase OptLinker starting
Error accessing file: C:\WorkSpace\source-code-for-RX62N-examples\Examples\Example001\Debug\port.obj
Phase will not be executed
Phase OptLinker finished
Build Finished
2 Errors, 1 Warning
}
I’m using HEW Version 4.09.00.007 and the Renesas’s RX standard toolchain version 1.2.0.0.
I believe that the examples where built using RX toolchain version 1.0.1.0 and that perhaps something was change on the toolchain side. I was wondering if anyone here had experienced this problem before and if there is a possible solution.
Thank you
halherta