Objective Development Forums

Re: working nicely on my laptop, but fail on my PC?

2011-07-04T12:14:14+02:00

Dear Christian!

You couldn't give an example filtrations of packets in functions usbFunctionWrite () and usbFunctionWriteOut ()?

Statistics: Posted by uchar — Mon Jul 04, 2011 12:14 pm

Re: working nicely on my laptop, but fail on my PC?

2011-05-09T10:50:37+02:00

We have made it possible for the application code to filter packets. See the option USB_CFG_CHECK_DATA_TOGGLING in usbconfig.h for details. This is in all versions since the October 2008 release.

Statistics: Posted by christian — Mon May 09, 2011 10:50 am

Re: working nicely on my laptop, but fail on my PC?

2011-05-09T07:57:16+02:00

@christian

have you solved the problem?
if yes, should I use latest version of vusb driver?

Statistics: Posted by Guest — Mon May 09, 2011 7:57 am

working nicely on my laptop, but fail on my PC?

2008-06-05T18:42:40+02:00

Thanks for the code!

And yes, a similar error can occur when sending data to the PC. This can only be corrected if we mark the transmit buffer as available only after an ACK is received.

Statistics: Posted by christian — Thu Jun 05, 2008 6:42 pm

working nicely on my laptop, but fail on my PC?

2008-06-04T18:58:40+02:00

OK. My code is somewhat ugly.
But will the similar error occur when sending data to PC?

Statistics: Posted by SimonQian — Wed Jun 04, 2008 6:58 pm

working nicely on my laptop, but fail on my PC?

2008-06-03T20:21:00+02:00

Thanks a lot for this capture! We are lucky and it contains the point of error!

It seems it's a bug / transmission error on the host side. The LA capture clearly shows that we send an ACK and the host does not react to it. That's what data toggling is good for, after all.

Here's the decoded capture. The first column is the time in microseconds, the second consists of the data bytes we decoded and the third is the trigger signal.

Code:

   9.700 e1 1   <--- OUT
  15.000 01 1
  20.300 c1 1
--------------
--------------
  37.000 c3 1   <--- DATA0
  42.400 ef 1
  47.700 01 1
  53.100 00 1
  58.400 00 1
  63.700 00 1
  69.100 00 1
  74.400 00 1
  79.700 00 1
  85.100 e0 1
  90.400 e1 1
--------------
--------------
 106.500 5a 1   <--- NAK
--------------
--------------
 124.500 e1 1   <--- OUT
 129.800 01 1
 135.100 c1 1
--------------
--------------
 151.800 c3 1   <--- DATA0
 157.200 ef 1
 162.500 01 1
 167.900 00 1
 173.200 00 1
 178.500 00 1
 183.900 00 1
 189.200 00 1
 194.500 00 1
 199.900 e0 1
 205.200 e1 1
--------------
--------------
 221.200 5a 1   <--- NAK
--------------
--------------
 239.300 e1 1   <--- OUT
 244.600 01 1
 249.900 c1 1
--------------
--------------
 266.600 c3 1   <--- DATA0
 272.000 ef 1
 277.300 01 1
 282.700 00 1
 288.000 00 1
 293.300 00 1
 298.700 00 1
 304.000 00 1
 309.300 00 1
 314.700 e0 1
 320.000 e1 1
--------------
--------------
 337.200 d2 1   <--- ACK [NOT HONORED BY HOST]
--------------
--------------
 357.900 e1 1   <--- OUT
 363.200 01 1
 368.500 c1 1
--------------
--------------
 385.300 c3 1   <--- DATA0
 390.600 ef 1
 396.000 01 1
 401.300 00 1
 406.600 00 1
 412.000 00 1
 417.300 00 1
 422.600 00 1
 428.000 00 1
 433.300 e0 1
 438.600 e1 1
--------------
--------------
 454.800 5a 1   <--- NAK
--------------
--------------
 472.900 e1 1   <--- OUT
 478.200 01 1
 483.500 c1 1
--------------
--------------
 500.300 c3 1   <--- DATA0
 505.600 ef 1
 511.000 01 1
 516.300 00 1
 521.600 00 1
 526.900 00 1
 532.300 00 1
 537.600 00 1
 542.900 00 1
 548.300 e0 1
 553.600 e1 1
--------------
--------------
 569.700 5a 1   <--- NAK
--------------
--------------
 587.700 e1 1   <--- OUT
 593.000 01 1
 598.300 c1 1
--------------
--------------
 615.100 c3 1   <--- DATA0
 620.400 ef 1
 625.800 01 1
 631.100 00 1
 636.400 00 1
 641.800 00 1
 647.100 00 1
 652.400 00 1
 657.700 00 1
 663.100 e0 1
 668.400 e1 1
--------------
--------------
 684.400 5a 1   <--- NAK
--------------
--------------
 702.500 e1 1   <--- OUT
 707.800 01 1
 713.100 c1 1
--------------
--------------
 729.900 c3 1   <--- DATA0
 735.200 ef 1
 740.600 01 1
 745.900 00 1
 751.200 00 1
 756.600 00 1
 761.900 00 1
 767.200 00 1
 772.600 00 1
 777.900 e0 1
 783.200 e1 1
--------------
--------------
 800.500 d2 1   <--- ACK
--------------
--------------
 818.800 e1 1   <--- OUT
 824.100 01 1
 829.400 c1 1
--------------
--------------
 846.200 4b 1   <--- DATA1
 851.500 00 1
 856.900 00 1
 862.200 00 1
 867.500 00 1
 872.900 00 1
 878.200 00 1
 883.500 00 1
 888.900 00 1
 894.200 3f 1
 899.500 e9 1
--------------
--------------
 915.700 5a 1   <--- NAK
--------------
--------------

So it's obvious that we must check for correct data toggling to be sufficiently USB compliant. Can you please send me a summary of your changes by e-mail? I'd like to add them to the next version of the driver or at least add hooks so that users can check for data toggling.

Statistics: Posted by christian — Tue Jun 03, 2008 8:21 pm

new data

2008-05-31T10:31:58+02:00

http://www.simonqian.com/download/temp/USB_new.zla

Statistics: Posted by SimonQian — Sat May 31, 2008 10:31 am

working nicely on my laptop, but fail on my PC?

2008-05-29T23:11:47+02:00

I'd like to have 99% data before the trigger and 1% after. The relevant things happen before the error is detected.

Statistics: Posted by christian — Thu May 29, 2008 11:11 pm

working nicely on my laptop, but fail on my PC?

2008-05-29T20:20:34+02:00

So you mean set the trigger position to where?
It's 10% by default, so there is 10% data before trigger and 90% after.

Statistics: Posted by SimonQian — Thu May 29, 2008 8:20 pm

working nicely on my laptop, but fail on my PC?

2008-05-26T21:52:36+02:00

Sorry for the delay, I was (and still am) busy with other projects.

I finally had the time to look at the data you set up for download. There's one full packet visible before the trigger point. And I can see that your logic analyzer is capable of recording more than 1 millisecond worth of data at this resolution. That would be up to 10 packets.

Can you please adjust the trigger so that you record everything leading up to the trigger, nothing past the trigger point? Since the trigger is raised when the error is detected, the problem must have been before it.

Thanks in advance!

Statistics: Posted by christian — Mon May 26, 2008 9:52 pm