Connection error to target through dev rocket
Dileep Raj - June 2, 2011
Dear support,
We have pxa300 based target board.
When we are connecting through devrocket the connection error is showing.
We have check the ping from target to host & host to target both are working fine.
Following error are geting in pop window of devrocket.
Internal error
Reason:
Connection error: Either host name or IP address specified for target is incorrect.Please verify also that the target you are trying to connect to is responding to requests.
Below are the steps we have followed:
1.Windows------> open perspective------->other-------> MontaVista target tools
2.Target ---------> Add new target
3.Name: IP address and clicked on mvlt check box
4.Open New Target Wizard window
Host Name: Target IP address
Description: target name
Device Name : /dev/ttyS0
Baud rate : 115200
device Bits: 8
5.Click on to finish with the default port6. After expanding Target IP address and clicking on to Browse Remot file system-------> /------->
then we are getting the error message after expanding root(/) which is highlighted above
It would be great help if you provide us a solution regarding above conncetion error.
More details please
Hi Dileep,
What version of DevRocket are you using? Is your target running MV Linux, if so, what version? Have you tried following the instructions in the DevRocket documentation, specifically: "Creating a Connection to a Remote MontaVista Linux System"?
Thanks
Bill
SSH is not available over serial
Hi Dileep Raj,
You are attempting to create a connection to the target over serial.
Whilst there is nothing wrong with a connection over serial to monitor output of the console, this is not what the target tools are meant to be used for - and I'll show a better way to do that below.
The target tools are meant to be used over an IP connection with the sshd daemon running on the target. Through ssh we provide you with the file system, the system information and the ability to run remote scripts (to gather processes, memory info and such).
I'm not sure about the version of DevRocket you are using - we haven't shipped a 'target tools' perspective for quite some time. If you are still using DevRocket 2 and have a current subscription, be sure to update to DevRocket 5.2.2 - it works with your platform too.
If you just want a serial console in DevRocket 5.1 or later, do this:
Connecting error to DevRocket
Hi ,
I am using DevRocket 2.x version with MontaVista Linux PRO 4.0.1 on my Target named as
PXA 300(xscale Architecture) .I tried following the instructions in the DevRocket
documentation,
specifically: "Creating a Connection to a Remote MontaVista Linux
System"?
but still i could not able to connect my target using DevRocket.
However, I customised the file system once again by including ssh packages which are
present through DevRocket platform image project but in vain and getting the error as below:
My target IP is 192.168.1.101
My host IP is 192.168.1.100
Error:
root@192.168.1.101# ssh 192.168.1.100(In Target terminal window)
Host key verification failed.
root@localhost # ssh 192.168.1.101(In Host terminal window)
ssh : connect to host 192.168.1.101 port 22 : connection refused
So , it will be pleasure and great help if you provide us the solution for connecting PXA Target
let's look closer
If I read your post, your target has 192.168.1.101 and apparently has no ssh daemon running.
That's something you can easily verify on your target by connecting through the serial console and running the ps command 'ps x' -> look for sshd.
I'm expecting that you won't find it - it's not running.
Let's try to run it from the command line:
/etc/init.d/sshd start
Two things can happen: it works or it doesn't :-)
If it works: yay.
If it doesn't work: look closer why.
I can think of a few different reasons why (but your system is probably creative and comes up with a new one):
Good luck!
facing problem with libcrypto
Hi ,
Thanks for your reply. I could not able to run SSH on my OMAP 5912 target although
i have included the necessary SSH packages while customising the file system(minimal file
system) with MontaVista DevRocket-Platform Image project. I am getting the error as below:
root@192.168.1.101:/# ssh 192.168.1.100
ssh: error while loading shared libraries: libcrypto.so.0.9.7: cannot open
share
d object file: No such file or directory
But when using the MontaVista Development Environment filesystem(1.3 GB) I could able to
communicate with SSH on my target to the Host.But when using the customised file system i
am facing the problem with SSH as mentioned above.
As per your suggestion after typing "ps x" in both Montavista Development Environment file
system(1.2 GB) and Customised file system(21.4 MB) i could able to find the difference
between them i.e,the commands which are not present in my customised file system.
Attached Logs is for your reference:
U-Boot 1.1.3 (Apr
26 2006 - 16:02:59)
U-Boot code: 11080000 -> 11096474
BSS: -> 1109AC48
RAM Configuration:
Bank #0: 10000000 32 MB
Flash: 32 MB
In: serial
Out: serial
Err: serial
OMAP5912 OSK # setenv bootargs=console=ttyS0,115200n8 root=/dev/nfs rw
ip=192.16
8.1.101 nfsroot=192.168.1.100:/mnt
OMAP5912 OSK # saveenv
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
Erasing sector 1 ... done
Erased 1 sectors
Writing to Flash...\done
Protected 1 sectors
OMAP5912 OSK # tftp 0x10000000 uImage
*** Warning: ethaddr is not set properly, ignoring!!
Using MAC Address 00:0E:99:02:05:11
TFTP from server 192.168.1.100; our IP address is 192.168.1.101
Filename 'uImage'.
Load address: 0x10000000
Loading: #################################################################
#################################################################
#################################################################
######################################
done
Bytes transferred = 1189208 (122558 hex)
OMAP5912 OSK # bootm 0x10000000
## Booting image at 10000000 ...
Image Name: Linux-2.6.10_mvl401-omap5912_osk
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1189144 Bytes = 1.1 MB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux.............................................................
.................. done, booting the kernel.
Linux version 2.6.10_mvl401-omap5912_osk (root@localhost.localdomain) (gcc
versi
on 3.4.3 (MontaVista 3.4.3-25.0.70.0501961 2005-12-18)) #2 Thu Jul 7 10:50:31
ED
T 2011
CPU: ARM926EJ-Sid(wt) [41069263] revision 3 (ARMv5TEJ)
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Machine: TI-OSK
Memory policy: ECC disabled, Data cache writethrough
OMAP_DIE_ID_0: 0x48960b0f
OMAP_DIE_ID_1: 0x81058f79 DIE_REV: 2
OMAP_PRODUCTION_ID_0: 0xc0aaaafc
OMAP_PRODUCTION_ID_1: 0x00016b18 JTAG_ID: 0x6b18
OMAP32_ID_0: 0x03320200
OMAP32_ID_1: 0x2b58c02f
JTAG_ID: 0xb58c DIE_REV: 2
OMAP1611b revision 2 handled as 16xx id: 81058f7948960b0f
Real-Time Preemption Support (c) Ingo Molnar
Built 1 zonelists
Kernel command line: console=ttyS0,115200n8=root=/dev/nfs rw ip=192.168.1.101
nf
sroot=192.168.1.100:/mnt
Total of 128 interrupts in 4 interrupt banks
OMAP GPIO hardware version 1.0
PID hash table entries: 256 (order: 8, 4096 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 32MB = 32MB total
Memory: 29816KB available (1981K code, 499K data, 104K init)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
spawn_desched_task(00000000)
desched cpu_callback 3/00000000
ksoftirqd started up.
softirq RT prio: 24.
desched cpu_callback 2/00000000
desched thread 0 started up.
NET: Registered protocol family 16
OMAP DMA hardware version 1
DMA capabilities: 000c0000:00000000:01ff:003f:007f
Initializing OMAP McBSP system
MUX: initialized AA9_USB0_VP
MUX: initialized R9_USB0_VM
USB: hmc 16, usb0 2 wires
OMAP I2C: Driver ver. 1.3
tps65010: version 20 Dec 2004
MUX: initialized N14_1610_UWIRE_CS0
MUX: initialized N15_1610_UWIRE_CS1
Interrupt measurement enabled at 6 ticks per usec.
Interrupt holdoff maximums being captured.
OMAP OCPI interconnect driver loaded
Power Management for TI OMAP.
MUX: initialized T20_1610_LOW_PWR
NetWinder Floating Point Emulator V0.97 (double precision)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
omapfb: configured for panel osk
OMAP LCD controller initialized.
MUX: initialized PWL
Console: switching to colour frame buffer device 30x40
OMAP framebuffer initialized vram=262144
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
ttyS1 at MMIO 0xfffb0800 (irq = 47) is a ST16654
Trying to free nonexistent resource <fffb9800-fffb981f>
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>
eth0: SMC91C94 (rev 9) at 0xc285e300 IRQ 160 [nowait]
eth0: Ethernet addr: 00:0e:99:02:05:11
i2c /dev entries driver
elevator: using anticipatory as default io scheduler
mice: PS/2 mouse device common for all mice
OMAP Keypad Driver
MUX: initialized P20_1610_GPIO4
OMAP OSK touchscreen driver initialized
NET: Registered protocol family 2
IP: routing cache hash table of 64 buckets, 3Kbytes
TCP: Hash tables configured (established 256 bind 315)
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: link up
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
device=eth0, addr=192.168.1.101,
mask=255.255.255.0, gw=255.255.255.255,
host=192.168.1.101, domain=,
nis-domain=(none),
bootserver=255.255.255.255,
rootserver=192.168.1.100, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.100
Looking up port of RPC 100005/1 on 192.168.1.100
VFS: Mounted root (nfs filesystem).
Freeing init memory: 104K
INIT: version 2.85 booting
0
Mounting local filesystems: mount mount: Mounting /dev/root on / failed: No
such
file or directory
failed (1: ).
Cleaning: /tmp BusyBox v1.01 (2005.12.18-04:57+0000) multi-call binary
Usage: find [PATH...] [EXPRESSION]
Search for files in a directory hierarchy.
The default PATH is
the current directory; default EXPRESSION is '-print'
EXPRESSION may consist of:
-follow Dereference symbolic links.
-name PATTERN File name (leading directories removed)
matches PATTERN.
-print Print (default and assumed).
-type X Filetype matches X (where X is one of:
f,d,l,b,c,...)
-perm PERMS Permissions match any of (+NNN); all of
(-NNN);
or exactly
(NNN)
-mtime TIME Modified time is greater than (+N); less
than (-N);
or exactly (N)
days
/var/lock BusyBox v1.01 (2005.12.18-04:57+0000) multi-call binary
Usage: find [PATH...] [EXPRESSION]
Search for files in a directory hierarchy.
The default PATH is
the current directory; default EXPRESSION is '-print'
EXPRESSION may consist of:
-follow Dereference symbolic links.
-name PATTERN File name (leading directories removed) matches
PATTERN.
-print Print (default and assumed).
-type X Filetype matches X (where X is one of:
f,d,l,b,c,...)
-perm PERMS Permissions match any of (+NNN); all of
(-NNN);
or exactly
(NNN)
-mtime TIME Modified time is greater than (+N); less
than (-N);
or exactly (N) days
/var/run BusyBox v1.01 (2005.12.18-04:57+0000) multi-call binary
Usage: find [PATH...] [EXPRESSION]
Search for files in a directory hierarchy.
The default PATH is
the current directory; default EXPRESSION is '-print'
EXPRESSION may consist of:
-follow Dereference symbolic links.
-name PATTERN File name (leading directories removed)
matches PATTERN.
-print Print (default and assumed).
-type X Filetype matches X (where X is one of:
f,d,l,b,c,...)
-perm PERMS Permissions match any of (+NNN); all of
(-NNN);
or exactly
(NNN)
-mtime TIME Modified time is greater than (+N); less
than (-N);
or exactly (N)
days
done.
Setting pseudo-terminal access permissions...done.
Updating /etc/motd...done.
: done.
INIT: Entering runlevel: 3
MontaVista(R) Linux(R) Professional Edition 4.0.1 (0502020)
192.168.1.101 login: root
Linux 192.168.1.101 2.6.10_mvl401-omap5912_osk #2 Thu Jul 7 10:50:31 EDT 2011
ar
mv5tejl unknown
Welcome to MontaVista(R) Linux(R) Professional Edition 4.0.1 (0502020).
login[813]: root login on `console'
root@192.168.1.101:~# cat /sys/vendor/mvista/lspinfo/summary
Board Name : TI OSK - OMAP
5912 Processor (little endian)
Lsp Name :
ti-omap5912_osk
LSP Revision : 0502020.1
MVL Architecture : arm_v5t_le
Patch Level : 286
root@192.168.1.101:~# cd /
root@192.168.1.101:/# ls
bin home media
root tmp
boot lib mnt sbin usr
dev linuxrc opt
srv var
etc lost+found proc
sys
root@192.168.1.101:/# du -sh
21.4M .
root@192.168.1.101:/# ssh 192.168.1.100
ssh: error while loading shared libraries: libcrypto.so.0.9.7: cannot open
share
d object file: No such file or directory
Customised file system logs:(21.4 MB)
root@192.168.1.101:/# ps x
PID
Uid VmSize Stat Command
1 root 516 S
init [3]
2 root SW
[ksoftirqd/0]
3 root SW< [desched/0]
4 root SW< [events/0]
5 root SW< [khelper]
10 root SW< [kthread]
16 root SW< [IRQ 19]
17 root SW< [IRQ 20]
18 root SW< [IRQ 21]
19 root SW< [IRQ 22]
20 root SW< [IRQ 23]
21 root SW< [IRQ 24]
22 root SW< [IRQ 85]
23 root SW< [IRQ 86]
24 root SW< [IRQ 87]
25 root SW< [IRQ 88]
26 root SW< [IRQ 89]
27 root SW< [IRQ 90]
28 root SW< [IRQ 91]
29 root SW< [IRQ 92]
30 root SW< [IRQ 93]
31 root SW< [IRQ 94]
32 root SW< [IRQ 25]
35 root SW< [kblockd/0]
41 root SW< [IRQ 36]
79 root SW
[pdflush]
80 root SW
[pdflush]
82 root SW< [aio/0]
81 root SW
[kswapd0]
86 root SW< [IRQ 31]
698 root SW< [IRQ 160]
707 root SW< [IRQ 33]
670 root SW
[kseriod]
704 root SW
[mtdblockd]
712 root SW< [IRQ 164]
718 root SW
[rpciod]
719 root SW< [IRQ 46]
813 root 1348 S
-bash
820 root 692 R
ps x
root@192.168.1.101:/#
MontaVista Development Environment Filesytem(1.2 GB) Logs:
root@192.168.1.101:/#
ps x
PID TTY STAT
TIME COMMAND
1 ? S
0:02 init [3]
2 ? S
0:05 [ksoftirqd/0]
3 ? S< 0:00 [desched/0]
4 ? S< 0:00 [events/0]
5 ? S< 0:00 [khelper]
10 ? S< 0:00 [kthread]
16 ? S< 0:00 [IRQ 19]
17 ? S< 0:00 [IRQ 20]
18 ? S< 0:00 [IRQ 21]
19 ? S< 0:00 [IRQ 22]
20 ? S< 0:00 [IRQ 23]
21 ? S< 0:00 [IRQ 24]
22 ? S< 0:00 [IRQ 85]
23 ? S< 0:00 [IRQ 86]
24 ? S< 0:00 [IRQ 87]
25 ? S< 0:00 [IRQ 88]
26 ? S< 0:00 [IRQ 89]
27 ? S< 0:00 [IRQ 90]
28 ? S< 0:00 [IRQ 91]
29 ? S<
0:00 [IRQ 92]
30 ? S< 0:00 [IRQ 93]
31 ? S< 0:00 [IRQ 94]
32 ? S< 0:00 [IRQ 25]
35 ? S< 0:00 [kblockd/0]
41 ? S< 0:00 [IRQ 36]
79 ? S
0:00 [pdflush]
80 ? S
0:00 [pdflush]
82 ? S< 0:00 [aio/0]
81 ? S
0:00 [kswapd0]
86 ?
S< 0:00 [IRQ 31]
670 ? S
0:00 [kseriod]
698 ? S< 0:05 [IRQ 160]
707 ? S< 0:00 [IRQ 33]
712 ? S< 0:00 [IRQ 164]
704 ? S
0:00 [mtdblockd]
718 ? S
0:01 [rpciod]
719 ? S< 0:00 [IRQ 46]
732 ? S<s 0:00 udevd
965 ? Ss
0:00 /sbin/syslogd -r
973 ? Ss
0:00 /sbin/klogd -x
988 ? Ss
0:00 /usr/sbin/inetd
992 ? Ssl
0:00 /usr/bin/mvltd -p 34577 -b /usr/lib/mvltd -M 5
1001 ? Ss
0:01 -bash
1006 ? R+
0:00 ps x
root@192.168.1.101:/#
please guide us to proceed further and thanks a lot for helping us.
Two issues
Hi Dileep,
I see two issues in your post.
Let's start with ssh.
There is a command line tool ssh - which in turn connects to an sshd, the server.
We usually have the host (i.e. the PC) connect to the sshd running on the target (i.e. the PXA). What I see you do, is use the ssh on the target to connect to the sshd on the host. That will not help you for DevRocket (did you already update to 5.2.3?).
If you are missing libcrypto on the target, you'll have to add that package in your platform image.
Second issue is that you're attempting to use a System V init with busybox. We're apparently talking busybox version 1.01 here - which by no means is advanced enough to support all the ugly tricks that are happening in the regular SysV scripts. This is clear if you look at the errors you get: e.g. busybox's find didn't have the -print option back then.
I usually suggest to people to go with the flow - if you are already using busybox for coreutils, fileutils and shell, also use busybox init and use a single init script in /etc/init.d/rcS .
update of busybox
Hi,
It was been so pleasure to interact with you and thanks for your valuable inputs.
As you suggested, I have updated my PRO 4.0.1 DevRocket from 2.0.2 to 2.0.5 version
besides i have updated the busy-box packages(busybox & busybox-debug info)
and openssh packages too.
i.e busybox packages from 1.01 to 1.6.0 & openssh packages from 3.8.1p1 to 4.3p2-1.0.13
which are available from montavista zone.
The problem is that it's not showing the updated version of busy-box packages and openssh
packages while customising the file system in platform image project under :
Packages tab------>properties---------> version---------> 1.0.1 but i could able to notice
through command line that it was been updated to the latest version(1.6.0 & 4.3p2-1.0.13).
i don't know where exactly the problem lies with and could not able to trace it after updating.
I came to know that openssl is the package available in devrocket which is responsible for
libcrypto.
I tried connecting PRO 5.0 DevRocket to my PRO 4.0.1 OMAP target but it does not work and still
i could not able to connect my target through DevRocket.
Awaiting for your kind response.
Successfully connected the DevRocket
Hi
We could able to connect successfully our PXA 300 target to our host by including
the mvltd daemon packages in our customised file system(24MB)and there
by running the below command on target as
"/usr/bin/mvltd -p 34577 -b /usr/lib/mvltd -M 5"
which we inferred from the Montavista Development file system(1.3 GB).
Now we are facing the problem with the Inerrupt latency tool error even though we
have enabled the Interrupt latency feature in kernel configuration and giving the
error as:
"Error Response : Receiving data failed : can't open /proc/maxoff: No such file or
directory.
Any way thanks a lot for your extreme support and guidance for helping
withsome pointers to connect our PXA target successfully