That patch didn't work,
one reason is that it has a mistake:
in kern_tc.c you defined this macro:
#define _Timecounter_Release(lock_context) \
+ *_ISR_lock_ISR_disable_and_acquire*(&_Timecounter_Lock, lock_context)
I think you meant:
*_ISR_lock_Release_and_ISR_enable*(&_Timecounter_Lock, lock_context)
The other reason is that as I said, the driver checks for the flag PENDSTSET
of the ICSR register, and I think this approach is wrong, because that flag
goes down when the tick interrupt is attended. I used the solution I
proposed before, but I'm still seeing some errors. I'll let you know what I
find.
On Wed, Dec 23, 2015 at 3:53 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Marcos,
>
> yes, nested interrupts are a problem for the current implementation. Its a
> general problem of the RTEMS testsuite that we cannot test nested
> interrupts. I think we have to fix this at some time.
>
> Could you please test the attached patch?
>
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail : sebastian.hu...@embedded-brains.de
> PGP : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
--
______________________________
<http://www.tallertechnologies.com>
Marcos Díaz
Software Engineer
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: +54 351 4217888 / +54 351 4218211/ +54 351 7617452
Skype: markdiaz22
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
