Re: [riot-devel] Unlocking mutex in RTC ISR and thread switching causes HardFault

2016-09-14 Thread Joakim Nohlgård 
Do you have some example code that you can share which triggers this fault?

Best regards, Joakim

On Sep 14, 2016 7:50 PM, "Anon Anonymous"  wrote:

> Hello,
>
> I trying to unlock mutex in RTC Alarm ISR and after alarm shoots and mutex
> is unlocked, the thread switch request is pending. RTC ISR in rtc.c file
> check that flag and calls thread_yield() to call a scheduler. After PendSV
> interrupt is triggered, HardFault occurs right after PendSV enabling
> command.
>
> When the same operations done from for example, TIM interrupt which used
> by xtimer, context switching goes well.
>
> FSR/FAR:
>>  CFSR: 0x0004
>>  HFSR: 0x4000
>>
>
>
> My device is STM32L151.
>
> Best regards,
> Anon
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Unlocking mutex in RTC ISR and thread switching causes HardFault

2016-09-14 Thread Anon Anonymous 
Hello,

I trying to unlock mutex in RTC Alarm ISR and after alarm shoots and mutex
is unlocked, the thread switch request is pending. RTC ISR in rtc.c file
check that flag and calls thread_yield() to call a scheduler. After PendSV
interrupt is triggered, HardFault occurs right after PendSV enabling
command.

When the same operations done from for example, TIM interrupt which used by
xtimer, context switching goes well.

FSR/FAR:
>  CFSR: 0x0004
>  HFSR: 0x4000
>


My device is STM32L151.

Best regards,
Anon
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel