Skip to main content
Topic: OLS files and utilities - Windows, Linux, Mac (Read 46310 times) previous topic - next topic

Re: OLS files and utilities - Windows, Linux, Mac

Reply #15
I am attempting to update my Open Bench Logic Sniffer (HW v1.04) using the command on a Mac OS X (10.8.2) machine:
AFTER pressing the RESET button while holding the UPDATE button.

Code: [Select]
ols_fwloader -f BOOT -n -P /dev/tty.usbmodemfa131 -V -W -w ~/Downloads/ols-0308/OLS_Upgrader/PIC_firmware/OLSv1.firmware.v3.0.hex
[/size]

Here is the transcript:

Code: [Select]
Proton:ols-fwloader-0.1 wayne$ ols_fwloader -f BOOT -n -P /dev/tty.usbmodemfa131 -V -W -w ~/Downloads/ols-0308/OLS_Upgrader/PIC_firmware/OLSv1.firmware.v3.0.hex
Found OLS HW: 1, FW: 2.2, Boot: 2
Found flash: WINBOND W25X40
OLS switched to bootloader mode
libusb: 0.000000 info [process_new_device] allocating new device for location 0xfa000000
libusb: 0.000072 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000084 info [process_new_device] found device with address 1 at 001-05ac-8006-09-00
libusb: 0.000453 info [process_new_device] allocating new device for location 0xfd000000
libusb: 0.000487 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000505 info [process_new_device] found device with address 1 at 001-05ac-8006-09-00
libusb: 0.000792 info [process_new_device] allocating new device for location 0xfd100000
libusb: 0.001268 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.001282 info [process_new_device] found device with address 2 at 002-0424-2513-09-00
libusb: 0.001630 info [process_new_device] allocating new device for location 0xfa100000
libusb: 0.001768 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.001777 info [process_new_device] found device with address 2 at 002-0424-2513-09-00
libusb: 0.002089 info [process_new_device] allocating new device for location 0xfa110000
libusb: 0.002341 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.002350 info [process_new_device] found device with address 4 at 004-0a5c-4500-09-00
libusb: 0.002658 info [process_new_device] allocating new device for location 0xfa200000
libusb: 0.150367 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.150391 info [process_new_device] found device with address 3 at 003-05ac-8509-ef-02
libusb: 0.150845 info [process_new_device] allocating new device for location 0xfd110000
libusb: 0.302223 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.302276 info [process_new_device] found device with address 3 at 003-05ac-8242-00-00
libusb: 0.302925 info [process_new_device] allocating new device for location 0xfa120000
libusb: 0.303779 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.303792 info [process_new_device] found device with address 5 at 005-05ac-0245-00-00
libusb: 0.304128 info [process_new_device] allocating new device for location 0xfa113000
libusb: 0.304618 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.304639 info [process_new_device] found device with address 8 at 008-05ac-821a-ff-01
libusb: 0.304972 info [process_new_device] allocating new device for location 0xfa130000
libusb: 0.305337 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.305346 info [process_new_device] found device with address 6 at 006-04d8-fc90-00-00
libusb: 0.305869 info [darwin_open] device open for access
libusb: 0.306290 error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
Cannot claim device
Unable to set alternative interface
libusb: 0.306657 info [darwin_async_io_callback] an async io operation has completed
libusb: 0.306737 info [op_handle_events] checking fd 4 with revents = 0
libusb: 0.306749 info [op_handle_events] checking fd 6 with revents = 1
libusb: 0.306757 info [darwin_handle_callback] handling control completion with kernel status 0
libusb: 0.306772 info [ep_to_pipeRef] converting ep address 0x81 to pipeRef and interface
libusb: 0.306778 warning [ep_to_pipeRef] no pipeRef found with endpoint address 0x81.
libusb: 0.306784 error [submit_bulk_transfer] endpoint not found on any open interface
Other error - recv
[/size]

Are there any suggestions?  I don't think the device is really open because I (as the user) have not caused any application to want to open the device.  I think the PIC did make it into BOOTLOADER mode because I cannot repeat the command until I reset the device (while holding the "UPDATE" button).  Here is what I get if I do NOT reset while holding update:
Code: [Select]
Proton:ols-fwloader-0.1 wayne$ ols_fwloader -f BOOT -n -P /dev/tty.usbmodemfa131 -V -W -w ~/Downloads/ols-0308/OLS_Upgrader/PIC_firmware/OLSv1.firmware.v3.0.hex
Unable to open port '/dev/tty.usbmodemfa131'
Unable to open OLS
[/size]

Re: OLS files and utilities - Windows, Linux, Mac

Reply #16
Quote
But when using Jawi's client, the "show device metadata" button comes up blank. In addition, using test mode and connecting to the wing connector does not give the correct test pattern, so I don't think I'm quite there yet. Suggestions?

I just got a new OLS from Seeed. I also followed all the instructions and am using Jawi's latest client.

I also cannot get the client to "show device metadata".

I have not tried the cable to wing connector in test mode. I'll try and get around to that soon. I wouldn't be surprised if the cable arrangement is wrong. The cable instructions are not clear at all; to me anyway.

But it looks like there's definitely something wrong with the "Show Device Metadata". Maybe Seeed is shipping with outdated firmware again - dunno, can't check the Metadata :-(

For this I am using an old (but yummy) IBM R51 laptop with Windows XP SP3+ and the latest JRE.

Re: OLS files and utilities - Windows, Linux, Mac

Reply #17
More than a month and still no reply to missing metadata. I'm not the only one seeing this problem. Is the DP forum the go-to place regarding OLS issues or should I look elsewhere?

Re: OLS files and utilities - Windows, Linux, Mac

Reply #18
Just tested out, works nice on my system with Ubuntu 12.10 64-bit and client 0.9.6.1, shown firmware is 3.07 which is true.

Can you give more info? Client version, system (Still XP?), firmware version and such?

If you suspect outdated firmware just try updating it, that should eliminate a possibility.

Re: OLS files and utilities - Windows, Linux, Mac

Reply #19
Hi, Tayken... I'm using WinXP SP3+ on an IBM R51 laptop with Jawi's ols-0.9.6 SP1 client released 29 October 2012. I don't know what the firmware version is because that's the problem; the firmware metadata is not being displayed. My OLS was purchased from Seeed in mid-January 2013, so that may give someone an idea what firmware it may contain. But then again, you never know what you're getting firmware-wise when you are buying from Seeed, sometimes they don't keep up. Yes, I could flash the latest firmware. But that's not the subject of this "no firmware metadata" discussion. Plus, the device seems to be working fine except for the firmware information. I wish I had the time and knowledge to fix this myself and contribute back - but I don't. Best regards...

Re: OLS files and utilities - Windows, Linux, Mac

Reply #20
@Drone: sorry about missing your 1st post. In general, when the OLS client does not display any metadata on a device, it most probably has an "old" firmware version flashed.

The metadata command was added later on, as an extension to the original SUMP protocol. It is always considered an optional addition to the original protocol, in the sense that devices can not respond to that command. As far as I now know, all devices produced by DP that include support for the SUMP protocol include support for the metadata command in their latest firmware versions.

So, getting back to the original question: yes, it is normal that the "show device metadata" function in the OLS client returns no information for a device. The device will still function correctly with the OLS client, but you need to make some manual changes to the settings yourself (information that is derived from the metadata that might otherwise be returned)...
when good software is not an alternative...

Re: OLS files and utilities - Windows, Linux, Mac

Reply #21
Hi guys,

I'm new to the OLS party (and to Logic Analyzers at all) and just bought a Bus Pirate (3.6) and got my Open Bench Logic Sniffer (1.04 board) today.
I'm on Mac OS X, too, currently on 10.8.4. Is there really still no support for OS X users?? The firmware download page over at the gadget factory site still says "coming soon". :-(

I downloaded the 0.4 binary of the ols-loader utility that was posted here in this thread and tried it but to no avail. I can't even read out which firmware version my logic sniffer board has:
Code: [Select]
stefan@mimac{~/Downloads} ./ols-loader -p:/dev/tty.usbmodem1a21 -t:115200 -status
Logic Sniffer ROM loader v0.3 (November 9, 2010)
Opening serial port '/dev/tty.usbmodem1a21' @ 115200 ... OK
Found OLS HW: 0, FW: 0.0, Boot: 0
Error - unknown flash type (00 00 00 00)

When I issued that command immediately after the above output again I even got:
Code: [Select]
stefan@mimac{~/Downloads} ./ols-loader -p:/dev/tty.usbmodem1a21 -t:115200 -status
Logic Sniffer ROM loader v0.3 (November 9, 2010)
Opening serial port '/dev/tty.usbmodem1a21' @ 115200 ... OK
Error reading OLS id

So am I the only one who's trying to use the OLS under a current OS X version? What do all the other Mac user do with their OLS?