All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Nicolas SCHURANDO <schurann@ext.essilor.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] VxWorks API on Xenomai 3.0
Date: Thu, 14 Jan 2016 18:24:43 +0100	[thread overview]
Message-ID: <5697D9DB.6070909@xenomai.org> (raw)
In-Reply-To: <CA+CJOCxoqmA1r0sGb_LwqvsXPzMG485YqUmR83hsfT2mTD6xnQ@mail.gmail.com>

On 01/14/2016 10:22 AM, Nicolas SCHURANDO wrote:
> Hello everyone,
> 
> In an attempt to migrate from Xenomai 2.6.4 on a Raspberry Pi 1 to Xenomai
> 3.0.1 on a Raspberry Pi 2, I get an error when trying to spawn a VxWorks
> task in a fairly simple test program. Here is the output :
> 
>    0"000.064| WARNING: [main] Xenomai compiled with full debug enabled,
>>                               very high latencies expected
>> [--enable-debug=full]
>>  [i] [main] Hello, launching root task ...
>>  200"747.521| BUG in wind_task_normalize_priority():
> 
> 
> The corresponding code is :
> 
> int main(int argc, char *argv[]) {
> 
> 
>> /* Hello world */
>> printf(" [i] [%s] Hello, launching root task ...\r\n", __FUNCTION__);
> 
> 
>> /* Spawn root task */
>> taskSpawn("root_task", 100, 0, 16 * 1024, (FUNCPTR) &root_task, 0, 0, 0,
>> 0, 0, 0, 0, 0, 0, 0);
> 
> 
>> [...]
> 
> 
>> }
> 
> 
> I've tracked down the problem to threadobj_high_prio being equal to 0,
> hence the following function expecting priorities from -1 to 0. I however
> have no idea where threadobj_high_prio gets its value from.
> 

Your application is not initializing properly, the Xenomai libs are not
bootstrapped. There are detailed explanations about the init flow here:
http://xenomai.org/2015/05/application-setup-and-init/

-- 
Philippe.


  reply	other threads:[~2016-01-14 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  9:22 [Xenomai] VxWorks API on Xenomai 3.0 Nicolas SCHURANDO
2016-01-14 17:24 ` Philippe Gerum [this message]
2016-01-15  9:57   ` Nicolas SCHURANDO
2016-01-18 11:55     ` Philippe Gerum
2016-01-18 12:34       ` Nicolas SCHURANDO
2016-01-18 15:19         ` Philippe Gerum
2016-01-18 18:15           ` Nicolas SCHURANDO
2016-01-19  8:22             ` Philippe Gerum
2016-01-25 15:37               ` Nicolas SCHURANDO

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=5697D9DB.6070909@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=schurann@ext.essilor.com \
    --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.