I have just received my logic sniffer. I downloaded 3.08 package. THen from OLS_Upgrader folder executed
initial_install.bat
ols_upgrader.bat
I chose defaults: fpga rom demon core 3.07 and
OLSv1.firmware.v3.0.hex
both executed without problems.
When I connect device to usb port PWR led is on and ACT flashes two times. And then stays off THen bright red led (ARM) is on.
Is so far OK ?
I downloaded ols 0.9.6-1 client. WHen I press show device metadata, it says 'detection failed'
Also if I just begin capture from 'capture' button statusbar show 'Capture failed! Device not found'
I execute in update mode this:
C:UsersmikaDownloadsols-0308ols-0308OLS_Upgraderwinbin>ols-loader.exe -p:
com6 -t:115200 -status
Logic Sniffer ROM loader v0.3 (November 9, 2010)
Opening serial port 'com6' @ 115200 ... OK
Found OLS HW: 1, FW: 3.0, Boot: 2
Found flash: WINBOND W25X40
OLS status: 00
Are there any other checks to verify everything is OK ?
Here's the video from me updating OBLS:
http://youtu.be/b4142knk5pk (http://youtu.be/b4142knk5pk)
Thanks.
Hi,
Can you check what port you have selected in the OLS client.
It looks like you have selected the wrong com port and the OLS client is talking to a different device.
Try this (it seems that you are on windows as you posted running the .exe version of the utilities):
Connect the OLS board
If the act led blinks several times and then turns off, that should be OK (normal operation).
The fact that you have the ARM led on that should also be ok (it is the same for me).
On the Logic Sniffer 101 page http://dangerousprototypes.com/docs/Logic_Sniffer_101 (http://dangerousprototypes.com/docs/Logic_Sniffer_101) it is stated that the trig should be on but maybe that was the case with an older bitstream.
The newer FPGA streams seem to activate ARM instead of TRIG.
At this point check in your device manager what com ports you have available (you should get the same list in the drop down list from the OLS client at the "analyzer port" on the connection tab.
Check that connection tab is set to serial and the port selected in the analyser port is the proper one (in your case it might be COM6), then check that the device type is Open Bench Logic Sniffer and click on the "show device metadata" button.
If that fails, it is likely that either you selected the wrong port or your OLS com port is in use by another application.
Regards,
tkg
Hi tkg!
.. and thanks for your reply. I am working on another computer now and COM port is 3. OS is Windows 7 64-bit.
I double checked the com port from OLS client and it is correct.
Device manager shows the device at communications port 3. Copy paste from details tab:
USBVID_04D8&PID_FC92&REV_0100
USBVID_04D8&PID_FC92
I also checked USB port info with usb tree view:
In 'device information' and 'address' line (marked with red) it says an error. Is this normal ?
[font=Courier New:]=========================== USB Port4 ===========================
Connection Status : Device is connected
Port Chain : 1-4
======================== USB Device ========================
+++++++++++++++++ Device Information ++++++++++++++++++
Friendly Name : Communications Port (COM3)
Device Description : Communications Port
Device ID : USBVID_04D8&PID_FC926&CCAF305&0&4
Kernel Name : DeviceUSBSER000
Driver KeyName : {4d36e978-e325-11ce-bfc1-08002be10318} 005
Driver : C:Windowssystem32DRIVERSusbser.sys (Version: 6.1.7600.16385 Date: 2009-07-14)
Legacy BusType : PNPBus
Class : Ports
Service : usbser
Enumerator : USB
Location Info : Port_#0004.Hub_#0001
Container ID : {3d9ff404-d734-11e2-9f10-914c50504968}
Manufacturer Info : Microchip Technology, Inc.
Capabilities : Removable, SurpriseRemovalOK
Address : 0 (*!*ERROR Should be equal to the port number)
Problem Code : 0
Power State : D0 (supported: D0, D1, D2, D3, wake from D0, wake from D2)
COM-Port : COM3 (DeviceUSBSER000)
---------------- Connection Information ---------------
Connection Index : 0x04
Connection Status : 0x01 (DeviceConnected)
Current Config Value : 0x01
Device Address : 0x01
Is Hub : 0x00 (no)
Number Of Open Pipes : 0x03 (3)
Device Bus Speed : 0x01 (Full-Speed)
Pipe0ScheduleOffset : 0x00 (0)
Pipe1ScheduleOffset : 0x00 (0)
Pipe2ScheduleOffset : 0x00 (0)
------------- Device Qualifier Descriptor -------------
bLength : 0x12 (18 bytes)
bDescriptorType : 0x01 (Device Qualifier Descriptor)
bcdUSB : 0x200 (USB Version 2.00)
bDeviceClass : 0x02 (Communications and CDC Control)
bDeviceSubClass : 0x00
bDeviceProtocol : 0x00
bMaxPacketSize0 : 0x08 (8 bytes)
idVendor : 0x04D8 (Microchip Technology Inc.)
idProduct : 0xFC92
bcdDevice : 0x100
iManufacturer : 0x01
Language 0x0409 : "Microchip Technology Inc."
iProduct : 0x02
Language 0x0409 : "Logic Sniffer CDC-232"
iSerialNumber : 0x00
bNumConfigurations : 0x01
-------------- Configuration Descriptor ---------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x02 (Configuration Descriptor)
wTotalLength : 0x0043 (67 bytes)
bNumInterfaces : 0x02
bConfigurationValue : 0x01
iConfiguration : 0x00
bmAttributes : 0x80 (Bus Powered)
MaxPower : 0x64 (200 mA)
---------------- Interface Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x04 (Interface Descriptor)
bInterfaceNumber : 0x00
bAlternateSetting : 0x00
bNumEndpoints : 0x01
bInterfaceClass : 0x02 (Communications and CDC Control)
bInterfaceSubClass : 0x02
bInterfaceProtocol : 0x01
iInterface : 0x00
-------------- CDC Interface Descriptor ---------------
bFunctionLength : 0x05 (5 bytes)
bDescriptorType : 0x24 (Interface)
bDescriptorSubType : 0x00 (Header Functional Descriptor)
bcdCDC : 0x110 (CDC Version 1.10)
-------------- CDC Interface Descriptor ---------------
bFunctionLength : 0x04 (4 bytes)
bDescriptorType : 0x24 (Interface)
bDescriptorSubType : 0x02 (Abstract Control Management Functional Descriptor)
bmCapabilities : 0x02
-------------- CDC Interface Descriptor ---------------
bFunctionLength : 0x05 (5 bytes)
bDescriptorType : 0x24 (Interface)
bDescriptorSubType : 0x06 (Union Functional Descriptor)
bControlInterface : 0x00
bSubordinateInterface[0] : 0x01
-------------- CDC Interface Descriptor ---------------
bFunctionLength : 0x05 (5 bytes)
bDescriptorType : 0x24 (Interface)
bDescriptorSubType : 0x01 (Call Management Functional Descriptor)
bmCapabilities : 0x00
bDataInterface : 0x01
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x82 (Direction=IN EndpointID=2)
bmAttributes : 0x03 (TransferType=Interrupt)
wMaxPacketSize : 0x08 (8 bytes)
bInterval : 0x02 (2 ms)
---------------- Interface Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x04 (Interface Descriptor)
bInterfaceNumber : 0x01
bAlternateSetting : 0x00
bNumEndpoints : 0x02
bInterfaceClass : 0x0A (CDC-Data)
bInterfaceSubClass : 0x00
bInterfaceProtocol : 0x00
iInterface : 0x00
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x03 (Direction=OUT EndpointID=3)
bmAttributes : 0x02 (TransferType=Bulk)
wMaxPacketSize : 0x40 (64 bytes)
bInterval : 0x00 (ignored)
----------------- Endpoint Descriptor -----------------
bLength : 0x07 (7 bytes)
bDescriptorType : 0x05 (Endpoint Descriptor)
bEndpointAddress : 0x83 (Direction=IN EndpointID=3)
bmAttributes : 0x02 (TransferType=Bulk)
wMaxPacketSize : 0x40 (64 bytes)
bInterval : 0x00 (ignored)[/font:]
I found this: http://www.sump.org/projects/analyzer/protocol/ (http://www.sump.org/projects/analyzer/protocol/) . Should these commands work with OBLS ?
So I tried communicating with OBLS with realterm serial terminal program.
I opened COM3 - that was OK. Sent byte 0x2 to device which should be id command. No reply. Should I get a reply ?
Is there any other "sanity" check for the device ?
D:UsersknockerdDownloadsOLSols-0308ols-0308OLS_Upgraderwinbin>ols-loader.exe -status -p:com16 -t:115200
Logic Sniffer ROM loader v0.3 (November 9, 2010)
Opening serial port 'com16' @ 115200 ... OK
Found OLS HW: 1, FW: 3.0, Boot: 2
Found flash: WINBOND W25X40
OLS status: 02
Here's the video from me updating OBLS:
http://youtu.be/b4142knk5pk (http://youtu.be/b4142knk5pk)
@knockerd: is your issue resolved by updating the FW, or are you still having troubles? Does upgrading my client to version 0.9.7 (RC1) (http://http://dangerousprototypes.com/forum/viewtopic.php?f=57&t=5693) perhaps help?
Hi Jawi! I sent the device back to seeedstudio. I am still waiting for that. I will report how it works once I get it.
[quote author="jawi"]@knockerd: is your issue resolved by updating the FW, or are you still having troubles? Does upgrading my client to version 0.9.7 (RC1) (http://http://dangerousprototypes.com/forum/viewtopic.php?f=57&t=5693) perhaps help?[/quote]
Received a new board and your 0.9.6-1 client works!
About the client: is there an option to have real-time / live analyzing? I would like to watch live stream from device sending data at 56k baud. I think with speeds like that amount of data would not be a problem with new PC's that have several gigas of RAM and processing power.
Hi Javi,
I got my logic sniffer v1.04 last week from seeedstudio. Unfortunately I am experiencing the same issue as Knockerd, namely whenever I start to capture I got a "device not found" error message.
I searched several forums, upgraded the firmware of PIC and FPGA, and tried version 0.9.7 rc1 of your client, both on Ubuntu 12.04 and Windows 7, but without success.
Should I return my logic sniffer to seeedstudio for replacement, or could I try something else to solve my problem?
Thank you very much!
[quote author="Michel83"]Hi Javi,
I got my logic sniffer v1.04 last week from seeedstudio. Unfortunately I am experiencing the same issue as Knockerd, namely whenever I start to capture I got a "device not found" error message.
I searched several forums, upgraded the firmware of PIC and FPGA, and tried version 0.9.7 rc1 of your client, both on Ubuntu 12.04 and Windows 7, but without success.
Should I return my logic sniffer to seeedstudio for replacement, or could I try something else to solve my problem?
Thank you very much![/quote]
I highly suggest returning it and ask for a replacement.