On 30/11/2018 15:23, Arturo Perez Garcia wrote:
Hello,
I did more tests using the same source files. But modifying the
priority of the threads and the scheduling algorithm used in the
creation of the semaphore. What I was expecting (and what I need) is
this:
task 1 start
ld adq by kernel.
Hello,
I did more tests using the same source files. But modifying the priority
of the threads and the scheduling algorithm used in the creation of the
semaphore. What I was expecting (and what I need) is this:
task 1 start
ld adq by kernel. kern_1
ld rel by kernel. kern_1
exe adq by kernel:
On 30/11/2018 11:55, Arturo Perez Garcia wrote:
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.
I used the RTEMS master to run the test. In RTEMS 4.11 the default
configu
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 e
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 pro
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.
Thanks.
El 2018-11-30 09:
