I withdraw the question.
Calling rt_dev_open() with "rtser0" is sufficient.
Cheers.
Am 16.10.20 um 16:09 schrieb Johannes Holtz via Xenomai:
Hi,
I work with an old i686 2.6 Xenomai.
As per documentation I note my interface details:
setserial /dev/ttyS0
/dev/ttyS0, UART: 16
Hi,
I work with an old i686 2.6 Xenomai.
As per documentation I note my interface details:
setserial /dev/ttyS0
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
Then remove the default driver:
setserial /dev/ttyS0 uart none
and insert the xenomai driver
modprobe xeno_16550A io=0x3f8 irq=4
Am 08.01.20 um 12:50 schrieb Jan Kiszka:
On 08.01.20 12:40, Johannes Holtz wrote:
Am 07.01.20 um 13:50 schrieb Jan Kiszka:
On 07.01.20 11:42, Johannes Holtz via Xenomai wrote:
Hi,
after a long and exhausting year I finally found time to experiment
on migrating our application from Xenomai
Am 07.01.20 um 13:50 schrieb Jan Kiszka:
On 07.01.20 11:42, Johannes Holtz via Xenomai wrote:
Hi,
after a long and exhausting year I finally found time to experiment
on migrating our application from Xenomai 2.6.4 to Xenomai 3.
So I downloaded the latest stable release 3.0.10 and somehow
Hi,
after a long and exhausting year I finally found time to experiment on
migrating our application from Xenomai 2.6.4 to Xenomai 3.
So I downloaded the latest stable release 3.0.10 and somehow found out I
can't use the 4.19 ipipe kernel but the 4.14 so i also got that.
patched, build,
Am 18.10.19 um 18:00 schrieb Johannes Holtz:
Am 18.10.19 um 17:36 schrieb Jan Kiszka:
On 18.10.19 17:13, Johannes Holtz via Xenomai wrote:
Am 18.10.19 um 16:57 schrieb Jan Kiszka:
On 18.10.19 16:47, Johannes Holtz via Xenomai wrote:
Am 18.10.19 um 16:33 schrieb Jan Kiszka:
On 18.10.19 16:10
Am 18.10.19 um 17:36 schrieb Jan Kiszka:
On 18.10.19 17:13, Johannes Holtz via Xenomai wrote:
Am 18.10.19 um 16:57 schrieb Jan Kiszka:
On 18.10.19 16:47, Johannes Holtz via Xenomai wrote:
Am 18.10.19 um 16:33 schrieb Jan Kiszka:
On 18.10.19 16:10, Johannes Holtz via Xenomai wrote:
Hi ,
I
Am 18.10.19 um 16:33 schrieb Jan Kiszka:
On 18.10.19 16:10, Johannes Holtz via Xenomai wrote:
Hi ,
I inherited a project where the RTnet stack is loaded manually at boot
time. To be specific. Instead of using the rtnet command line programs
the rtnet.ko kernel object as well as the necessary
Hi ,
I inherited a project where the RTnet stack is loaded manually at boot
time. To be specific. Instead of using the rtnet command line programs
the rtnet.ko kernel object as well as the necessary drivers are loaded
with insmod. The devices are then brought up with rtifconfig and rtroute.
Hi,
My program opens a RTnet socket successfully but the program gets killed
by a different issue that has nothing to do with this. However, the
RTnet socket is still bound. If I try to start the program again i get
the error "Address already in use". If it would be a normal unix socket
I
Hi,
While sending a multitude of SDOs via RTcan I get some EMSGSIZE errors.
There is no obvious pattern to the occurrences and most of the messages
are sent OK. I checked the parameters that I use and each frame is send
with the same size ( sizeof(can_frame_t) ) and each frame has a dlc of 8.
Preface:
Xenomai 2.6
Vanilla kernel 3.8.13 i686
RTnet 0.9.13
I have two PCs (M and S) connected via Ethernet exclusively for RTnet use.
M--[switch]---S
M's NIC is driven by the rt_r8169 driver
S's NIC by the rt_e1000 driver
The problem is that the connection is unstable and about 80% of
Am 12.02.19 um 18:53 schrieb Wolfgang Grandegger:
Am 12.02.19 um 18:24 schrieb Johannes Holtz:
Am 12.02.19 um 18:05 schrieb Wolfgang Grandegger:
Am 12.02.19 um 16:19 schrieb Johannes Holtz:
Am 12.02.19 um 16:00 schrieb Wolfgang Grandegger:
Hello Johannes,
Am 12.02.19 um 15:38 schrieb
Am 12.02.19 um 18:05 schrieb Wolfgang Grandegger:
Am 12.02.19 um 16:19 schrieb Johannes Holtz:
Am 12.02.19 um 16:00 schrieb Wolfgang Grandegger:
Hello Johannes,
Am 12.02.19 um 15:38 schrieb Johannes Holtz:
Am 12.02.19 um 12:24 schrieb Wolfgang Grandegger:
Hello,
Am 12.02.19 um 11:42
Am 12.02.19 um 16:00 schrieb Wolfgang Grandegger:
Hello Johannes,
Am 12.02.19 um 15:38 schrieb Johannes Holtz:
Am 12.02.19 um 12:24 schrieb Wolfgang Grandegger:
Hello,
Am 12.02.19 um 11:42 schrieb Johannes Holtz:
Am 11.02.19 um 17:46 schrieb Wolfgang Grandegger:
... snip ...
UI suggest to
Am 12.02.19 um 12:24 schrieb Wolfgang Grandegger:
Hello,
Am 12.02.19 um 11:42 schrieb Johannes Holtz:
Am 11.02.19 um 17:46 schrieb Wolfgang Grandegger:
... snip ...
UI suggest to write a simple test program to demonstrate the issue. It
should just open the socket and trying to receive
Am 12.02.19 um 12:24 schrieb Wolfgang Grandegger:
Hello,
Am 12.02.19 um 11:42 schrieb Johannes Holtz:
Am 11.02.19 um 17:46 schrieb Wolfgang Grandegger:
... snip ...
UI suggest to write a simple test program to demonstrate the issue. It
should just open the socket and trying to receive
Holtz:
Am 11.02.19 um 13:40 schrieb Wolfgang Grandegger:
Hello,
Am 11.02.19 um 12:55 schrieb Johannes Holtz:
Am 11.02.19 um 12:26 schrieb Wolfgang Grandegger:
Hello,
Am 11.02.19 um 10:16 schrieb Johannes Holtz via Xenomai:
Hi,
In my application i set up a RTCAN socket and a pair of rt-threads
Holtz:
Am 11.02.19 um 12:26 schrieb Wolfgang Grandegger:
Hello,
Am 11.02.19 um 10:16 schrieb Johannes Holtz via Xenomai:
Hi,
In my application i set up a RTCAN socket and a pair of rt-threads.
One
to read and one to write. Writing works perfectly and I receive
answers
in the initial phase
Am 11.02.19 um 12:14 schrieb Philippe Gerum:
On 2/11/19 10:16 AM, Johannes Holtz via Xenomai wrote:
Hi,
In my application i set up a RTCAN socket and a pair of rt-threads. One
to read and one to write. Writing works perfectly and I receive answers
in the initial phase of the program
Am 11.02.19 um 13:40 schrieb Wolfgang Grandegger:
Hello,
Am 11.02.19 um 12:55 schrieb Johannes Holtz:
Am 11.02.19 um 12:26 schrieb Wolfgang Grandegger:
Hello,
Am 11.02.19 um 10:16 schrieb Johannes Holtz via Xenomai:
Hi,
In my application i set up a RTCAN socket and a pair of rt-threads
Am 11.02.19 um 12:26 schrieb Wolfgang Grandegger:
Hello,
Am 11.02.19 um 10:16 schrieb Johannes Holtz via Xenomai:
Hi,
In my application i set up a RTCAN socket and a pair of rt-threads. One
to read and one to write. Writing works perfectly and I receive answers
in the initial phase
Am 11.02.19 um 12:14 schrieb Philippe Gerum:
On 2/11/19 10:16 AM, Johannes Holtz via Xenomai wrote:
Hi,
In my application i set up a RTCAN socket and a pair of rt-threads. One
to read and one to write. Writing works perfectly and I receive answers
in the initial phase of the program
Am 13.01.19 um 05:08 schrieb Jan Kiszka:
> On 11.01.19 22:55, Johannes Holtz via Xenomai wrote:
>> Hi,
>>
>> I managed to leave some labeled XDDP and IDDP FDs open after a
segfault.
>> Even though the process is killed the resources/FDs are not freed.
Is there a
&
Hi,
I managed to leave some labeled XDDP and IDDP FDs open after a segfault.
Even though the process is killed the resources/FDs are not freed. Is
there a
way to close them or do I have to restart the box?
Cheers,
Johannes
Am 04.12.18 um 14:46 schrieb Jan Kiszka:
On 04.12.18 12:04, Johannes Holtz via Xenomai wrote:
Hello,
When I request a socket with AF_RTIPC I get an EAFNOSUPPORT in return.
int sock = socket(AF_RTIPC, SOCK_DGRAM, IPCPROTO_IDDP);
You likely didn't wrap this posix application to link against
26 matches
Mail list logo
