Hi,
is any of the StarterWare examples capable of implementing some memory-stick functionality with the BBB? Means when the BBB is connected via USB it provides its internal flash memory to the host computer as some kind of external drive?
Thanks!
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
is any of the StarterWare examples capable of implementing some memory-stick functionality with the BBB? Means when the BBB is connected via USB it provides its internal flash memory to the host computer as some kind of external drive?
Thanks!
Hi Hans,
Please refer usb_dev_msc example in the StarterWare package. In this example the DDR is used as storage and the board exposes itself as a mass storage device to the host PC. If you refer this forum you would also find people trying to configure the SD card as the medium of storage for the usb interface.
Vineeth,
I already tried this example but it does not seem to work for BBB, no drive is attached to host system.
When yo uare interested I can provide the dmsg output...
Hans
Hi Hans,
We have not tested our examples on BBB as of now. I was expecting the usb_dev_msc to work. Can you paste the dmsg log.
Regards
Vineeth
[ 207.301081] usb 1-3: new high-speed USB device number 2 using ehci-pci [ 207.416480] usb 1-3: New USB device found, idVendor=1cbe, idProduct=0005 [ 207.416487] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 207.416492] usb 1-3: Product: Mass Storage Device [ 207.416496] usb 1-3: Manufacturer: Texas Instruments [ 207.416499] usb 1-3: SerialNumber: 12345678 [ 207.416791] usb-storage 1-3:1.0: USB Mass Storage device detected [ 207.418546] scsi6 : usb-storage 1-3:1.0 [ 208.420774] scsi 6:0:0:0: Direct-Access TI Mass Storage 1.00 PQ: 0 ANSI: 0 [ 208.422360] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 208.424402] sd 6:0:0:0: [sdb] 32768 512-byte logical blocks: (16.7 MB/16.0 MiB) [ 208.425122] sd 6:0:0:0: [sdb] Write Protect is off [ 208.425128] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 208.425742] sd 6:0:0:0: [sdb] No Caching mode page found [ 208.425749] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 208.428732] sd 6:0:0:0: [sdb] No Caching mode page found [ 208.428741] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 208.430056] sdb: unknown partition table [ 208.432371] sd 6:0:0:0: [sdb] No Caching mode page found [ 208.432379] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 208.432385] sd 6:0:0:0: [sdb] Attached SCSI removable disk
It seems to look good but the problem is message
[ 208.430056] sdb: unknown partition table
The device is in no usable state, /dev/sdb can't neither be mounted nor partitioned due to this partition table problem.
Great!.
Are you intending to use the OCMC or the internal SRAM as the media ? If yes you need to move the ram_disk() array( refer ramdisk.c) into that particular location either using the a new section defined in the linker or by using a #pragma directive to place this array at the required address (refer AM335x memory map for addresses). Hope you have understood the size limitation for these memories.
Hm, not exactly - I'd like to use the internal flash instead of RAM (the flash where the Angstrom-Linux is installed by default).
So simply remapping the address should not do the job in this case?