On Mon, Oct 21, 2019, 6:30 PM Shane Thomas <code...@gmail.com> wrote:
> I don't see anything that looks like source, found a server that has some
> RTEMS folders on it (where the source might of been?) but all that is left
> is a .img file, and a folder full of notes on RTEMS. Looks like from what
> I see though the version might be 4.6, or 4.7 if that even is in the realm
> of reality?
>
All of that makes sense and is within the realm of possibility. Both 4.6
and 4.7 are quite old with both being a decade or more old from memory.
There are challenges starting from scratch with versions that old primarily
because the gcc, etc associated with them are correspondingly old.
I suspect you are looking at a boot server and the .img file is a boot
image. That's normal for RTEMS. The source was built on another computer
into that image.
Any chance there is a software repository somewhere?
After that, archaeology is an option. Finding out who built the system
would help you a lot. Is there anyone left who knows?
>
>
> On Mon, Oct 21, 2019 at 4:15 PM Joel Sherrill <j...@rtems.org> wrote:
>
>>
>>
>> On Mon, Oct 21, 2019, 6:00 PM Shane Thomas <code...@gmail.com> wrote:
>>
>>> I am suspect it is running cexp, it says to type that but typing that
>>> gives me a cexp error, though typing help() works and gives this for a help
>>> command, which seems to be missing the mount method :(
>>> (also Peter Dufault recommended using ikup("mount") but that yielded no
>>> command either). cexpr() failed as a command too. The login showed:
>>>
>>> telnet 10.50.1.111
>>>
>>> Trying 10.50.1.111...
>>>
>>> Connected to 10.50.1.111.
>>>
>>> Escape character is '^]'.
>>>
>>> Password:
>>>
>>> [Telnet:] starting cexp on /dev/pty0
>>>
>>> Type 'cexp.help()' for help (no quotes)
>>>
>>> cexp.help() though is a lie, but help() produces the following:
>>> (Somewhere the source code has to be abound but not sure where, we got
>>> no documentation from outgoing IT).
>>>
>>>
>>> alt-rotator>help()
>>>
>>>
>>> Module commands:
>>>
>>> mod = ld("filename") - load filename object and return handle for
>>> unld()
>>>
>>> lsmod() - list loaded modules and their handle
>>>
>>> unld(mod) - unload inactive module by its handle
>>>
>>>
>>> Files and directories:
>>>
>>> cat(filename) - copy file to screen
>>>
>>> cd(path)
>>>
>>> copy(filename,filename) - usually used to install files from /rtems
>>> to /apo
>>>
>>> ls()
>>>
>>> home() - change directory to $HOME. Right now /apo
>>>
>>> mkdir(path)
>>>
>>> new_rtems()
>>>
>>> pwd()
>>>
>>> rm(filename)
>>>
>>>
>>> System:
>>>
>>> i
>>>
>>> memShow
>>>
>>> reboot
>>>
>>> stackShow
>>>
>>> top
>>>
>>>
>>> Network:
>>>
>>> icmpShow - display ICMP packet statistics
>>>
>>> ifShow - display statistics gathered by network interfaces
>>>
>>> ipShow - display IP packet statistics
>>>
>>> mbufShow - display mbuf statistics
>>>
>>> routeShow - display the routing table
>>>
>>> tcpShow - display TCP packet statistics
>>>
>>> udpShow - display UdP packet statistics
>>>
>>>
>>>
>>>
>>>
>> The bottom groups are names of VxWorks functions which hints there are
>> pieces of cexp in there.
>>
>> Do you have the source? I don't recall that being answered in the thread.
>>
>> Also running strings on the executable might turn up the version string.
>>
>>>
>>>
>>> On Thu, Oct 17, 2019 at 12:07 AM Chris Johns <chr...@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@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/users
>>
>>
_______________________________________________
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
