BeagleBone and Windows XP - Inconsistent Image Behavior

Since I've had problems getting all the software on the BeagleBone
running correctly, I've done a set of experiments, trying 3 different
images and evaluating the differences. Interestingly, the behavior of
each image is different. The image Angstrom-Cloud9-IDE-eglibc-ipk-
v2012.01-core-beaglebone-2012.01.11.img comes the closest to operating
as advertised, but not quite. I'd like any insight anyone may have as
to:
   1) Why the images behave differently
   2) What I can do to get all the software running as advertised

Below is the information from my experiments. Thanks for your help.

John

BeagleBone Startup Behavior

Base Platform
Windows XP SP 3
Intel Pentium M 2 GHz
2 Gb RAM
Browser – Chrome
Console Terminal - PuTTY
Wireless Ethernet connection shared with services turned on.
BeagleBone Rev A3

Image 1

Angstrom-Cloud9-IDE-eglibc-ipk-v2011.11-core-beaglebone-2011.11.16.img

Configuration
1. USB cable
2. Crossover Ethernet cable
3. 5V Power Adapter
Process
1. Plug in Ethernet cable
2. Power up card
3. Plug in USB cable once in normal blinking mode
Result
1. BeagleBone shows up as “BeagleBone Getting Started (E:)”
2. Can read files on E drive
3. Unable to connect serial console to BeagleBone
4. Web server inaccessible
Next Step
1. Eject E drive
2. Still Unable to connect serial console to BeagleBone
3. Web server inaccessible
Next Step
1. With the BeagleBone powered externally, unplug the USB cable
2. Reconnect the USB cable
3. Connect serial console and login
Result
1. BeagleBone 101 presentation runs at 192.168.7.2
2. GateOne DOES NOT RUN at https://192.168.7.2. First message –
Security certificate not trusted. Select “Proceed Anyway”. Error
message: “This webpage has a redirect loop”
3. Cloud9 IDE runs at http://192.168.7.2:3000
4. Console command “ifconfig” SHOWS NO inet addr for eth0.

Image 2

Angstrom-Cloud9-IDE-eglibc-ipk-v2012.01-core-beaglebone-2012.01.11.img

Configuration
1. USB cable
2. Crossover Ethernet cable
3. 5V Power Adapter
Process
1. Plug in Ethernet cable
2. Power up card
3. Plug in USB cable once in normal blinking mode
Result
1. BeagleBone shows up as “BeagleBone Getting Started (E:)”
2. Can read files on E drive
3. Unable to connect serial console to BeagleBone
4. Web server inaccessible
Next Step
1. Eject E drive
2. Connect serial console and login
Result
1. BeagleBone 101 presentation DOES NOT RUN at 192.168.7.2
2. GateOne eventually runs at https://192.168.7.2. First message –
Security certificate not trusted. Select “Proceed Anyway”. GateOne
begins to run.
3. Cloud9 IDE runs at http://192.168.7.2:3000
4. Console command “ifconfig” shows inet addr 192.168.0.193 for eth0.
5. PuTTY can connect for SSH session to 192.168.0.193

Image 3

Angstrom-Cloud9-IDE-eglibc-ipk-v2012.01-core-beaglebone-2012.01.27.img

Configuration
1. USB cable
2. Crossover Ethernet cable
3. 5V Power Adapter
Process
1. Plug in Ethernet cable
2. Power up card
3. Plug in USB cable once in normal blinking mode
Result
1. BeagleBone shows up as “BeagleBone Getting Started (E:)”
2. Can read files on E drive
3. Unable to connect serial console to BeagleBone
4. Web server inaccessible
Next Step
1. Eject E drive
2. Still Unable to connect serial console to BeagleBone
3. GateOne eventually runs at https://192.168.7.2. First message –
Security certificate not trusted. Select “Proceed Anyway”. GateOne
begins to run.
Next Step
1. With the BeagleBone powered externally, unplug the USB cable
2. Reconnect the USB cable
3. Connect serial console and login
Result
1. BeagleBone 101 presentation DOES NOT RUN at 192.168.7.2
2. GateOne still runs at https://192.168.7.2.
3. Cloud9 IDE DOES NOT RUN at http://192.168.7.2:3000
4. Console command “ifconfig” shows inet addr 192.168.0.146 for eth0.
5. PuTTY can connect for SSH session to 192.168.0.146

It appears your USB serial driver was never loaded (probably not installed).
What does your %SystemRoot%\setupapi.log file say about this?

Thanks for the suggestion, but in reviewing the log file, it shows
both "BeagleBone USB Serial Port" and "Linux USB Ethernet/RNDIS
Gadget" successfully installed. Given that I can access everything
over the USB cable, I don't think that is the problem. The issue
seems to be that different services run (or not) depending on the
image. This inconsistency is a bit frustrating when I'm just trying
to get myself a stable fully functioning setup. Any other thoughts on
the variations in images or what can be done to get a stable fully
functioning setup? Thanks.

John

A bit more information:
I'm new to embedded linux development and just starting to understand
some of it. When I look at the status of bone101.service it appears
to be enabled, but failed to start.

root@beaglebone:~# systemctl status bone101.service
bone101.service - Beaglebone 101 presentation
          Loaded: loaded (/lib/systemd/system/bone101.service;
enabled)
          Active: failed since Wed, 11 Jan 2012 08:52:05 +0000; 2min
5s ago
         Process: 96 ExecStart=/usr/bin/node bone101.js (code=exited,
status=1/FAILURE)
          CGroup: name=systemd:/system/bone101.service

I start the service and still see a similar situation.

root@beaglebone:~# systemctl start bone101.service
root@beaglebone:~# systemctl status bone101.service
bone101.service - Beaglebone 101 presentation
          Loaded: loaded (/lib/systemd/system/bone101.service;
enabled)
          Active: failed since Wed, 11 Jan 2012 08:55:10 +0000; 30s
ago
         Process: 345 ExecStart=/usr/bin/node bone101.js (code=exited,
status=1/FAILURE)
          CGroup: name=systemd:/system/bone101.service

On another image, the issue is the same, though I see a bit more
information.

root@beaglebone:~# systemctl start bone101.service
root@beaglebone:~# systemctl status bone101.service
bone101.service - Beaglebone 101 presentation
          Loaded: loaded (/lib/systemd/system/bone101.service;
enabled)
          Active: failed since Fri, 27 Jan 2012 04:29:31 +0000; 15s
ago
         Process: 331 ExecStart=/usr/bin/node bone101.js (code=exited,
status=1/ FAILURE)
          CGroup: name=systemd:/system/bone101.service

Jan 27 04:29:31 beaglebone node[331]: curl http://npmjs.org/install.sh

bash

Jan 27 04:29:31 beaglebone node[331]: npm install fibers
Jan 27 04:29:31 beaglebone node[331]: Delay operations loops will
consume C...es
Jan 27 04:29:31 beaglebone node[331]: Invoke using 'node-fibers' if
node ve....2
Jan 27 04:29:31 beaglebone node[331]: node.js:134
Jan 27 04:29:31 beaglebone node[331]: throw e; // process.nextTick
error, o...ck
Jan 27 04:29:31 beaglebone node[331]: ^
Jan 27 04:29:31 beaglebone node[331]: Error: EADDRINUSE, Address
already in use
Jan 27 04:29:31 beaglebone node[331]: at Array.<anonymous> (net.js:
1116:7)
Jan 27 04:29:31 beaglebone node[331]: at EventEmitter._tickCallback
(node.j...6)

I'm perplexed that the service won't run. Any suggestions on how to
explore this further? Thanks.

John