Sign Up to our social questions and Answers Engine to ask questions, answer people's questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people's questions & connect with other people.
Volt.Tech
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using Renesas RX66T on a e2studio Version: 2022-04 (22.4.0) with CC-RX compiler. Is there a way to reserve a certain area of the ROM so that the linker does not insert any variables to the addresses in the range?
I am using Renesas RX66T on a e2studio Version: 2022-04 (22.4.0) with CC-RX compiler.
Is there a way to reserve a certain area of the ROM so that the linker does not insert any variables to the addresses in the range?
Read lessI am using FreeRTOS on the RA6M2, and what I need is a fairly accurate detention that works in the range of 1- 64 forevers. The software detention is way out in this range( 60us software detention turned out to be 84us), indeed when using critical task section and disabling irqs.I have tried rather using a tackle timekeeper like belowThis will not be veritably accurate but I was hoping the outflow would be small enough that I could ignore it. still, when I try this, the do while noway exits. ...Read more
I am using FreeRTOS on the RA6M2, and what I need is a fairly accurate detention that works in the range of 1- 64 forevers. The software detention is way out in this range( 60us software detention turned out to be 84us), indeed when using critical task section and disabling irqs.
I have tried rather using a tackle timekeeper like below
This will not be veritably accurate but I was hoping the outflow would be small enough that I could ignore it. still, when I try this, the do while noway exits. For some reason the timekeeper counter keeps resetting indeed though this is a one shot timekeeper. Can someone tell me where I am going wrong with this? I am using the configurator in the e2Studio IDE to set up the timekeeper.
Any results to this problem will be appreciated.
Read less
You need to create the callback in the FSP configurator first, then inside your code create its implementation like this: volatile uint8_t timer_done; ....................... /* Example callback called when timer expires. */ void timer_callback (timer_callback_args_t * p_args) { if (TIMER_EVENT_CRead more
You need to create the callback in the FSP configurator first, then inside your code create its implementation like this:
volatile uint8_t timer_done;......................./* Example callback called when timer expires. */void timer_callback (timer_callback_args_t * p_args){ if (TIMER_EVENT_CYCLE_END == p_args->event) { timer_done = 1;
}}............................set_output(OUTPUT1, IO_HIGH);timer_done = 0;
R_GPT_Start(&g_timer0_ctrl);
while (!timer_done);
R_GPT_Reset(&g_timer0_ctrl);GCC has Ofast option, but e2studio cannot be set from the menu. For RA series, how can I set the Ofast optimization level?
GCC has Ofast option, but e2studio cannot be set from the menu. For RA series, how can I set the Ofast optimization level?
Read less
Could you try adding it to Other optimization flags? When compiling, you see both -o2 …. -ofast, I think the later options will overwrite the earlier ones.(hopefully). arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -mfloat-abi=hard -mfpu=fpv5-sp-d16 -O2 -fmessage-length=0 -fsigned-char -ffunctioRead more
Could you try adding it to Other optimization flags? When compiling, you see both -o2 …. -ofast, I think the later options will overwrite the earlier ones.(hopefully).
arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -mfloat-abi=hard -mfpu=fpv5-sp-d16 -O2 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Ofast -Wunused -Wuninitialized …
See lessHow to configure RA2L1 Flash Start address and length.
How to configure RA2L1 Flash Start address and length.
Read less
Hi, I have attached an example project on RA2L1 for your reference done on FSP2.3.0. Please update it to latest version if incase you use this example. You would have to edit the linker script, to change the start address in Code flash of the application, however the file memory_regions.ld is an autRead more
Hi,
I have attached an example project on RA2L1 for your reference done on FSP2.3.0. Please update it to latest version if incase you use this example.
You would have to edit the linker script, to change the start address in Code flash of the application, however the file memory_regions.ld is an auto-generated file so any edits are overwritten. Make a copy of memory_regions.ld and give it a different name, e.g. memory_regions_application.ld.
and change the reference from “memory_regions.ld” to the name of the copy of the file you made, at the top of fsp.ld :-
/*
Linker File for Renesas FSP
*/
INCLUDE memory_regions_application.ld
in the file memory_regions_application.ld change the start address and size of the code flash :-
FLASH_START = 0x00008000;
FLASH_LENGTH = 0x38000;
and then in the debug configuration for the application, in the “Run Commands” at the bottom of the Startup tab set the Program counter, Initial Stack pointer and VTOR register to the moved location :-
set $pc = *0x00008004
set $sp = *0x00008000
set {int}0xE000ED08 = 0x00008000
If you already start your section at 0xFFF80010, as far as this project is concern, 0xFFF80000~0xFFF8000F doesn't exist. Isn't this what you want? You choose the start of ROM. If you want to make a middle section disappear, ROM = 0xFFF80000 - 0xFFF8FFFF ROM2=0xFFF90010 - 0xFFFFFFFF use cpu = stridRead more
If you already start your section at 0xFFF80010, as far as this project is concern, 0xFFF80000~0xFFF8000F doesn’t exist. Isn’t this what you want?
You choose the start of ROM. If you want to make a middle section disappear,
ROM = 0xFFF80000 – 0xFFF8FFFF
ROM2=0xFFF90010 – 0xFFFFFFFF
use cpu = stride so the middle section is un-assigned.
From ccrx manual
.section C, ROMDATA B is for RAM. C=constant.
See less