Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Oct 2022 17:57:29 +0200
From:      Hans Petter Selasky <hps@selasky.org>
To:        Axel Rau <Axel.Rau@Chaos1.DE>
Cc:        hardware@freebsd.org, freebsd-hackers@freebsd.org
Subject:   Re: Accessing I2C-Bus via ELV USB-I2C
Message-ID:  <2cb6203f-03da-9a05-24a5-c851f1424503@selasky.org>
In-Reply-To: <602324D8-515B-4061-8689-5638E9A82759@Chaos1.DE>
References:  <996df5c0-ffa7-f1bf-a9e2-6dd47d7b49e6@Chaos1.DE> <35D556D7-56EC-4295-93D6-80A4CFE6DCE9@Chaos1.DE> <37c55124-5cd5-6fd1-ca46-9265ebe47b18@selasky.org> <602324D8-515B-4061-8689-5638E9A82759@Chaos1.DE>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/3/22 17:50, Axel Rau wrote:
> 15:46:38.539679 usbus1.3 DONE-CTRL-EP=00000000,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 
control transfer gets split into multiple parts.

Can you show the full sequence from the SUBM-CTRL-EP ?

FYI: The frame[0] never contains any data payload for USB control transfers.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2cb6203f-03da-9a05-24a5-c851f1424503>