BBB with Debian lose ability to use PuTTY through USB 192.168.7.2

Hi,

I have the BBB with the factory installed Linux:

Angstrom v2012.12 - Kernel \r
Linux 3.8.6 armv7l

On my WindowsXP machine I can run PuTTY terminal and connect with the BBB through the USB port at the IP address 192.168.7.2 with no problem.

I can also run PuTTY through the IP address assigned to the BBB by the LAN router with no problem. I can also ping the BBB address from my WinXP.

However, the application I want to run requires the following system software:

Debian GNU/Linux 7 \n \l
Linux 3.8.13xenomai-bone23 armv7l

I loaded that software on to an SDHC card. It boots up and runs fine except I can no longer use a PuTTY terminal through the USB port. Also when I try to ping the 192.168.7.2 address from my XP, I no longer get any response.

I can still get response with PuTTY by running through the LAN IP address before. I can run Xming on the WinXP and run my applications just fine through the LAN. This works with no problem, but I would like to be able to run “headless” through the USB port (not the LAN). This will allow me to run both the XP and the Linux on the same machine (WinXP station) with only the USB connection.

If I do an ifconfig, I get the following information regarding the USB port:

usb0 Link encap:Ethernet HWaddr 0e:39:c8:21:b0:b1
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
inet6 addr: fe80::c39:c8ff:fe21:b0b1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:76 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14045 (13.7 KiB) TX bytes:598 (598.0 B)

It would appear as the the port and IP address are there (on the BBB side). I seems as though they are no being made accessible.

When the Debian BBB boots up, it will appear on my WinXP machine as a drive (E: on my machine, and my WinXP can access the files there, so the USB connection is still good). But if I double click on the “BeagleBone Getting Started” label on WinXP “My Computer” page it tries to load from the E: drive which gets translated to trying to load from 192.168.7.2 again, and this fails.

So I know the WinXP side is good. I know the BBB and USB port electronics are all good. It seems that the Debian is not loading some driver (or something) that is required to make the 192.168.7.2 port visible through the USB port, even though it exists in ifconf.

Can anyone tell me what I need to load/run/install/etc. on the Debian to get it to allow access through the USB port like the Angstom did.

Thanks,

Jeff

Hi,

  I have the BBB with the factory installed Linux:

Angstrom v2012.12 - Kernel \r
Linux 3.8.6 armv7l

On my WindowsXP machine I can run PuTTY terminal and connect with the BBB
through the USB port at the IP address 192.168.7.2 with no problem.

I can also run PuTTY through the IP address assigned to the BBB by the LAN
router with no problem. I can also ping the BBB address from my WinXP.

  However, the application I want to run requires the following system
software:

Debian GNU/Linux 7 \n \l
Linux 3.8.13xenomai-bone23 armv7l

That sounds an awful lot like my MachineKit image.

  I loaded that software on to an SDHC card. It boots up and runs fine
except I can no longer use a PuTTY terminal through the USB port. Also
when I try to ping the 192.168.7.2 address from my XP, I no longer get any
response.

  I *can* still get response with PuTTY by running through the LAN IP
address before. I can run Xming on the WinXP and run my applications just
fine through the LAN. This works with no problem, but I would like to be
able to run "headless" through the USB port (not the LAN). This will allow
me to run both the XP and the Linux on the same machine (WinXP station)
with only the USB connection.

If you _are_ using my MachineKit image, I removed the udhcp package from
the package list, because in testing it was trying to assign IP
addresses on the LAN interface (causing networking problems for anything
else on the same Ethernet segment). You will need a dhcp server running
(on the USB interface only) if you want USB networking to work "out of
the box".

  If I do an ifconfig, I get the following information regarding the USB
port:

usb0 Link encap:Ethernet HWaddr 0e:39:c8:21:b0:b1
          inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
          inet6 addr: fe80::c39:c8ff:fe21:b0b1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14045 (13.7 KiB) TX bytes:598 (598.0 B)

  It would appear as the the port and IP address are there (on the BBB
side). I seems as though they are no being made accessible.

  When the Debian BBB boots up, it will appear on my WinXP machine as a
drive (E: on my machine, and my WinXP can access the files there, so the
USB connection is still good). But if I double click on the "BeagleBone
Getting Started" label on WinXP "My Computer" page it tries to load from
the E: drive which gets translated to trying to load from 192.168.7.2
again, and this fails.

  So I know the WinXP side is good. I know the BBB and USB port
electronics are all good. It seems that the Debian is not loading some
driver (or something) that is required to make the 192.168.7.2 port visible
through the USB port, even though it exists in ifconf.

That would be the dhcp server, which Windows will use to get an IP
address. Alternatively, you could probably assign a static IP address
on the windows side for the USB ethernet interface.

  Can anyone tell me what I need to load/run/install/etc. on the Debian to
get it to allow access through the USB port like the Angstom did.

apt-get install the dhcp server of your choice, and properly configure
it to hand out IP address leases for the USB link network and *NOT* the
network connected to the physical Ethernet jack.

Hi Charles,

Indeed it is your Machinekit. I originally mentioned my build intentions on the LinuxCNC group that I had gotten the PuTTY working through the Ethernet (thanks to your help). I later learned that it was possible to do similar communications through the USB port, which is what I really wanted in the first place.

Again, thanks to your suggestions, I was able to (finally) get the USB port work. I can now use PuTTY to get an xterm. But, unfortunately the Xming Xlaunch no longer makes a connection to give me an xterm, so now I have to figure that one out… (if you have any hints, they’d be gladly accepted).

Thanks,

Jeff

I haven't used the USB networking or Xwing (I use Ethernet and the
cygwin tools with the X11 server installed). But for general X
problems, make sure you have the X server running, and make sure you
have X11 forwarding enabled in your putty session when lanuching.

Note if you are using USB networking, the BeagleBone won't be able to
see anything past your Windows host machine, and won't have working name
resolution.