Sponsored Content
Operating Systems Linux Android 32MB USB Memory Stack Not Supported on Android? Post 302605660 by Neo on Thursday 8th of March 2012 05:52:14 AM
Old 03-08-2012
32MB USB Memory Stack Not Supported on Android?

Running latest Android for Galaxy Tab 8.9 and bought a 32GB USB flash memory stick for file transfers, etc. Would not work. Searched the net for clues and could not find any. Then, back at the IT store, found out that Galaxy Tab currently only supports up to 16GB for the USD flash memory stick.

Does anyone know if this is an Android limitation based on the current OS, or is the limited tied to some other parameter like available internal memory?

Seems to be that the available memory does not matter; and the issue is that 32GB is not yet supported by Android (for these USB memory sticks).

Anyone have experiences to share?
 

10 More Discussions You Might Find Interesting

1. Programming

memory stack problem

Hi, I am writing a C program under SCO Unix. I have a memory stack problem but do not know how to go about fixing it. I have tried running INSURE but that does not detect any problems. Essentially the problem is that the memory address shifts on return from a routine. I pass a pointer to... (3 Replies)
Discussion started by: jkeagy
3 Replies

2. UNIX for Dummies Questions & Answers

memory stack

Hello everbody: when issuing the ulimit -a, on my tru64 machone, I get the following: root@billing4# ulimit -a time(seconds) unlimited file(blocks) unlimited data(kbytes) 10485760 stack(kbytes) 32768 memory(kbytes) 10190528 coredump(blocks) 0... (1 Reply)
Discussion started by: aladdin
1 Replies

3. UNIX for Dummies Questions & Answers

Using USB Memory Sticks to backup

I'm trying to set up a RELIABLE backup routine using several USB memory sticks on a SCO 6 Server. Does anybody have any experience of how to do this? I presume I have to mount the memory stick, copy the files to it & then unmount the stick so that another memory stick could be used for the next... (5 Replies)
Discussion started by: ifleet2007
5 Replies

4. Solaris

USB Hard Disk Drive Supported by Sun Fire V890

Hi, Can anyone suggest me any USB Hard Disk Drive which I can connect to Sun Fire V890 and take backup at a quick speed. A test with SolidState USB Hard Drive for backup work was taking writing at 2GB per hour for a 75GB backup. Regards, Tushar Kathe (1 Reply)
Discussion started by: tushar_kathe
1 Replies

5. SCO

How do I copy files into USB memory stick

SCO Unix ver 5.07 How do I copy files onto an USB memory stick? Is SCO Unix ver 5.07 able to handle USB memory devices? (2 Replies)
Discussion started by: Schnell
2 Replies

6. Solaris

usb memory card

I just got a removable memory card. I tried the following bu still my OS solaris x86 cannot detect it and also i got an error touch /reconfigure init 0 I inserted the removable memory card and the powered the system on I got the following on at boot up when i fully logged in I did ... (2 Replies)
Discussion started by: seyiisq
2 Replies

7. Linux

Help with Porting USB Host Stack to VXWORKS 653 OS+HPCNET8641D

My name is Patrik Mark.S . i am using the Vxworks 653 OS with HPCNET Board with 8641D processor, Since there is no USB Host Stack in Vxworks 653 so i am tring to port UsbHost Stack onto vxworks 653. at the lowest layer(HCD Layer) of usb Host stack i need usbPciStub.c File related to my Board... (1 Reply)
Discussion started by: mark.S
1 Replies

8. Solaris

Supported Memory Configurations on Netra T2000

I need to upgrade the memory configuration on our T2000s to 24 Gb. I presently have 8x2Gb DIMMS in Rank 0 and 8x1Gb DIMMS in Rank 1, but the OS only recognizes 16Gb. How can I upgrade these T2000s to 24Gb? (2 Replies)
Discussion started by: iambernieb
2 Replies

9. OS X (Apple)

USB File Transfer MacOS 10.6.5 to Android 2.2?

I'm trying to get a MacBook Air (MBA) running 10.6.5 to recognize a Samsung Galaxy S (Android 2.2) vis the USB interface for simple file transfers back and forth. Nothing works so far. I've tried many things! :wall: I noticed when I connect my phone to the MBA, there is a message in system.log... (2 Replies)
Discussion started by: Neo
2 Replies

10. UNIX for Dummies Questions & Answers

Stack Memory

I have a java process that piles up the stack memory. ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 10 stack size ... (9 Replies)
Discussion started by: mohtashims
9 Replies
DFU-PROGRAMMER(1)														 DFU-PROGRAMMER(1)

NAME
dfu-programmer - USB firmware upgrading for Atmel microcontrollers SYNOPSIS
dfu-programmer target command [options] [parameters] DESCRIPTION
dfu-programmer is a Linux command line Device Firmware Upgrade (DFU) based programmer for the flash memory on Atmel AVR, AVR32 and 8051 based microcontrollers which ship with a USB boot loader. It supports In System Programming (ISP) for developers and potentially product updates in the field. Those boot loaders are patterned after the standard USB DFU 1.0 class specification, but depend on extensions defined by Atmel to the extent that standard DFU drivers will not work. To use it, first connect the device to be programmed and ensure that it comes up in DFU mode. The microcontrollers come up in that mode as shipped by Atmel; or they may reenter that mode after a special hardware reset. Then invoke this program to issue one or more DFU commands. You will normally need to start by issuing the "erase" command; the default security policies prevent extracting firmware, to prevent reverse engineering of what is usually proprietary code. SUPPORTED MICROCONTROLLERS
These chip names are used as the command line "target" parameter. 8051 based controllers: at89c51snd1c, at89c51snd2c, at89c5130, at89c5131, and at89c5132. AVR based controllers: at90usb1287, at90usb1286, at90usb647, at90usb646, at90usb162, at90usb82, atmega32u6, atmega32u2, atmega32u4, atmega8u2 and atmega16u4. AVR32 based controllers: at32uc3a0128, at32uc3a1128, at32uc3a0256, at32uc3a1256, at32uc3a0512, at32uc3a1512, at32uc3a0512es, at32uc3a1512es, at32uc3a364, at32uc3a364s, at32uc3a3128, at32uc3a3128s, at32uc3a3256, at32uc3a3256s, at32uc3b064, at32uc3b164, at32uc3b0128, at32uc3b1128, at32uc3b0256, at32uc3b1256, at32uc3b0256es, at32uc3b1256es, at32uc3b1512, at32uc3b0512, at32uc3c064, at32uc3c0128, at32uc3c0256, at32uc3c0512, at32uc3c164, at32uc3c1128, at32uc3c1256, at32uc3c1512, at32uc3c264, at32uc3c2128, at32uc3c2256 and at32uc3c2512. USAGE
There are no mechanisms for selecting which single device should be programmed, or to implement gang programming. Accordingly, you will usually avoid connecting more than one device of a given family (AVR, AVR32 or 8051) at a time. All of these commands support the "global options". Unless you override it, commands which write to the microcontroller will perform a validation step that rereads the data which was written, compares it to the expected result, and reports any errors. configure register [--suppress-validation] data Bootloaders for 8051 based controllers support writing certain configuration bytes. dump Reads all the available flash memory, and writes it as binary data to stdout. dump-eeprom Reads all the available eeprom memory, and writes it as binary data to stdout. dump-user Reads the user space flash on the AVR32 chips and writes it as binary data to stdout. erase [--suppress-validation] Erases all the flash memory. This is required before the bootloader will perform other commands. flash [--suppress-validation] [--suppress-bootloader-mem] file or STDIN Writes flash memory. The input file (or stdin) must use the "ihex" file format convention for a memory image. --suppress-bootloader-mem ignores any data written to the bootloader memory space when flashing the device. This option is particularly useful for the AVR32 chips trampoline code. flash-user [--suppress-validation] file or STDIN Writes to user space flash on the AVR32 chips. This block of flash is out of the normal range of flash blocks and is designed to contain configuration parameters. The input file (or stdin) mus use the "ihex" file format convention for a memory image. eeprom-flash [--suppress-validation] file or STDIN Writes to eeprom memory. The input file (or stdin) must use the "ihex" file format convention for a memory image. get register Displays various product identifier bytes. reset Resets microcontroller using watchdog timer start Starts the application firmware by having the microcontroller jump to address zero. version This prints a string identifying the version of this utility. Global Options --quiet - minimizes the output --debug level - enables verbose output at the specified level Configure Registers The standard bootloader for 8051 based chips supports writing data bytes which are not relevant for the AVR based chips. BSB - boot status byte SBV - software boot vector SSB - software security byte EB - extra byte HSB - hardware security byte Get Register bootloader-version - currently flashed bootloader version ID1 - device boot identification 1 ID2 - device boot identification 2 manufacturer - the hardware manufacturer code family - the product family code product-name - the product name product-revision - the product revision HSB - same as the configure_register version BSB - same as the configure_register version SBV - same as the configure_register version SSB - same as the configure_register version EB - same as the configure_register version BUGS
None known. KNOWN ISSUES
The at90usb series chips do not make available any read/write protect flags so the dump or flash command may fail with a less than helpful error message. To remove any write or read protection from any chips, a full chip erasure is required. You may need to be a member of the uucp group in order to have access to the device without needing to be root. AUTHOR
Weston Schmidt <weston_schmidt@alumni.purdue.edu> SEE ALSO
http://dfu-programmer.sourceforge.net http://atmel.com/dyn/resources/prod_documents/doc7745.pdf COPYRIGHT
Copyright (C) 2005-2008 Weston Schmidt This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA DFU-PROGRAMMER December 10, 2008 DFU-PROGRAMMER(1)
All times are GMT -4. The time now is 04:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy