-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Update Renesas GCC compiler #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Dinh Van Nam <[email protected]>
* RX600v2 * RX600 * RX100 Signed-off-by: Dinh Van Nam <[email protected]>
|
Hello Dinh Van Nam, The configINCLUDE_PLATFORM_H_INSTEAD_OF_IODEFINE_H and R_BSP_SECNAME_INTVECTTBL were introduced by me when I ported Amazon FreeRTOS to RX MCU and CC-RX/GNURX. Now I think that the following is better for GNURX. Your proposal (i.e. Renesas RX FreeRTOS Package v10.0.3): port.c My proposal: portmacro.h (The following is picked up from [my RX700v3 DPFPU's portmacro.h which is being developed](url https://github.com/NoMaY-jp/FreeRTOS-Kernel/blob/b6bb3a60c1a2138193d2bc9f996c53f51b5d4be4/portable/GCC/RX700v3_DPFPU/portmacro.h).) port.c (The following is picked up from [my RX700v3 DPFPU's port.c which is being developed](url https://github.com/NoMaY-jp/FreeRTOS-Kernel/blob/b6bb3a60c1a2138193d2bc9f996c53f51b5d4be4/portable/GCC/RX700v3_DPFPU/port.c).) Best regards, |
|
Hello Dinh Van Nam, The following topic (both threads are the same topic) is not subject of your pull request, but I think that it is better for you to keep this topic in your mind if you don't know it. [Improper access to an on-chip peripheral register in Renesas RX port layer](url https://forums.freertos.org/t/improper-access-to-an-on-chip-peripheral-register-in-renesas-rx-port-layer/9851/) <-- in English [Question about FreeRTOS code](url https://japan.renesasrulz.com/cafe_rene/f/forum5/5878/freertos/) <-- Please note that original title and all contents are in Japanese Best regards, |
|
Hi NoMaY, Thank you so much for your proposal and your contribution on RX MCU. My team will consider your proposal in detail and resubmit pull request as soon as possible. Best regards, |
|
Hello @VanNamDinh We are in the process of reviewing this PR. Are you considering to resubmit this PR with the changes from NoMaY as proposed above ? |
|
@VanNamDinh Should the declaration above be guarded with |
|
Hello @ravibhagavandas,
Yes. As I wrote before, Dinh Van Nam's proposal is based on my work when I ported Amazon FreeRTOS to RX MCU and CC-RX/GNURX two years ago. At that time, I did not notice that configTICK_VECTOR is defined in FreeRTOSConfig.h of existing GNURX projects in FreeRTOS's zip file and FreeRTOS's repository though configTICK_VECTOR is not used in the GNURX port layers. Your comment makes me noticed that such thing just now. So, I have to say that it is mandatory (not enough 'better') to use configINCLUDE_PLATFORM_H_INSTEAD_OF_IODEFINE_H in the GNURX port layers. I'm sorry for my mistake. Best regards, |
|
Hello @ravibhagavandas, I have reported this problem to Renesas Electronics Corporation via Japanese user forum (in the following post) but Renesas Japan is in company's summer holidays this week. (I have no direct communication method with them and Dinh Van Nam.) (I'm sorry that all contents are in Japanese.) Best regards, |
|
The changes for this PR are merged in PR #135 . Please feel free to open a new PR if you have additional changes. |
Co-authored-by: Cobus van Eeden <[email protected]> Co-authored-by: Aniruddha Kanhere <[email protected]>
Description
Port for GCC RX Family (RX100, RX200, RX600 and RX600v2). This work with new FIT version from Renesas as well. The RX GCC of Amazon FreeRTOS has not been updated for a while so that GCC projects can't be built and run.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.