wrong behavior binary semaphore

Arturo Perez Garcia arturo.perez at upm.es
Fri Nov 30 10:55:00 UTC 2018


Hello, thanks for the feedback. I checked the confdefs file and the 
macro CONFIGURE_MAXIMUM_SEMAPHORES is set to 0 by default. I don't know 
why I didn't get those errors.

Once RTEMS is correctly configured. Did you obtain the same results as 
me?

Thanks

El 2018-11-30 11:35, Sebastian Huber escribió:
> Hello,
> 
> On 30/11/2018 11:24, Arturo Perez Garcia wrote:
>> Here are the source files. I created a README file explaining the 
>> intended goal of the semaphore under text. Under this context, I 
>> developed the test. I also put the output obtained.
>> 
>> I hope these tests help you to find the root of the problems I'm 
>> currently facing.
> 
> if I run the test I get the following output:
> 
> Error creating sync semaphore: RTEMS_TOO_MANY
> task 1 start
> error obtaining sync semaphore with sc:RTEMS_INVALID_ID
> 2 error obtaining a3k semaphore with sc:RTEMS_INVALID_ID
> error obtaining sync semaphore with sc:RTEMS_INVALID_ID
> sleeping kernel : kern_1
> ...
> 
> The semaphore creation fails since no semaphores are configured. You
> can fix this with:
> 
> #define CONFIGURE_MAXIMUM_SEMAPHORES 1
> 
> You may also just use:
> 
> #define CONFIGURE_UNLIMITED_OBJECTS
> #define CONFIGURE_UNIFIED_WORK_AREAS

-- 
Arturo Perez Garcia - arturo.perez at upm.es

Researcher
Center of Industrial Electronics
Universidad Politecnica de Madrid




More information about the users mailing list