Skip to main content ↑ ↓

Show Posts

This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.

Messages - knockerd

1
Open Bench Logic Sniffer / Re: 'Detection failed' in logic analyzer client 0.9.6-1 *VID
[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.
2
Open Bench Logic Sniffer / Re: 'Detection failed' in logic analyzer client 0.9.6-1 *VID
[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) 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.
6
Open Bench Logic Sniffer / Re: Update mode is not activated
Thanks! I'm going to do some tests today and record a video.

Quote
Anyway, the important part is to have the matching bootloader AND configuration bits for the crystal you have if the hex file you want to use does not have them exported from mplab.

I believe I now have the correct bootloader because I was able to flash new firmware. OLSv1-bootloader-v2-16MHz

But what are the configuration bits ?

Also could you check from Device Manager - communications port - driver details. What files it is using ? Mine is using:

hhdspmc62.sys
usbser.sys
7
Open Bench Logic Sniffer / Re: Update mode is not activated
Ok. Finally got the bootloader to run.
Turns out my OBLS has 16MHZ and NOT 20MHZ crystal !! I was flashing 20MHZ bootloader with BP like it says in the rescue information.

I highly suggest to add note there to first check what crystal is in OBLS and then choose the correct bootloader!
8
Open Bench Logic Sniffer / Re: Update mode is not activated
I was able to update the bootloader with Bus Pirate from BP-OLS-bootloaderrescue-v1.zip according to these instructions:
http://dangerousprototypes.com/2010/06/ ... er-rescue/

I checked before and after programming that PIC is read correctly in the program. Programming really should have some verification function even it is slow.

Still no go: I then tried to update firmware with fw_update:

D:UserslainemiDownloadsOLSBP-OLS-bootloaderrescue-v1Firmware-0506update>fw
_update -e -w -m flash -vid 0x04D8 -pid 0xFC90 -ix OLSv1-firmware-v05-20MHz.hex

U2IO flash erasing: FAILED.
Device is not found.
Operation aborted.

D:UserslainemiDownloadsOLSBP-OLS-bootloaderrescue-v1Firmware-0506update>pa
use
Press any key to continue . . .

Again usbtreeview does not identify OBLS bootloader:


    =========================== USB Port1 ===========================

Connection Status        : Device failed enumeration
Port Chain              : 3-1-5-1

      ======================== USB Device ========================

        +++++++++++++++++ Device Information ++++++++++++++++++
Device Description      : Unknown Device
Device ID                : USBVID_0000&PID_00007&34A5C852&0&1
Driver KeyName          : {36fc9e60-c465-11cf-8056-444553540000}033
Legacy BusType          : PNPBus
Class                    : USB
Service                  :
Enumerator              : USB
Location Info            : Port_#0001.Hub_#0005
Manufacturer Info        : (Standard USB Host Controller)
Capabilities            : Removable, RawDeviceOK
Address                  : 1
Problem Code            : 43 (CM_PROB_FAILED_POST_START)
Power State              : D3 (supported: D0, D2, D3, wake from D0, wake from D2)

        ---------------- Connection Information ---------------
Connection Index        : 0x01
Connection Status        : 0x02 (DeviceFailedEnumeration)
Current Config Value    : 0x00
Device Address          : 0x00
Is Hub                  : 0x00 (no)
Number Of Open Pipes    : 0x00 (0)
Device Bus Speed        : 0x00 (Low-Speed)

        ------------- Device Qualifier Descriptor -------------
bLength                  : 0x00 (0 bytes)
9
Open Bench Logic Sniffer / Re: Update mode is not activated
Ok, so I jumpered PGC and PGD pins and press reset. Nothing happens.

Port status from Usbtreeview program:


    =========================== USB Port3 ===========================

Connection Status        : Device failed enumeration
Port Chain              : 1-3

      ======================== USB Device ========================

        ---------------- Connection Information ---------------
Connection Index        : 0x03
Connection Status        : 0x02 (DeviceFailedEnumeration)
Current Config Value    : 0x00
Device Address          : 0x00
Is Hub                  : 0x00 (no)
Number Of Open Pipes    : 0x00 (0)
Device Bus Speed        : 0x00 (Low-Speed)

        ------------- Device Qualifier Descriptor -------------
bLength                  : 0x00 (0 bytes)


Where can I get the latest .hex to update the bootloader? I seem to be having v 1.04 board
10
Open Bench Logic Sniffer / Update mode is not activated
I'm trying to do firmware upgrade for OBLS. When I press UPDATE and RESET buttons ACT led does not turn on like it is said in the manuals.  What are my options ? Is the device hardware damaged ? Will I get refund ?
11
Open Bench Logic Sniffer / Re: 'Detection failed' in logic analyzer client 0.9.6-1
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/ . 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 ?
12
Open Bench Logic Sniffer / 'Detection failed' in logic analyzer client 0.9.6-1 *VIDEO*
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

Thanks.
13
Bus Pirate Support / RTS, CTS and DTR support in Bus Pirate ?
Does Bus Pirate support RTS, CTS and DTR pins in bridge mode or live monitor mode  ? I would want it to work in transparent bridge mode to watch the communication and this old hardware device uses DTR, RTS and CTS pins.

Edit: should I buy logic sniffer instead because I am more interested on the pins and not the data ?

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#TimeMemoryFunctionLocation
10.01522439560session_write_close ( )...(null):0
20.01552571136ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )...(null):0
30.01552571912Database_MySQL->query( ).../DatabaseHandler.php:119
40.05922710632Database_MySQL->error( ).../Db-mysql.class.php:273