Sorry, you need to enable JavaScript to visit this website.

Speedway Linux tutorial RSE setup

Unsolved
12 posts / 0 new
james t kennedy's picture
james t kennedy
Junior(0)
Speedway Linux tutorial RSE setup

I have problems connecting to Zedboard up with linux from SDK using Remote System Explorer SSH connection for lab 4-1. is there a way to connect to zedboard with the target (Zedboard) and my laptop attached to a router? using dhclient?

james t kennedy's picture
james t kennedy
Junior(0)
can anyone suggest a solution?

after linux boots, i can ping my pc; but when i try to make the remote connection in SDK, it accepts the target ipaddr, but when i try to access files, it asks for password and does not work for authorization. again, i can see the zedboard attached on my router page. can anyone spot what i am missing? thanks.

zedhed's picture
zedhed
Moderator(25)
can anyone suggest a solution?

Hi james t kennedy,

When you you say you are using a router between your laptop and ZedBoard, are you using the switched side between the two hosts or are you using the routed side?

Using the switched side should be fine since none of the network traffic should be filtered in that case. If you are using the routed side, it is possible that the router firewall is filtering your network traffic which would explain why you are unable to view the remote filesystem which is provided by SFTP. Also, you can check your Windows firewall settings to make sure that port 22 connections are not being blocked.

Another thing to try in order to eliminate your router as a culprit is to simply use a direct patch cable from your laptop to ZedBoard. This is what we do during the live SpeedWay events. When trying this, make sure that you turn your wireless adapter off first so that there is no confusion with SDK attempting to connect to the appropriate remote host. Yes, I know this can be frustrating to do each time but it is the only way that I have found a reliable means of connecting to the target board.

Regards,

-Kevin

james t kennedy's picture
james t kennedy
Junior(0)
failed with direct connection

okay. i removed my ethernet cable from the router and plugged it into the zedboard. i changed my laptop ip address to a static 192.168.1.11. and i disabled both the windows and norton firewalls. booted up linux on the zedboard and can ping 192.168.1.11 from teraterm. but from sdk, when i create the connection and try to access the files, i get authorization failure. it is assuming a userid of "james" from from windows 7 laptop, i think, but it won't connect to get me access and gives me "auth fail," with any userid combo (root or james). any idea what i need to do to allow the connection? btw, i did allow port 22 connections as you suggested. (windows 7 pro 64bit, 14.2 xilinx tools as recommended" norton internet security).

james t kennedy's picture
james t kennedy
Junior(0)
wireless adapter is disabled

per your suggestion!

m.russell's picture
m.russell
Junior(0)
Hi

Hi

The username and password to connect to the Zynq are both 'root'. Section 9.5.3 of the Xilinx CTT gives a step by step guide if you're still having problems

http://www.xilinx.com/support/documentation/sw_manuals/xilinx14_3/ug873-...

Matthew

james t kennedy's picture
james t kennedy
Junior(0)
ug873 or Speedway course

matthew,
thanks for your reply.
i have updated my ug873 document and read the section to which you refer.
however i was working from the new speedway course to the same end and followed similar instructions to open the connection to the zedboard from with SDK. root/root has not worked for me.
i will try to make sure that the zedboard's ip is indeed 192.168.1.10.
BTW, it says in the lower pane that i already have 2 connections to it. and adds a third when i connect. but it keeps asking me the password when i open the root direcory and does not accept root/root and eventually fails with the "auth" error i described above.
thanks for trying to help, but i think i have some other problem than the password.

zedhed's picture
zedhed
Moderator(25)
RE: ug873 or Speedway course

Hi james t kennedy,

It sounds like you are getting a bit further with the connection at least and now it is an authentication problem. One other thing to check is something that came up with the Avnet FAEs in Japan. I am not entirely sure if it was the result of their PDF reader not interpreting the characters in the document correctly or if it was getting corrupted in transfer through the clipboard, but somehow their /etc/passwd file was not created correctly. This file is created during Lab 2.2, Experiment 3, Step 10 where this string is written to the /etc/passwd file:

root:$1$qC.CEbjC$SVJyqm.IG.gkElhaeM.FD0:0:0:root:/root:/bin/sh

That long ugly string was somehow getting corrupted and since that is the hashed password for the root account, they were unable to login with the root/root credentials.

If you are not using Adobe Reader X (or later) or if you are using a non-English version of Reader, perhaps you are experiencing something similar. One quick way to check this would be to use the Root File System image ramdisk32M.image.gz from the Lab 2.2 solution folder in place of the one that you created. If the solution solves your problem, then the /etc/passwd file is likely the culprit. If the solution does not solve your problem, then there is something else interfering with the authentication (maybe another 192.168.1.10 host on your network? probably not if you are using a direct cable connection to your ZedBoard).

Please let us know if this gets you any further.

Regards,

-Kevin

james t kennedy's picture
james t kennedy
Junior(0)
passwd file was solution

hi kevin,

thanks for helping me sort this out. i did indeed both the creation of the passwd file in step 10. and using the solution allowed me to access the root on the zedboard.
and this was without a direct connection, as my router dhcp assigned ip addr on my laptop happened to be 192.168.1.2.
again thanks for sorting this out for me, and rousing my scrutiny to find likely error origins by meticulous review of the components.

cheers,

james

zedhed's picture
zedhed
Moderator(25)
RE: passwd file was solution

Hi James,

Glad to hear that it is working out for you and thank you for posting your results back here for others to see.

Can you elaborate on what you believe the problem was in creating the /etc/passwd file? I am trying to track down the cause of this and whether or not it is a cut and paste error or just a simple mis-typing when creating the file by hand.

If there is something that I can do to improve the documentation so that others do not get stuck here, that would be a benefit for all of us.

Thanks,

-Kevin

james t kennedy's picture
james t kennedy
Junior(0)
RSE problem traced back to ramdisk32M.image creation

Kevin,

I'm afraid that it was just human error in the creation of the _rootfs. In my case, the leading 'r' got omitted in the creation of the etc/passwd file. nothing as elborate as the Japanese PDF cut and paste.

However, I compared the boot logs with the two ramdisk (before and after passwd fix), and there was no distinguishable difference. In other words, it is up to you to be certain that the system folders and startup scripts are created correctly.

Perhaps problems encountered in the use of the booted linux images ramdisk could be tabulated with trace back to a likely cause or origin in the creation of the _rootfs.

Or to simply stress the importance of examining the contents of _rootfs before copying and gzip.

Thanks,

James

zedhed's picture
zedhed
Moderator(25)
RE: RSE problem traced back to ramdisk32M.image creation

James,
Thanks for the suggestion.  I am not sure if there is an easy way to check to see if the RAM disk image was created successfully.  I thought maybe this could be done using an MD5 checksum on the image, but then I realized that even whitespace character differences in the startup scripts could result in a different MD5 values and I would rather that users not waste time tracking down innocuous differences.
If you have any suggestions, I would appreciate your thoughts on this.
Regards,
-Kevin