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.
Power Factor in DOB(Driver on Board)
Before you may increase the PF, we must first determine the VD resistance; please find the formula below. Vref=0.5-1.26R/RD*(VD-1) Thanks Sandeep
Before you may increase the PF, we must first determine the VD resistance; please find the formula below.
Vref=0.5-1.26R/RD*(VD-1)
Thanks
Sandeep
See lessWhile doing OTA we are getting following error from function esp_ota_end(out_handle) in Espressif.
1. Example for OTA is "esp-idf /examples/ system/ota " ? 2. Please use the simple_ota_example(In ESP-IDF) to test over "HTTP Server" for OTA. You can refer to the "ESP32 HTTP OTA test " guide .
1. Example for OTA is “esp-idf /examples/ system/ota ” ?
2. Please use the simple_ota_example(In ESP-IDF) to test over “HTTP Server” for OTA. You can refer to the “ESP32 HTTP OTA test ” guide .
See lessWhy RA6M2 Take Accurate Second Timekeeper
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);
Renesas RA6M4 MCU interfacing with touchscreen.
The CapTouch driver in the FSP is for the Capacitive Touch Sensing Unit peripheral (CTSU) built into the RA MCU devices. You will need to build the driver for the the external touch screen chip using the basic drivers the FSP provides (e.g. I2C, SPI external IRQ).
The CapTouch driver in the FSP is for the Capacitive Touch Sensing Unit peripheral (CTSU) built into the RA MCU devices.
You will need to build the driver for the the external touch screen chip using the basic drivers the FSP provides (e.g. I2C, SPI external IRQ).
See lessUnrecognized #pragma directive
While trying to write portable code I would surround the pragma with a conditional compiler directive, e.g.: #if defined(COMPILER_1) #pragma … #endif
While trying to write portable code I would surround the pragma with a conditional compiler directive, e.g.:
#if defined(COMPILER_1)
#pragma …
#endif
See lessSCI_UART in Renesas EK-RA4M2
The pins P410, P411 are connected to the SCI0, and pins P601, P602 are connected to the SCI9. Have you changed the channel number in the UART stack like this? Also make sure that the Rx/Tx pins have both CMOS output type:
The pins P410, P411 are connected to the SCI0, and pins P601, P602 are connected to the SCI9. Have you changed the channel number in the UART stack like this?
Also make sure that the Rx/Tx pins have both CMOS output type:
See lessReserve ROM area in linker
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 lessERROR CONNECTING TO E1 DEBUGGER IN CS+
Do you have the connect settings allowed to set the OPJTAG? The error is usually caused by improperly set debug config in the option bytes, but having this setting for the debugger will allow it read, confirm, and update the values if necessary.
Do you have the connect settings allowed to set the OPJTAG?
The error is usually caused by improperly set debug config in the option bytes, but having this setting for the debugger will allow it read, confirm, and update the values if necessary.
See lessReading the correct reset status from a Bootloadble project.
A global in both projects: CY_SECTION(".reset_info") volatile struct t_reset_info reset_info; Then in the linker script of each project: MEMORY { rom (rx) : ORIGIN = 0x0, LENGTH = 262144 ram (rwx) : ORIGIN = 0x20000000 - (65536 / 2), LENGTH = 65536 - 128 nld (rw) : ORIGIN = 0x20000000Read more
A global in both projects:
Then in the linker script of each project:
That way, it’s certain that the two programs will both have access to the same NOLOAD memory, and neither will corrupt it by having the memory used for anything else.
See lessCamera Web server
If you are using ESP32CAM AI Thinker, the embedded camera is an OV2640 so only part of the code will be compiled/executed, see below. The bottom line is you could leave code as-is, it should be ok Note that frame size can take following values : frame size QQVGA(160x120),HQVGA(240x176),QVGA(320x240)Read more
If you are using ESP32CAM AI Thinker, the embedded camera is an OV2640 so only part of the code will be compiled/executed, see below.
See lessThe bottom line is you could leave code as-is, it should be ok
Note that frame size can take following values :
frame size QQVGA(160×120),HQVGA(240×176),QVGA(320×240),CIF(400×296),VGA(640×480),SVGA(800×600),XGA(1024×768),SXGA(1280×1024),UXGA(1600×1200)