Thanks a lot for your help, tested it on 3 different systems (real and virtual) today, still nothing new, it keeps telling "Device not found". I also tested the latest release that jack.gassett pointed out, no relief... :-(
Jack, I'd like to send the hw to you in order to get fixed / replaced. can you please send me your contact details /?
I had the 2.5 firmware and the Logic_Sniffer_dynamic_depth.bit loaded. This firmware and bitstream were in the ols-06FEB2011-package.zip you posted. Now I loaded firmware 3.0 and verilog7 bitstream as you proposed. Still about the same behaviour (device not found), although I see the ARM led lit. (do not recall it lit before) the TRIG led is off. When I connect the usb or reset the ACT led briefly flashes .
What baudrate should I select in the client ?
@jack: I did not load the package you suggested, will do later. If all else fails and the board is faulty I will probably send it to you for repair, as this is more convenient for me. but first, let's make sure the HW is faulty....
My first post was over a year ago having a non-working OLS. I kind of gave up and had it in a box for some time and dug it up the other day, updated it to both the bitstream and the firmware (2.5) the Ian posted on 06 Feb 2011. Updating worked without a problem, but still everything I try to get the OLS to work with a client (pc | mac) fails with "device not found". (tested all baudrates, BTW, what baudrate is default ??)
I have the sniffer directly connected to my laptop, no hub, no other device. The lap- top is a macbook pro. voltages on the board are ok (see earlier). I see leds blinking when power is applied (act) and I see the comport in the device tree, and the ols enumerates OK, so .... Am I stuck with a bad board after all ?? (it has the seeedstudio OC sticker, so must be ok ?!) Or: am I doing something WRONG ??
I tried my OLS on my macbook pro 15", directly to the USB port, cable length 6 ft. both using the software for windows in a VMWare session as well as directly for mac I have no success whatsoever. I see tha driver installed (win) and giving a COM4, but then device not found. Also on my mac natively I see the device created, but same saga... Device not foud, See the msgs in the mac OSX thread.
Next I will test on a hub with power.
Checked he supply voltages (device connected to USB) ... (No activity...) According to my recently calibrated Fluke 112:
1.2 V rail : 1.204 V 2.5 V rail : 2.495 V 3.3 V rail : 3.310 V 5.0 V rail : 4.919 V
BTW, on startup of the board, I see the act led flashing to program the fpga, so the board is doing tricks :-)
Still no go for me, how hard I try :-( My OLS enumerates to /dev/cu.usbmodem621 or /dev/tty.usbmodem621, but with the client I still get : Attaching to: /dev/cu.usbmodem621 (115200bps) Run started Device ID: 0x0 Run aborted java.io.IOException: Device not found. at org.sump.analyzer.devices.FpgaDevice.run(FpgaDevice.java:648) at org.sump.analyzer.devices.FpgaDeviceController.run(FpgaDeviceController.java:546) at java.lang.Thread.run(Thread.java:637)
Or Attaching to: /dev/tty.usbmodem621 if I select this in the gui.
Also if I try to talk to the device using a terminal program, I do not get any reply nor do I see lights flashing at the board (except for the ACT led if it starts up) giving some comms feedback. Weird.... If I reset the board with the switch I see a term Serdevice error in my terminal, but that is all there is...
Unfortunately I'm on a mac only environment, I do not easily have a Linux or Win box to test ...
Got my board today (Thank you Seeed .... !) To get stuff fired up, I just copied the libs from Arduino18, then plugged in the board to my Macbook Pro, and started the java app... (java -d32 -jar analyzer.jar ) and up plops the GUI (the excitement grew with the minute here...)
The logging showed Device Controller found: org.sump.analyzer.devices.FpgaDeviceController and /dev/tty.usbmodem621 /dev/cu.usbmodem621
So: I felt good, but after trying to start the LA by pressing the button, it showed that it could not find any device... (logging showed: /dev/tty.usbmodem621 (115200bps) ) so: what is the thing here, Do I need to flash the board first ?? BTW I checked every baudrate :-) and selected the FPGA controller...
I tried to connect using screen, that messed up the ftdi driver I think as it generated a kernel panic, which resulted in a reboot of the mac, no big deal.... After that, I reconnected, using screen, saw the msg, typed yes (lowercase), worked... Then I used the ds30 command line util and upgraded to firmware 4.1..
All is fine now (and a happy user again)... THANKS for the support !
Looks like I missed the step programming the bootloader. Did that, got to the point where I have my bp telling me:
DS30 Loader installer v0.2 (ALPHA) (C)hris 2010 Released under Creative Commons null license. This will install bootloader v4.1. Type 'Yes' to program the new bootloader. Disconnect power if unsure (no harm done).
Fine, but when I type the magic 'yes' word (yes, without quotes), it does not accept my chars as correct, and keeps repeating the message on every keystroke. (I use Zterm on mac, 115200/n/8/1 the terminal that just works on my bp, never had problems with sending chars).
Tried the bootloader update program utility on a mac, but no luck yet. I use the version that is in the zipfile as directed by pppds post in this forum, but the mac version bails out with:
Opening serial device /dev/tty.usbserial-A600aSsn...OK Configuring serial port settings...OK Sending Hello to the Bootloader...ERROR No reply from the bootloader, or invalid reply received: 0 Please make sure that PGND and PGC are connected, replug the devide and try again
Serial device is the right device, pins are connected, mode led is on.
We're talking about a BP v3a, (sep 2009) that otherwise runs fine:
