“The Balena EtcherPro already read CIDs” that is the current explanation of the hardware capabilities. I’m not sure what you mean by “host” SD card though? That means, changes to drivelist will not be enough, i guess. Okay, so on the EtcherPro hardware+OS tweaks are needed to read the CIDs because the Card-Readers are running in USB-Mass Storage Mode and not SPI mode. Yes, the solution will read the serial number from the flash targets Hi thank you for the issue and the link to this thread, i had a look into the drivelist project now. I will keep you posted on future updates. I do plan on implementing a native solution on Linux so we don’t have to rely on lsblk on the user’s system, although, since pretty much every linux machine is probably going to have lsblk, is hasn’t been a priority. So, the technical challenges of actually getting the serial number are mostly done, it’s other stuff happening in the background that I am working on, that is specific to Balena. It might be a little longer before we can actually deploy the fix though. I haven’t actually tried on Mac yet, because I started working on the technical debt I mentioned earlier, but I am hoping to get this resolved this week. There was some technical debt built up that I am taking care of, but as soon as that is fixed, we should be able to add the field to Etcher-SDK.įor your reference, in Etcher, we actually don’t use lsblk and parse the output from that, so that work is done for us.įor Windows we will use IOCTL_STORAGE_GET_MEDIA_SERIAL_NUMBER. I have gotten it working on Windows and Linux at least, but I am now working on integrating the solution into our codebase. I have loaded a region from my 'blue nav' mapping program onto an sd cardfor my magellan meridian gps.as part of the copy protection system magellan requires that you go thru areauthorization process to copy this region onto a different card.my original sd card has failed for some reason and i cannot get it toreformat.I Markus, we are able to get the serial number from the card already. CARD IS FORMATTED.I:dirVolume in drive I is WIPEDVolume Serial Number is 2409-16E7.I would like to be able to get a unique serial number for the card itself, not of the volume or partition inside the disk. CARD IS FORMATTED.I:dirVolume in drive I is CLEANVolume Serial Number is 40F4-0355. Thank you for the response.I am able to get unique 'Volume Serial Numbers' from the SD card when using the dir command in MS-DOS, though this number changes every time the card is formatted:I:dirVolume in drive I is WIPEDVolume Serial Number is C688-0DDD. Fedora 9.īacktrack 4I had the same results with each combination of card reader/SD card. Adata Suber SD Duo 1.0 GBOperating systems. Would this be the case? And if so, is it possible to force the mmccore driver to pass through the USB card reader and be used directly with the SD card?Īre there any PCI MMC/SD card readers that would be able to have lower level access to the cards?Thank you in advance.Information:Card readers. I had read that the sgraw command allowes for sending arbitrary HEX formatted commands to a device, though none seemed to pass through the reader to the SD card itself (I tried the binary commands that where listed in the MMC spec and the SD spec).When looking at the linux drivers for MMCs and SD cards (sdmod, mmccore) it seems that if the mmccore driver were to be used to interface with the card, the serial number ( cid.serial in 'mmc.c' in mmccore) would be obtained during the card initialization period. I was running various commands on the device (/dev/sdc and /dev/sg3) trying to get any response from the SD card, but I was only getting responses from USB connected reader. Under Linux I have found the sg3-utils that send SCSI instructions to devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |