Getting version of rtems, and writing files
Shane Thomas
codejoy at gmail.com
Mon Oct 28 21:27:16 UTC 2019
Hello Peter thanks again for the response. A few answers to some questions:
- What is the application? What does "alt-rotator" do?
- I'm really interested: How did you inherit this application and what do
you need to do?
Alt-rotator is the altitude drive of a 3.5m telescope an observatory, I
inherited this system because the last engineer that worked on this retired
and left no documentation. I came on as a Software Engineer inherited many
things, this is one thing that is coming up. We need to edit a flat file
that holds various coefficients on how to move the motors better etc.
Hence the need for my ability to somehow get on this box with more than
telnet or get an editor on it to make these changes to values in the ini
file.
- "cexpr" expects C language a C language compatible command line, your
"mount -t.." command will definitely not work. If you are not a C language
programmer you face a major challenge and will need an awful lot of help to
continue.
- The function I suggested you try wasn't "ikup", it was "lkup". That's
short for "look up". Try 'lkup("mount")' and see what you see.
" If you are not a C language programmer you face a major challenge and
will need an awful lot of help to continue." It has been 10 years or
so...i am guessing the OS "prompt" is more like an interactive c shell
then? I guess it is learning how to use these functions (what arguments to
pass) to make it where we can edit the ini files.
I have been successful at of course using ls, and cd (I can find the INI
files I need to edit), I just had zero idea on how to edit these files, but
the lkup("mount") command already gives me some ideas of how this might be
achieved. Though since this is an active production box I am very scared
to go throwing commands at it and 'learning as I go' since this is the main
system and no backup :o
So I am learning as I go but this is already helping and maybe nudging me
towards that 'aha' moment (I would even settle for the 'oh duh' moment too)
Totally my mistake on ikup vs lkup, when i try lkup("mount")
alt-rotator>lkup("mount")
===== In module 'SYSTEM' (0x04a238dc) =====:
0x1bd2b4[ 4]: long (*)() IMFS_fsunmount
0x1bd970[ 4]: long (*)() IMFS_mount
0x1bdc54[ 4]: long (*)() IMFS_unmount
0x2de044[ 0]: VOID void
RTEMS_Malloc_Sbrk_amount
0x2a950c[ 0]: VOID void
configuration_mount_table
0x1d7e73[ 4]: long (*)()
file_systems_below_this_mountpoint
0x1020d4[ 4]: long (*)()
filesys_fsmount
0x1d41c0[ 4]: long (*)()
init_fs_mount_table
0x1d41e4[ 4]: long (*)() mount
0x2a951c[ 0]: VOID void
rtems_filesystem_mount_table
0x2de094[ 0]: VOID void
rtems_filesystem_mount_table_control
0x2a9520[ 0]: VOID void
rtems_filesystem_mount_table_size
0x1bb4ba[ 4]: long (*)() rtems_fsmount
0x1bb400[ 4]: long (*)()
rtems_fsmount_create_mountpoint
0x1be24e[ 4]: long (*)()
rtems_ftp_mount_me
0x1d7eaa[ 4]: long (*)() unmount
===== In module 'nfs.obj' (0x04a37f70) =====:
0x4aa65ff[ 96]: long (*)() xdr_mountbody
0x4aa6532[ 35]: long (*)() xdr_mountlist
USER VARIABLES:
0x00000000 (0)
On Fri, Oct 25, 2019 at 3:29 PM <dufault at hda.com> wrote:
>
>
> > On Oct 23, 2019, at 15:11 , Shane Thomas <codejoy at gmail.com> wrote:
> >
> > So I think I found the source, there is no ikup command when I am
> telnet'ed in.
> >
> > There is a mount command it seems but I have no idea how to use it, ones
> suggestion of using it as:
> > mount -t nfs foo:/bar /net
> >
> > fails but calling mount("something") fails differently:
> > I am not sure what all the numbers mean from the returning values items
> etc.
> >
> >
> > 0x001d41e4 (1917412)
> > alt-rotator>mount -t nfs 10.50.1.1:/test /test
> > Cexp syntax error: syntax error, unexpected IDENT
> > alt-rotator>mount("")
> > 0xffffffff (-1)
> > alt-rotator>mount
> > 0x001d41e4 (1917412)
> >
> >
> >
> > I also goofed (already) and when I mkdir test i forgot the quotes
> > so I put mkdir(test) and created something I cannot seem to remove :/ .
> (the UWVS?? etc)
> >
> > alt-rotator>ls()
> > 2, 2948b, 0.0 00755 dev/
> > 16, 16384b, 0.0 00000 apo/
> > 12959797, 4096b, 501.501 00775 rtems/
> > 16, 0b, 0.0 00000 UWVS???l$4?|$8??t$<?
> > 17, 0b, 0.0 00000 test/
> >
> >
> > And to the question:
> > - Can you say what the board support package and application are?
> >
> > I am not sure what specifically you mean here, in the folder I found the
> source code (it was messy) i found all these other folders which might be
> packages compiled to it? and the README said to use the rtems-4.7.1 folder
> (where the code is)
> >
> > [root at devel1 tools]# ls
> > build-4.6 cexp-1.5-4.6
> ntp-4.1.1a-rtems-20030127.tar rtems-4.6.99.3.APO
> rtems-4.7.1.APO-RS232-Driver rtems-nfs-1.3
> > build-4.7 cexp-1.5-4.7 openntpd-3.9p1
> rtems-4.6.99.3.ORIG rtems-4.7.3
> rtems-nfs-1.4
> > build-4.7.1 ntp-4.1.1a-rtems-20030127 Python
> rtems-4.7 RTEMS-GeSys_2.1.beta rtemsNfs-1.5
> > build-4.7.1 . ntp-4.1.1a-rtems-20030127.APO README
> rtems-4.7.1 RTEMS-GeSys_2.1.beta-4.6
> rtems-telnetd-1.1.beta
> > cexp-1.5 ntp-4.1.1a-rtems-20030127.OLD rtems-4.6.6
> rtems-4.7.1.APO-Network-Mod RTEMS-GeSys_2.1.beta-4.7 temp
> >
> > Sort of progress, just not sure how or where :D and totally sad I seemed
> to of created a corrupted file on the fs.
> >
> >
> >
>
> You're using something that is tied to what's used in EPICS that dates
> from a while back. I'm not an EPICS user, but I know "GeSys" is some sort
> of "generic system" for RTEMS on EPICS. Again, EPICS is at
> https://epics.anl.gov.
>
> When you executed "mkdir(test)" without quotes around "test" you created a
> directory on whatever you are using as a file system that used the address
> of the symbol "test" as a character string and the "mkdir" function
> dutifully created that directory. Don't worry about that, if you figure
> out how to use the system you can get rid of it. Actually, "rmdir(test)"
> (without quotes around test) will probably remove it.
>
> I'm getting very curious.
>
> - What is the application? What does "alt-rotator" do?
> - "cexpr" expects C language a C language compatible command line, your
> "mount -t.." command will definitely not work. If you are not a C language
> programmer you face a major challenge and will need an awful lot of help to
> continue.
> - I'm really interested: How did you inherit this application and what do
> you need to do?
> - The function I suggested you try wasn't "ikup", it was "lkup". That's
> short for "look up". Try 'lkup("mount")' and see what you see.
>
>
> Peter
> -----------------
> Peter Dufault
> HD Associates, Inc. Software and System Engineering
>
> This email is delivered through the public internet using protocols
> subject to interception and tampering.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20191028/537744ba/attachment-0001.html>
More information about the users
mailing list