On 10/5/22 18:31, Axel Rau wrote:
Am 05.10.2022 um 16:46 schrieb Hans Petter Selasky :
On 10/5/22 13:55, Axel Rau wrote:
If I do not want to touch th USB stuff, can I get the same effect by close/open
of the serial device?
The uslcom driver only does this right after attach, in 13-stable
> Am 05.10.2022 um 16:46 schrieb Hans Petter Selasky :
>
> On 10/5/22 13:55, Axel Rau wrote:
>> If I do not want to touch th USB stuff, can I get the same effect by
>> close/open of the serial device?
>
> The uslcom driver only does this right after attach, in 13-stable and 14-main.
>
> Does
On 10/5/22 13:55, Axel Rau wrote:
If I do not want to touch th USB stuff, can I get the same effect by close/open
of the serial device?
The uslcom driver only does this right after attach, in 13-stable and
14-main.
Does the attached patch make any difference for you?
--HPS
From
> Am 04.10.2022 um 13:43 schrieb Hans Petter Selasky :
>
> Did you clear the endpoint halt condition (for RX BULK endpoint and TX BULK
> endpoint), to reset the so-called USB data-toggle, before starting to
> communicate with the device? Else you risk loosing a USB packet?
If I do not want
On 10/4/22 12:03, Axel Rau wrote:
Am 04.10.2022 um 10:39 schrieb Hans Petter Selasky :
That looks normal.
The DONE transaction transferred the SETUP packet, but still lists frame [0],
but is not dumping the data, because it has already been sent. frame [0] is
always the SETUP packet for
Am 04.10.2022 um 10:39 schrieb Hans Petter Selasky :
>
> That looks normal.
>
> The DONE transaction transferred the SETUP packet, but still lists frame [0],
> but is not dumping the data, because it has already been sent. frame [0] is
> always the SETUP packet for control endpoints.
>
So
> Am 04.10.2022 um 10:39 schrieb Hans Petter Selasky :
>
>
> That looks normal.
>
> The DONE transaction transferred the SETUP packet, but still lists frame [0],
> but is not dumping the data, because it has already been sent. frame [0] is
> always the SETUP packet for control endpoints.
>
On 10/4/22 01:35, Axel Rau wrote:
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 -- -- --
> 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: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
> 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: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
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
The application daemon speaks twi over the serial line (/dev/cuaU0)
Everything works perfectly.
Thanks, Axel
Am 27.04.22 um 23:08 schrieb Axel Rau:
Next journey starts:
For the home2l project, I need a supported I2C interface via USB.
I got this one:
14 matches
Mail list logo
