Is there a compatibility problem with Ultra SDHC aka SDHC UHS-I cards?

My company uses these cards exclusively and I've never had a problem.

I have had problems using DD to write disk images, however. I am guessing it is something to do with not having the SD card geometry quite right. There's also the fact that not all SD cards are alike (copying one 1GB card image to another 1GB sd card with DD may fail in my experience).

Of course, the disk geometry stuff probably only matters if you intend to boot from the SD.

This link might be helpful:

I use a script based on the old 'gumutils' to format cards (see this link):

Script works great, although to run on Ubuntu 12.04 I had to install some HAL stuff to get it to play nice (and possibly force it to ignore fact that I had modern python).

Best of luck!


On Tue, Jul 2, 2013 at 7:14 AM, Ross Berteig <> wrote:
On 6/28/2013 5:28 PM, Ross Berteig wrote:
> I have a brand new AirSTORM that I am trying to boot from a Sandisk
> Ultra 8GB microSDHC card.
> I downloaded a Linaro image from
> on the premise that a
> pre-built image would be an easy starting point. On that basis, I
> started from overo-alip.img.gz, which I uncompressed and copied to the
> card without any significant issues....
> Inserting the card in the AirSTORM and applying power produces nothing.
> The red and blue LEDs on the Chestnut43 board are both stuck on. The
> console port spat out a couple noise characters. Other than that,
> nothing. No message from X-Loader, nothing.

Update. I bought a brand new Lexar 8GB microSDHC card this morning. I
inserted into the AirSTORM and booted, and noticed that the boot
proceeded as expected (from the NAND) and the factory-supplied 8GB FAT32
partition was detected and mounted successfully.

I then moved the card over to my Ubuntu PC and used dd to write the same
image to it. Now, the AirSTORM will not boot at all with the card
inserted, and also crashes when the card is inserted after boot. The
card appears to be fine on both a Windows PC and on the Ubuntu PC, the
latter showing both partitions with what looks plausibly like a complete
root file system in the second partition, and bootable FAT partition
holding the usual suspect files.

So at this point I apparently have a highly successful recipe for
ruining microSD cards for use in the AirSTORM, and no further idea about
what actually went wrong and what to try next.

> ....
> Any ideas of what to try next to identify the actual problem?

Ross Berteig                     
Cheshire Engineering Corp. 

This email is sponsored by Windows:

Build for Windows Store.
gumstix-users mailing list