Embedded arm runing linux

Yoavkarmon wrote:

Hi,
i bought a linux base arm dev kit - devkit8500d , similar to devkit8000 from embest.

the board specification is interesting. Rich in features.

I got the board that it allready running linux kernel 2.6.

good. You are lucky for not getting with WinCE

1. I am unable to connect to it using telnet or ssh.

1. First, you need to ensure the telnet and SSH are enabled. Since you have terminal access, that will be dead easy to check. And as mfillpot mentioned, you may need to change the config file. If you found difficult, feel free to get back here with your config files of both. But, SSH is safer than telnet.

2. Then you need to ensure, your system and the board are in same class of IP family. that is, ip address and netmask should be configured correctly. And gateway can be your system or board ip itself.

3. Then try with "ping" command to board IP from system and from board to system IP. If possible, try to post, " /etc/hosts" file.

2.dont know how to imstall gcc on the board.

Can you please a bit clear. Are you want to
1. code and compile in the board itself
or
2. want to run the assembler output [ binary output of c code ], in the board.

Depending on that the procedure will change.
But, my personal opinion, you can do cross compile procedure. That is, do the coding in your system then just run the executables in the board, which saves lot of space in the board and work load in the board will get reduced to a notable one.

And again, the board specification is excellent. You can do so many things.

Yoavkarmon wrote:

2. how do i ensure the telnet and SSH are "enabled"?

1. you told that you can able to open the terminal, right ? . Just do that.
2. login as root
3. then
*

# cd /usr/bin
# chmod 0755 ssh

i can see that telnetd on user space, but when i try to connect from my pc, to the board i get "connection refused".

since you have 2.6 kernel, by default telnet is disabled. But, you can use SSH instead.

i want to download the SSH source code-> compile it using cross compiler -> download it the the board.

I guess 2.6 has ssh by default. You need to enable as mentioned previously.

a.download the source code

yes you have to. if ssh not in board. But, I am sure it will be there. And if you want, you have to download for ARM architecture not for intel/AMD and so on.
I am running with slow internet connection, so I can not give you exact link to download. But, google will help you to get ssh for ARM.

b. compile it on the cross compiler using "make" -> how do i make sure it will be compiled to arm?

you need ssh package which is built for ARM

c. then do make install -> but it will install it on the host PC not on target, should i copy it to the target and then run "make install"?

you need to transfer the package using ftp to the board. then from your terminal of the board you can install the package.
If you are using Windows OS , you can use filezila to transfer the package to the board using board IP.

I guess, all the procedures are supposed to be with the board package box. Any CD or hardcopy guide is included ?
Feel free to get back here.

* regarding ssh enable procedure, I guess that ' chmod ' command is enough. If not working, let us to see your config file of ssh. And we have more Admin people here. They will help you more .

Generally the source code is the same as x86, you only need to configure the build for your selected architecture.

http://ftp.slackware.org.uk/armedslack/armedslack-13.37/source/n/openssh/openssh.SlackBuild has an example of the build flags needed to build openssh on an ARM processor.

Yoavkarmon wrote:

Code:




1.no ssh on /usr/bin

interesting. Need to dig more in file structure.

2. how do i enable telnet?

1.

# chmod 0755 /bin/telnet

2. then open , "/etc/inetd.conf" , using

# vi  /etc/inetd.conf

as a root user.
[ Now, you should be careful, since you have opened one important file as a root user. ]

3. look for the word " telnet " and that line should be commented, by adding " # " at the beginning.

4. after you found that line , you just remove the " # " in that line.

5. then reboot the board .

6. To ensure the telnet working state, after powered up , give

#telnet localhost

or

#telnet 127.0.0.1

that should ask for user name and password . thats it.

Then after that, you can use telnet to communicate with the board.

Note: Please make sure, you did not made any other changes in inetd.conf file. Or else, I suggest you to make copy of that for safer side.

#cp /etc/inetd.conf <your_destination>

chekkizhar wrote:

mfillpot wrote:

Generally the source code is the same as x86, you only need to configure the build for your selected architecture.

http://ftp.slackware.org.uk/armedslack/armedslack-13.37/source/n/openssh/openssh.SlackBuild has an example of the build flags needed to build openssh on an ARM processor.

Great and thanks for the link.
If possible, using a simple Slackware script can you please explain it step by step in a blog post.
I really want to know more regarding the scripts, which will be easier to solve ,most of the situations. And, without any doubt, that will help the New Slackware users to know more about the system functionalities by going through concern scripts.

Thank you for the recommendation, I think I will write a quick post using the slackbiuld example scripts to explain how a slackbuild is structured so people can learn to use them as learning tools..

Yoavkarmon wrote:

results:
1.

---

[email protected]:~# telnet 127.0.0.1
telnet: cannot connect to remote host (127.0.0.1): Connection refused

---

its because, telnet should be enabled . Means, in the inetd.conf file, that step must be done. Since you are saying, you can not able to find that file itself, its difficult .

2.cant find etc/inetd.conf

1. Try to find that file.Start from directory, " / " . Not direct "etc" , its "/etc" It should be there to support network related stuff. And, didn't you received any guide or procedure from the board vendor ?
2. On sunday I will spend time for your board problem and will try to help you more regarding this.

what next?

yeh, meanwhile try giving,

# cd /etc
#grep telnet *

and post the output .

You can also look at http://www.gumstix.com/ for modular open source hardware that when combined can offer many of the same attributes.