From owner-freebsd-arm@freebsd.org  Wed Dec 14 12:21:02 2016
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FF31C77F10
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Wed, 14 Dec 2016 12:21:02 +0000 (UTC)
 (envelope-from John.Kitz@xs4all.nl)
Received: from lb3-smtp-cloud2.xs4all.net (lb3-smtp-cloud2.xs4all.net
 [194.109.24.29])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (Client CN "*.xs4all.nl",
 Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2820E1F87
 for <freebsd-arm@freebsd.org>; Wed, 14 Dec 2016 12:21:01 +0000 (UTC)
 (envelope-from John.Kitz@xs4all.nl)
Received: from picard ([82.95.89.208]) by smtp-cloud2.xs4all.net with ESMTP
 id KoLq1u00B4VixDu01oLt5q; Wed, 14 Dec 2016 13:20:53 +0100
Reply-To: <John.Kitz@xs4all.nl>
From: "John W. Kitz" <John.Kitz@xs4all.nl>
To: "'Ganbold Tsagaankhuu'" <ganbold@gmail.com>
Cc: <freebsd-arm@freebsd.org>
References: <585066dd.1c7c630a.8fe44.4233SMTPIN_ADDED_BROKEN@mx.google.com>
 <CAGtf9xPQq1qGjmHci4n52uXx=E+yuHrNkRcuAyDDQvRt8a5rYQ@mail.gmail.com>
In-Reply-To: <CAGtf9xPQq1qGjmHci4n52uXx=E+yuHrNkRcuAyDDQvRt8a5rYQ@mail.gmail.com>
Subject: RE: When first hooking up a cubieboard2...
Date: Wed, 14 Dec 2016 13:20:54 +0100
Message-ID: <003501d25604$843a0ae0$8cae20a0$@Kitz@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdJVqeZfEplYU54lTzaAdTubtGWkGQAWGITA
Content-Language: en-us
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2016 12:21:02 -0000

Ganbold,

> On Wed, Dec 14, 2016 at 5:22 AM, John W. Kitz <John.Kitz@xs4all.nl> =
wrote:
> Hi,
>
> When attaching a new cubieboard2 to a FreeBSD system for the first =
time I
> get:
>
> "ugen1.2: <USB Developer> at usbus1
> umass0: <Mass Storage> on usbus1
> umass0:  SCSI over Bulk-Only; quirks =3D 0x4000
> umass0:4:0: Attached to scbus4
>
> da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
> da0: <USB 2.0 USB Flash Driver 0100> Removable Direct Access SCSI-2 =
device
> da0: 40.000MB/s transfers
> da0: Attempt to query device size failed: NOT READY, Medium not =
present
> da0: quirks=3D0x2<NO_6_BYTE>
>
> da1 at umass-sim0 bus 0 scbus4 target 0 lun 1
> da1: <USB 2.0 USB Flash Driver 0100> Removable Direct Access SCSI-2 =
device
> da1: 40.000MB/s transfers
> da1: Attempt to query device size failed: NOT READY, Medium not =
present
> da1: quirks=3D0x2<NO_6_BYTE>
>
> da2 at umass-sim0 bus 0 scbus4 target 0 lun 2
> da2: <USB 2.0 USB Flash Driver 0100> Removable Direct Access SCSI-2 =
device
> da2: 40.000MB/s transfers
> da2: Attempt to query device size failed: NOT READY, Medium not =
present
> da2: quirks=3D0x2<NO_6_BYTE>"
>
> While looking at the hardware schematic, am I correct in assuming that =
da0
> represents the SD card slot, and da1 and da2 represent USB port 1 and =
2
> respectively?
>
> I don't remember the details, but there are 2 USB host ports exposed =
on the board, and 1 USB otg port.
> SD would be mmcsd0.

Well not the answer I was looking for, but this is what I got when =
attaching the OTG port of a new cubieboard2 (NOT in FEL mode) to a USB =
port on an AMD64 / FreeBSD system. Since the messages all seem to refer =
to removable storage devices attached to the same bus on which the =
storage medium itself doesn't seem to be present, resulting in the =
devices being reported as not ready, the only thing I could imagine were =
the SD card slot (I believe using a converter it is possible to connect =
that to a USB port as well) and the two other (i.e. non OTG) USB ports.

Regards, Jk.