Nimbus 100 vs. Sheevaplug

[Fletch]

Are there any differences between the Sheevaplug and the Nimbus 100?  Can I assume that the Nimbus 100 has the same ports (including JTAG), same memory map, etc?  In other words, will any existing tools, installers or instructions written for the Sheevaplug "just work" with the Nimbus 100?

[Fletch]

Hmm.  Does the Nimbus 100 JTAG module use the same USB chip?  The FTDI linux driver which works with my Sheevaplg and Guruplug doesn't detect the Nimbus 100.

[snake]

Hello Fletch,

Hmm.  Does the Nimbus 100 JTAG module use the same USB chip?  The FTDI linux driver which works with my Sheevaplg and Guruplug doesn't detect the Nimbus 100.

I think the IONICS plug uses a different VID / PID. Maybe try issuing an "lsusb" command on your Linux Host console to check these values then use a modprobe command:

# modprobe ftdi_sio vendor=0x1c0c product=0x0102
# dmesg |grep FTDI


Hope this helps. 

[Fletch]

Thanks!  I'm sure that's it, but I'm not quite there yet.  lsusb does indeed report:

Bus 004 Device 004: ID 1c0c:0102 

But "modprobe ftdi_sio vendor=0x1c0c product=0x0102" does not add a new ttyUSB nor log anything to dmesg about ftdi.  What am I missing?  I'm using the libftdi1 0.17-1 that ships with Ubuntu Lucid.  Do I need to manually install something newer for this serial chip?

[birdman]

But "modprobe ftdi_sio vendor=0x1c0c product=0x0102" does not add a new ttyUSB nor log anything to dmesg about ftdi.  What am I missing?

Is the Nimbus 100 plugged in and switched on at the time?
When you do attach it and power it on (without running modprobe), what ends up at the end of the dmesg output?

[Fletch]

Thanks for your help - I'm sure this is something simple...

When I attach the Nimbus to my laptop, the only thing logged is:

[1121122.944080] usb 2-2: new full speed USB device using uhci_hcd and address 31
[1121123.147429] usb 2-2: configuration #1 chosen from 1 choice

Nothing further is logged when I run modprobe and no new ttyUSB is added.

When I use a Sheevaplug or Guruplug, I see references to ftdi_sio logged and a new ttyUSB appears.  This happens without needing to manually run modprobe (or anything else).

[Fletch]

Got it working.  Your advice got me started - the rest was user error on my end.  Thanks for the help.

[guidol]

Nothing further is logged when I run modprobe and no new ttyUSB is added.

and what was the error at your end? was no new ttyUSB added because the
"old" configuration -1- was used and a ttyUSB was already configured?

[Fletch]

I had installed some Ubuntu updates (including a kernel) and forgot to reboot.  Once I booted into the new kernel, everything worked as expected.

[imike24]

Nice

__________________
traction devices exercise programs enhancement patches enhancement pills traction devices exercise programs enhancement patches enhancement pills antiaging webhost weightloss reviews female libido pe guide

[badlongyin]

It works, thanks