Hi Philippe, I switched to branch stable-3.0.x, retrieved your commit b411e4c "lib/cobalt: add init trace points", and rebuilt everything.
Below is what I have with the new --trace option. With static linking : > -- xenomai_init() running > -- cobalt->init() > -- connected to Cobalt > -- memory locked > -- memory heaps mapped > -- boilerplate->init() > 0"000.070| WARNING: [main] Xenomai compiled with full debug enabled, > very high latencies expected > [--enable-debug=full] > -- initialization complete > [i] [main] Hello, launching root task ... > 0"001.747| BUG in wind_task_normalize_priority(): I also decided to try with dynamic linking as well, to see if it was producing anything different : > -- xenomai_init() running > -- cobalt->init() > -- connected to Cobalt > -- memory locked > -- memory heaps mapped > -- boilerplate->init() > -- copperplate->init() > -- vxworks->init() > 0"016.431| WARNING: [rpi-test-bug-wa] low resolution clock disabled > [--enable-lores-clock] > 0"019.474| WARNING: [rpi-test-bug-wa] vxworks_init: failed to > initialize VxWorks clock (res=1000000 ns) > 0"022.093| WARNING: [main] setup call vxworks failed > 0"024.535| BUG in xenomai_init(): [main] initialization failed, EINVAL Regards 2016-01-18 16:19 GMT+01:00 Philippe Gerum <[email protected]>: > On 01/18/2016 01:34 PM, Nicolas SCHURANDO wrote: > > Hi Philippe, > > > > In your previous message you suggested that something might be wrong > > with the way the application is initialized. And my message was an > > attempt at further describing what I had already done. > > > > Oh, I see. I suppose the tense of my message was misleading. I meant > > that I had already read the documentation prior to reaching out to you, > > and the compiler and linker commands above are the one I had already > used. > > > > Are you confirming that the init seems to happen fine ? And if so, what > > could explain the error I get when trying to spawn the VxWorks task ? > > > > The only reason would be that copperplate_init() did not run, which > means that your application init sequence does not work as expected. > > You may want to pick the latest changes from stable-3.0.x, and start > your application with the --trace option. This will trace the init > sequence from xenomai_init() onward. For a VxWorks application based on > the copperplate layer running over Cobalt, you should see something > along these lines: > > # /your/application --trace > -- xenomai_init() running > -- cobalt->init() > -- connected to Cobalt > -- memory locked > -- memory heaps mapped > -- boilerplate->init() > -- copperplate->init() > -- alchemy->init() > -- initialization complete > > If you don't see such output, then something is wrong. > > -- > Philippe. > _______________________________________________ Xenomai mailing list [email protected] http://xenomai.org/mailman/listinfo/xenomai
