You are here

VESC Keeps resetting from IWDT timeout_init()

2 posts / 0 new
Last post
gowrav
Offline
Last seen: 2 months 1 week ago
Joined: 2019-06-11 16:48
Posts: 17
VESC Keeps resetting from IWDT timeout_init()

After replacing the MOSFET s on my VESC 75/300 ., the USB communication with the host system started to act flaky and had to retouch all the pins on the microcontroller to eliminate any loose connections ., this lands me in the current situation where the STM32 microcontroller keeps resetting every 2 seconds with a blink on both the [strong] Red and [faint]Green LED's ., the USB communication is not established as the window of reset is too small.



Upon debugging the code its evident that the issue is in relation to the IWDT Independent Watch Dog Timer routine ., as the VESC establishes communications and works if the timeout_init() function is commented out from the main.c file...

I tried replacing the STM32 to no avail .., tested the 8mhz xtal using the logic analyzer which shows that the frequency of the crystal output is around 8.33Mhz with 60% duty cycle...that seems to be within limits considering that the logic analyzer probe will have some parasitic impedance..



I don't think that the crystal is faulty although I have a replacement to confirm that .., I don't think the STM32 microcontroller is faulty as the new one did the exact same thing ...

I don't thing VESC firmware is corrupted either as the flash verification routine is working well and says that its good.



I feel that the IWDT is the root cause and not any other included parameters in relation to FOC or otherwise ...which could be due to the LSI but then again it can't be same between microcontrollers so the final test would be to change the IWDT reload counter and see if the reset gets extra time somehow or to validate the pin-voltage of the LSI internal oscillator to ensure that the IWDT is indeed running.. which might have been because of re-soldering of microcontroller..



Any suggestions would be certainly helpful

gowrav
Offline
Last seen: 2 months 1 week ago
Joined: 2019-06-11 16:48
Posts: 17

This seems to be the behaviour with the Firmware built using MACOS..the linux version is fine..

GL