On 03/21/2012 05:46 AM, Glen Wernersbach wrote:
I am going to start trying to see if I can figure out what is not getting
set.
You could get useful information from the pipeline tracer, by enabling
CONFIG_IPIPE_TRACE, observing what exactly happens in kernel space from
the issuing of the ioctl() syscall until the the read() syscall on the
serial link.
You could set markers using Xenomai's I-pipe trace API in userland to
highlight portions of interest in your app code, freezing the capture to
snapshot a particular moment in the execution timeline. See
http://xenomai.org/index.php/I-pipe:Tracer.
NOTE: pay attention to the value in /proc/ipipe/trace/back_trace_points
to hold enough data.
By the way. This board also has 4 other serial ports on a 8250.c driver. It
also fails under the xeno build.
On 3/20/12 4:35 PM, "Gilles Chanteperdrix"
<[email protected]> wrote:
On 03/20/2012 09:19 PM, Glen Wernersbach wrote:
I actually think in is in the settings because if run just the setup part of
the code without reading and writing, on the kernel that works my activity
LED turns off.
On the xeno kernel the LED never changes.
I actually think that CONFIG_XENO_OPT_PERVASIVE does not make any
difference which could cause a difference of hardware behaviour. So, it
must be another option triggered by this config change. So, if you want
us to help you, please post the .configs.
--
Philippe.
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
