Menu
▾
▴
javax-usb-devel
|
From: SANJAY G. <gup...@sa...> - 2013-10-02 10:36:30
|
Sorry for a mistake.
The code is working fine but I am facing problem if I want to change the outData i.e. either increase the size, reduce the size or change the data.
Thanks,
Sanjay Gupta
------- Original Message -------
Sender : SANJAY GUPTA<gup...@sa...> S5/Senior Engineer/Architecture Analysis Lab./Samsung Electronics
Date : Oct 02, 2013 19:23 (GMT+09:00)
Title : [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
Hi All,
Please look below the sample scenario:-
final byte[] outData = new byte[] {
(byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
(byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
(byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
(byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
(byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
(byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
(byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
(byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
final byte[] inData = new byte[13];
log("Synchronously submitting the byte[] to UsbPipe ...");
outUsbPipe.syncSubmit(data);
//Synchronously read the status from IN UsbPipe
log("Synchronously reading the status from IN UsbPipe ...");
inUsbPipe.syncSubmit(inData);
This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
The control gets hang on reading the status data from the Input UsbPipe.
Any suggestion on below points will be helpful:-
1. Is there any specific data format (may be starting header) in the actual data being transferred?
2. What is the data size which can be transferred using single invocation of syncSubmit()?
3. What is the status data size which is received on Input Pipe as a result of out data transfer?
Thanks in Advance..
Sanjay Gupta
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
javax-usb-devel mailing list
jav...@li...
https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
|
From: SANJAY G. <gup...@sa...> - 2013-10-04 03:02:03
|
<HTML><HEAD><TITLE>Samsung Enterprise Portal mySingle</TITLE>
<META content=IE=5 http-equiv=X-UA-Compatible>
<META content="text/html; charset=euc-kr" http-equiv=Content-Type>
<STYLE id=mysingle_style type=text/css>P {
MARGIN-BOTTOM: 5px; FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN-TOP: 5px
}
TD {
MARGIN-BOTTOM: 5px; FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN-TOP: 5px
}
LI {
MARGIN-BOTTOM: 5px; FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN-TOP: 5px
}
BODY {
FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN: 10px; LINE-HEIGHT: 1.4
}
</STYLE>
<META name=GENERATOR content=ActiveSquare></HEAD>
<BODY>
<P>Thanks,<BR>Sanjay Gupta<p>&nbsp;</p><p>&nbsp;</p><BR><BR>------- Original Message -------<BR>Sender : Dan Streetman<dds...@ie...> <BR>Date : Oct 02, 2013 22:31 (GMT+09:00)<BR>Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])<BR><BR>On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:<BR>> Hi All,<BR>><BR>> Please look below the sample scenario:-<BR>><BR>> final byte[] outData = new byte[] {<BR>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,<BR>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,<BR>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,<BR>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,<BR>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,<BR>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,<BR>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,<BR>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }<BR>> final byte[] inData = new byte[13];<BR>><BR>> log("Synchronously submitting the byte[] to UsbPipe ...");<BR>> outUsbPipe.syncSubmit(data);<BR>><BR>> //Synchronously read the status from IN UsbPipe<BR>> log("Synchronously reading the status from IN UsbPipe ...");<BR>> inUsbPipe.syncSubmit(inData);<BR>><BR>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.<BR>> The control gets hang on reading the status data from the Input UsbPipe.<BR>> Any suggestion on below points will be helpful:-<BR>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?<BR><BR>Data formats are entirely up to the device, unless the device<BR>implements a higher level spec (like HID, mass storage, etc) that<BR>itself contains the API for the data format. USB doesn't specify any<BR>data format at all, except for the control pipe 8-byte setup packet<BR>that must preface each control transfer, and the various default<BR>control pipe standard requests (set interface, clear stall, etc).<BR><BR></P>
<P><SPAN style="COLOR: #0000ff">===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.</SPAN></P>
<P><SPAN style="COLOR: #0000ff">But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.</SPAN></P>
<P><SPAN style="COLOR: #0000ff">And then I have no choice but the unplug the device.</SPAN><BR><BR><BR><BR>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?<BR><BR>it's been a while, but IIRC there's no limit in java, although I think<BR>the platform may enforce limits. I don't really remember the details<BR>though. For interrupt pipes, you of course should usually submit<BR>exactly the pipe size (wMaxPacketSize).<BR></P>
<P><SPAN style="COLOR: #0000ff"><SPAN style="COLOR: #0000ff">===> Mass-storage device and BULK type UsbEndpoint.</SPAN></SPAN><BR><BR>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?<BR><BR>it's entirely dependent on your device. although if your input pipe<BR>is an interrupt pipe, it should be the wMaxPacketSize from the<BR>endpoint descriptor.<BR><BR>Also, assuming your input pipe is interrupt type, it's probably better<BR>for you to keep a buffer on it, which will cause continuous polling of<BR>the device, as required by spec when the device is in use. You can do<BR>that either with a separate Thread that does nothing except<BR>syncSubmit() a buffer or irp to the pipe, then passes the returned<BR>data off somewhere else to process and immediately syncSubmit() a new<BR>buffer, or you can use asyncSubmit() with either a listener on the<BR>pipe or a separate Thread to waitUntilComplete() for the irp, and then<BR>also hand off the returned data to process somewhere else and<BR>immediately sync or async submit again a new buffer. With<BR>asyncSubmit(), you can submit multiple buffers, which is better<BR>because it keeps the low level platform queued up with buffers so that<BR>the device polling never stops, and you don't have to try to be quite<BR>so fast at resubmitting a new buffer.<BR></P>
<P><SPAN style="COLOR: #0000ff">===> Mass-storage device and BULK type UsbEndpoint.</SPAN></P>
<P><BR><BR>><BR>> Thanks in Advance..<BR>> Sanjay Gupta<BR>><BR>> ------------------------------------------------------------------------------<BR>> October Webinars: Code for Performance<BR>> Free Intel webinars can help you accelerate application performance.<BR>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from<BR>> the latest Intel processors and coprocessors. See abstracts and register ><BR>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk<BR>> _______________________________________________<BR>> javax-usb-devel mailing list<BR>> jav...@li...<BR>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel<BR></P></BODY></HTML><img src='http://ext.samsung.net/mailcheck/SeenTimeChecker?do=5b5b806e569672b08cefaf4d8420c5e41c40cf68e6889fd228f41a3773fe88f8a28a0f20ff0f747d3545973b7b0cb61b980b3871b38ac66662d74ed859d628c32758cd62c5cf0684a728c55b39cc59eacf878f9a26ce15a0' border=0 width=0 height=0 style='display:none'> |
|
From: Dan S. <dds...@ie...> - 2013-10-04 17:58:33
|
On Thu, Oct 3, 2013 at 11:01 PM, SANJAY GUPTA <gup...@sa...> wrote:
>
> Thanks,
> Sanjay Gupta<p> </p><p> </p>
>
> ------- Original Message -------
> Sender : Dan Streetman<dds...@ie...>
> Date : Oct 02, 2013 22:31 (GMT+09:00)
> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>
>
>
> On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
> > Hi All,
> >
> > Please look below the sample scenario:-
> >
> > final byte[] outData = new byte[] {
> > (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
> > (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
> > (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
> > (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
> > (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
> > (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
> > (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
> > (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
> > final byte[] inData = new byte[13];
> >
> > log("Synchronously submitting the byte[] to UsbPipe ...");
> > outUsbPipe.syncSubmit(data);
> >
> > //Synchronously read the status from IN UsbPipe
> > log("Synchronously reading the status from IN UsbPipe ...");
> > inUsbPipe.syncSubmit(inData);
> >
> > This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
> > The control gets hang on reading the status data from the Input UsbPipe.
> > Any suggestion on below points will be helpful:-
> > 1. Is there any specific data format (may be starting header) in the actual data being transferred?
>
> Data formats are entirely up to the device, unless the device
> implements a higher level spec (like HID, mass storage, etc) that
> itself contains the API for the data format. USB doesn't specify any
> data format at all, except for the control pipe 8-byte setup packet
> that must preface each control transfer, and the various default
> control pipe standard requests (set interface, clear stall, etc).
>
> ===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
>
> But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
>
> And then I have no choice but the unplug the device.
Sorry, I don't understand what you are talking about.
>
>
>
> > 2. What is the data size which can be transferred using single invocation of syncSubmit()?
>
> it's been a while, but IIRC there's no limit in java, although I think
> the platform may enforce limits. I don't really remember the details
> though. For interrupt pipes, you of course should usually submit
> exactly the pipe size (wMaxPacketSize).
>
> ===> Mass-storage device and BULK type UsbEndpoint.
I believe the only restriction on size is from the platform (i.e. OS),
for which you should get a UsbPlatformException if you exceed it (I
think). Last I checked (a long time ago) I believe it was around 16k
max for bulk. But remember that no more than the device's max packet
size will be transferred at once; the OS will break up your larger
buffer into max packet sized chunks and transfer those. So really,
you do not need to transfer gigantic buffers - just break it up into
reasonably-sized buffers and submit them; you can asyncSubmit()
multiple buffers at once which will queue up and transfer as fast as
one giant buffer would.
>
> > 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
>
> it's entirely dependent on your device. although if your input pipe
> is an interrupt pipe, it should be the wMaxPacketSize from the
> endpoint descriptor.
>
> Also, assuming your input pipe is interrupt type, it's probably better
> for you to keep a buffer on it, which will cause continuous polling of
> the device, as required by spec when the device is in use. You can do
> that either with a separate Thread that does nothing except
> syncSubmit() a buffer or irp to the pipe, then passes the returned
> data off somewhere else to process and immediately syncSubmit() a new
> buffer, or you can use asyncSubmit() with either a listener on the
> pipe or a separate Thread to waitUntilComplete() for the irp, and then
> also hand off the returned data to process somewhere else and
> immediately sync or async submit again a new buffer. With
> asyncSubmit(), you can submit multiple buffers, which is better
> because it keeps the low level platform queued up with buffers so that
> the device polling never stops, and you don't have to try to be quite
> so fast at resubmitting a new buffer.
>
> ===> Mass-storage device and BULK type UsbEndpoint.
The size on an input bulk pipe is entirely up to the device; but
again, it's transferred at the low level in max packet sized chunks.
So just asyncSubmit multiple buffers that are a sized as a multiple of
the max packet size, or even just buffers that are exactly the max
packet size.
>
>
>
> >
> > Thanks in Advance..
> > Sanjay Gupta
> >
> > ------------------------------------------------------------------------------
> > October Webinars: Code for Performance
> > Free Intel webinars can help you accelerate application performance.
> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> > the latest Intel processors and coprocessors. See abstracts and register >
> > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> > _______________________________________________
> > javax-usb-devel mailing list
> > jav...@li...
> > https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>
|
|
From: SANJAY G. <gup...@sa...> - 2013-10-07 05:38:29
Attachments:
201310071438489_BGFC2LL5.gif
|
<HTML><HEAD><TITLE>Samsung Enterprise Portal mySingle</TITLE>
<META content=IE=5 http-equiv=X-UA-Compatible>
<META content="text/html; charset=euc-kr" http-equiv=Content-Type>
<STYLE id=mysingle_style type=text/css>P {
MARGIN-BOTTOM: 5px; FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN-TOP: 5px
}
TD {
MARGIN-BOTTOM: 5px; FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN-TOP: 5px
}
LI {
MARGIN-BOTTOM: 5px; FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN-TOP: 5px
}
BODY {
FONT-SIZE: 12pt; FONT-FAMILY: 굴림체, arial; MARGIN: 10px; LINE-HEIGHT: 1.4
}
</STYLE>
<META name=GENERATOR content=ActiveSquare></HEAD>
<BODY>
<P><SPAN style="FONT-SIZE: 10pt">Thanks for your great support.</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt">I tried below as suggested:-</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 10pt"> </SPAN><SPAN style="FONT-SIZE: 10pt"><SPAN style="FONT-SIZE: 8pt">int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );<BR> log("Max Packet Size: " + maxPacketSize);<BR> final byte[] buffer = new byte[8192];</SPAN></SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"> for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {<BR> final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );<BR> usbIrp.setData(buffer, offset, maxPacketSize);</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 8pt"> //Asynchronously submit the UsbIrp to UsbPipe</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"> log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");<BR> outUsbPipe.asyncSubmit(usbIrp);</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 8pt"> //Wait for the UsbIrp to complete<BR> log("Waiting for the UsbIrp to complete ...");<BR> usbIrp.waitUntilComplete();</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 8pt"> log("!!! Successfully submitted the UsbIrp to UsbPipe ...");<BR> }</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 10pt">But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 10pt"><EM><SPAN style="FONT-SIZE: 8pt">Max Packet Size: 512<BR>==> Asynchronously submitting the UsbIrp to UsbPipe ...<BR>Waiting for the UsbIrp to complete ...<BR>!!! Successfully submitted the UsbIrp to UsbPipe ...<BR>==> Asynchronously submitting the UsbIrp to UsbPipe ...<BR>Waiting for the UsbIrp to complete ...<BR>!!! Successfully submitted the UsbIrp to UsbPipe ...<BR>==> Asynchronously submitting the UsbIrp to UsbPipe ...<BR>Waiting for the UsbIrp to complete ...<BR>!!! Successfully submitted the UsbIrp to UsbPipe ...<BR>==> Asynchronously submitting the UsbIrp to UsbPipe ...<BR>Waiting for the UsbIrp to complete ...</SPAN></EM><SPAN style="FONT-SIZE: 8pt"><BR></SPAN></SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"><SPAN style="FONT-SIZE: 8pt"> </P></SPAN></SPAN>
<P><SPAN style="FONT-SIZE: 10pt">I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"></SPAN> </P><SPAN style="FONT-SIZE: 10pt">
<P><SPAN style="FONT-SIZE: 8pt">final UsbPipeListener listener = new UsbPipeListener() {</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"> @Override<BR> public void errorEventOccurred(UsbPipeErrorEvent event) {<BR> // TODO Auto-generated method stub</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"> }</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"> @Override<BR> public void dataEventOccurred(UsbPipeDataEvent event) {<BR> final int transferLength = event.getActualLength();<BR> log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 8pt"> //Asynchronously read the status in byte[] from IN UsbPipe<BR> log("Asynchronously reading the status in byte[] from IN UsbPipe ...");<BR> UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);</SPAN></P>
<P><SPAN style="FONT-SIZE: 8pt"></SPAN> </P>
<P><SPAN style="FONT-SIZE: 8pt"> //Wait for the UsbIrp to complete<BR> log("Waiting for the reading to complete ...");<BR> irp.waitUntilComplete();<BR> }<BR> };<BR> inUsbPipe.addUsbPipeListener(listener);</SPAN></SPAN></P>
<P><EM><SPAN style="FONT-SIZE: 10pt"></SPAN></EM> </P>
<P><SPAN style="FONT-SIZE: 10pt">------- Original Message -------<BR>Sender : Dan Streetman<dds...@ie...> <BR>Date : Oct 02, 2013 22:31 (GMT+09:00)<BR>Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])<BR><BR>On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:<BR>> Hi All,<BR>><BR>> Please look below the sample scenario:-<BR>><BR>> final byte[] outData = new byte[] {<BR>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,<BR>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,<BR>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,<BR>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,<BR>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,<BR>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,<BR>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,<BR>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }<BR>> final byte[] inData = new byte[13];<BR>><BR>> log("Synchronously submitting the byte[] to UsbPipe ...");<BR>> outUsbPipe.syncSubmit(data);<BR>><BR>> //Synchronously read the status from IN UsbPipe<BR>> log("Synchronously reading the status from IN UsbPipe ...");<BR>> inUsbPipe.syncSubmit(inData);<BR>><BR>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.<BR>> The control gets hang on reading the status data from the Input UsbPipe.<BR>> Any suggestion on below points will be helpful:-<BR>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?<BR><BR>Data formats are entirely up to the device, unless the device<BR>implements a higher level spec (like HID, mass storage, etc) that<BR>itself contains the API for the data format. USB doesn't specify any<BR>data format at all, except for the control pipe 8-byte setup packet<BR>that must preface each control transfer, and the various default<BR>control pipe standard requests (set interface, clear stall, etc).<BR><BR></SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt; COLOR: #0000ff">===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt; COLOR: #0000ff">But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt; COLOR: #0000ff">And then I have no choice but the unplug the device.</SPAN><SPAN style="FONT-SIZE: 10pt"><BR><BR><BR><BR>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?<BR><BR>it's been a while, but IIRC there's no limit in java, although I think<BR>the platform may enforce limits. I don't really remember the details<BR>though. For interrupt pipes, you of course should usually submit<BR>exactly the pipe size (wMaxPacketSize).<BR></SPAN></P>
<P><SPAN style="COLOR: #0000ff"><SPAN style="FONT-SIZE: 10pt; COLOR: #0000ff">===> Mass-storage device and BULK type UsbEndpoint.</SPAN></SPAN><SPAN style="FONT-SIZE: 10pt"><BR><BR>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?<BR><BR>it's entirely dependent on your device. although if your input pipe<BR>is an interrupt pipe, it should be the wMaxPacketSize from the<BR>endpoint descriptor.<BR><BR>Also, assuming your input pipe is interrupt type, it's probably better<BR>for you to keep a buffer on it, which will cause continuous polling of<BR>the device, as required by spec when the device is in use. You can do<BR>that either with a separate Thread that does nothing except<BR>syncSubmit() a buffer or irp to the pipe, then passes the returned<BR>data off somewhere else to process and immediately syncSubmit() a new<BR>buffer, or you can use asyncSubmit() with either a listener on the<BR>pipe or a separate Thread to waitUntilComplete() for the irp, and then<BR>also hand off the returned data to process somewhere else and<BR>immediately sync or async submit again a new buffer. With<BR>asyncSubmit(), you can submit multiple buffers, which is better<BR>because it keeps the low level platform queued up with buffers so that<BR>the device polling never stops, and you don't have to try to be quite<BR>so fast at resubmitting a new buffer.<BR></SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt; COLOR: #0000ff">===> Mass-storage device and BULK type UsbEndpoint.</SPAN></P>
<P><SPAN style="FONT-SIZE: 10pt"><BR><BR>><BR>> Thanks in Advance..<BR>> Sanjay Gupta<BR>><BR>> ------------------------------------------------------------------------------<BR>> October Webinars: Code for Performance<BR>> Free Intel webinars can help you accelerate application performance.<BR>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from<BR>> the latest Intel processors and coprocessors. See abstracts and register ><BR>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk<BR>> _______________________________________________<BR>> javax-usb-devel mailing list<BR>> jav...@li...<BR>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel<BR></SPAN></P><SPAN style="FONT-SIZE: 10pt"><IMG style="DISPLAY: none" border=0 src="http://ext.samsung.net/mailcheck/SeenTimeChecker?do=5b5b806e569672b08cefaf4d8420c5e41c40cf68e6889fd228f41a3773fe88f8a28a0f20ff0f747d3545973b7b0cb61b980b3871b38ac66662d74ed859d628c32758cd62c5cf0684a728c55b39cc59eacf878f9a26ce15a0" width=0 height=0> </SPAN>
<P><SPAN style="FONT-SIZE: 10pt"></SPAN> </P>
<TABLE id=confidentialsignimg>
<TBODY>
<TR>
<TD NAMO_LOCK>
<P><SPAN style="FONT-SIZE: 10pt"><IMG border=0 src="cid:XOK...@na..." width=520></SPAN></P></TD></TR></TBODY></TABLE></BODY></HTML><img src='http://ext.samsung.net/mailcheck/SeenTimeChecker?do=5b5b806e569672b0bc92d2761ed4130879e64b9460f8cf0c28f41a3773fe88f8a28a0f20ff0f747d3545973b7b0cb61b980b3871b38ac66662d74ed859d628c32758cd62c5cf0684a728c55b39cc59eacf878f9a26ce15a0' border=0 width=0 height=0 style='display:none'> |
|
From: SANJAY G. <gup...@sa...> - 2013-10-07 05:48:13
|
Reposting the query after removing formatting...
Thanks for your great support.
I tried below as suggested:-
int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );
log("Max Packet Size: " + maxPacketSize);
final byte[] buffer = new byte[8192];
for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {
final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );
usbIrp.setData(buffer, offset, maxPacketSize);
//Asynchronously submit the UsbIrp to UsbPipe
log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");
outUsbPipe.asyncSubmit(usbIrp);
//Wait for the UsbIrp to complete
log("Waiting for the UsbIrp to complete ...");
usbIrp.waitUntilComplete();
log("!!! Successfully submitted the UsbIrp to UsbPipe ...");
}
But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-
Max Packet Size: 512
==> Asynchronously submitting the UsbIrp to UsbPipe ...
Waiting for the UsbIrp to complete ...
!!! Successfully submitted the UsbIrp to UsbPipe ...
==> Asynchronously submitting the UsbIrp to UsbPipe ...
Waiting for the UsbIrp to complete ...
!!! Successfully submitted the UsbIrp to UsbPipe ...
==> Asynchronously submitting the UsbIrp to UsbPipe ...
Waiting for the UsbIrp to complete ...
!!! Successfully submitted the UsbIrp to UsbPipe ...
==> Asynchronously submitting the UsbIrp to UsbPipe ...
Waiting for the UsbIrp to complete ...
I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.
final UsbPipeListener listener = new UsbPipeListener() {
@Override
public void errorEventOccurred(UsbPipeErrorEvent event) {
// TODO Auto-generated method stub
}
@Override
public void dataEventOccurred(UsbPipeDataEvent event) {
final int transferLength = event.getActualLength();
log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);
//Asynchronously read the status in byte[] from IN UsbPipe
log("Asynchronously reading the status in byte[] from IN UsbPipe ...");
UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);
//Wait for the UsbIrp to complete
log("Waiting for the reading to complete ...");
irp.waitUntilComplete();
}
};
inUsbPipe.addUsbPipeListener(listener);
------- Original Message -------
Sender : Dan Streetman<dds...@ie...>
Date : Oct 02, 2013 22:31 (GMT+09:00)
Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
> Hi All,
>
> Please look below the sample scenario:-
>
> final byte[] outData = new byte[] {
> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
> final byte[] inData = new byte[13];
>
> log("Synchronously submitting the byte[] to UsbPipe ...");
> outUsbPipe.syncSubmit(data);
>
> //Synchronously read the status from IN UsbPipe
> log("Synchronously reading the status from IN UsbPipe ...");
> inUsbPipe.syncSubmit(inData);
>
> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
> The control gets hang on reading the status data from the Input UsbPipe.
> Any suggestion on below points will be helpful:-
> 1. Is there any specific data format (may be starting header) in the actual data being transferred?
Data formats are entirely up to the device, unless the device
implements a higher level spec (like HID, mass storage, etc) that
itself contains the API for the data format. USB doesn't specify any
data format at all, except for the control pipe 8-byte setup packet
that must preface each control transfer, and the various default
control pipe standard requests (set interface, clear stall, etc).
===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
And then I have no choice but the unplug the device.
> 2. What is the data size which can be transferred using single invocation of syncSubmit()?
it's been a while, but IIRC there's no limit in java, although I think
the platform may enforce limits. I don't really remember the details
though. For interrupt pipes, you of course should usually submit
exactly the pipe size (wMaxPacketSize).
===> Mass-storage device and BULK type UsbEndpoint.
> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
it's entirely dependent on your device. although if your input pipe
is an interrupt pipe, it should be the wMaxPacketSize from the
endpoint descriptor.
Also, assuming your input pipe is interrupt type, it's probably better
for you to keep a buffer on it, which will cause continuous polling of
the device, as required by spec when the device is in use. You can do
that either with a separate Thread that does nothing except
syncSubmit() a buffer or irp to the pipe, then passes the returned
data off somewhere else to process and immediately syncSubmit() a new
buffer, or you can use asyncSubmit() with either a listener on the
pipe or a separate Thread to waitUntilComplete() for the irp, and then
also hand off the returned data to process somewhere else and
immediately sync or async submit again a new buffer. With
asyncSubmit(), you can submit multiple buffers, which is better
because it keeps the low level platform queued up with buffers so that
the device polling never stops, and you don't have to try to be quite
so fast at resubmitting a new buffer.
===> Mass-storage device and BULK type UsbEndpoint.
>
> Thanks in Advance..
> Sanjay Gupta
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
|
From: Dan S. <dds...@ie...> - 2013-10-07 12:37:42
|
On Mon, Oct 7, 2013 at 1:48 AM, SANJAY GUPTA <gup...@sa...> wrote:
> Reposting the query after removing formatting...
>
> Thanks for your great support.
> I tried below as suggested:-
>
> int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );
> log("Max Packet Size: " + maxPacketSize);
> final byte[] buffer = new byte[8192];
> for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {
> final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );
> usbIrp.setData(buffer, offset, maxPacketSize);
Well I don't think I suggested splitting the output data into max
packet sized irps, that's certainly unnecessary and will drastically
cut down on your throughput. I think I said use "reasonable" buffer
sizes. I'm pretty sure 8k is ok to send in a single irp.
>
> //Asynchronously submit the UsbIrp to UsbPipe
> log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");
> outUsbPipe.asyncSubmit(usbIrp);
>
> //Wait for the UsbIrp to complete
> log("Waiting for the UsbIrp to complete ...");
> usbIrp.waitUntilComplete();
>
> log("!!! Successfully submitted the UsbIrp to UsbPipe ...");
> }
>
> But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-
>
> Max Packet Size: 512
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
> !!! Successfully submitted the UsbIrp to UsbPipe ...
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
> !!! Successfully submitted the UsbIrp to UsbPipe ...
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
> !!! Successfully submitted the UsbIrp to UsbPipe ...
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
>
>
> I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.
did you actually submit one or more buffers to the input pipe? You
obviously will never get anything if you don't submit a buffer to be
filled.
>
> final UsbPipeListener listener = new UsbPipeListener() {
> @Override
> public void errorEventOccurred(UsbPipeErrorEvent event) {
> // TODO Auto-generated method stub
> }
> @Override
> public void dataEventOccurred(UsbPipeDataEvent event) {
> final int transferLength = event.getActualLength();
> log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);
>
> //Asynchronously read the status in byte[] from IN UsbPipe
> log("Asynchronously reading the status in byte[] from IN UsbPipe ...");
> UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);
you shouldn't be using getActualLength to size the next buffer to send
- it should be consistent, or at least based on the device's protocol,
and the actual length is simply how many bytes this irp returned.
>
> //Wait for the UsbIrp to complete
> log("Waiting for the reading to complete ...");
> irp.waitUntilComplete();
um...what is the point of asyncSubmit() and then immediately in the
same thread waiting for it to complete? Additionally, your listener
callback is supposed to be quick, since calls will come sequentially.
And what is the point of waiting for the irp to complete right before
you exit the method?
> }
> };
> inUsbPipe.addUsbPipeListener(listener);
>
> ------- Original Message -------
> Sender : Dan Streetman<dds...@ie...>
> Date : Oct 02, 2013 22:31 (GMT+09:00)
> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>
> On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
>> Hi All,
>>
>> Please look below the sample scenario:-
>>
>> final byte[] outData = new byte[] {
>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
>> final byte[] inData = new byte[13];
>>
>> log("Synchronously submitting the byte[] to UsbPipe ...");
>> outUsbPipe.syncSubmit(data);
>>
>> //Synchronously read the status from IN UsbPipe
>> log("Synchronously reading the status from IN UsbPipe ...");
>> inUsbPipe.syncSubmit(inData);
>>
>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
>> The control gets hang on reading the status data from the Input UsbPipe.
>> Any suggestion on below points will be helpful:-
>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?
>
> Data formats are entirely up to the device, unless the device
> implements a higher level spec (like HID, mass storage, etc) that
> itself contains the API for the data format. USB doesn't specify any
> data format at all, except for the control pipe 8-byte setup packet
> that must preface each control transfer, and the various default
> control pipe standard requests (set interface, clear stall, etc).
>
>
> ===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
> But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
> And then I have no choice but the unplug the device.
>
>
>
>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?
>
> it's been a while, but IIRC there's no limit in java, although I think
> the platform may enforce limits. I don't really remember the details
> though. For interrupt pipes, you of course should usually submit
> exactly the pipe size (wMaxPacketSize).
>
> ===> Mass-storage device and BULK type UsbEndpoint.
>
>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
>
> it's entirely dependent on your device. although if your input pipe
> is an interrupt pipe, it should be the wMaxPacketSize from the
> endpoint descriptor.
>
> Also, assuming your input pipe is interrupt type, it's probably better
> for you to keep a buffer on it, which will cause continuous polling of
> the device, as required by spec when the device is in use. You can do
> that either with a separate Thread that does nothing except
> syncSubmit() a buffer or irp to the pipe, then passes the returned
> data off somewhere else to process and immediately syncSubmit() a new
> buffer, or you can use asyncSubmit() with either a listener on the
> pipe or a separate Thread to waitUntilComplete() for the irp, and then
> also hand off the returned data to process somewhere else and
> immediately sync or async submit again a new buffer. With
> asyncSubmit(), you can submit multiple buffers, which is better
> because it keeps the low level platform queued up with buffers so that
> the device polling never stops, and you don't have to try to be quite
> so fast at resubmitting a new buffer.
>
> ===> Mass-storage device and BULK type UsbEndpoint.
>
>
>>
>> Thanks in Advance..
>> Sanjay Gupta
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>> _______________________________________________
>> javax-usb-devel mailing list
>> jav...@li...
>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
|
From: SANJAY G. <gup...@sa...> - 2013-10-08 07:51:19
|
Thanks,
Sanjay Gupta<p> </p><p> </p>
------- Original Message -------
Sender : Dan Streetman<dds...@ie...>
Date : Oct 07, 2013 21:37 (GMT+09:00)
Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
On Mon, Oct 7, 2013 at 1:48 AM, SANJAY GUPTA <gup...@sa...> wrote:
> Reposting the query after removing formatting...
>
> Thanks for your great support.
> I tried below as suggested:-
>
> int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );
> log("Max Packet Size: " + maxPacketSize);
> final byte[] buffer = new byte[8192];
> for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {
> final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );
> usbIrp.setData(buffer, offset, maxPacketSize);
Well I don't think I suggested splitting the output data into max
packet sized irps, that's certainly unnecessary and will drastically
cut down on your throughput. I think I said use "reasonable" buffer
sizes. I'm pretty sure 8k is ok to send in a single irp.
==> If I transmit the whole buffer of 8K in single submission using asyncSubmt() and wait for it to complete, the submission never gets completed and stucks on waitUntilComplete(). The same thing happens while using syncSubmit(). I do wait for the asynSubmit() to complete because my purpose is to capture the completion time for the submission for different sized buffers.
Also, please not that the hang happens only when the buffer is uninitialized. If I initialize the buffer then the UsbStallException is thrown.
for (int index=0; index<buffer.length; index++) {
buffer[index] = (byte) index;
}
>
> //Asynchronously submit the UsbIrp to UsbPipe
> log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");
> outUsbPipe.asyncSubmit(usbIrp);
>
> //Wait for the UsbIrp to complete
> log("Waiting for the UsbIrp to complete ...");
> usbIrp.waitUntilComplete();
>
> log("!!! Successfully submitted the UsbIrp to UsbPipe ...");
> }
>
> But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-
>
> Max Packet Size: 512
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
> !!! Successfully submitted the UsbIrp to UsbPipe ...
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
> !!! Successfully submitted the UsbIrp to UsbPipe ...
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
> !!! Successfully submitted the UsbIrp to UsbPipe ...
> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
> Waiting for the UsbIrp to complete ...
>
>
> I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.
did you actually submit one or more buffers to the input pipe? You
obviously will never get anything if you don't submit a buffer to be
filled.
==> My mistake. But I have a feeling that if the status data from the Input pipe is not read then further submission gets stuck. So, how to know that there is some data to be read on the input pipe?
>
> final UsbPipeListener listener = new UsbPipeListener() {
> @Override
> public void errorEventOccurred(UsbPipeErrorEvent event) {
> // TODO Auto-generated method stub
> }
> @Override
> public void dataEventOccurred(UsbPipeDataEvent event) {
> final int transferLength = event.getActualLength();
> log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);
>
> //Asynchronously read the status in byte[] from IN UsbPipe
> log("Asynchronously reading the status in byte[] from IN UsbPipe ...");
> UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);
you shouldn't be using getActualLength to size the next buffer to send
- it should be consistent, or at least based on the device's protocol,
and the actual length is simply how many bytes this irp returned.
>
> //Wait for the UsbIrp to complete
> log("Waiting for the reading to complete ...");
> irp.waitUntilComplete();
um...what is the point of asyncSubmit() and then immediately in the
same thread waiting for it to complete? Additionally, your listener
callback is supposed to be quick, since calls will come sequentially.
And what is the point of waiting for the irp to complete right before
you exit the method?
> }
> };
> inUsbPipe.addUsbPipeListener(listener);
>
> ------- Original Message -------
> Sender : Dan Streetman<dds...@ie...>
> Date : Oct 02, 2013 22:31 (GMT+09:00)
> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>
> On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
>> Hi All,
>>
>> Please look below the sample scenario:-
>>
>> final byte[] outData = new byte[] {
>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
>> final byte[] inData = new byte[13];
>>
>> log("Synchronously submitting the byte[] to UsbPipe ...");
>> outUsbPipe.syncSubmit(data);
>>
>> //Synchronously read the status from IN UsbPipe
>> log("Synchronously reading the status from IN UsbPipe ...");
>> inUsbPipe.syncSubmit(inData);
>>
>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
>> The control gets hang on reading the status data from the Input UsbPipe.
>> Any suggestion on below points will be helpful:-
>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?
>
> Data formats are entirely up to the device, unless the device
> implements a higher level spec (like HID, mass storage, etc) that
> itself contains the API for the data format. USB doesn't specify any
> data format at all, except for the control pipe 8-byte setup packet
> that must preface each control transfer, and the various default
> control pipe standard requests (set interface, clear stall, etc).
>
>
> ===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
> But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
> And then I have no choice but the unplug the device.
>
>
>
>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?
>
> it's been a while, but IIRC there's no limit in java, although I think
> the platform may enforce limits. I don't really remember the details
> though. For interrupt pipes, you of course should usually submit
> exactly the pipe size (wMaxPacketSize).
>
> ===> Mass-storage device and BULK type UsbEndpoint.
>
>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
>
> it's entirely dependent on your device. although if your input pipe
> is an interrupt pipe, it should be the wMaxPacketSize from the
> endpoint descriptor.
>
> Also, assuming your input pipe is interrupt type, it's probably better
> for you to keep a buffer on it, which will cause continuous polling of
> the device, as required by spec when the device is in use. You can do
> that either with a separate Thread that does nothing except
> syncSubmit() a buffer or irp to the pipe, then passes the returned
> data off somewhere else to process and immediately syncSubmit() a new
> buffer, or you can use asyncSubmit() with either a listener on the
> pipe or a separate Thread to waitUntilComplete() for the irp, and then
> also hand off the returned data to process somewhere else and
> immediately sync or async submit again a new buffer. With
> asyncSubmit(), you can submit multiple buffers, which is better
> because it keeps the low level platform queued up with buffers so that
> the device polling never stops, and you don't have to try to be quite
> so fast at resubmitting a new buffer.
>
> ===> Mass-storage device and BULK type UsbEndpoint.
>
>
>>
>> Thanks in Advance..
>> Sanjay Gupta
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>> _______________________________________________
>> javax-usb-devel mailing list
>> jav...@li...
>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
|
From: Dan S. <dds...@ie...> - 2013-10-08 12:28:46
|
On Tue, Oct 8, 2013 at 3:51 AM, SANJAY GUPTA <gup...@sa...> wrote:
> Thanks,
> Sanjay Gupta<p> </p><p> </p>
>
> ------- Original Message -------
> Sender : Dan Streetman<dds...@ie...>
> Date : Oct 07, 2013 21:37 (GMT+09:00)
> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>
> On Mon, Oct 7, 2013 at 1:48 AM, SANJAY GUPTA <gup...@sa...> wrote:
>> Reposting the query after removing formatting...
>>
>> Thanks for your great support.
>> I tried below as suggested:-
>>
>> int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );
>> log("Max Packet Size: " + maxPacketSize);
>> final byte[] buffer = new byte[8192];
>> for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {
>> final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );
>> usbIrp.setData(buffer, offset, maxPacketSize);
>
> Well I don't think I suggested splitting the output data into max
> packet sized irps, that's certainly unnecessary and will drastically
> cut down on your throughput. I think I said use "reasonable" buffer
> sizes. I'm pretty sure 8k is ok to send in a single irp.
>
> ==> If I transmit the whole buffer of 8K in single submission using asyncSubmt() and wait for it to complete, the submission never gets completed and stucks on waitUntilComplete(). The same thing happens while using syncSubmit(). I do wait for the asynSubmit() to complete because my purpose is to capture the completion time for the submission for different sized buffers.
>
> Also, please not that the hang happens only when the buffer is uninitialized. If I initialize the buffer then the UsbStallException is thrown.
>
> for (int index=0; index<buffer.length; index++) {
> buffer[index] = (byte) index;
> }
This sounds like you don't understand the protocol of your device.
>
>>
>> //Asynchronously submit the UsbIrp to UsbPipe
>> log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");
>> outUsbPipe.asyncSubmit(usbIrp);
>>
>> //Wait for the UsbIrp to complete
>> log("Waiting for the UsbIrp to complete ...");
>> usbIrp.waitUntilComplete();
>>
>> log("!!! Successfully submitted the UsbIrp to UsbPipe ...");
>> }
>>
>> But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-
>>
>> Max Packet Size: 512
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>>
>>
>> I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.
>
> did you actually submit one or more buffers to the input pipe? You
> obviously will never get anything if you don't submit a buffer to be
> filled.
>
> ==> My mistake. But I have a feeling that if the status data from the Input pipe is not read then further submission gets stuck. So, how to know that there is some data to be read on the input pipe?
When you get a buffer back (i.e. a completed IRP), either when
syncSubmit() returns or waitUntilComplete() returns or your listener
gets triggered, the device has already sent data back, that is now in
the buffer you provided.
Knowing that there is data "to be read" on the pipe isn't possible
(except predicting that there *should* be data sent back from the
device based on the specific device protocol, of course). Generally
you should just keep buffer(s) "pending" on any input pipe, since most
specs describe actions that the driver (you) should take when the
device sends any data in. The pending buffer will then just return to
you immediately with the data (and you should then resubmit another
buffer - it's good to keep multiple buffers pending so there's never
any gap in device polling).
Keep in mind that using javax.usb isn't high level programming.
You're doing very low level device communication, and it's
complicated, because the usb spec is very complicated.
>
>>
>> final UsbPipeListener listener = new UsbPipeListener() {
>> @Override
>> public void errorEventOccurred(UsbPipeErrorEvent event) {
>> // TODO Auto-generated method stub
>> }
>> @Override
>> public void dataEventOccurred(UsbPipeDataEvent event) {
>> final int transferLength = event.getActualLength();
>> log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);
>>
>> //Asynchronously read the status in byte[] from IN UsbPipe
>> log("Asynchronously reading the status in byte[] from IN UsbPipe ...");
>> UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);
>
> you shouldn't be using getActualLength to size the next buffer to send
> - it should be consistent, or at least based on the device's protocol,
> and the actual length is simply how many bytes this irp returned.
>
>>
>> //Wait for the UsbIrp to complete
>> log("Waiting for the reading to complete ...");
>> irp.waitUntilComplete();
>
> um...what is the point of asyncSubmit() and then immediately in the
> same thread waiting for it to complete? Additionally, your listener
> callback is supposed to be quick, since calls will come sequentially.
> And what is the point of waiting for the irp to complete right before
> you exit the method?
>
>> }
>> };
>> inUsbPipe.addUsbPipeListener(listener);
>>
>> ------- Original Message -------
>> Sender : Dan Streetman<dds...@ie...>
>> Date : Oct 02, 2013 22:31 (GMT+09:00)
>> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>>
>> On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
>>> Hi All,
>>>
>>> Please look below the sample scenario:-
>>>
>>> final byte[] outData = new byte[] {
>>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
>>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
>>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
>>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
>>> final byte[] inData = new byte[13];
>>>
>>> log("Synchronously submitting the byte[] to UsbPipe ...");
>>> outUsbPipe.syncSubmit(data);
>>>
>>> //Synchronously read the status from IN UsbPipe
>>> log("Synchronously reading the status from IN UsbPipe ...");
>>> inUsbPipe.syncSubmit(inData);
>>>
>>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
>>> The control gets hang on reading the status data from the Input UsbPipe.
>>> Any suggestion on below points will be helpful:-
>>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?
>>
>> Data formats are entirely up to the device, unless the device
>> implements a higher level spec (like HID, mass storage, etc) that
>> itself contains the API for the data format. USB doesn't specify any
>> data format at all, except for the control pipe 8-byte setup packet
>> that must preface each control transfer, and the various default
>> control pipe standard requests (set interface, clear stall, etc).
>>
>>
>> ===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
>> But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
>> And then I have no choice but the unplug the device.
>>
>>
>>
>>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?
>>
>> it's been a while, but IIRC there's no limit in java, although I think
>> the platform may enforce limits. I don't really remember the details
>> though. For interrupt pipes, you of course should usually submit
>> exactly the pipe size (wMaxPacketSize).
>>
>> ===> Mass-storage device and BULK type UsbEndpoint.
>>
>>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
>>
>> it's entirely dependent on your device. although if your input pipe
>> is an interrupt pipe, it should be the wMaxPacketSize from the
>> endpoint descriptor.
>>
>> Also, assuming your input pipe is interrupt type, it's probably better
>> for you to keep a buffer on it, which will cause continuous polling of
>> the device, as required by spec when the device is in use. You can do
>> that either with a separate Thread that does nothing except
>> syncSubmit() a buffer or irp to the pipe, then passes the returned
>> data off somewhere else to process and immediately syncSubmit() a new
>> buffer, or you can use asyncSubmit() with either a listener on the
>> pipe or a separate Thread to waitUntilComplete() for the irp, and then
>> also hand off the returned data to process somewhere else and
>> immediately sync or async submit again a new buffer. With
>> asyncSubmit(), you can submit multiple buffers, which is better
>> because it keeps the low level platform queued up with buffers so that
>> the device polling never stops, and you don't have to try to be quite
>> so fast at resubmitting a new buffer.
>>
>> ===> Mass-storage device and BULK type UsbEndpoint.
>>
>>
>>>
>>> Thanks in Advance..
>>> Sanjay Gupta
>>>
>>> ------------------------------------------------------------------------------
>>> October Webinars: Code for Performance
>>> Free Intel webinars can help you accelerate application performance.
>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>>> the latest Intel processors and coprocessors. See abstracts and register >
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> javax-usb-devel mailing list
>>> jav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>> _______________________________________________
>> javax-usb-devel mailing list
>> jav...@li...
>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
|
From: SANJAY G. <gup...@sa...> - 2013-10-10 02:20:14
|
Thanks,
Sanjay Gupta<p> </p><p> </p>
------- Original Message -------
Sender : Dan Streetman<dds...@ie...>
Date : Oct 08, 2013 21:28 (GMT+09:00)
Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
On Tue, Oct 8, 2013 at 3:51 AM, SANJAY GUPTA <gup...@sa...> wrote:
> Thanks,
> Sanjay Gupta<p> </p><p> </p>
>
> ------- Original Message -------
> Sender : Dan Streetman<dds...@ie...>
> Date : Oct 07, 2013 21:37 (GMT+09:00)
> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>
> On Mon, Oct 7, 2013 at 1:48 AM, SANJAY GUPTA <gup...@sa...> wrote:
>> Reposting the query after removing formatting...
>>
>> Thanks for your great support.
>> I tried below as suggested:-
>>
>> int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );
>> log("Max Packet Size: " + maxPacketSize);
>> final byte[] buffer = new byte[8192];
>> for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {
>> final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );
>> usbIrp.setData(buffer, offset, maxPacketSize);
>
> Well I don't think I suggested splitting the output data into max
> packet sized irps, that's certainly unnecessary and will drastically
> cut down on your throughput. I think I said use "reasonable" buffer
> sizes. I'm pretty sure 8k is ok to send in a single irp.
>
> ==> If I transmit the whole buffer of 8K in single submission using asyncSubmt() and wait for it to complete, the submission never gets completed and stucks on waitUntilComplete(). The same thing happens while using syncSubmit(). I do wait for the asynSubmit() to complete because my purpose is to capture the completion time for the submission for different sized buffers.
>
> Also, please not that the hang happens only when the buffer is uninitialized. If I initialize the buffer then the UsbStallException is thrown.
>
> for (int index=0; index<buffer.length; index++) {
> buffer[index] = (byte) index;
> }
This sounds like you don't understand the protocol of your device.
>
>>
>> //Asynchronously submit the UsbIrp to UsbPipe
>> log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");
>> outUsbPipe.asyncSubmit(usbIrp);
>>
>> //Wait for the UsbIrp to complete
>> log("Waiting for the UsbIrp to complete ...");
>> usbIrp.waitUntilComplete();
>>
>> log("!!! Successfully submitted the UsbIrp to UsbPipe ...");
>> }
>>
>> But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-
>>
>> Max Packet Size: 512
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>>
>>
>> I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.
>
> did you actually submit one or more buffers to the input pipe? You
> obviously will never get anything if you don't submit a buffer to be
> filled.
>
> ==> My mistake. But I have a feeling that if the status data from the Input pipe is not read then further submission gets stuck. So, how to know that there is some data to be read on the input pipe?
When you get a buffer back (i.e. a completed IRP), either when
syncSubmit() returns or waitUntilComplete() returns or your listener
gets triggered, the device has already sent data back, that is now in
the buffer you provided.
Knowing that there is data "to be read" on the pipe isn't possible
(except predicting that there *should* be data sent back from the
device based on the specific device protocol, of course). Generally
you should just keep buffer(s) "pending" on any input pipe, since most
specs describe actions that the driver (you) should take when the
device sends any data in. The pending buffer will then just return to
you immediately with the data (and you should then resubmit another
buffer - it's good to keep multiple buffers pending so there's never
any gap in device polling).
Keep in mind that using javax.usb isn't high level programming.
You're doing very low level device communication, and it's
complicated, because the usb spec is very complicated.
###==> Can you please provide a example code to poll the input pipe to read buffer.
>
>>
>> final UsbPipeListener listener = new UsbPipeListener() {
>> @Override
>> public void errorEventOccurred(UsbPipeErrorEvent event) {
>> // TODO Auto-generated method stub
>> }
>> @Override
>> public void dataEventOccurred(UsbPipeDataEvent event) {
>> final int transferLength = event.getActualLength();
>> log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);
>>
>> //Asynchronously read the status in byte[] from IN UsbPipe
>> log("Asynchronously reading the status in byte[] from IN UsbPipe ...");
>> UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);
>
> you shouldn't be using getActualLength to size the next buffer to send
> - it should be consistent, or at least based on the device's protocol,
> and the actual length is simply how many bytes this irp returned.
>
>>
>> //Wait for the UsbIrp to complete
>> log("Waiting for the reading to complete ...");
>> irp.waitUntilComplete();
>
> um...what is the point of asyncSubmit() and then immediately in the
> same thread waiting for it to complete? Additionally, your listener
> callback is supposed to be quick, since calls will come sequentially.
> And what is the point of waiting for the irp to complete right before
> you exit the method?
>
>> }
>> };
>> inUsbPipe.addUsbPipeListener(listener);
>>
>> ------- Original Message -------
>> Sender : Dan Streetman<dds...@ie...>
>> Date : Oct 02, 2013 22:31 (GMT+09:00)
>> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>>
>> On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
>>> Hi All,
>>>
>>> Please look below the sample scenario:-
>>>
>>> final byte[] outData = new byte[] {
>>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
>>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
>>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
>>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
>>> final byte[] inData = new byte[13];
>>>
>>> log("Synchronously submitting the byte[] to UsbPipe ...");
>>> outUsbPipe.syncSubmit(data);
>>>
>>> //Synchronously read the status from IN UsbPipe
>>> log("Synchronously reading the status from IN UsbPipe ...");
>>> inUsbPipe.syncSubmit(inData);
>>>
>>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
>>> The control gets hang on reading the status data from the Input UsbPipe.
>>> Any suggestion on below points will be helpful:-
>>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?
>>
>> Data formats are entirely up to the device, unless the device
>> implements a higher level spec (like HID, mass storage, etc) that
>> itself contains the API for the data format. USB doesn't specify any
>> data format at all, except for the control pipe 8-byte setup packet
>> that must preface each control transfer, and the various default
>> control pipe standard requests (set interface, clear stall, etc).
>>
>>
>> ===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
>> But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
>> And then I have no choice but the unplug the device.
>>
>>
>>
>>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?
>>
>> it's been a while, but IIRC there's no limit in java, although I think
>> the platform may enforce limits. I don't really remember the details
>> though. For interrupt pipes, you of course should usually submit
>> exactly the pipe size (wMaxPacketSize).
>>
>> ===> Mass-storage device and BULK type UsbEndpoint.
>>
>>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
>>
>> it's entirely dependent on your device. although if your input pipe
>> is an interrupt pipe, it should be the wMaxPacketSize from the
>> endpoint descriptor.
>>
>> Also, assuming your input pipe is interrupt type, it's probably better
>> for you to keep a buffer on it, which will cause continuous polling of
>> the device, as required by spec when the device is in use. You can do
>> that either with a separate Thread that does nothing except
>> syncSubmit() a buffer or irp to the pipe, then passes the returned
>> data off somewhere else to process and immediately syncSubmit() a new
>> buffer, or you can use asyncSubmit() with either a listener on the
>> pipe or a separate Thread to waitUntilComplete() for the irp, and then
>> also hand off the returned data to process somewhere else and
>> immediately sync or async submit again a new buffer. With
>> asyncSubmit(), you can submit multiple buffers, which is better
>> because it keeps the low level platform queued up with buffers so that
>> the device polling never stops, and you don't have to try to be quite
>> so fast at resubmitting a new buffer.
>>
>> ===> Mass-storage device and BULK type UsbEndpoint.
>>
>>
>>>
>>> Thanks in Advance..
>>> Sanjay Gupta
>>>
>>> ------------------------------------------------------------------------------
>>> October Webinars: Code for Performance
>>> Free Intel webinars can help you accelerate application performance.
>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>>> the latest Intel processors and coprocessors. See abstracts and register >
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> javax-usb-devel mailing list
>>> jav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>> _______________________________________________
>> javax-usb-devel mailing list
>> jav...@li...
>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
|
From: SANJAY G. <gup...@sa...> - 2013-10-10 03:09:44
|
Thanks,
Sanjay Gupta<p> </p><p> </p>
------- Original Message -------
Sender : Dan Streetman<dds...@ie...>
Date : Oct 08, 2013 21:28 (GMT+09:00)
Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
On Tue, Oct 8, 2013 at 3:51 AM, SANJAY GUPTA <gup...@sa...> wrote:
> Thanks,
> Sanjay Gupta<p> </p><p> </p>
>
> ------- Original Message -------
> Sender : Dan Streetman<dds...@ie...>
> Date : Oct 07, 2013 21:37 (GMT+09:00)
> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>
> On Mon, Oct 7, 2013 at 1:48 AM, SANJAY GUPTA <gup...@sa...> wrote:
>> Reposting the query after removing formatting...
>>
>> Thanks for your great support.
>> I tried below as suggested:-
>>
>> int maxPacketSize = outUsbPipe.getUsbEndpoint().getUsbEndpointDescriptor().wMaxPacketSize( );
>> log("Max Packet Size: " + maxPacketSize);
>> final byte[] buffer = new byte[8192];
>> for (int offset=0; offset<buffer.length; offset+=maxPacketSize) {
>> final UsbIrp usbIrp = outUsbPipe.createUsbIrp( );
>> usbIrp.setData(buffer, offset, maxPacketSize);
>
> Well I don't think I suggested splitting the output data into max
> packet sized irps, that's certainly unnecessary and will drastically
> cut down on your throughput. I think I said use "reasonable" buffer
> sizes. I'm pretty sure 8k is ok to send in a single irp.
>
> ==> If I transmit the whole buffer of 8K in single submission using asyncSubmt() and wait for it to complete, the submission never gets completed and stucks on waitUntilComplete(). The same thing happens while using syncSubmit(). I do wait for the asynSubmit() to complete because my purpose is to capture the completion time for the submission for different sized buffers.
>
> Also, please not that the hang happens only when the buffer is uninitialized. If I initialize the buffer then the UsbStallException is thrown.
>
> for (int index=0; index<buffer.length; index++) {
> buffer[index] = (byte) index;
> }
This sounds like you don't understand the protocol of your device.
###==> I noticed that the maxPacketSize which the UsbEndpoint of my device can transfer is 512 bytes and the maximum buffer size which I can transfer to the out UsbPipe is 1536 bytes (which is exactly 3 times the maxPacketSize).
After transmitting this size of buffer, I cannot transfer any more byte to the pipe.
Even after closing the pipe & releasing the interface, and again claim() and open() the next time, the data transfer gets stuck.
I feel sorry bothering you but I am unable to understand whats the issue with the trasnfer data size.
It is also to be noted that, the I am able to transfer only 1536 bytes, no matter in what sequece.
Either I send all bytes at the same time or by splitting them in different exececutions (close pipe and again open), the extra data transfer gets stuck.
And I have to unplug the device and plug it again to execute.
>
>>
>> //Asynchronously submit the UsbIrp to UsbPipe
>> log("==> Asynchronously submitting the UsbIrp to UsbPipe ...");
>> outUsbPipe.asyncSubmit(usbIrp);
>>
>> //Wait for the UsbIrp to complete
>> log("Waiting for the UsbIrp to complete ...");
>> usbIrp.waitUntilComplete();
>>
>> log("!!! Successfully submitted the UsbIrp to UsbPipe ...");
>> }
>>
>> But after successfully executing the loop for 3 times, it goes stuck on waitUntilComplete() as below-
>>
>> Max Packet Size: 512
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>> !!! Successfully submitted the UsbIrp to UsbPipe ...
>> ==> Asynchronously submitting the UsbIrp to UsbPipe ...
>> Waiting for the UsbIrp to complete ...
>>
>>
>> I even put a UsbPipeListener before the above code to poll the UsbPipeDataEvent on Input UsbPipe but failed to receive any event.
>
> did you actually submit one or more buffers to the input pipe? You
> obviously will never get anything if you don't submit a buffer to be
> filled.
>
> ==> My mistake. But I have a feeling that if the status data from the Input pipe is not read then further submission gets stuck. So, how to know that there is some data to be read on the input pipe?
When you get a buffer back (i.e. a completed IRP), either when
syncSubmit() returns or waitUntilComplete() returns or your listener
gets triggered, the device has already sent data back, that is now in
the buffer you provided.
Knowing that there is data "to be read" on the pipe isn't possible
(except predicting that there *should* be data sent back from the
device based on the specific device protocol, of course). Generally
you should just keep buffer(s) "pending" on any input pipe, since most
specs describe actions that the driver (you) should take when the
device sends any data in. The pending buffer will then just return to
you immediately with the data (and you should then resubmit another
buffer - it's good to keep multiple buffers pending so there's never
any gap in device polling).
Keep in mind that using javax.usb isn't high level programming.
You're doing very low level device communication, and it's
complicated, because the usb spec is very complicated.
###==> Can you please provide a example code to poll the input pipe to read buffer.
>
>>
>> final UsbPipeListener listener = new UsbPipeListener() {
>> @Override
>> public void errorEventOccurred(UsbPipeErrorEvent event) {
>> // TODO Auto-generated method stub
>> }
>> @Override
>> public void dataEventOccurred(UsbPipeDataEvent event) {
>> final int transferLength = event.getActualLength();
>> log("UsbPipeDataEvent occurred on IN UsbPipe with data size " + transferLength);
>>
>> //Asynchronously read the status in byte[] from IN UsbPipe
>> log("Asynchronously reading the status in byte[] from IN UsbPipe ...");
>> UsbIrp irp = inUsbPipe.asyncSubmit(new byte[transferLength]);
>
> you shouldn't be using getActualLength to size the next buffer to send
> - it should be consistent, or at least based on the device's protocol,
> and the actual length is simply how many bytes this irp returned.
>
>>
>> //Wait for the UsbIrp to complete
>> log("Waiting for the reading to complete ...");
>> irp.waitUntilComplete();
>
> um...what is the point of asyncSubmit() and then immediately in the
> same thread waiting for it to complete? Additionally, your listener
> callback is supposed to be quick, since calls will come sequentially.
> And what is the point of waiting for the irp to complete right before
> you exit the method?
>
>> }
>> };
>> inUsbPipe.addUsbPipeListener(listener);
>>
>> ------- Original Message -------
>> Sender : Dan Streetman<dds...@ie...>
>> Date : Oct 02, 2013 22:31 (GMT+09:00)
>> Title : Re: [javax-usb-devel] Hang problem with UsbPipe.syncSubmit(byte[])
>>
>> On Wed, Oct 2, 2013 at 6:23 AM, SANJAY GUPTA <gup...@sa...> wrote:
>>> Hi All,
>>>
>>> Please look below the sample scenario:-
>>>
>>> final byte[] outData = new byte[] {
>>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00,
>>> (byte) 0x08, (byte) 0x09, (byte) 0x0A, (byte) 0x01B,
>>> (byte) 0x0C, (byte) 0x0D, (byte) 0x0E, (byte) 0x0F,
>>> (byte) 0x00, (byte) 0x01, (byte) 0x02, (byte) 0x03,
>>> (byte) 0x04, (byte) 0x05, (byte) 0x06, (byte) 0x07,
>>> (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x00 }
>>> final byte[] inData = new byte[13];
>>>
>>> log("Synchronously submitting the byte[] to UsbPipe ...");
>>> outUsbPipe.syncSubmit(data);
>>>
>>> //Synchronously read the status from IN UsbPipe
>>> log("Synchronously reading the status from IN UsbPipe ...");
>>> inUsbPipe.syncSubmit(inData);
>>>
>>> This code is working fine but I am facing problem if I want to change (reduce/reduce/modify) the outData.
>>> The control gets hang on reading the status data from the Input UsbPipe.
>>> Any suggestion on below points will be helpful:-
>>> 1. Is there any specific data format (may be starting header) in the actual data being transferred?
>>
>> Data formats are entirely up to the device, unless the device
>> implements a higher level spec (like HID, mass storage, etc) that
>> itself contains the API for the data format. USB doesn't specify any
>> data format at all, except for the control pipe 8-byte setup packet
>> that must preface each control transfer, and the various default
>> control pipe standard requests (set interface, clear stall, etc).
>>
>>
>> ===> Thanks A lot. I am using a mass-storage device and BULK type UsbEndpoint for data transfer.
>> But the problem is, suppose I keep the value of outData[8] as non-zero with all other things intact, the submission gets hanged which never completes.
>> And then I have no choice but the unplug the device.
>>
>>
>>
>>> 2. What is the data size which can be transferred using single invocation of syncSubmit()?
>>
>> it's been a while, but IIRC there's no limit in java, although I think
>> the platform may enforce limits. I don't really remember the details
>> though. For interrupt pipes, you of course should usually submit
>> exactly the pipe size (wMaxPacketSize).
>>
>> ===> Mass-storage device and BULK type UsbEndpoint.
>>
>>> 3. What is the status data size which is received on Input Pipe as a result of out data transfer?
>>
>> it's entirely dependent on your device. although if your input pipe
>> is an interrupt pipe, it should be the wMaxPacketSize from the
>> endpoint descriptor.
>>
>> Also, assuming your input pipe is interrupt type, it's probably better
>> for you to keep a buffer on it, which will cause continuous polling of
>> the device, as required by spec when the device is in use. You can do
>> that either with a separate Thread that does nothing except
>> syncSubmit() a buffer or irp to the pipe, then passes the returned
>> data off somewhere else to process and immediately syncSubmit() a new
>> buffer, or you can use asyncSubmit() with either a listener on the
>> pipe or a separate Thread to waitUntilComplete() for the irp, and then
>> also hand off the returned data to process somewhere else and
>> immediately sync or async submit again a new buffer. With
>> asyncSubmit(), you can submit multiple buffers, which is better
>> because it keeps the low level platform queued up with buffers so that
>> the device polling never stops, and you don't have to try to be quite
>> so fast at resubmitting a new buffer.
>>
>> ===> Mass-storage device and BULK type UsbEndpoint.
>>
>>
>>>
>>> Thanks in Advance..
>>> Sanjay Gupta
>>>
>>> ------------------------------------------------------------------------------
>>> October Webinars: Code for Performance
>>> Free Intel webinars can help you accelerate application performance.
>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>>> the latest Intel processors and coprocessors. See abstracts and register >
>>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> javax-usb-devel mailing list
>>> jav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
>> _______________________________________________
>> javax-usb-devel mailing list
>> jav...@li...
>> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> javax-usb-devel mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
|
Thanks for helping keep SourceForge clean.
X