hanging in 2nd while loop of CY_ISR(IntDefaultHandler).

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

cross mob
Anonymous
Not applicable

Hi ,

I am using PSOC  4  Bluetooth low energy pioneer kit ,

In my project I am trying to add Upgradable Stack OTA Bootloader

But it is hanging in 2nd while loop of CY_ISR(IntDefaultHandler).

Please help me to solve this issue.

0 Likes
1 Solution
Anonymous
Not applicable

Try checking for timers or WDT, Serial, BLE, UART, SPI, CAN, or any other component that generates interrupts. And verify that all of the interrupts being generated are being handled correctly, otherwise the interrupts will jump to the default handler and busy-lock the chip.

View solution in original post

0 Likes
7 Replies
Anonymous
Not applicable

If the software is jumping to CY_ISR(IntDefaultHandler), then there is most likely an error with your code causing a hardware issue with the BLE radio based on the order/functions you are calling in your software.

Here is the comment in the CY_ISR(IntDefaultHandler) function:

/***************************************************************************

    * We must not get here. If we do, a serious problem occurs, so go into

    * an infinite loop.

    ***************************************************************************/

0 Likes
Anonymous
Not applicable

Yes ,but the same program without adding  Upgradable Stack OTA Bootloader,

it is working fine .I suspect there should be some other error.

Please help me to find that.

0 Likes
Anonymous
Not applicable

Sorry, but I haven't worked with the OTA bootloader at all. If you upload your project, perhaps some other users might take a look at it and help you out?

All in all, if the code is reading the default interrupt handler, then you are not handling an interrupt or function call correctly somewhere. Double check your interrupts being generated are all being handled correctly.

0 Likes
Anonymous
Not applicable

sorry, I can not upload my project here because of some restriction.

any other option apart from uploading? 

0 Likes
Anonymous
Not applicable

Try checking for timers or WDT, Serial, BLE, UART, SPI, CAN, or any other component that generates interrupts. And verify that all of the interrupts being generated are being handled correctly, otherwise the interrupts will jump to the default handler and busy-lock the chip.

0 Likes
Anonymous
Not applicable

Yes,the  problem was with switch interrupt ,now it is working fine.

Thank you for helping me to find the problem .

Anonymous
Not applicable

You're welcome. Glad you fixed the problem!

0 Likes