> Am 03.10.2022 um 17:57 schrieb Hans Petter Selasky :
>
> Can you show the full sequence from the SUBM-CTRL-EP ?
- - -
15:46:38.538480 usbus1.3 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
frame[0] WRITE 8 bytes
41 07 01 01 00 00 00 00 -- -- -- -- -- -- -- -- |A...|
On 10/3/22 17:26, Axel Rau wrote:
Questions:
1. On usbdump, why is the hexdump mssing on some lines like
frame[0] WRITE bytes ?
The -s arguments tells to only grab the first 1024 bytes. Maybe it is
truncated.
Try setting -s to 65536
--HPS
> Am 03.10.2022 um 17:38 schrieb Hans Petter Selasky :
>
> On 10/3/22 17:26, Axel Rau wrote:
>> Questions:
>> 1. On usbdump, why is the hexdump mssing on some lines like
>> frame[0] WRITE bytes ?
>
> The -s arguments tells to only grab the first 1024 bytes. Maybe it is
> truncated.
>
On 10/3/22 17:50, Axel Rau wrote:
15:46:38.539679 usbus1.3
DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0
frame[0] WRITE 8 bytes
Hi,
For USB control transfers frame[0] contains a copy of the SETUP packet.
Maybe the total length exceeds the internal buffer, so that the USB
From time to time the I2C layer on top of the uart locks up
and can’t be recovered via its built in reset command.
Initialialization at [1]:2564 is missing the greeting message.
looking at the traffic with
usbdump -d ugen1.3 -v -v -v -s 1024 > usb.txt
I’m missing some response data from
