VADC0_G3_3_IRQHandler

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
User22005
Level 1
Level 1
5 replies posted 5 questions asked First reply posted
I am using an XMC 4700 and Dave APPS. My code sometimes winds up at VADC0_G3_3_IRQHandler. I can see one case of this happening by setting a breakpoint. Sometimes the code stops running and I have no idea what happened to it. From my reading, VADC0_G3_3_IRQHandler is where things wind up if you don’t set other fault handlers. I have used CPU_CTRL_XMC4_0 and checked all the checkboxes on the Exception Settings tab. That didn’t change anything, so I checked Enable MPU, Enable background memory region, and Enable MPU during NMI and hard fault handlers. Still no specific handlers being called.

What do you have to do in DAVE/Eclipse to setup fault handling?

I’m also not sure what to expect if any of these handlers do get called. Will it give me a stack trace back to the fault? Is there a command to run that will tell me something?
0 Likes
1 Solution
Vasanth
Moderator
Moderator
Moderator
250 sign-ins 500 solutions authored First question asked

Hi,

Even though you are being pointed to VADC handler, the real issue is not right there. Define default handlers and other fault handlers and you should be able to track down the real issue.

Best Regards,
Vasanth

View solution in original post

0 Likes
3 Replies
Vasanth
Moderator
Moderator
Moderator
250 sign-ins 500 solutions authored First question asked
Hi,

Could you make sure that you have regenerated the code after making the changes to the dave app ? Additionally you can check CFSR, SHCSR, BFAR, MMFAR registers too. The code ending up in
VADC0_G3_3_IRQHandler points to the fact that a fault has occured.

Best Regards,
Vasanth
0 Likes
User22005
Level 1
Level 1
5 replies posted 5 questions asked First reply posted
This is what my debug window shows during the fault:

D2GL_SC_FMCW Standard [GDB SEGGER J-Link Debugging]
D2GL_SC_FMCW.elf
Thread #1 57005 (Suspended : Step)
VADC0_G3_3_IRQHandler() at 0x8000290
0xffffffe8
JLinkGDBServerCL.exe
arm-none-eabi-gdb
Semihosting and SWV

I regenerated the APP code to make sure, and the problem persists. I did a search on BusFault_Handler thinking I should find some code for it.
It appears that BusFault_Handler, VADC0_G3_3_IRQHandler, and many other things are set to the same address (0x08000200).


.reset 0x08000000 0x294 ./Startup/startup_XMC4700.o
0x08000000 __Vectors
0x08000200 Reset_Handler
0x08000290 DebugMon_Handler
0x08000290 VADC0_C0_0_IRQHandler
0x08000290 CAN0_4_IRQHandler
0x08000290 VADC0_G2_0_IRQHandler
0x08000290 USIC0_5_IRQHandler
0x08000290 POSIF0_0_IRQHandler
0x08000290 POSIF1_0_IRQHandler
0x08000290 VADC0_G1_1_IRQHandler
0x08000290 PendSV_Handler
0x08000290 NMI_Handler
0x08000290 USIC1_3_IRQHandler
0x08000290 SCU_0_IRQHandler
0x08000290 ERU0_0_IRQHandler
0x08000290 USIC1_5_IRQHandler
0x08000290 DSD0_4_IRQHandler
0x08000290 CCU80_1_IRQHandler
0x08000290 CCU81_0_IRQHandler
0x08000290 UsageFault_Handler
0x08000290 USIC0_0_IRQHandler
0x08000290 POSIF1_1_IRQHandler
0x08000290 ERU0_2_IRQHandler
0x08000290 CCU81_1_IRQHandler
0x08000290 ERU1_1_IRQHandler
0x08000290 VADC0_G2_3_IRQHandler
0x08000290 VADC0_G2_2_IRQHandler
0x08000290 CCU42_3_IRQHandler
0x08000290 ERU0_3_IRQHandler
0x08000290 DSD0_5_IRQHandler
0x08000290 DSD0_7_IRQHandler
0x08000290 CAN0_6_IRQHandler
0x08000290 CCU43_0_IRQHandler
0x08000290 VADC0_G0_1_IRQHandler
0x08000290 CCU81_2_IRQHandler
0x08000290 USIC2_4_IRQHandler
0x08000290 CCU81_3_IRQHandler
0x08000290 USIC2_5_IRQHandler
0x08000290 CCU40_0_IRQHandler
0x08000290 CAN0_0_IRQHandler
0x08000290 ERU1_0_IRQHandler
0x08000290 CCU42_2_IRQHandler
0x08000290 Default_Handler
0x08000290 USIC1_4_IRQHandler
0x08000290 ERU1_3_IRQHandler
0x08000290 POSIF0_1_IRQHandler
0x08000290 VADC0_G0_0_IRQHandler
0x08000290 DSD0_2_IRQHandler
0x08000290 CCU80_3_IRQHandler
0x08000290 CCU41_3_IRQHandler
0x08000290 CCU80_2_IRQHandler
0x08000290 VADC0_G1_3_IRQHandler
0x08000290 VADC0_G0_3_IRQHandler
0x08000290 PMU0_0_IRQHandler
0x08000290 CAN0_7_IRQHandler
0x08000290 DSD0_1_IRQHandler
0x08000290 CCU41_2_IRQHandler
0x08000290 VADC0_C0_1_IRQHandler
0x08000290 CCU43_2_IRQHandler
0x08000290 MemManage_Handler
0x08000290 VADC0_G3_1_IRQHandler
0x08000290 DAC0_0_IRQHandler
0x08000290 SVC_Handler
0x08000290 VADC0_G3_3_IRQHandler
0x08000290 ERU1_2_IRQHandler
0x08000290 DSD0_6_IRQHandler
0x08000290 CCU43_1_IRQHandler
0x08000290 VADC0_G1_2_IRQHandler
0x08000290 CAN0_2_IRQHandler
0x08000290 VADC0_G0_2_IRQHandler
0x08000290 VADC0_G2_1_IRQHandler
0x08000290 CAN0_3_IRQHandler
0x08000290 ETH0_0_IRQHandler
0x08000290 USIC0_3_IRQHandler
0x08000290 DSD0_0_IRQHandler
0x08000290 VADC0_C0_2_IRQHandler
0x08000290 FCE0_0_IRQHandler
0x08000290 VADC0_G1_0_IRQHandler
0x08000290 CAN0_5_IRQHandler
0x08000290 CCU80_0_IRQHandler
0x08000290 USIC0_1_IRQHandler
0x08000290 VADC0_G3_2_IRQHandler
0x08000290 BusFault_Handler
0x08000290 LEDTS0_0_IRQHandler
0x08000290 USIC0_4_IRQHandler
0x08000290 CCU43_3_IRQHandler
0x08000290 ERU0_1_IRQHandler
0x08000290 VADC0_G3_0_IRQHandler
0x08000290 USIC1_2_IRQHandler
0x08000290 DSD0_3_IRQHandler
0x08000290 SDMMC0_0_IRQHandler
0x08000290 CAN0_1_IRQHandler
0x08000290 USIC0_2_IRQHandler
0x08000290 DAC0_1_IRQHandler
0 Likes
Vasanth
Moderator
Moderator
Moderator
250 sign-ins 500 solutions authored First question asked

Hi,

Even though you are being pointed to VADC handler, the real issue is not right there. Define default handlers and other fault handlers and you should be able to track down the real issue.

Best Regards,
Vasanth

0 Likes