#12 F330/USB ToolStick (PID 0x8253)

[Frieder Ferlemann]

Hi Ricky,

I'm trying to connect to an "ToolStick F330 DC"
with a ToolStick that shows up on the USB bus
with a vendor/product of ID 0x10c4, 0x8253 but
so far have no success.

Using latest cvs and hacking PID within the two files:
ec2drv/src/ec2tools/ec3adapters.c
ec2drv/src/ec2drv/ec2drv.c
(as also done in support request #1698256) results in:

# ec2device --port=USB --debug

*********************************************************************
* WARNING: Auto detection of mode may cause initialisation sequence *
* to differ significantly from the SiLabs IDE. *
* In the case of problems specify --mode=C2 or --mode=JTAG *
*********************************************************************

0x10c4, 0x8253
can we talk to it?
ec2_reset C2
TX: 03 00 00 00
ec2device:ec2drv.c:1865:
usb_interrupt_write in write_usb returned -2 : No such file or directory
exiting now
TX: 01 21
ec2device:ec2drv.c:1865:
usb_interrupt_write in write_usb returned -2 : No such file or directory
#

(I'll attach a Snoopy Pro Usb Log to this report when I
find time and a Windows PC:)

[Frieder Ferlemann]

strace ec2device --port=USB --debug 2>ec2device.strace

[Frieder Ferlemann]

Snoopy Pro USB Log (Plugin, then connect from IDE2.91)

[Frieder Ferlemann]

Logged In: YES
user_id=589052
Originator: YES

File Added: USBLog3.usblog

[Ricky White]

Logged In: YES
user_id=22723
Originator: NO

Thanks for the capture, sorry It took me so long to get round to looking at it.

I think I have made the changes necessary to work with this toolstick to the subversion trunk.
Unfortunaltly I can't test the toolstick part as I don't have one of those.

The main difference for the toolstick is that it does not use a bootloader and just starts straight into the debugger application whereas an EC3 needs to be told to leave its bootloader.

Thanks
Ricky

[Frieder Ferlemann]

Logged In: YES
user_id=589052
Originator: YES

Thanks:) SVN revision 333 recognizes and resets the toolstick fine but stops a little later:

---8<--------------------------------------------------------------------
# ec2device --port=USB --debug
*********************************************************************
* WARNING: Auto detection of mode may cause initialisation sequence *
* to differ significantly from the SiLabs IDE. *
* In the case of problems specify --mode=C2 or --mode=JTAG *
*********************************************************************

0x0424, 0x2228
0x0424, 0x2602
0x0424, 0x2502
0x0000, 0x0000
0x0000, 0x0000
Found ToolStick F330 DC
ec2_reset C2
ToolStick F330 DC debugger, no version information
TX: 01 20
ec2device:ec2drv.c:1918:
usb_interrupt_write in write_usb returned -2 : No such file or directory
exiting now
TX: 01 21
ec2device:ec2drv.c:1918:
usb_interrupt_write in write_usb returned -2 : No such file or directory
--->8--------------------------------------------------------------------

I'm attaching the strace output of:
# strace -tt -s80 ec2device --port=USB --debug 2>ec2drv.strace.r330
to the report. Should I give some other info?

Greetings,
Frieder
File Added: ec2drv.strace.r330

[Frieder Ferlemann]

strace -tt -s80 ec2device --port=USB --debug 2>ec2drv.strace.r330

[Ricky White]

Logged In: YES
user_id=22723
Originator: NO

Hi
Sorry about the delay,
I got busy with christmas and redecorating another room etc.

Looking at your result it looks like it dies quite early so I'm not sure what is going on.
I'm thinking there is something in the USB setup control commands that is wrong causing the device to disconnect from the USB port causing the "write_usb returned -2 : No such file or directory".

I'll have another look at the debug traces (especially the control transfers) to see If I can spot anything. Failing that I'm about to order some more chips so I will probably order one of these toolsticks to have a play with at the same time.

These toolsticks seem to be becomming more common.

Ricky