Getting version of rtems, and writing files

Wed Oct 23 19:11:30 UTC 2019

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.

On Thu, Oct 17, 2019 at 11:22 AM Peter Dufault <dufault at hda.com> wrote:

>
>
> > On Oct 17, 2019, at 02:07 , Chris Johns <chrisj at rtems.org> wrote:
> >
> > On 17/10/19 4:20 am, Shane Thomas wrote:
> >> I had a question, I inherited a system that uses rtems
> >
> > Welcome.
> >
> >> and I am not sure how to
> >> edit files on that system.   There is no vim or vi.  I telnet into them
> and then
> >> get a message right away that says:
> >>
> >> cexp.help() for help (which does't work) but help() does show some
> commands like
> >> cat, pwd, home, mod = ld("filename")
> >
> > The cexp shell is a 3rd party shell package that is not formally part of
> RTEMS.
> > A lot of people use it however I do not and do not know anything about
> it. Sorry.
> >
> >> etc...
> >> but nothing that would let me edit files that are on that system.  Also
> no
> >> ftp/sftp to let me edit locally and then move them to that system.   I
> am not
> >> sure the version of rtems this is running even (not sure how to get
> that).
> >>
> >> Signed up to this mailing list just to ask this question, not sure what
> >> else/where else to look.
> >
> > I use the shell RTEMS provides in the cpukit/libmisc/shell directory and
> we have
> > documented, see docs.rtems.org and click on the shell documents.
> >
> > To transfer files on to and off boards I set up a machine in the lab as
> an NFS
> > server and then mount it in RTEMS using the mount command:
> >
> > $ cd /
> > $ mkdir net
> > $ mount -t nfs foo:/bar /net
> >
> > If I need to edit text files on a target I add the `edit` shell command.
> It is
> > OK at performing small editing tasks on the target. Saving, exiting etc
> are
> > mapped to function keys.
> >
> > I hope this helps.
> >
> > Chris
> > _______________________________________________
> > users mailing list
> > users at rtems.org
> > http://lists.rtems.org/mailman/listinfo/users
>
> "cexpr()" originated at SLAC (Stanford Linear Accelerator) and is
> frequently used as part of the EPICS (https://epics.anl.gov) system.
> "cexpr()" is a "C" language expression parser, for better or worse, so you
> can call any C function from the command line.  Be sure to include the
> decimal point (3.0 not 3) if you're passing a floating point!
>
> The 'mod = ld("filename")' message shows it supports dynamic loading as
> well.
>
> Typically you do not edit files on those systems.  Usually the will use
> NFS to mount remote file systems so that you can edit files on the host
> system.  Try 'lkup("mount")'
>
> Are you sure there isn't an RTEMS version in the boot-up text?  I have
> access to an old system that uses "cexpr()" and it prints out the version:
>
>    Welcome to rtems-4.7.1(PowerPC/PowerPC 7455/beatnik) ($Name:
> R_beatnik_20060214 )
>    Build Date: Sat Sep 22 14:10:53 EDT 2007
>    Board Type: MVME5500-0161 (S/N E1834D9)
>
> Here's an example of using "cexpr()" to figure out the version on that
> system:
>
> ------
> cexp_main>lkup("version")
> =====  In module 'SYSTEM' (0x01ad43d8) =====:
>   0x20fa3c[     0]: VOID                          void
> _RTEMS_version
>   0x271028[     0]: VOID                          void
> __fdlib_version
>    0xdaf1c[     4]:                               long (*)()
> _bfd_elf_slurp_version_tables
>
> USER VARIABLES:
> 0x00000000 (0)
> cexp_main>printf("%s\n",(char *)&_RTEMS_version)
> rtems-4.7.1(PowerPC/PowerPC 7455/beatnik)
> 0x0000002a (42)
> cexp_main>
> -----
>
> - Do you have the source?
> - Can you say what the board support package and application are?
>
> 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/20191023/43d99d24/attachment-0001.html>