Discussions among users of RTEMS real-time executive

headers manish jain | 22 May 2013 18:35

_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

Hello,

I've been working the bsp for the mvme177. It's looking pretty good at 
this point.

Currently, I'm trying to get rshell to work. After some debugging I find 
that the "spawned_shell()" function
in "telnetd.c" is trying to open "/dev/pty0" and failing. I tried to do 
a simple "fopen("/dev/pty0", "r+")" within
"main.c" and that fails as well.

Here are my configs from "main.c": The "CONFIGURE_SHELL..." stuff is 
commented out here, but enabled in another file.

/* configuration information */

#define CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER // need this for "sleep()"
#define CONFIGURE_APPLICATION_NEEDS_LIBBLOCK
#define CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER
#define CONFIGURE_APPLICATION_NEEDS_NULL_DRIVER // experimental 20130518

#define CONFIGURE_LIBIO_MAXIMUM_FILE_DESCRIPTORS 20
#define CONFIGURE_USE_IMFS_AS_BASE_FILESYSTEM

#define CONFIGURE_NUMBER_OF_TERMIOS_PORTS       4

#define CONFIGURE_EXECUTIVE_RAM_SIZE            (32 * 512*1024)

#define CONFIGURE_MEMORY_OVERHEAD               256 // this is in kbytes!!

#define CONFIGURE_MESSAGE_BUFFER_MEMORY         (256 * 1024)

#define CONFIGURE_MAXIMUM_SEMAPHORES            40
#define CONFIGURE_MAXIMUM_TASKS                 20
#define CONFIGURE_MAXIMUM_MESSAGE_QUEUES        20
#define CONFIGURE_MAXIMUM_PTYS                  10       // needed for 
telnet
#define CONFIGURE_MAXIMUM_DRIVERS               10

#define CONFIGURE_MINIMUM_TASK_STACK_SIZE       (64 * 1024) // more bigger

#define CONFIGURE_INIT_TASK_STACK_SIZE          (16*1024)
#define CONFIGURE_INIT_TASK_PRIORITY    120
#define CONFIGURE_INIT_TASK_INITIAL_MODES (RTEMS_PREEMPT | \
                                            RTEMS_NO_TIMESLICE | \
                                            RTEMS_NO_ASR | \
                                            RTEMS_INTERRUPT_LEVEL(0))

#if 0
#define CONFIGURE_POSIX_INIT_THREAD_TABLE
#endif
#define CONFIGURE_RTEMS_INIT_TASKS_TABLE

#define CONFIGURE_INIT

#include <rtems/confdefs.h>

//#define CONFIGURE_SHELL_USER_ALIASES &Shell_USERECHO_Alias
//#define CONFIGURE_SHELL_COMMANDS_INIT
//#define CONFIGURE_SHELL_COMMANDS_ALL
//#define CONFIGURE_SHELL_COMMANDS_ALL_NETWORKING

#include <rtems/shellconfig.h>

Help appreciated.

Robert W.
_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

Hello,

I've executed paranoia test on 3 personal computers and on all of
them, I get the following result at the end:
"The number of  FAILUREs  encountered =       4.
The number of  SERIOUS DEFECTs  discovered = 5.
The number of  DEFECTs  discovered =         3.
The number of  FLAWs  discovered =           2.

The arithmetic diagnosed has unacceptable Serious Defects.
Potentially fatal FAILURE may have spoiled this program's subsequent diagnoses."

This is while the test runs perfectly on LPC3250 and here is the result:
"No failures, defects nor flaws have been discovered.
Rounding appears to conform to the proposed IEEE standard P754.
The arithmetic diagnosed appears to be Excellent!"

I wonder is there any consideration I'm missing for x86 platform!?
As far as I know, stack overflow, and floating point exception
handlers not being installed are possible reasons of failure. Am I
doing something wrong?

Thanks
SAeeD
_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

Arrow recently notified my client using the MVME5500 that it is end-of-life with a last order coming up in
June.  I told them to check if the situation is the same for the MVME6100.

Is there anyone else using PowerPC, VME, and RTEMS that has a similar issue and what are you thinking of?  My
thinking is that since you can still get MVME167 boards without too much trouble my client should start a
migration to a modern architecture, away from VME, to complete over the next few years.  If the MVME6100
isn't end-of-life then switch to that during the change-over, if not just stick with the MVME5500 during
the change.

Or is there something special about the availability of old boards like the MVME167 that doesn't apply to
the MVME5500?

Peter
-----------------
Peter Dufault
HD Associates, Inc.      Software and System Engineering

_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

Hello,

as we have announced before, we will have another open RTEMS class in
Munich/Germany in the time of

		June 25 - June 28 2013.

Maybe you or some of your colleagues like to join in? See our updated
website

http://www.embedded-brains.de/index.php?id=rtems_class&L=1

for more details.

Please note, that the closing date for registrations is May, 22th 2013,
so if you would like to attend, NOW is the right time to register 

Please send us an email or use the website form if you and/or your
colleagues are interested to attend, so we can reserve seats for you.

wkr,
Thomas Doerfler.

--

-- 
--------------------------------------------
embedded brains GmbH
Thomas Doerfler
Dornierstr. 4
D-82178 Puchheim
Germany
email: Thomas.Doerfler@...
Phone: +49-89-18 94 741-12
Fax: +49-89-18 94 741-09
PGP: Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

_______________________________________________
rtems-users mailing list
rtems-users@...
http://www.rtems.org/mailman/listinfo/rtems-users

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

109	May 2013
267	April 2013
202	March 2013
183	February 2013
27	January 2013
32	December 2012
99	November 2012
74	October 2012
132	September 2012
149	August 2012
115	July 2012
61	June 2012
165	May 2012
151	April 2012
264	March 2012
169	February 2012
66	January 2012
94	December 2011
155	November 2011
75	October 2011
115	September 2011
111	August 2011
129	July 2011
91	June 2011
158	May 2011
128	April 2011
235	March 2011
144	February 2011
99	January 2011
49	December 2010
140	November 2010
90	October 2010
92	September 2010
56	August 2010
79	July 2010
198	June 2010
144	May 2010
134	April 2010
173	March 2010
111	February 2010
112	January 2010
75	December 2009
106	November 2009
155	October 2009
167	September 2009
59	August 2009
113	July 2009
177	June 2009
130	May 2009
140	April 2009
220	March 2009
175	February 2009
154	January 2009
141	December 2008
125	November 2008
151	October 2008
207	September 2008
168	August 2008
110	July 2008
80	June 2008
270	May 2008
317	April 2008
363	March 2008
151	February 2008
138	January 2008
146	December 2007
191	November 2007
180	October 2007
169	September 2007
194	August 2007
132	July 2007
209	June 2007
255	May 2007
138	April 2007
138	March 2007
152	February 2007
100	January 2007
166	December 2006
187	November 2006
97	October 2006
3	June 2006
21	May 2006
16	April 2006
2	March 2006
29	February 2006
212	September 2005
193	August 2005
151	July 2005
79	June 2005
116	May 2005
40	April 2005
16	March 2005
3	September 2004
1	March 2004
2	December 2003
3	November 2003
4	October 2003
2	June 2003
2	December 2002
2	June 2002

sparc-rtems4.10-gcc linker warning for _start symbol

Unused Variable Error while building binutil-2.20.1

RTEMS-4.10.2 Building Error

Driver Manager for LEON BSP

mvme177: pty's

RTEMS classic timers

Paranoia Test Failure on Personal Computers

mvme5500, PowerPC, VME, and end-of-life issues

Final call: RTEMS open class in Munich/Germany, June 25th 2013

bfin simulator problems

Does the arm gdb support timer?