Memory Card Serial Number Reader

1. Serial Number Lookup

If you have reason to change the serial number on your memory card, you will need the VolumeID utility. Insert your memory card into a card reader. A serial number is an identifying code assigned to a piece of hardware. Change SD card Serial Number. All electronic storage devices, including memory cards, have such a number. If you have reason. But when copying a file using a fast memory card reader, you might not even get. A genuine SanDisk SD memory card always contains a serial number on the.

For my current project, I tried to read the SD Card serial number because the number is factory stamped and unchangeable, so it easily could be used to protect embedded firmware from being copied. The serial number is stored in the Card Identification Register (CID) which is read by ‘Command 10’ as stated in the. Unfortunately, it is not possible to read the CID of the card with a USB adapter — you need a ‘direct’ SD interface. My iMX233 based development board has 2 of them, so it was an easy task to improve our firmware to read the CID and extract the serial number, but how do I check if I get the correct information? Reading SD-Card SIDLuckily the Linux kernel provides the CID via the so you may use a Linux device containing a direct SD interface like your Android phone or an embedded Linux board. Unfortunately, you cannot know the real path of the SD card in the /sys file system so I can only give some examples and you have to try out the actual path yourself.For example, on my Samsung Galaxy Note running Gingerbread, there is a /sys/block/mmcblk0 soft link pointing to. Not used, always 1 - 1 0:0To convert the hexadecimal number to a binary one, please have a look at my multiplatform.Based on an iMX233 CPU Board it may be easy to build an intelligent USB card-reader, supporting, for example, CID / CSD information and autonomic card tests.

Serial Number Lookup

What do you think, is there a need for such a card-reader? Your comments are welcome in the comment section below. Update:I got a few emails pointing out that using the CID as copy protection is not a good idea because there are some cards on the market which are not compliant with the standard. These cards don’t prohibit CMD26 in SPI mode and therefore allow writing the CID.

However, I’ve never seen such a card. Update 2:You can find an online CID decoder here. September 9, 2013 9:14 amHi Glenn, sorry for the late reply.Maybe your card reader is attached internally via USB and therefore will not work. I’ve good results reading CID with several iMX233 boards. If you want to read CID only from micro SD cards you can use the OLinuXino Boards by Olimex. If you want to read the CID of standard SD cards you may use the original iMX233 dev board by Freescale or our Bones Audio Dev Board.Btw: Bunny has a great post about fake SD cards and CID on her blog:For further questions you may use this comment section or private mail via mikeatbonesdotch.

STeve December 12, 2013 8:38 pmHI MikeThanks for the info, very very useful.I have however a problem and maybe you can point me in the right direction.I’m trying to read the CID on a SD card plugged in a Sheevaplug.The Sheevaplug has a SD card reader, not an USB one.At the location in your example I can actually read something, but I’m not sure is a CID.I say so because I tested different SD cards with on a Linux distribution (Debian Wheezy). On some of them, using your method to read the CID, I obtain the same identical number.However during the boot, the boot loader shows the SD card serial number and it is different for each card.So, I have to assume that the CID field in the Linux distro (/sys/block/mmcblk0/device/cid) is not correctly assigned. Do you have some more info about how the /sys/block/mmcblk0/device/cid field is assigned?STeve. December 13, 2013 11:36 amHi Steve,I tried it on our board with Linux (Kernel 3.12) as well as with our own software and getting the same numbers per card and always different numbers for different cards.I took some screenshots:Linux:Own:The Linux kernel code reading the CID is located within:int mmcsendcid(struct mmchost.host, u32.cid)file:driversmmccoremmcops.cand is called during the initialization of the card.I hope this is of some help.Btw.

I’m very interested in you findings, so I’ll be very happy if you share them in this thread.ThanksMike. STeve December 13, 2013 6:23 pmHi Mike, thanks!!The Debian distro I’m using on the Sheevaplug has a 3.2.0-4 kernel (here the uname -a return: Linux tsiserver 3.2.0-4-kirkwood #1 Debian 3.2.51-1 armv5tel GNU/Linux.I’ll try to follow the initialization operations.Just to be sure. When you say “during the initialization of the card”, are you referring to the “preparation of the SD card”, i.e. When you load the distribution on the SD card, or are you referring to an operation performed every time the kernel starts?I’m asking that because the final purpose is to be able to “clone” an SD card from a generic image (copied from a generated SD card).i.e. I need to avoid to spend two hours every time I need to install the distro on a Sheevaplug.Initially I though that when cloning the SD card the CID was cloned as well, but then I noticed that the bootloader was always reporting a different serial number for each SD card used.So I’m sure each SD card has a different CID, but cloned cards reports the same CID in the /sys/block/mmcblk0/device/cid field.Since the /sys/block/mmcblk0/device/cid field is built runtime I have to discovery the reading mechanism.Sure I’ll report any progress (or failure) here.ThanksSTeve.

This release was created for you, eager to use Memory Card Recovery 3.60 By Maddy full and with without limitations.Our intentions are not to harm Memory software company but to give the possibility to those who can not pay for any pieceof software out there. This should be your intention too, as a user, to fully evaluate Memory Card Recovery 3.60 By Maddy withoutrestrictions and then decide.If you are keeping the software and want to use it longer than its trial time, we strongly encourage you purchasing the license keyfrom Memory official website. Our releases are to prove that we can! Nothing can stop us, we keep fighting for freedomdespite all the difficulties we face each day.Last but not less important is your own contribution to our cause. You should consider to submit your ownserial numbers or share other files with the community just as someone else helped you with Memory Card Recovery 3.60 By Maddy serial number.Sharing is caring and that is the only way to keep our scene, our community alive.