All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: get the simulator running...
Date: Sat, 18 Mar 2006 18:25:13 +0100	[thread overview]
Message-ID: <441C4279.10800@domain.hid> (raw)
In-Reply-To: <441C2574.4030901@domain.hid>

Jan Kiszka wrote:
> Philippe,
> 
> here are some patches and comments on the simulator "quick"-start
> process. I guess the patches are due to latest changes in trunk, and I
> cannot guarantee that they are clean - but the simulator compiles now.
> 
> Regarding the rest of its build and start process: There are two hidden
> requirements, namely gcc < 4 (due to -fwritable-strings)

Normally, availability of --fwritable-strings should be auto-detected by 
the configure script. So there is something wrong going there, I will 
look at it.

  and gdb 5.x. A

I've been unlucky with GDB 6.x too, but did not check the latest 
release; I'm currently using 5.3 when running simulations.

> note in sim/README about them would be great. Or do you have a fix for
> those issues scheduled?

--fwritable-strings should be fixed. I'm not sure if the requirement for 
GDB 5.x still applies though.
> 
> Well, once you got this far (i.e. the xenoscope is built and an ancient
> gdb has been prepared), the next step is to produce a test program. Am I
> overseeing some example?

Look into ksrc/skins/{vxworks,psos+}/demos. The Makefile also produces a 
simulation executable for satch. Then run "xenoscope satch_sim"

  Fortunately, I had that demo I once produced
> (last year), but that one was easier to build. I first had to drag in
> the libs and includes of both the simulator and a regular xenomai
> installation (I think to remember this once worked without this
> add-ons). Then I need this additional trick in the simulators include dir:
> 
> mkdir asm
> ln -s <xeno-inst-dir>/include/asm-sim asm/xenomai
> 
> This maps #include <asm/xenomai/system.h> to the correct "arch".
> Shouldn't this be created automatically during the simulator
> installation? Or is something else broken on my box?
> 

You clearly should not need this trick to compile apps against the 
simulation environment; the instrumenter (gcic) sets the proper flags. 
I'm going to rebuild one and let you know.

> In case there is no demo prepared, I could pack my own tiny stuff and
> submit it.
> 
> Jan
> 
> 
> ------------------------------------------------------------------------
> 
> Index: ksrc/skins/vxworks/msgQLib.c
> ===================================================================
> --- ksrc/skins/vxworks/msgQLib.c	(Revision 742)
> +++ ksrc/skins/vxworks/msgQLib.c	(Arbeitskopie)
> @@ -199,7 +199,7 @@
>      appendq(&wind_msgq_q, &queue->link);
>      xnlock_put_irqrestore(&nklock, s);
>      
> -#ifdef CONFIG_XENO_OPT_REGISTRY
> +#ifdef CONFIG_XENO_EXPORT_REGISTRY
>      sprintf(queue->name,"mq%lu",msgq_ids++);
>  
>      if (xnregistry_enter(queue->name,queue,&queue->handle,&msgq_pnode))
> @@ -208,7 +208,7 @@
>  	msgQDelete((MSG_Q_ID)queue);
>  	return 0;
>  	}
> -#endif /* CONFIG_XENO_OPT_REGISTRY */
> +#endif /* CONFIG_XENO_EXPORT_REGISTRY */
>  
>      return (MSG_Q_ID) queue;
>  }
> Index: ksrc/skins/vxworks/wdLib.c
> ===================================================================
> --- ksrc/skins/vxworks/wdLib.c	(Revision 742)
> +++ ksrc/skins/vxworks/wdLib.c	(Arbeitskopie)
> @@ -123,7 +123,7 @@
>      appendq(&wind_wd_q,&wd->link);
>      xnlock_put_irqrestore(&nklock, s);
>  
> -#ifdef CONFIG_XENO_OPT_REGISTRY
> +#ifdef CONFIG_XENO_EXPORT_REGISTRY
>      sprintf(wd->name,"wd%lu",wd_ids++);
>  
>      if (xnregistry_enter(wd->name,wd,&wd->handle,&wd_pnode))
> @@ -132,7 +132,7 @@
>  	wdDelete((WDOG_ID)wd);
>  	return 0;
>  	}
> -#endif /* CONFIG_XENO_OPT_REGISTRY */
> +#endif /* CONFIG_XENO_EXPORT_REGISTRY */
>  
>      return (WDOG_ID) wd;
>  }
> Index: ksrc/skins/vxworks/semLib.c
> ===================================================================
> --- ksrc/skins/vxworks/semLib.c	(Revision 742)
> +++ ksrc/skins/vxworks/semLib.c	(Arbeitskopie)
> @@ -479,7 +479,7 @@
>      xnlock_get_irqsave(&nklock, s);
>      appendq(&wind_sem_q,&sem->link);
>      xnlock_put_irqrestore(&nklock, s);
> -#ifdef CONFIG_XENO_OPT_REGISTRY
> +#ifdef CONFIG_XENO_EXPORT_REGISTRY
>      sprintf(sem->name,"sem%lu",sem_ids++);
>  
>      if (xnregistry_enter(sem->name,sem,&sem->handle,&sem_pnode))
> @@ -488,7 +488,7 @@
>  	semDelete((SEM_ID)sem);
>  	return 0;
>  	}
> -#endif /* CONFIG_XENO_OPT_REGISTRY */
> +#endif /* CONFIG_XENO_EXPORT_REGISTRY */
>  
>      return (SEM_ID) sem;
>  }
> Index: include/asm-sim/system.h
> ===================================================================
> --- include/asm-sim/system.h	(Revision 742)
> +++ include/asm-sim/system.h	(Arbeitskopie)
> @@ -80,6 +80,7 @@
>  
>  #define XNARCH_DEFAULT_TICK         10000000 /* ns, i.e. 10ms */
>  #define XNARCH_HOST_TICK            0 /* No host ticking service. */
> +#define HZ                          0 /* dummy define for HZ */
>  
>  #define XNARCH_THREAD_STACKSZ 0 /* Let the simulator choose. */
>  #define XNARCH_ROOT_STACKSZ   0	/* Only a placeholder -- no stack */


-- 

Philippe.


  parent reply	other threads:[~2006-03-18 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 15:21 [Xenomai-core] get the simulator running Jan Kiszka
2006-03-18 17:01 ` Gilles Chanteperdrix
2006-03-18 17:23   ` Jan Kiszka
2006-03-18 17:25 ` Philippe Gerum [this message]
2006-03-18 17:33   ` [Xenomai-core] " Philippe Gerum
2006-03-18 18:37     ` Jan Kiszka
2006-03-18 18:45       ` Philippe Gerum
2006-03-18 18:56         ` Jan Kiszka
2006-03-19 12:08           ` Philippe Gerum
2006-03-19 12:48             ` Jan Kiszka
2006-03-18 17:30 ` Philippe Gerum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=441C4279.10800@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.