Undefined reference to DEBUG_puts in RTEMS 4.8

Aitor.Viana.Sanchez at esa.int Aitor.Viana.Sanchez at esa.int
Mon Sep 17 09:59:05 UTC 2007

Hi all,

i have an error with sparc-rtems- 
that I got from Gaisler research. The RTEMS version within this package is 
4.8 . 
I got a piece of SW already compiled and proved with RTEMS 4.6. When I 
updated to the 4.8 RTEMS version and tried to re-compile the SW I got a 
linker error:

In function `lan91cxx_interrupt_handler':
undefined reference to `DEBUG_puts'

The strange thing here is that the path /home/daniel/reps...etc etc does 
not exist in my machine. I think maybe this is an error of the compiled 
version I got.

any clue?

rtems skyeye <skyeye.rtems at gmail.com> 
Sent by: rtems-users-bounces+aitor.viana.sanchez=esa.int at rtems.org
03/09/2007 16:50

rtems-users at rtems.org, yanmiaobest at gmail.com

SPAM:**** Fwd: design Real-Time Process in RTEMS

  Good idea!
  I think we can first realize the initial VM support in RTEMS.
  because there  are already  some page support funcs in rtems X86 port.
  then we can try syscall,....

---------- Forwarded message ---------- 
From: 阎淼 <yanmiaobest at gmail.com>
Date: Sep 3, 2007 11:21 AM
Subject: Re: design Real-Time Process in RTEMS 
To: rtems skyeye <skyeye.rtems at gmail.com>


   I have been thinking about it too.
   here is what I think:

   1.  page routine should be created to support page manipulations( 
page table operation, TBL, page allocate, set page state ...)
   2.  identify all system call routines
   3.  create entry points and exit points for system call
   4.  adjust context switch ralated routine
   5.  add privilege transition code

   best regards!

2007/8/31, rtems skyeye <skyeye.rtems at gmail.com>:
> hi,
>   VxWorks 6.x have the Real-Time Process (RTP) extension. 
>   I think we also can implement the RTP in RTEMS.
>   The Idea is :
>   1 RTP contains 1~n user-level rtems-task, and process the
> virtual memory related things.
>   2 the mapping relation of virtual memory :phyiscal memory is 1:1 
>   3 the user-level task in RTP can access kernel function
> by syscall
>   4 the user-level tasks and the kernel-level tasks are in the same
> scheduling strategy.
>   the advantage of RTP is: 
>    1 the crash of user-level tasks in RTP can not destroy user-level
> tasks in other RTP and the kernel.
>    2 compatible with the old task model.
>    3 the context switch  is faster than that of general OS (such as 
>    anyone have  some advices on RTP in RTEMS?
> Regards
>   skyeye.rtems
> _______________________________________________
> rtems-users mailing list 
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users

rtems-users mailing list
rtems-users at rtems.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20070917/b0451b8b/attachment-0001.html>

More information about the users mailing list