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.
Renesas MCU as we know Renesas makes microcontrollers (mcu) that provide expand ability while allowing customers to make full use of existing resources.
Some of the popular microcontrollers (mcu) made by Renesas are:
RL78 is the family name for a range of 16-bit microcontrollers.
The RX MCU family
The RX, an acronym for Renesas Xtreme, is the family name for a range of 32-bit microcontrollers developed by Renesas.
The RA, an acronym for Renesas Advanced, is the family name for a range of 32-bit microcontrollers with Arm Cortex processor cores.
Hello Volt.Tech Community,What is the difference between R-Car and RZG2L SoCs? I have seen both RCAR and RZG2L config options empowered within the Kernel configurations, so I thought similarities will be there.Thank You in Advance
Hello Volt.Tech Community,
What is the difference between R-Car and RZG2L SoCs? I have seen both RCAR and RZG2L config options empowered within the Kernel configurations, so I thought similarities will be there.
Thank You in Advance
Read lessWhat are the external memory types supported with RA8 Series MCUs and can the RA8 Series MCU’s support HyperFlash and HyperRAM devices?
What are the external memory types supported with RA8 Series MCUs and can the RA8 Series MCU’s support HyperFlash and HyperRAM devices?
Read less
Hi Von, Thank you for your post! RA8 Series MCUs support xSPI-compliant Octal SPI( OSPI) interface with support for Execute-In-Place and Decryption-on-the-cover ( DOTF). The OSPI interface is compliant with JEDEC standard JESD251( Profile1.0 and2.0), JESD251- 1 and JESD252. The RA8 Series is compatiRead more
Hi Von,
Thank you for your post!
RA8 Series MCUs support xSPI-compliant Octal SPI( OSPI) interface with support for Execute-In-Place and Decryption-on-the-cover ( DOTF). The OSPI interface is compliant with JEDEC standard JESD251( Profile1.0 and2.0), JESD251- 1 and JESD252.
The RA8 Series is compatible with all flash devices that are JESD251 standard compliant and supports both Octal Flash & Octal RAM and HyperFlash & HyperRAM devices compatible with the Infineon HyperBus specification. RA8 xSPI guarantees operation with JESD251( xSPI for Non-Volatile Memory) compliant memory.
The RA8 series MCUs have been tested and are verified to be compatible with these memory P/ Ns.
Thank You
Alex
Hello,I would like to apply Renesas Motor Workbench but I do not understand all the parameters that can be manipulated.I apply the program RA6T2_MCILV1_SPM_LESS_120_E2S_V110 and then’s the list of parameters:Does anyone experience ...Read more
Hello,
I would like to apply Renesas Motor Workbench but I do not understand all the parameters that can be manipulated.
I apply the program RA6T2_MCILV1_SPM_LESS_120_E2S_V110 and then’s the list of parameters:
Does anyone experience where to discover clarification on this subject?
Thank you in advance.
Best Regards,
Nathan
Read lessHello Nathan, These parameters are internal variables of the vector control c design. Let us explain some of them ref_speed_rpm: it's the quickness that an external user sets via a potentiometer.over the current limit: the max current value, over this value you have the faulty condition of the motorRead more
Hello Nathan,
These parameters are internal variables of the vector control c design.
Let us explain some of them
ref_speed_rpm: it's the quickness that an external user sets via a potentiometer.
over the current limit: the max current value, over this value you have the faulty condition of the motor
overvoltage_limit: maximum dc voltage, over this value you have over voltage at dc link of your topology
overspeed_limit_rpm: is the maximum speed that your motor has designed
lowvoltage_limit: the minimal voltage that requires the inverter to drive your motor
limit_speed_change: the maximum acceptable change of the motor speed that the user can give
However, please feel free to ask, If you can not understand any specific system parameter.
Best Regards,
Vikas Nagpal
Hello everyone,I make a new RA2E2 hardware board. But it can’t start up flash programmer connect fail with SCI, and SWD connect fail too.I check some pinsVCC3.3 VVCL1.5 VP201/ MD can switch 0V or 3.3 V with key.RES can switch ...Read more
Hello everyone,
I make a new RA2E2 hardware board. But it can’t start up flash programmer connect fail with SCI, and SWD connect fail too.
I check some pins
VCC3.3 V
VCL1.5 V
P201/ MD can switch 0V or 3.3 V with key.
RES can switch 0 V or3.3 V with key.
timing is right when PC send data to RA2E2 board.
But RA2E2 have no any response.
Are there any other debug way for RA2E2? or any user guide doc for this issue?
Thanks.
Read less
Hello, Are you testing to connect with Renesas Flash Programmer? What debugger are you applying? Please check the E2/E2 Lite recommended connections for SWD: For VCL pin: The MD pin should be high to enter debugging mode and low to enter serial programming mode via SCI: The RES pin should be connectRead more
Hello,
Are you testing to connect with Renesas Flash Programmer? What debugger are you applying?
Please check the E2/E2 Lite recommended connections for SWD:
For VCL pin:
The MD pin should be high to enter debugging mode and low to enter serial programming mode via SCI:
The RES pin should be connected to pull- up.
Best & Regards
Hi,I trying to do an worst case error estimation in my ADC readings and according to the Datasheet as shown below I’ve other error factors Offset, Full- scale, Absolute Accuracy, DNL, INL.We’re ...Read more
Hi,
I trying to do an worst case error estimation in my ADC readings and according to the Datasheet as shown below I’ve other error factors Offset, Full- scale, Absolute Accuracy, DNL, INL.
We’re trying to mitigate the Offset and Full- scale error by applying a Two-Point Calibration Method.
I would like to know do I need to consider Absolute accuracy as ± 2 even though I’ve compensated Offset and Full-scale error.
Also what about DNL and INL errors do I want to consider both in my calculations and INL is the integral sum of DNL errors.
Also should I consider Typ or Max values what’s the difference between them?
Thank You in Advance
Read lessHello Jameshleo, Thanks for reaching out to the Volt Tech Community. First, the max values for errors defined on the user's manual are the worst error values measured in the laboratory test environment for the full voltage range, while typical is the most usual error value without compensation. UsinRead more
Hello Jameshleo,
Thanks for reaching out to the Volt Tech Community.
First, the max values for errors defined on the user’s manual are the worst error values measured in the laboratory test environment for the full voltage range, while typical is the most usual error value without compensation.
Using software techniques such as Two- a point calibration system you cancel/ compensate offset and full-scale error.
In the case of the Renesas specification, the Absolute Accuracy value is the total uncompensated error for all error terms( INL, DNL, Offset, Gain, and Quantization error terms).
So, you can improve the Absolute Accuracy to be lower than using compensation methods.
Also, find attached the INL meaning:
The INL depends on the internal circuit architecture and from any possible distortion, caused by the front-end signal conditioning circuit.
I hope it helps!
Regards,
Vikas Nagpal
Hello, I’m presently working on a RA2L1 custom board and using the E2 emulator lite for debugging by e2 studio. I want to flash the device. still, I’m not finding any clear methodology documented for the same. It would be ...Read more
Hello,
I’m presently working on a RA2L1 custom board and using the E2 emulator lite for debugging by e2 studio. I want to flash the device. still, I’m not finding any clear methodology documented for the same. It would be helpful if the following points are clarified.
1. Do I’ve to use the Renesas flash programmer for flashing or it can be done through e2 studio?
2. Do I need to alter include anything in the code (tested fine in debug mode) specifically for flashing purpose?
3. Does the code need to be copied from flash to RAM in runtime for better performance? If yes, how do I insure that?
A step-wise guide application note on this topic would be of great help.
Regards,
Read lessHello, Thanks for sharing your question with Volt Engineering Community! Please take a look at Code written for downloading and debugging with E2 will most likely just hang when run without a debugger attached. 1. RFP is an option, or any development environment such as e2 studio or 3rd party toolsRead more
Hello,
Thanks for sharing your question with Volt Engineering Community!
Please take a look at Code written for downloading and debugging with E2 will most likely just hang when run without a debugger attached.
1. RFP is an option, or any development environment such as e2 studio or 3rd party tools can program the flash of the device.
2. No special accommodations in the application code are necessary to enable flashing the device. Most designs will incorporate a custom charge-loader that uses a particular interface (UART, CAN, etc.) with a proprietary comm protocol, but this isn’t needed if the serial programming mode of the device can be set and a tool used that supports factory programming protocol.
3. Renesas devices are optimized to execute code from the flash. Some designs that use comparatively slow flash technology can profit from RAM execution but that isn’t the case for RA devices.
Kind Regards,
Vikas Nagpal
Hello, I am working on the USB. I added the” USB PCDC” stack. But there’s an error” Requires USB clock to be 48 MHz”. How can I fix it?Please see attached screenshot. Thanks.
Hello,
I am working on the USB. I added the” USB PCDC” stack. But there’s an error” Requires USB clock to be 48 MHz”. How can I fix it?
Please see attached screenshot.
Thanks.
Hello, You need to go to the" Clocks" tab of the FSP configurator and enable the UCLK clock. also, adjust your PLL Mul and UCLK Div to reach the UCLK frequency of 48 MHz. Kind regards,
Hello,
You need to go to the” Clocks” tab of the FSP configurator and enable the UCLK clock. also, adjust your PLL Mul and UCLK Div to reach the UCLK frequency of 48 MHz.
Kind regards,
Hello, How reliable is the data flash (using FSP VEE module) in case of interrupting power supply during write/erase operation?
Hello,
How reliable is the data flash (using FSP VEE module) in case of interrupting power supply during write/erase operation?
Read lessHi, However, it seems that if 2 consecutive power interrupts during write operations occur, the data aren't copied again after the second power interrupt, If I understand your concern right. So the VEEPROM has no valid data in this case. I hope it helps. Thank You
Hi,
However, it seems that if 2 consecutive power interrupts during write operations occur, the data aren’t copied again after the second power interrupt, If I understand your concern right. So the VEEPROM has no valid data in this case.
I hope it helps.
Thank You
See lessDear Volt.Tech, I’ve been trying to run the IIC master example code with the EK- RA6M3 board but it doesn’t make with the latest FSP version(4.0.0). To workaround this I installed v3.8.0 but I’m facing issues with the IDE where it doesn’t enter the function which has a multi-byte i2c read sequence. I’m using the MAX86161 detector to test this out. Thanks & Regards
Dear Volt.Tech,
I’ve been trying to run the IIC master example code with the EK- RA6M3 board but it doesn’t make with the latest FSP version(4.0.0). To workaround this I installed v3.8.0 but I’m facing issues with the IDE where it doesn’t enter the function which has a multi-byte i2c read sequence. I’m using the MAX86161 detector to test this out.
Thanks & Regards
Read lessHi, Thanks for reaching out to Engineering Community. Could you please check your e² studio version? Please note that FSP versions of 3.7.0 and later require a minimal e² studio version of 2022- 04 and FSP versions of 4.0.0 and later require a minimum e² studio version of 2022- 07. Best regards,
Hi,
Thanks for reaching out to Engineering Community.
Could you please check your e² studio version? Please note that FSP versions of 3.7.0 and later require a minimal e² studio version of 2022- 04 and FSP versions of 4.0.0 and later require a minimum e² studio version of 2022- 07.
Best regards,
See less
Hi, I am curious about what kind of the internal flash of RA6T2 is? Is it NOR flash or NAND flash? According to the program and erase size, it seems to be NOR flash? still, what’s the physical interface of the flash? ...Read more
Hi,
I am curious about what kind of the internal flash of RA6T2 is? Is it NOR flash or NAND flash?
According to the program and erase size, it seems to be NOR flash?
still, what’s the physical interface of the flash? Does it use the SPI or other?
If it was NOR flash.Thanks
RA6T2 uses the Renesas proprietary Metal Oxide Nitride Oxide Semiconductor( MONOS) flash technology, it's neither NOR nor NAND. You can search the general web or the Renesas web pages and find information about this. The interface is a direct register grounded via the flash application command interRead more
RA6T2 uses the Renesas proprietary Metal Oxide Nitride Oxide Semiconductor( MONOS) flash technology, it’s neither NOR nor NAND. You can search the general web or the Renesas web pages and find information about this.
The interface is a direct register grounded via the flash application command interface( FACI). From the RA6T2 hardware U/ M
The FCU( flash control unit) controls the programming and erasure of the flash memory. The FACI( flash application command interface) controls the FCU according to the specified FACI commands.
Hello Max, There, is a massive difference. Not just in silicon and performance, but utilizing case and tool/chains/IDE etc. R-CAR is intended to support functional safety/ improved security. G2LC is intended as a section-level common reason MPU. It's not an apples-for-apples comparison at all. ThankRead more
Hello Max,
See lessThere, is a massive difference. Not just in silicon and performance, but utilizing case and tool/chains/IDE etc. R-CAR is intended to support functional safety/ improved security. G2LC is intended as a section-level common reason MPU. It’s not an apples-for-apples comparison at all.
Thanks & Regards
Julian White