Date: Thu, 15 Dec 2016 11:52:55 +0100 From: "John W. Kitz" <John.Kitz@xs4all.nl> To: <ticso@cicely.de> Cc: "'Emmanuel Vadot'" <manu@bidouilliste.com>, "'Ian Lepore'" <ian@freebsd.org>, <freebsd-arm@freebsd.org> Subject: RE: When first hooking up a cubieboard2... Message-ID: <000901d256c1$6a959330$3fc0b990$@Kitz@xs4all.nl> In-Reply-To: <20161215050935.GL313@cicely7.cicely.de> References: <585066dd.1c7c630a.8fe44.4233SMTPIN_ADDED_BROKEN@mx.google.com> <CAGtf9xPQq1qGjmHci4n52uXx=E%2ByuHrNkRcuAyDDQvRt8a5rYQ@mail.gmail.com> <1481739755.1889.376.camel@freebsd.org> <1481749803.1889.406.camel@freebsd.org> <20161214225633.160d9d06ddb0ae4a380ccf82@bidouilliste.com> <7fee533d65c2760ffb9c42d5448c3ee9@xs4all.nl> <20161215050935.GL313@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd, <removed portion of email thread> > > > Probably none. > > > What the software running on the board is doing is called usb gadget > > > mode. It uses the OTG port to act as a device and it seems that it > > > act as some multiple usb disk. But this doesn't mean that the device > > > it's exporting match some device on the board. It could be directory > > > or file on the filesystem. > > > > Ian, > > > > The question may not have been related to running FreeBSD on a > > cubieboard (yet), but it did involve FreeBSD, albeit on AMD64 and a > > ARM board. That's why I posted it here. > > Sure it does involve FreeBSD, but FreeBSD sees whatever the attached device claims to be. > It claims to be 3 USB mass storage devices, so FreeBSD lists 3 USB mass storage devices. That was indeed my original question and both Emmanuel and you seem to confirm my initial remarks (also refer to https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/usb-disks.html, in particular section 17.4.1). So thanks for that. > But FreeBSD has no clue about what they are intended to be used for and you can't even read them, since whatever is running on the cubieboard notes > them as not ready. > Unless someone on the list knows what the software delivered on the cubieboard actually does, you won't get an answer. > This is like plugging an USB memory stick into a FreeBSD computer and asking on a FreeBSD list what pictures are on the stick. True, if I had asked about the possible content, which I didn't. > You'd better ask the person who knows about the USB stick, right? > Well - we could tell you how to read data from the stick and try to find out, but in this case the da devices are not ready, so even that is > impossible. > My own guess (as in starring at my crystal ball), would be that it might allow writing to an SD card if one would have been inserted. Based on the information so far, I guessed that too. In which case inserting an SD card would probably have resulted in a status change (from "NOT READY, Medium not present" to something else) of one of the devices da0, da1 or da2 (assuming they behave as there enumeration on the FreeBSD system would suggest). However inserting an SD card did not cause a status change. So, unless that was caused by the SD card I used (it is an older one) at this stage it probably isn't possible to write anything to an SD card in the SD card slot of the board. > No idea why it lists 3 da devices though. > Nevertheless this could easily be done with any kind of USB card reader as well, so nothing important after all. Regards, Jk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000901d256c1$6a959330$3fc0b990$>