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.
Error in burning program in XDPL8210 IC
As the XDPL8210 chip on the 35 W reference design PCB has a first full set of parameters in its One-Time Programmable (OTP) memory space, only changed parameters are written in the OTP memory. 1 Load configuration file (see example in Figure 7). 2 Modify the parameter value needed, then press [File]Read more
As the XDPL8210 chip on the 35 W reference design PCB has a first full set of parameters in its One-Time
Programmable (OTP) memory space, only changed parameters are written in the OTP memory.
1 Load configuration file (see example in Figure 7).
2 Modify the parameter value needed, then press [File] >> [Save] or [File] >> [Save as] to save
the configuration file. Otherwise, proceed to step 3.
3
(optional)
Disconnect or turn off AC input voltage and check the hardware connection for configuration,
see Figure 2 and Figure 3.
4 Press to supply power and establish connection to the target XDPL8210. After this,
XDPL8210 will enter configuration mode and the device status should change to .
5
Press to burn the configuration into target XDPL8210.
After this step, a window pops up, like one of these below.
Note: If the parameter configuration is equivalent to to the pre-existing parameters, the
See lessXDPL8210 will not burn them in the OTP memory.
6 Press “Proceed” or “Yes” to burn the configuration. After this, a window pops up indicating
success.
7 Press “OK” on the pop-up window then disconnect the programming cable from the board
connector and test the application, if needed.
Language change in Smart Configurator project from C to C++
I am not sure if this is possible with smart configurator but with the latest Eclipse CDT, it is possible to add/remove the nature of the project. Then you can convert to C++. Try searching about using eclipse to convert C projects to C++ project.
I am not sure if this is possible with smart configurator but with the latest Eclipse CDT, it is possible to add/remove the nature of the project. Then you can convert to C++. Try searching about using eclipse to convert C projects to C++ project.
See lessRenesas R7FA6E10F2CFP programming issues
Are you using a Renesas reference design, or is this custom hardware? Have you checked your connection with the document E2 Emulator, E2 Emulator Lite Additional Document for User's Manual (Notes on Connection of RA Devices)? Which tool are you using - E2 or E2-lite? This matters, because the E2 sRead more
Are you using a Renesas reference design, or is this custom hardware? Have you checked your connection with the document E2 Emulator, E2 Emulator Lite Additional Document for User’s Manual (Notes on Connection of RA Devices)?
Which tool are you using – E2 or E2-lite? This matters, because the E2 supports both JTAG & SWD while E2-Lite only supports SWD. From On-chip Debuggers Performance Property:
DA9063B DA9210 Power Commander GUI
The GUI runs ok on windows 10. Have you tried to cleanly re-install the GUI?
The GUI runs ok on windows 10.
Have you tried to cleanly re-install the GUI?
See lessSteps to run a Bootloader from RAM
The FSP flash driver will run from RAM if code flash programming is enabled in the configuration of the driver, for the parts of the flash driver driver that actually do the programming or erasing.
The FSP flash driver will run from RAM if code flash programming is enabled in the configuration of the driver, for the parts of the flash driver driver that actually do the programming or erasing.
See lessUART
There are basically two way to change the UART baud rate at run-time. It depends how you allocated the UART. If you allocated by PDL-method (ie. In the PSoC Creator TopDesign or Modustoolbox Device Configurator [design.modus]) then use the PDL SysClk API calls: Configure Baud Rate To get the UARTRead more
There are basically two way to change the UART baud rate at run-time. It depends how you allocated the UART.
If you allocated by PDL-method (ie. In the PSoC Creator TopDesign or Modustoolbox Device Configurator [design.modus]) then use the PDL SysClk API calls:
Configure Baud Rate
To get the UART to operate with the desired baud rate, the clk_scb frequency and the oversample must be configured. Use the SysClk (System Clock) driver API to configure clk_scb frequency. Set the oversample parameter in configuration structure to define the number of the SCB clocks within one UART bit-time.
* For clk_peri = 50 MHz, select divider value 36 and get SCB clock = (50 MHz / 36) = 1,389 MHz.
* Select Oversample = 12. These setting results UART data rate = 1,389 MHz / 12 = 115750 bps.
*/
Cy_SysClk_PeriphSetDivider (UART_CLK_DIV_TYPE, UART_CLK_DIV_NUMBER, 35UL);
Cy_SysClk_PeriphEnableDivider(UART_CLK_DIV_TYPE, UART_CLK_DIV_NUMBER);
Refer to the technical reference manual (TRM) section UART sub-section Clocking and Oversampling to get information about how to configure the UART to run with desired baud rate.
link: file:///C:/Program%20Files%20(x86)/Cypress/PDL/3.1.1/doc/pdl_api_reference_manual/html/group__group_…
If you allocated the UART by the HAL-method use:
cyhal_uart_set_baud() link: Hardware Abstraction Layer (HAL)
See lessInterrupt sample program for Renesas RH850-F1KM-S1
I believe there are several interrupts used in this sample code: Y-ASK-RH850F1KM-S1-V3 Sample Code
I believe there are several interrupts used in this sample code:
Y-ASK-RH850F1KM-S1-V3 Sample Code
See lessRenesas RA6M3 debugger not working
On the options for target, utilities tab, select Use External tool for Flash Programming (leave blank, command & argument)
On the options for target, utilities tab, select
Use External tool for Flash Programming (leave blank, command & argument)
See lessRenesas RA6M4 sub clock not working – bug fix.
You could disable the sub-oscillator in the user code :- /* Call pre clock initialization hook. */ R_BSP_WarmStart(BSP_WARM_START_RESET); is called before /* Configure system clocks. */ bsp_clock_init(); in the SystemInit() function, in the file system.c. The function R_BSP_WarmStart() is created inRead more
You could disable the sub-oscillator in the user code :-
/* Call pre clock initialization hook. */
R_BSP_WarmStart(BSP_WARM_START_RESET);
is called before
/* Configure system clocks. */
bsp_clock_init();
in the SystemInit() function, in the file system.c.
The function R_BSP_WarmStart() is created in the file src\hal_entry.c, so you could add the code to stop the sub oscillator there :-
void R_BSP_WarmStart(bsp_warm_start_event_t event)
{
if (BSP_WARM_START_RESET == event)
{
uint16_t prcr = R_SYSTEM->PRCR;
R_SYSTEM->PRCR = 0xA501;
R_SYSTEM->SOSCCR = 1; //disable the SOSC
R_SYSTEM->PRCR = (uint16_t)(0xA500 | (prcr & 0x00FF));
}
}
You might not want to stop the sub-oscillator if the device has been running on the VBATT power supply with the RTC running, and VCC is re-applied, as stopping the sub oscillator would also stop the RTC, so you might only want to stop the sub oscillator on a cold boot of the device.
The SOMCR register should only be modified if the sub oscillator is not running (i.e. the SOSTP bit in the SOSCR register is 1), so just commenting out the check:-
if (R_SYSTEM->SOSCCR)
is not reccomended, the sub oscillator should first be stopped, before modifying the SOMCR register.
See lessSetting Ofast optimization level for RA Series.
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 less