46
Messages
This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.
Messages - frank26080115
47
Breakout boards / Re: Re: What breakout do you need/want?
48
Breakout boards / Re: What breakout do you need/want?
Why not 100 pins?
49
Hardware biz / Re: How do you design for pick-n-place?
50
Hardware biz / How do you design for pick-n-place?
Also I've seen http://www.youtube.com/watch?v=VXE_dh38HjU which is pretty neat but it's too general
51
Open Bench Logic Sniffer / Re: "Capture Aborted! Device Not Found!" after update
Great work with the open source stuff, but the USBee client software can analyze USB packets at a low level, which I hold in high regard
52
Open Bench Logic Sniffer / Re: "Capture Aborted! Device Not Found!" after update
53
Open Bench Logic Sniffer / Re: "Capture Aborted! Device Not Found!" after update
Quote
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.api:1.0.1.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.tool.base:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.client:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.tool.i2c:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.export.image:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.logging:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.device.logicsniffer:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.tool.measure:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.fel
ix.log:1.0.0
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.fel
ix.prefs:1.0.4
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.fel
ix.shell:1.4.2
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.fel
ix.shell.remote:1.1.2
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.rxtx:2.2.0
.8
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.tool.spi:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.tool.state:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.device.test:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.tool.uart:1.0.0.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.util:1.0.4.SNAPSHOT
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: nl.lxtreme.ols
.export.vcd:1.0.0.SNAPSHOT
[16/01/11 10:19:59 PM - INFO - nl.lxtreme.ols.client.Host]: LogicSniffer v0.9.0 started ...
the new 0.9.2 does not show the same errors and now it works, sort of, data captured at various settings display data that is obviously wrong and sort of patterned, sometimes it starts and never finishes capturing
ps, why are we using CDC and not USB bulk transfers?
54
Open Bench Logic Sniffer / Re: "Capture Aborted! Device Not Found!" after update
Classic client is version "OpenBench Logic Sniffer 2.1"
PIC upgraded to "OLSv1-firmware-v2.1"
the Xilinx is loaded with "Logic_Sniffer_dynamic_depth.mcs"
The upgrade all went through and I can keep upgrading to the same firmware.
55
Open Bench Logic Sniffer / "Capture Aborted! Device Not Found!" after update
I just checked back, downloaded the latest windows installer, and ran all the upgrades. Now I can't capture any data. It says "Capture Aborted! Device Not Found!" when I try to start a capture.
The COM port is selected correctly (COM11, Logic Sniffer CDC-232). No other software is using the same COM port. VID is 04D8 and PID is FC92. The PWR LED is on, ACT LED is off, TRIG LED is on, ARM LED is off.
If I go into update mode, PUMO loader reports:
Opening serial port 'COM11' @ 921600 ... OK
Found PUMP HW: 1, FW: 2.1, Boot: 1
Found flash: ATMEL AT45DB041D
Downloading and re-installing the mchpcdc.inf does not help
I cannot find a way to re-assign the COM port number
Java is up-to-date
I'm running Win7 Pro 64-bit with test mode enabled (driver signing disabled)
edit: oh sorry I didn't realize this was some sort of new client with a bug report thread already
edit: wow you guys need a bug tracker instead of one massive thread, I was going to repost this to the thread and ask you to delete this one but now I don't know what's a better idea so I'll let the mods decide
edit: I just ran the old "classic" client and the rocket button doesn't do anything, no error messages, the diagram and tools menu are greyed-out
56
Open Bench Logic Sniffer / Re: erratic data after period of capture
it works as expected with RLE off, i just find the 16k sample depth disappointing, seeedstudio is advertising 24k depth but i don't even see that option
right now i pretty much do not have a good way of viewing USB device enumeration at 20mhz sample rate, even at 10mhz, there isn't enough sample depth to bridge the massive delay between connection and enumeration, hence why i really REALLY need RLE to work
57
Open Bench Logic Sniffer / erratic data after period of capture
screenshot is attached
what i expect to see is USB traffic on channel 1 and 2, channel 0 is connected to my AVR's reset pin, D- on channel 3 is used as the trigger
there seems to be a visual pattern to this madness, i think there might be a synchronization issue? see attached screenshot for what i mean and also i've included my settings
i've recently updated to everything in the 2.1 release package
running win7 ultimate 64 bit in test mode