Unable to get device serial number about lm4tools HOT 19 OPEN

Hi

Could you please check if this workaround works for you:

https://github.com/zyga/lm4tools/tree/develop

It will work as before and if you have just one board attached it should just work

from lm4tools.

Greg,

Please build lm4flash with DEBUG enabled. Uncomment the line #define DEBUG 1 which is commented out in the code. This will provide some extra info. Also it would be nice setting libusb debug. Please insert the following line just after the call to libusb_init() in the code:

libusb_set_debug(ctx, 3);

Then provide the output here. With that info we'll able to see what's happening and fix the issue.

from lm4tools.

Greg,

Please try the following. Download this file:

http://utzig.net/files/lm4f120_icdi.tgz

Then unpack it at /System/Library/Extensions.

$ cd /System/Library/Extensions
$ sudo tar xzvf ~/lm4f120_icdi.tgz

Need to be root to do that! Touch it:

$ sudo touch lm4f120_icdi.kext

Wait some time and try running lm4flash again. If this fixes your problem please let us know!

from lm4tools.

The one at commit cc49426 uploads fine. Should I still try the kext?

from lm4tools.

That version you mentioned works because it didn't use the board serial number (uses another type of usb request). Other people are already testing this on Mac OS X now so if you're fine with that older version you could keep it. But new versions/features will most probably require this driver. It was already tested and it seems to work ok.

from lm4tools.

This is from the newest commit. This is what happens when I try to upload project0.bin after I compiled lm4flash with debug enabled and added libusb_set_debug(ctx, 3);

$ ./lm4flash ../project0.bin 
libusb: 0.000000 info [process_new_device] allocating new device for location 0xfa000000
libusb: 0.000105 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000121 info [process_new_device] found device with address 1 at 001-05ac-8006-09-00
libusb: 0.000702 info [process_new_device] allocating new device for location 0xfd000000
libusb: 0.000772 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.000788 info [process_new_device] found device with address 1 at 001-05ac-8006-09-00
libusb: 0.001290 info [process_new_device] allocating new device for location 0x1a000000
libusb: 0.001353 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.001364 info [process_new_device] found device with address 1 at 001-05ac-8005-09-00
libusb: 0.001856 info [process_new_device] allocating new device for location 0x3a000000
libusb: 0.001915 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.001926 info [process_new_device] found device with address 1 at 001-05ac-8005-09-00
libusb: 0.002418 info [process_new_device] allocating new device for location 0x5a000000
libusb: 0.002480 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.002491 info [process_new_device] found device with address 1 at 001-05ac-8005-09-00
libusb: 0.002986 info [process_new_device] allocating new device for location 0x3d000000
libusb: 0.003044 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.003055 info [process_new_device] found device with address 1 at 001-05ac-8005-09-00
libusb: 0.003543 info [process_new_device] allocating new device for location 0x5d000000
libusb: 0.003606 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.003617 info [process_new_device] found device with address 1 at 001-05ac-8005-09-00
libusb: 0.004088 info [process_new_device] allocating new device for location 0x1d000000
libusb: 0.004143 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.004153 info [process_new_device] found device with address 1 at 001-05ac-8005-09-00
libusb: 0.004609 info [process_new_device] allocating new device for location 0x1a200000
libusb: 0.006570 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.006589 info [process_new_device] found device with address 2 at 002-046d-c318-00-00
libusb: 0.007048 info [process_new_device] allocating new device for location 0x5a100000
libusb: 0.012562 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.012576 info [process_new_device] found device with address 2 at 002-045e-0047-00-00
libusb: 0.012956 info [process_new_device] allocating new device for location 0xfa100000
libusb: 0.019587 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.019598 info [process_new_device] found device with address 2 at 002-046d-081b-ef-02
libusb: 0.019932 info [process_new_device] allocating new device for location 0x1d200000
libusb: 0.021237 info [darwin_check_configuration] active config: 1, first config: 1
libusb: 0.021255 info [process_new_device] found device with address 2 at 002-1cbe-00fd-ef-02
libusb: 0.021780 error [darwin_open] USBDeviceOpen: another process has device opened for exclusive access
libusb: 0.021799 info [darwin_open] device open for access
libusb: 0.022055 error [submit_control_transfer] control request failed: no async port has been opened for interface
Unable to get device serial number: LIBUSB_ERROR_OTHER
Unable to find any ICDI devices
libusb: 0.022174 info [event_thread_main] thread exiting

from lm4tools.

.kext works great by the way! Now time to add this to the Readme!

from lm4tools.

As soon as other issues are fixed, it will. Thanks!

from lm4tools.

This works for me on Mountain Lion too. Thanks!

from lm4tools.

Hi there,

lm4f120_icdi.kext fixes the problem with not being able to find serial numbers for the Stellaris Launch Pad on Mountain Lion, but it causes trouble with other USB devices on my system. In particular, the Nokia Device Browser 1.9.1 (62) software that I use to transfer files to and from my phone.

With lm4f120_icdi.kext installed in the /System/Library/Extensions folder, the Nokia software keeps throwing an error when I connect my phone (Nokia E55) that the device doesn't support some mode of operation and I'm no longer able to access the phone.

When I remove lm4f120_icdi.kext the Nokia software works properly.

I am using lm4flash v 0.1 and libusb 1.0.9_0 (installed via macports) on OS X 10.8.2

I can provide more information if you need anything in particular, just let me know.

from lm4tools.

@letaage The driver should only be responsible for devices with VID=0x1cbe and PID=0x00fd. Could you confirm the VID/PID used by your Nokia device without lm4f120_icdi.kext installed?

from lm4tools.

It comes up with:

Product ID: 0x01d4
Vendor ID: 0x0421 (Nokia Corporation)

And the problem persists, however it seems more reliable if I don't connect my phone via the keyboard USB hub, which is weird because it's been working fine for years.

Also strange that the problem only started when I installed the kext - probably just one of those unfortunate coincidences. I'll keep an eye on it for now.

from lm4tools.

utzig: Thanks, you kext fixed the original issue I had too.

from lm4tools.

Hi,

for me under OSX 10.8.2 the problem still exists. Debug log looks just the same as posted above. The link for the kext is not available. I already tried the developer version linked above without success.

Is there a new workaround available or can someone please re-upload the kext?

Thanks

from lm4tools.

@thefloe1 You can get it here:

http://69.55.60.135/files/lm4f120_icdi.tgz

I changed the DNS so the name doesn't point to the same place anymore. Btw, I'll add the sources for this to the project tomorrow (if I don't forget...) so anyone can build it.

from lm4tools.

how can I access UART using this driver? my mac now flashs fine but I don't have /dev/tty.* anymore.

from lm4tools.

I was going to post the same thing; for now I've rolled back to cc49426 but I'd prefer to use the later versions.

Could the reading of the serial number please be skipped if the option to match it has not been used?

from lm4tools.

@jmeosbn As you suggested I just pushed a version that doesn't use serial number at all no MacOSX. Better leave it out while things are fixed.

from lm4tools.

Thanks, works great!

from lm4tools.