VxWorks lkup?
hadi motamedi
To find a command on my VxWorks , I can try as the followings :
->lkup "ss7"
It will list the commands having say 'ss7' keyword in their syntax .
But how can I get manual help on an intended command ? Please let me
know .
Regards
Gary Johnson
Depending on the type of host on which your VxWorks development tools
are installed, this may work when executed on the development system:
MANPATH=$WIND_BASE/man man name
where 'name' is the name of the command.
Also, depending on the version of VxWorks you're running, you may be
able to switch to an alternate target or host shell by executing
cmd
in your VxWorks shell. That will give you a Unix-shell-like command
line. Some commands will print a page of help to the screen if you just
type their name or their name followed by -h. I'd give you an example,
but I don't have a VxWorks target running at the moment.
You can get back to the original C-interpreter command line by executing
C
--
Gary Johnson
hadi motamedi
Thanks for your reply . I am using VxWorks 5.4.2 and the (lkup "cmd")
does not return a pure cmd command . Can you please draw what are my
options on this VxWorks version here ? And please let me know how can
I distinguish the VxWorks commands from the lkup output ? I mean it
will list all of the global parameters and the commands that contain
the specific character strings indicated in the lkup body , so how to
differentiate between the pramaters and the commands ?
Gary Johnson
I'm not very familiar with the differences among VxWorks versions. We
used to run 5.x and I never used "cmd" with those versions, so I don't
think it existed then. We now run 6.6 and "cmd" is available there.
I don't think 5.x has any documentation available at the VxWorks shell
prompt other than "help".
Commands should be in the text segment while variables should be in the
bss or data segment. The segment is given in the third column of the
"lkup" output, at least when using VxWorks 6.6. I thought that column
was included in the output of the 5.x "lkup", too, but I'm not sure.
Getting back to the original question: I would poke around in the
directory hierarchy where VxWorks was installed on your development
system and see if you can find a man or doc directory. I prefer man
pages so that's what I use with 6.6, but I think a lot of the 5.x
documentation was in HTML.
If you can't find any other documentation, you can revert to reading the
source code, if you have access to that. It's OK for parameters, not so
good for behavior.
I should mention that while I'm somewhat familiar with the VxWorks
environment installed where I work, I have no idea what variations are
available from Wind River or whether our installation is typical.
--
Gary Johnson