On this same card you can also see that it has the number 1 inside of the U shape. This identifies that the card is also rated at UHS Class 1. On the SanDisk card you can see that the card has the 1 inside of the U, indicated that the card is rated at UHS Class 1. You asked about internal 10-digit serial number of micro SD memory card. AFAIK it cannot be read from Garmin 60CSx hidden service menu - at least pages I accessed from an earlier post in this thread.

• Micro Sd Card Number Meaning
• Graphics Card Serial Number
• Symbols On Micro Sd Card

I have created a map for using with GPS devices. The map is copied to a microSD card and then, GPS can read the map data from the card. How can I create copy/clone protection of my data on microSD cards? Because my business depends on it.

schroeder♦

3 Answers

I think the OP is after the DRM protection built into SD cards:http://en.wikipedia.org/wiki/Secure_Digital

Thats why they're called 'SD' as in 'Secure Digital'.

The access to the DRM encoding Equipment for SD cards is limited to those buying a license, so I would suggest you Contact the SD Association for purchasing a license:http://www.sdcard.org/

This DRM protection can perform a challenge-response type of authentication before allowing access to the content on SD-card, which will be encrypted during transmission. Preferably, your GPS device will contain a 'smart card chip' containing keys, and your map SD card will communicate with this chip to create a encrypted channel. Then you could generate symmetric keys using a secret algorithm based on the GPS device's serial number + a secret master key as input. The master key is only stored in your production equipment.

When a customer wants to purchase a map, they will have to specify the GPS device serial number, they will then be sent a SD card tailored for that GPS device.

sebastian nielsensebastian nielsen

At best you can do obfuscation of the data with some crypto. The key will have to be stored somewhere in the program then, so it can be reversed. Making a foolproof DRM to prevent copying is not possible. Many have tried, all have failed.

Lucas KauffmanLucas Kauffman

Not sure any here have nailed exactly how SD cards secure data.

My take on how it works is that the SD card itself is the secure device and cannot be cloned by normal methods. The software is tied to that particular card which has embedded code in an unwritable section which is read by the software. Good luck finding and changing that part of the code in the software which itself can be obfuscated such that only the most knowledgeable could attempt a hack if it was even worth it.

A European map and GPS manufacturer have been using this technique for years for handhelds and especially their premium marine-based maps and equipment.

An Australian digital map seller uses the same tech. Its damn near foolproof really and I wonder why Garmin don't use it but my guess is it haven't suffered greatly profit-wise since their 25 digit software code was cracked a few years ago. The real money is in the hardware I believe.

Not the answer you're looking for? Browse other questions tagged protection or ask your own question.

Upon power up, in default 'NewLog' mode, OpenLog will output 12< (note the less than sign) at which time you can start throwing characters at it. Those characters will be recorded to LOG#####.TXT. Pressing Ctrl+z (ASCII 26 decimal) three consecutive times will cause OpenLog to exit record mode and drop into command mode. Command mode is signified with a > (greater than) sign. You can then enter the following commands.

While OpenLog is in command mode STAT1 will toggle on/off for every character received. The LED will stay on until the next character is received.

Tip: Once you're in command mode the list of available commands can be brought up by typing ?.

###Basic Commands###

newfile: Creates a new file (named file) in the current directory. Only standard 8.3 file names are supported. '12345678.123' is acceptable. '123456789.123' is not.

• Ex: new file1.txt

appendfile: Appends text to the end of file. Serial data is then read in from the UART in a stream and is not echoed. This is the most common way to use the logger. To exit this state, send the command Ctrl+z (ASCII 26) and OpenLog will return to the '>' prompt. If the file does not exist it will be created.

• Ex: append newfile.csv

writefile OFFSET: Writes text to file starting from the location OFFSET within the file. The text is read from the UART, line by line, and echoed back. To exit this state, send an empty line.

• Ex: write logs.f17 516

rmfile: Deletes file from the current directory. Wild cards are supported starting in version 1.2.

• Ex: rm me.txt
• In v2.4 and above: You can remove directories and any files that may be contained in them.
• Ex: rm -rf mydirectory

sizefile: Displays size of file in bytes.

• Ex: size LOG00004.txt
• Output: 11

###Directory Manipulation###

ls: This is the letters 'L' and 'S'. Also called list file. Shows the content of the current directory. Wild cards are supported starting in version 1.2.

Micro Sd Card Number Meaning

• Ex: ls

mddirectory: Creates a sub directory in the current directory.

• Ex: md july_14

cddirectory: Change to a sub directory

• Ex: cd day_22

cd ..: Change to lower directory in tree. This is a bit weird because I'm used to 'cd..'. There is a space in between cd and .. to allow the string parser to see the cd command.

• Ex: cd ..

rmdirectory: Remove a sub directory

• Ex: rm temps
• Note the directory must be empty for this command to work. To remove a directory with files in it, use the rm -rf temps command.

###Viewing Files###

readfile +start+ length TYPE: (New in v1.2) Outputs the contents of a file in visible form of a file starting from +start+ and going to length. A file name is required. If +start+ is omitted the entire file is reported. If length is omitted the entire contents from the starting point is read. If TYPE is omitted the unit will report in ASCII. There are three TYPEs of output, ASCII = 1, HEX = 2, and RAW = 3. You may leave off some trailing arguments as shown:

• Example basic read, omitted flags: read LOG00004.TXT
• Output: Accelerometer X=12 Y=215 Z=317
• Example read from start with length of 5: read LOG00004.TXT 0 5
• Output: Accel
• Example read, from position 1, length of 5, in HEX: read LOG00004.TXT 1 5 2
• Output: 63 63 65 6C
• Example read, from position 0, length 50, in RAW: read LOG00137.TXT 0 50 3
• Output: André---þ Extended Character Test (note that printing option RAW will depend on how your terminal will handle the extended characters)

catfile: Writes the contents of a file in hex to the screen for viewing. This is sometimes helpful to see that a file is recording correctly without having to pull the SD card and view the file on a computer.

• Ex: cat LOG00004.txt
• Output:
  • 00000000: 41 63 63 65 6c 3a 20 31**
  • 00000008: 32 32 0d**

###System Settings###

Remember, on version 1.6 and above, system configuration can be done via the CONFIG.TXT file.

echoon/off: New in version 2.3. This command allows you to turn on or off echo. This command is stored in memory and can be controlled by editing the config file. By turning echo off, OpenLog will not echo typed text on the command prompt. This is helpful if OpenLog is embedded into a system where the system does not read back the echoed characters. If you are playing with OpenLog via a terminal, you probably want to leave echo on so that you can see the text you are sending to OpenLog. Note: During normal logging you will not see the characters sent to OpenLog. This is because it takes too much system resources to echo back the text that is being received.

verboseon/off: New in version 2.3. This command turns on or off verbose error reporting. This command is stored in memory and can be controlled by editing the config file. By turning off verbose errors, OpenLog will respond with only a '!' if there is an error rather that 'unknown command: oodf' (for example). This '!' character is easier for embedded systems to parse than the full error. If you are playing with OpenLog via a terminal, you probably want to leave verbose on so that you can see full error messages.

baud: Brings up a system menu to enter a baud rate. 9600 8N1 is the default. Any baudrate between 300bps and 1Mbps is supported. You can put OpenLog in a baud rate of 67715 (very weird, unsupported rate) so be cautious. You can always change the baud rate via the configuration file as well. The baud rate selection is immediate and OpenLog requires a power cycle for the settings to take effect. The baud rate is stored to EEPROM and is loaded every time OpenLog powers up.

Remember: If you get OpenLog stuck into an unknown baud rate, there is a safety mechanism built-in. Tie the RX pin to ground and power up OpenLog. You should see the LEDs blink back and forth for 2 seconds, then blink in unison. Now power down OpenLog and remove the RX/GND jumper. OpenLog is now reset to 9600bps with an escape character of 'ctrl+z' pressed three consecutive times. Note: This feature can be overridden by setting the Emergency Override bit to 1. See configuration file for more information.

Graphics Card Serial Number

set*: Brings up a system menu to select the boot up mode. These settings will occur at the next power-on and are stored in non-volatile EEPROM:

1. New File Logging (default): This mode creates a new file each time OpenLog powers up. OpenLog will transmit 1 (UART is alive) then 2 (SD card is initialized) then < (OpenLog is ready to receive data). All data will be recorded to a LOG#####.txt. The ##### number increases every time you power up OpenLog. This number is stored in EEPROM and can be reset from the set menu. All received characters are not echoed. You can exit this mode and enter command mode by sending Ctrl+z (ASCII 26). All buffered data will be stored. Note: If too many logs have been created (65533 logs is max), OpenLog will output error Too many logs, then exit this mode, then it will drop to Command Prompt. If you are parsing OpenLog output, look for 12< before sending serial strings. If you see 12!Too many logs! instead, you know there has been an error.
2. Append File Logging: Also known as sequential mode. This mode creates a file called SEQLOG.txt (if it is not already there) and appends any received data to the file. OpenLog will transmit 12< at which time OpenLog is ready to receive data. All received characters are not echoed. You can exit this mode and enter command mode by sending Ctrl+z (ASCII 26). All buffered data will be stored.
3. Command Prompt: OpenLog will transmit 12> at which time OpenLog is ready to receive commands. Note the 'greater than' sign indicates OpenLog is now ready to receive commands, not data. You can easily create files and append data to files from the command prompt. This however requires a few more steps and some serial parsing (to check for errors) so we do not set this mode by default.
4. Reset New File Number: Selecting this option will reset the log file number to LOG000.txt. This is helpful if you've recently cleared out an SD card and want the log file numbers to start over again.
5. New Escape Character: OpenLog will then prompt user to enter a character such as ctrl+z or $. This will be the new escape character. This setting is reset to ctrl+z during an emergency reset.
6. Number of Escape Characters: OpenLog will then prompt user to enter a character such as 1 or 3 or 17 (that's just silly!). This will be the new number of escape characters needed to drop to command mode. For example, 3 will require the user to hit ctrl+z three times to get to command mode. This setting is reset to 3 during an emergency reset.

Escape characters explained:Original OpenLog firmware (versions v1.5 and below) required you to press ctrl+z to enter command mode. What we found was that many users had OpenLog attached to the TX pin on an Arduino. When you hit the 'Upload' button in the Arduino IDE, serial characters start flowing to the Arduino board in rapid succession - the Arduino is reprogramming! The problem is that there is a strong chance that one of these reprogramming characters will be ctrl+z (ASCII 26) causing OpenLog (who is diligently logging all these crazy characters as it 'listens' to the TX pin) to drop to command mode. Now when you go to run your sketch, OpenLog is not responding? That's because it's sitting in command mode. Firmware v1.51 and above fixes this issue by setting the escape sequence to three ctrl+z characters. You have to hit ctrl+z three times to get it to drop to command mode. During a bootload of an Arduino, it is highly unlikely (but still possible) to see three such characters stream by. Both the type of escape character and the number of required escape characters are user configurable. '$$$' is a common configuration string for old AT systems. We decided to stick with ctrl+z because that's what we've been using since the beginning. Remember: if things get out of hand and you forget what escape character you've set, or how many you need to hit, you can always do an emergency reset by holding the RX pin to ground during a power up. This will cause OpenLog to default to 9600bps, with escape character of ctrl+z sent three times.

Note for Arduino users:If you are using OpenLog with either the built-in serial library, or new software serial library, you may have noticed that command mode appears to be not working. This is because Serial.println() appears to send both newline AND carriage return. To overcome this use the r instead of Serial.println():

or separately send the value 13 by using

###Low Level Commands###

disk: Shows card manufacturer ID, serial number, manufacturer date and card size. Below is an example of a 1GB generic card:

init: Re-initializes the and re-opens the SD card. This is helpful if the SD card stops responding.

sync: Synchronize, or write the current contents of the buffer to the SD card. This command is useful if you have less than 512 characters in the buffer and want to have them committed to the SD card.

Symbols On Micro Sd Card

reset: This will cause OpenLog to jump to location zero and re-run bootloader and then init code. This command is helpful if you need to edit the config file then have OpenLog reset and start using the new configuration. It's not a completely clean reset (watchdog would be better but does not currently work), so use some caution.

###Configuring OpenLog via a File###

As of firmware version 1.6 and above, you no longer need to use a terminal to reconfigure OpenLog. Simply edit the config.txt file (capitalization is not important) and change 9600 to 57600 and OpenLog will operate at 57600bps the next time you power it up. This is pretty handy! Rather than hooking up a serial connection and opening up a terminal window, you can now edit many of the settings on OpenLog via an SD card reader and a text editor. See the Config File page for more information.

OpenLog Wiki Pages: