From owner-freebsd-usb@freebsd.org  Tue Mar 20 07:35:42 2018
Return-Path: <owner-freebsd-usb@freebsd.org>
Delivered-To: freebsd-usb@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE8F2F5A0E4
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Tue, 20 Mar 2018 07:35:42 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4B44184884
 for <freebsd-usb@FreeBSD.org>; Tue, 20 Mar 2018 07:35:38 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.128.70])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id C602B2602E8
 for <freebsd-usb@FreeBSD.org>; Tue, 20 Mar 2018 08:35:37 +0100 (CET)
From: Hans Petter Selasky <hps@selasky.org>
Subject: Re: R: usb's quirks ... how to sniff bios'es messages addressed to
 usb rom chip
To: "freebsd-usb@FreeBSD.org" <freebsd-usb@FreeBSD.org>
References: <!&!AAAAAAAAAAAYAAAAAAAAANB1sR69XHJMoG+MU1AT/qLCgAAAEAAAAP7hvnBBMjhJr+v0J6Z9h1UBAAAAAA==@alice.it>
 <77f62042-bb44-7b36-0845-b88d233bfed0@selasky.org>
 <000401d3bfbe$c7f99370$57ecba50$@it>
Message-ID: <670d0202-09a7-259e-c03c-54bc255d702a@selasky.org>
Date: Tue, 20 Mar 2018 08:35:33 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <000401d3bfbe$c7f99370$57ecba50$@it>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 07:35:42 -0000

On 03/19/18 21:13, Vincenzo Di Salvo wrote:
> Thanks.
> 
> I have read the usbdump man page ... and I know that is wireshark is able to sniff usb traffic.
> 
> My problem is how to detect the bit that increment the counter (always that the chip of the usb drive allows a such action).
> 

Hi,

I think you misunderstand what USB is. USB is a protocol. A processor 
runs on the USB device replying to this protocol. There is no direct 
hardware access. You need to ask the manufacturer which USB request 
returns the counter you are asking for.

--HPS

> Again: I kindly contact you to know if someone of the list has already done this test, if he can address me on the right street among the numerous informations shown by wireshark or usbdump.
> 
> Tutorials weblink are appreciated (if they exist).
> 
> Regards.
> 
> Vincenzo.