Re: [UrJTAG-dev] urjtag and libusb1

[Xiaofan C. <xia...@gm...>]

On Fri, Jun 25, 2010 at 12:30 AM, Mike Frysinger <va...@ge...> wrote:

> ignoring all that, urjtag cant touch drivers since it doesnt run as root (and
> if you are running it as root, you're doing it wrong).

Typically I use udev rules to set the permission.

>> Older V3 J-Link does not work. UrJtag may take some codes from
>> the OpenOCD project to support older J-Link models (V3/V4).
>
> more importantly, does the cable work *without* my patch and using libusb-0.x
> API ?  if so, then my changes are irrelevant to this issue and i'll go ahead
> and commit them.

You can commit the patch. The V3 does not work before your patch
with libusb-0.1.

>> mcuee@ubuntu64-laptop:/sys/bus/usb/drivers/ftdi_sio$ lsusb
>> ...
>> Bus 003 Device 003: ID 0403:bcd9 Future Technology Devices
>> International, Ltd Stellaris Evaluation Board
>
> urjtag only attaches to USB VID:PID's it knows about.  certainly the default
> USB VID:PID from the FTDI default eeprom will not work, so this is currently
> expected behavior.  the kernel also cannot know to blacklist either of the
> endpoints for the eval board, so you'll need to remove the driver yourself.

I see. This is the TI/Luminary EK-LM3s1968 demo board.

>> jtag> detect
>> IR length: 4
>> Chain length: 1
>> Device Id: 00111011101000000000010001110111 (0x3BA00477)
>>   Unknown manufacturer! (01000111011)
>
> looks like you should add this part to the urjtag database

It is TI/Luminary Cortex M3 part: LM3S1968. I have the
Olimex LPC-P2148 for NXP LPC-2148 ARM7) board as well.
I do not see the support of these chips in UrJTAG. Maybe
I will try to get some boards supported.



-- 
Xiaofan http://mcuee.blogspot.com