Re: [Xenomai-help] Analogy cmd_write example explanation

[Alexis Berlemont <berlemont.hauw@domain.hid>]

Hi,

Sorry for answering so late. I took a few days off far from any internet
connection.

It seems you sent many mails related with Analogy. Many thanks for your
interest. I have not read all of them yet. However, I am beginning by
this one (which seems unanswered). The answer is quick and easy :)

Daniele Nicolodi wrote:
> Hello. I'm looking into the analogy cmd_write example.
> 
> I'm not sure I understand the reason for the rt_task_set_mode() function
> call into the data acquisition loop (lines 413 or 464 in the code
> shipped with xenomai 2.5.1).
> 
> I do not understand why we have to set the primary mode at every
> iteration, when we set it before for the task (line 380).
> 
> Is it because the dump_function() uses system calls that can make the
> task to switch to secondary mode, or there is a deeper reason I'm missing?
> 
You are right. The dumping routine triggers a switch to secondary mode.
That is why, the program switches back to primary mode after.

Almost all the Analogy programs (cmd_read, cmd_write, insn_read,
insn_write, insn_bits) are just demonstration examples. That is why the
code is so linear, lengthy and repetitive. Furthermore, the code was not
meant to be efficient. I just wanted to test the RT and NRT entries.

By the way, I started to improve them. One change (which is still
missing) is the use of rtdk.

> Thanks. Cheers,

Alexis.