Re: Instructions for Networking with Xilinx BSP and Qemu

On 18/06/2016 01:40, Joel Sherrill wrote: Are there instructions for doing this? Or even the realview BSP? I am not sure. It has been a while since I ran this. Last time I used qemu and the Xilinx BSP I used VDE with a 32 port VDE switch connected to a bridge between my test network port and

Re: Error Running HelloWorld on new BSP

Break at get_baud_div() or initialize(), since they appear in your printout of the *frame, which is the interrupted thread context at the point of the unhandled exception. On Fri, Jun 17, 2016 at 1:44 PM, Olufowobi, Habeeb wrote: > Hi Joel, > > When I set the breakpoint at boot_card, this how far

Re: Error Running HelloWorld on new BSP

Hi Joel, When I set the breakpoint at boot_card, this how far I could get; (gdb) step _Terminate (the_source=RTEMS_FATAL_SOURCE_EXCEPTION, is_internal=false, the_error=536874976) at ../../../../../../../rtems.git/c/src/../../cpukit/score/src/interr.c:52 52 _CPU_Fatal_halt( the_source

Raspberry pi not working with latest compiler and rtems-git

I refreshed my RSB build and pulled the latest rtems git changes. ( as of today ) and the Raspberry Pi BSPs are not working. I built the sparc/sis RSB and BSP and my tests run fine on that. I will troubleshoot in the next day or so and try to find the error. What is the best ARM simulator BSP to t

Re: Error Running HelloWorld on new BSP

On Fri, Jun 17, 2016 at 11:33 AM, Olufowobi, Habeeb < habeeb.olufow...@bison.howard.edu> wrote: > Hi, > > I was able to print the frame and below is the result. Also, I realised > the problem is from the uart. Any ideas on how to resolve this? > > > (gdb) print *frame > $1 = {register_r0 = 115200,

Re: Error Running HelloWorld on new BSP

Hi, I was able to print the frame and below is the result. Also, I realised the problem is from the uart. Any ideas on how to resolve this? (gdb) print *frame $1 = {register_r0 = 115200, register_r1 = 1, register_r2 = 0, register_r3 = 1073790976, register_r4 = 0, register_r5 = 0, register_r6

Instructions for Networking with Xilinx BSP and Qemu

Hi Are there instructions for doing this? Or even the realview BSP? Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Rework thread priority management and EDF scheduler

The thread priority is manifest in two independent areas. One area is the user visible thread priority along with a potential thread queue. The other is the scheduler. Currently, a thread priority update via _Thread_Change_priority() first updates the user visble thread priority and the thread qu

[PATCH 15/16] score: Move _RBTree_Find()

The _RBTree_Find() is no longer used in the score. Move it to sapi and make it rtems_rbtree_find(). Move corresponding types and support functions to sapi. --- cpukit/sapi/Makefile.am | 1 + cpukit/sapi/include/rtems/rbtree.h| 72 ++- cp

[PATCH 03/16] posix: Delete POSIX_API_Control::ss_high_priority

This field was unused. --- cpukit/posix/include/rtems/posix/threadsup.h | 5 - cpukit/posix/src/pthreadsetschedparam.c | 4 2 files changed, 9 deletions(-) diff --git a/cpukit/posix/include/rtems/posix/threadsup.h b/cpukit/posix/include/rtems/posix/threadsup.h index 51c9564..60bf0e

[PATCH 07/16] posix: Make POSIX API aware of scheduler instances

--- cpukit/posix/include/rtems/posix/priorityimpl.h | 82 ++--- cpukit/posix/src/mutexgetprioceiling.c | 1 + cpukit/posix/src/mutexinit.c| 5 +- cpukit/posix/src/mutexsetprioceiling.c | 35 +++ cpukit/posix/src/psxpriorityisvalid

[PATCH 04/16] posix: Delete POSIX_API_Control::schedpolicy

This field was redundant. --- cpukit/posix/include/rtems/posix/threadsup.h | 2 -- cpukit/posix/src/pthread.c | 3 +-- cpukit/posix/src/pthreadcreate.c | 3 +-- cpukit/posix/src/pthreadgetschedparam.c | 2 +- cpukit/posix/src/pthreadsetschedparam.c | 3 +--

[PATCH 05/16] posix: Delete POSIX_API_Control::schedparam

This field was redundant. --- cpukit/posix/include/rtems/posix/threadsup.h | 4 ++-- cpukit/posix/src/pthread.c | 14 +- cpukit/posix/src/pthreadcreate.c | 3 +-- cpukit/posix/src/pthreadgetschedparam.c | 2 +- cpukit/posix/src/pthreadsetschedparam

[PATCH 06/16] posix: Rework sporadic server scheduling policy

Instead of lowering the priority in case the initial budget is consumed raise the priority for each new period. Restore the normal priority once the initial budget is consumed. This makes it later easier to combine the high priority phase with temporary priority boosts (e.g. via priority ceiling

[PATCH 12/16] score: Modify release job scheduler operation

Pass the deadline in watchdog ticks to the scheduler. --- cpukit/rtems/src/ratemonperiod.c | 7 --- cpukit/score/include/rtems/score/scheduler.h | 4 ++-- cpukit/score/include/rtems/score/schedulercbs.h | 2 +- cpukit/score/include/rtems/score/scheduleredf.h | 2 +- cpuki

[PATCH 02/16] posix: _POSIX_Mutex_Default_attributes

Make _POSIX_Mutex_Default_attributes constant and independent of the scheduler instance. Use INT_MAX to indicate the default ceiling priority. --- cpukit/posix/Makefile.am| 2 +- cpukit/posix/include/rtems/posix/muteximpl.h| 2 +- cpukit/posix/include/rtems/posix/pri

[PATCH 14/16] score: Move _RBTree_Insert()

The _RBTree_Insert() is no longer used in the score. Move it to sapi and make it rtems_rbtree_insert(). --- cpukit/sapi/Makefile.am | 1 + cpukit/sapi/include/rtems/rbtree.h| 32 +++-- cpukit/sapi/src/rbtreeinsert.c| 57 ++

[PATCH 16/16] score: Add thread priority to scheduler nodes

The thread priority is manifest in two independent areas. One area is the user visible thread priority along with a potential thread queue. The other is the scheduler. Currently, a thread priority update via _Thread_Change_priority() first updates the user visble thread priority and the thread qu

[PATCH 01/16] posix: pthread_mutexattr_setprioceiling()

Accept all priority values in pthread_mutexattr_setprioceiling(). This is in line with POSIX and FreeBSD. The priority is validated in pthread_mutex_init(). Validate the priority only for priority ceiling mutexes. --- cpukit/posix/src/mutexattrsetprioceiling.c | 9 - cpukit/posix/src/m

[PATCH 10/16] score: Introduce map priority scheduler operation

Introduce map/unmap priority scheduler operations to map thread priority values from/to the user domain to/from the scheduler domain. Use the map priority operation to validate the thread priority. The EDF schedulers use this new operation to distinguish between normal priorities and priorities o

[PATCH 11/16] score: Remove hidden deadline overrule for CBS

Do what the user commands. Maybe we should add a rtems_cbs_period() that calls rtems_rate_monotonic_period() with the right parameter. --- cpukit/score/src/schedulercbsreleasejob.c | 30 -- 1 file changed, 8 insertions(+), 22 deletions(-) diff --git a/cpukit/score/src

[PATCH 13/16] score: Rework EDF scheduler

Use inline red-black tree insert. Do not use shifting priorities since this is not supported by the thread queues. Due to the 32-bit Priority_Control this currently limits the uptime to 49days with a 1ms clock tick. --- cpukit/score/include/rtems/score/scheduleredf.h| 25 ++--- .../score/in

[PATCH 09/16] score: Delete unused _Scheduler_Priority_compare()

By convention, thread priorities must be integers in RTEMS. Smaller values represent more important threads. --- cpukit/score/Makefile.am | 2 - cpukit/score/include/rtems/score/scheduler.h | 6 --- cpukit/score/include/rtems/score/schedulercbs.h| 1 - cpuki

[PATCH 08/16] posix: Generalize _POSIX_Priority_To_core()

Move POSIX API priority validation into _POSIX_Priority_To_core(). --- cpukit/posix/include/rtems/posix/priorityimpl.h | 29 +++-- cpukit/posix/src/mutexinit.c| 4 +--- cpukit/posix/src/mutexsetprioceiling.c | 7 ++ cpukit/posix/src/psxpriorit