Hi,

IRQ 17 is the Radio interrupt handler.
I think your implementing a new radio stack (?), e.g. not using Nimble, and may 
have just overlooked setting up that handler for your stack.

Regards
Wayne 

> On 10 Jan 2017, at 09:10, then yon <[email protected]> wrote:
> 
> Dear Fabio,
> 
> Sorry for the late response, have been interrupted by other task.
> 
> I have tried on your recommendation but it doesn't make any different.
> 
> Beside that the SWI0_EGU0_IRQHandler is a default peripheral interrupt 
> handler defined in gcc_startup_nrf52.s (just like TIMER2_IRQHandler); it 
> doesn't seem to be correct by defining it our-self.
> 
> Let me know if i understand it wrongly.
> 
> 
> Thank you.
> 
> Regards,
> 
> Then Yoong Ze
> 
> 
>> On 6/1/2017 6:04 PM, Fabio Utzig wrote:
>> Hi,
>> 
>> The unhandled exception is most probably caused by missing to define a
>> handler function. Before enabling the IRQ, try adding something like
>> (assuming the IRQ you want to handle is SWI0_EGU0_IRQ):
>> 
>> NVIC_SetVector(SWI0_EGU0_IRQn, (uint32_t) my_swi0_handler);
>> 
>> Att,
>> Fabio Utzig
>> 
>>> On Fri, Jan 6, 2017, at 05:02 AM, then yon wrote:
>>> Dear Support,
>>> 
>>> I was working on ESB mode in myNewt; what i did was porting the working
>>> code from my original working eclipse code.
>>> 
>>> Some how i was stuck at the ESB_EVT_IRQ(SWI0_EGU0_IRQ), whenever i
>>> enable this interrupt it gave me the following error when receiving
>>> packet from ESB:
>>> 1069: > Unhandled interrupt (17), exception sp 0x20001cf0 29711:
>>> r0:0x00000011 r1:0x00000001 r2:0x50000000 r3:0x00020000 29711:
>>> r4:0x000179c5 r5:0x00000001 r6:0x20001928 r7:0x00008171 29711:
>>> r8:0x00000000 r9:0x00000000 r10:0x20000000 r11:0x00000000
>>> 29711:r12:0x00000000 lr:0x000081a5 pc:0x0000819c psr:0x21000200
>>> 29711:ICSR:0x00421811 HFSR:0x00000000 CFSR:0x00000000
>>> 29711:BFAR:0xe000ed38 MMFAR:0xe000ed34
>>> 
>>> Can i know what is the meaning of that?
>>> 
>>> Please let me know if you need more info on this.
>>> 
>>> Thank you.
>>> 
>>> Regards,
>>> Then Yoong Ze
>> .
>> 
> 

Reply via email to