UHS-I / SD cards investigation

Started by nikfreak, July 30, 2014, 05:46:56 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

andy kh

70D
test with the updated sd_uhs.mo
sandisk extreme pro 64 gb remains the same with dfort's build but i can see difference with the sony card 94mb/s 32 gb card

below is the test with sony card
===================
2018/04/06 00:52:28
===================
Before the hack: r:39MB/s w:25MB/s  W:28MB/s R:40MB/s  8)  [best 25MB/s]
SDR50 @ 96MHz  : r:40MB/s w:18MB/s  W:34MB/s R:40MB/s  meh [best 25MB/s]
SDR50 @ 96MHz  : r:40MB/s w:19MB/s  W:30MB/s R:39MB/s  meh [best 25MB/s]
SDR50 @ 80MHz  : r:34MB/s w:13MB/s  W:27MB/s R:34MB/s  meh [best 25MB/s]
SDR50 @ 80MHz  : r:34MB/s w:17MB/s  W:12MB/s R:34MB/s  meh [best 25MB/s]
SDR50 @ 120MHz : r:47MB/s w:13MB/s  W:35MB/s R:47MB/s  meh [best 25MB/s]
SDR50 @ 120MHz : r:48MB/s w:20MB/s  W:18MB/s R:47MB/s  meh [best 25MB/s]
SDR104 @ 96MHz : D0 D0 r:39MB/s w:35MB/s  W:35MB/s R:39MB/s  8)  [best 35MB/s]
SDR104 @ 96MHz : D1 D1 r:39MB/s w:19MB/s  W:29MB/s R:39MB/s  meh [best 35MB/s]
SDR104 @ 80MHz : D0 D0 r:34MB/s w:17MB/s  W:26MB/s R:34MB/s  ??? [best 35MB/s]
SDR104 @ 80MHz : D1 D1 r:34MB/s w:17MB/s  W:28MB/s R:33MB/s  ??? [best 35MB/s]
SDR104 @ 120MHz: D0 D0 r:48MB/s w:20MB/s  W:22MB/s R:48MB/s  meh [best 35MB/s]
SDR104 @ 120MHz: D1 D1 r:48MB/s w:28MB/s  W:39MB/s R:47MB/s  meh [best 35MB/s]
SDR104 @ 132MHz: D0 D0 r:52MB/s w:8.3MB/s  W:20MB/s R:51MB/s  ??? [best 35MB/s]
SDR104 @ 132MHz: D1 D1 r:52MB/s w:11MB/s  W:21MB/s R:47MB/s  ??? [best 35MB/s]
SDR104 @ 160MHz: D0 D0 r:60MB/s w:21MB/s  W:46MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D1 D1 r:61MB/s w:21MB/s  W:37MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D2 D2 r:60MB/s w:22MB/s  W:26MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D3 D3 r:60MB/s w:18MB/s  W:20MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D0 D0 r:61MB/s w:12MB/s  W:15MB/s R:60MB/s  ??? [best 35MB/s]
SDR104 @ 160MHz: D1 D1 r:60MB/s w:22MB/s  W:14MB/s R:61MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D2 D2 r:61MB/s w:13MB/s  W:41MB/s R:61MB/s  ??? [best 35MB/s]
SDR104 @ 160MHz: D3 D3 r:52MB/s w:20MB/s  W:17MB/s R:61MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D0 D0 r:61MB/s w:18MB/s  W:40MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D1 D1 r:61MB/s w:22MB/s  W:26MB/s R:59MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D2 D2 r:61MB/s w:31MB/s  W:28MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D3 D3 r:60MB/s w:18MB/s  W:17MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D0 D0 r:60MB/s w:21MB/s  W:13MB/s R:61MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D1 D1 r:60MB/s w:22MB/s  W:41MB/s R:60MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D2 D2 r:60MB/s w:21MB/s  W:26MB/s R:61MB/s  meh [best 35MB/s]
SDR104 @ 160MHz: D3 D3 r:61MB/s w:6.6MB/s  W:26MB/s R:61MB/s  ??? [best 35MB/s]
Best: D0 D0 r:40MB/s w:11MB/s  W:11MB/s R:39MB/s  ??? [best 35MB/s]
Best: D0 D0 r:39MB/s w:18MB/s  W:18MB/s R:39MB/s  meh [best 35MB/s]

Done.
Please run THOROUGH tests before using!!!


5D Mark III - 70D

Hans_Punk







Benchmark from brand new SanDisk Extreme Pro 64GB 95 MB/s card - 3849.6 MB/s Write, 2836.5 MB/s Read!
Benchmark was done in a blink of an eye!!!

(After sd_uhs.mo was run in photo mode with only Benchmark and sd_uhs.mo loaded within 5D3 fw123 "4K raw video recording; lossless compression" version of ML).


But...

Tried a test recording out of curiosity but was unable to...the camera displayed 'Card Full' message and refused to initiate recording.

After quickly realising that something was not right (or probably healthy for the card), I tried a clean install procedure (format SD card to Exfat, clean install of Crop 4k 123 5D3 build with SD_uhs.mo in module root). As before, I was getting solid 20MB/s R&W before overclock...then up to 45MB/s with overclock but with apparent errors (like a couple have had so far with this card type):

SDR104 @ 120MHz: D0 D0 r:err [SAFE] D0  [BACK] D0
until the end...
SDR104 @ 160MHz: D3 D3 r:err [SAFE] D0  [BACK] D3

I was able to record at approx 45MB/s speed using the improved overclock speed.

Did another ML card benchmark...and R&W speeds are same as above screenshot. Tried a test recording again> 'Card Full' message again> Restarted camera> camera did not turn on.
SD card now appears to be dead as a dodo. Cannot get it to be discovered on win PC through disk management.

Removed SD card, camera turned on and booted fine with my slower Sandisk SD card with ML (all back to normal).
Foolishly I should have quit earlier to recover the logs from the SD card, but alas that Sandisk appears to be toast, hence the lack of precise data - just my anecdotal report.

So, the Sandisk extreme pro 64 gb 95MB/s card might not be a wise choice right now (for some) Unless I overlooked instructions from the thread about not running ML benchmark speed test after SD overclock?

SD Card was new item from Amazon reputable seller - 2017 version of the card according to the box.

I'm happy to take one for the team on such an early offshoot discovery (and potentially look stupid)...but figured it best to report in case it is of any information of value.

a1ex

Ouch, that's not good. Can you try the card on a Linux PC (possibly an Ubuntu Live CD/USB) and show the last lines from "dmesg" after inserting it?

Those huge numbers sound like an uncaught error in the benchmark code.

Going to order one of these to check the signals, to make sure the controller is not somehow switching back to 3.3V while the card is in UHS mode (1.8V). Meanwhile, found out what driver strength means, and reverted the module to the previous changeset, just in case.

Do not try on expensive cards until we figure out what happened!

Walter Schulz

Quote from: a1ex on April 06, 2018, 08:47:46 AMThose huge numbers sound like an uncaught error in the benchmark code.

Seen this error before. Looks like benchmark not checking card for unused size required. Giving those incorrect numbers after filling card.

If this card was unused (=not filled with footage) I suspect a counterfeited card. I strongly recommend to verify card integrity for each and every card after purchasing. Respected seller or not.
h2testw for Windows or F3/F3X for OS X/macOS.
And CrystalDiskMark (or others) for Windows or Blackmagic Disk Speed Test for OS X/macOS and a decent cardreader.

Markus

Trying to activate brute force mode for testning on the Sandisk Extreme pro 512GB bit it does not seem to react to me pushing halfshutter when the test starts?

I think i accedently got it runnig the first time i tried this module but now it just does the normal tests.

Hans_Punk

Quote from: a1ex on April 06, 2018, 08:47:46 AM
Ouch, that's not good. Can you try the card on a Linux PC (possibly an Ubuntu Live CD/USB) and show the last lines from "dmesg" after inserting it?

Those huge numbers sound like an uncaught error in the benchmark code.

Going to order one of these to check the signals, to make sure the controller is not somehow switching back to 3.3V while the card is in UHS mode (1.8V). Meanwhile, found out what driver strength means, and reverted the module to the previous changeset, just in case.

Do not try on expensive cards until we figure out what happened!

Cheers a1ex!

Unfortunatly I am unable to test on Linux machine...or get the SD card to register as showing up as a device at all. Shows all the signs of being completely dead (tried numerous device detection methods on PC).
It would make sense that the SD card could have been subjected to over-voltage in UHS mode, as the the card appears to be totally non-responsive (cooked) - not even 'recognised' as a non-recognised device to attempt a repair or recovery.

It seemed that running the ML benchmark test after running sd_uhs.mo is what somehow triggered an error - maybe resulting in voltage change that cooked or 'knocked-out' the card when in UHS mode?
Before running the ML Card Benchmark test, I was successfully recording raw video at around the improved 45MB/s speeds (from 20MB/s original) which falls into similar results others have recently reported on Sandisk Extreme pro cards.

I purposely bought the SD card at full price from the top rated seller on Amazon - just in case something like this happened. Not a foolproof way to ensure a non-counterfeit product, but more reliable than some other online sources...at least an easy refund should be possible :)

Here is a video of the benchmark speeds on second attempt to check the card after clean re-install - It was obvious something was wrong, but part of me really wished it was a real stable write speed from the SD card that could be harnessed by ML
I can dream can't I? :)

https://www.youtube.com/watch?v=dRHMtZIq-J4&feature=youtu.be

RIP Sandisk
 

loknar

This is just amazing  :o
5 years old camera that i bought for $150 can do continuous 2.5K (2520x1072 - 2.35:1)@24 fps video in 12-bit compressed RAW (~56MB/s), wow, just wow  :D

Sandisk Extreme (microSD, not even Pro) results (in replay mode)
===================
2018/04/06 22:29:28
===================
Before the hack: r:37MB/s w:34MB/s  W:32MB/s R:37MB/s  :)  [best 34MB/s]
SDR50 @ 96MHz  : r:37MB/s w:32MB/s  W:33MB/s R:37MB/s  meh [best 34MB/s]
SDR50 @ 96MHz  : r:37MB/s w:19MB/s  W:33MB/s R:38MB/s  meh [best 34MB/s]
SDR50 @ 80MHz  : r:32MB/s w:30MB/s  W:28MB/s R:32MB/s  meh [best 34MB/s]
SDR50 @ 80MHz  : r:36MB/s w:34MB/s  W:35MB/s R:37MB/s  :)  [best 34MB/s]
SDR50 @ 120MHz : r:54MB/s w:52MB/s  W:52MB/s R:55MB/s  :)  [best 52MB/s]
SDR50 @ 120MHz : r:54MB/s w:50MB/s  W:52MB/s R:55MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:42MB/s  W:42MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:41MB/s  W:42MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:36MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:35MB/s  W:35MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 120MHz: r:55MB/s w:53MB/s  W:52MB/s R:55MB/s  :)  [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:51MB/s  W:50MB/s R:55MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:51MB/s w:48MB/s  W:48MB/s R:51MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:50MB/s w:48MB/s  W:48MB/s R:51MB/s  meh [best 53MB/s]
SDR104 @ 160MHz: r:72MB/s w:70MB/s  W:67MB/s R:73MB/s  :)  [best 70MB/s]
SDR104 @ 160MHz: r:72MB/s w:68MB/s  W:64MB/s R:73MB/s  meh [best 70MB/s]

Done.
Please run THOROUGH tests before using!!!


saulbass

running magiclantern-crop_rec_4k.2018Mar10.650D104 with a1ex's sd_uhs module loaded
doesn't seem to give a performance improvement on the 650D.104 despite the card benchmarks matching others improvements using a 700D.
running crop mode 1920x1076 24fps 12bit LossLess gives 144 frames on multiple runs filming same shot whether to not the sd_uhs module is running or not. Tested multiple times.

mk11174

Hey, been out of the loop for a long time, found new hobby with drones, LOL! Saw this very exciting module and thought I would share my results for the Devs. Here are the only 2 cards I have, my older 16gig and my newer 32gig I use with my drone mostly, but also use in the camera as well.

Tests were run in Photomode, no Live view.

Used the latest update of the module as of April 6th.

Keep up the great work guys!

Card Used



Before Bench



After Bench




Log

===================
2018/04/07 03:11:29
===================
Before the hack: r:43MB/s w:41MB/s  W:39MB/s R:43MB/s  8)  [best 41MB/s]
SDR50 @ 96MHz  : r:43MB/s w:41MB/s  W:40MB/s R:44MB/s  ::) [best 41MB/s]
SDR50 @ 96MHz  : r:43MB/s w:41MB/s  W:40MB/s R:43MB/s  :)  [best 41MB/s]
SDR50 @ 80MHz  : r:36MB/s w:35MB/s  W:34MB/s R:36MB/s  meh [best 41MB/s]
SDR50 @ 80MHz  : r:36MB/s w:35MB/s  W:34MB/s R:36MB/s  meh [best 41MB/s]
SDR50 @ 120MHz : r:53MB/s w:47MB/s  W:45MB/s R:54MB/s  8)  [best 47MB/s]
SDR50 @ 120MHz : r:53MB/s w:47MB/s  W:45MB/s R:54MB/s  ::) [best 47MB/s]
SDR104 @ 96MHz : r:43MB/s w:23MB/s  W:22MB/s R:43MB/s  ??? [best 47MB/s]
SDR104 @ 96MHz : r:43MB/s w:23MB/s  W:22MB/s R:43MB/s  ??? [best 47MB/s]
SDR104 @ 80MHz : r:36MB/s w:21MB/s  W:20MB/s R:36MB/s  ??? [best 47MB/s]
SDR104 @ 80MHz : r:36MB/s w:21MB/s  W:20MB/s R:36MB/s  ??? [best 47MB/s]
SDR104 @ 120MHz: r:45MB/s w:25MB/s  W:25MB/s R:46MB/s  meh [best 47MB/s]
SDR104 @ 120MHz: r:45MB/s w:25MB/s  W:25MB/s R:46MB/s  meh [best 47MB/s]
SDR104 @ 132MHz: r:45MB/s w:24MB/s  W:24MB/s R:46MB/s  meh [best 47MB/s]
SDR104 @ 132MHz: r:45MB/s w:24MB/s  W:24MB/s R:46MB/s  meh [best 47MB/s]
SDR104 @ 160MHz: r:45MB/s w:15MB/s  W:20MB/s R:22MB/s  ??? [best 47MB/s]
SDR104 @ 160MHz: r:22MB/s w:21MB/s  W:21MB/s R:22MB/s  ??? [best 47MB/s]
Best: r:22MB/s w:21MB/s  W:20MB/s R:22MB/s  ??? [best 47MB/s]
Best: r:22MB/s w:21MB/s  W:20MB/s R:22MB/s  ??? [best 47MB/s]

Done.
Please run THOROUGH tests before using!!!


Card Used



Before Bench



After Bench



Log
===================
2018/04/07 02:52:24
===================
Before the hack: r:44MB/s w:41MB/s  W:41MB/s R:44MB/s  8)  [best 41MB/s]
SDR50 @ 96MHz  : r:44MB/s w:40MB/s  W:41MB/s R:44MB/s  ::) [best 41MB/s]
SDR50 @ 96MHz  : r:44MB/s w:41MB/s  W:41MB/s R:44MB/s  ::) [best 41MB/s]
SDR50 @ 80MHz  : r:37MB/s w:34MB/s  W:35MB/s R:37MB/s  meh [best 41MB/s]
SDR50 @ 80MHz  : r:37MB/s w:33MB/s  W:34MB/s R:37MB/s  meh [best 41MB/s]
SDR50 @ 120MHz : r:55MB/s w:50MB/s  W:49MB/s R:55MB/s  8)  [best 50MB/s]
SDR50 @ 120MHz : r:55MB/s w:52MB/s  W:50MB/s R:55MB/s  :)  [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:40MB/s  W:41MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 96MHz : r:44MB/s w:40MB/s  W:41MB/s R:44MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:34MB/s  W:35MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 80MHz : r:37MB/s w:36MB/s  W:35MB/s R:37MB/s  meh [best 52MB/s]
SDR104 @ 120MHz: r:55MB/s w:49MB/s  W:50MB/s R:55MB/s  ::) [best 52MB/s]
SDR104 @ 120MHz: r:55MB/s w:48MB/s  W:52MB/s R:55MB/s  ::) [best 52MB/s]
SDR104 @ 132MHz: r:51MB/s w:46MB/s  W:48MB/s R:51MB/s  meh [best 52MB/s]
SDR104 @ 132MHz: r:51MB/s w:49MB/s  W:47MB/s R:51MB/s  ::) [best 52MB/s]
SDR104 @ 160MHz: r:73MB/s w:64MB/s  W:65MB/s R:72MB/s  8)  [best 64MB/s]
SDR104 @ 160MHz: r:72MB/s w:61MB/s  W:67MB/s R:72MB/s  ::) [best 64MB/s]
Best: r:73MB/s w:64MB/s  W:66MB/s R:72MB/s  :)  [best 64MB/s]
Best: r:72MB/s w:68MB/s  W:64MB/s R:72MB/s  :)  [best 68MB/s]

Done.
Please run THOROUGH tests before using!!!
500D/T1i  550D/T2i  600D/T3i  700D/T5i

a1ex

@mk11174: please try this module on both cards:

sd_uhs_d.mo (rename to sd_uhs.mo, otherwise it doesn't work for some reason)

Supported models for this diagnostic version: 5D3 1.1.3 and 700D 1.1.5.

700D: it won't perform any overclocking (will only run some tests to print card capabilities returned by CMD6).
5D3 1.1.3: it will only install the basic version of the hack (with 700D parameters) and will run some tests to print card capabilities.

I'd like the same test to be run on SanDisk cards from 5D3 1.1.3, if you don't mind the possibility of damaging the card (risk hopefully minimized, but unfortunately I cannot be 100% certain).

Levas

My new shiny Sandisk Extreme Pro card was delivered today.
Ran the first version of the SD_UHS module on it, yes 70Mb write speed on the 6d  :D :D :D


===================
2018/04/07 16:05:21
===================
Before the hack: r:44MB/s w:42MB/s  W:42MB/s R:44MB/s  :)  [best 42MB/s]
SDR50 @ 96MHz  : r:44MB/s w:40MB/s  W:41MB/s R:44MB/s  meh [best 42MB/s]
SDR50 @ 96MHz  : r:43MB/s w:43MB/s  W:43MB/s R:43MB/s  :)  [best 43MB/s]
SDR50 @ 80MHz  : r:36MB/s w:35MB/s  W:35MB/s R:36MB/s  meh [best 43MB/s]
SDR50 @ 80MHz  : r:36MB/s w:36MB/s  W:36MB/s R:36MB/s  meh [best 43MB/s]
SDR50 @ 120MHz : r:54MB/s w:53MB/s  W:51MB/s R:54MB/s  :)  [best 53MB/s]
SDR50 @ 120MHz : r:54MB/s w:52MB/s  W:53MB/s R:54MB/s  meh [best 53MB/s]
SDR104 @ 96MHz : r:44MB/s w:41MB/s  W:41MB/s R:43MB/s  meh [best 53MB/s]
SDR104 @ 96MHz : r:43MB/s w:43MB/s  W:42MB/s R:44MB/s  meh [best 53MB/s]
SDR104 @ 80MHz : r:36MB/s w:35MB/s  W:35MB/s R:36MB/s  meh [best 53MB/s]
SDR104 @ 80MHz : r:36MB/s w:36MB/s  W:36MB/s R:36MB/s  meh [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:53MB/s  W:51MB/s R:54MB/s  :)  [best 53MB/s]
SDR104 @ 120MHz: r:54MB/s w:52MB/s  W:53MB/s R:54MB/s  meh [best 53MB/s]
SDR104 @ 132MHz: r:60MB/s w:59MB/s  W:56MB/s R:60MB/s  :)  [best 59MB/s]
SDR104 @ 132MHz: r:60MB/s w:58MB/s  W:58MB/s R:60MB/s  meh [best 59MB/s]
SDR104 @ 160MHz: r:72MB/s w:68MB/s  W:67MB/s R:72MB/s  :)  [best 68MB/s]
SDR104 @ 160MHz: r:72MB/s w:70MB/s  W:69MB/s R:72MB/s  :)  [best 70MB/s]

Done.
Please run THOROUGH tests before using!!!


domasa

I tested five slow SD cards with 5D Mark III :


SanDisk Ultra 64GB (white/gray) : 33 MB/s


Before the hack: r:22MB/s w:19MB/s  W:21MB/s R:22MB/s  8)  [best 19MB/s]
SDR50 @ 96MHz  : r:43MB/s w:23MB/s  W:18MB/s R:43MB/s  8)  [best 23MB/s]
SDR50 @ 96MHz  : r:43MB/s w:19MB/s  W:16MB/s R:43MB/s  meh [best 23MB/s]
SDR50 @ 80MHz  : r:36MB/s w:12MB/s  W:19MB/s R:36MB/s  meh [best 23MB/s]
SDR50 @ 80MHz  : r:36MB/s w:16MB/s  W:12MB/s R:36MB/s  meh [best 23MB/s]
SDR50 @ 120MHz : r:54MB/s w:19MB/s  W:12MB/s R:54MB/s  meh [best 23MB/s]
SDR50 @ 120MHz : r:54MB/s w:17MB/s  W:15MB/s R:54MB/s  meh [best 23MB/s]
SDR104 @ 96MHz : r:43MB/s w:20MB/s  W:15MB/s R:43MB/s  meh [best 23MB/s]
SDR104 @ 96MHz : r:43MB/s w:24MB/s  W:21MB/s R:43MB/s  :)  [best 24MB/s]
SDR104 @ 80MHz : r:36MB/s w:18MB/s  W:21MB/s R:36MB/s  meh [best 24MB/s]
SDR104 @ 80MHz : r:36MB/s w:33MB/s  W:12MB/s R:36MB/s  8)  [best 33MB/s]
SDR104 @ 120MHz: r:54MB/s w:16MB/s  W:17MB/s R:ERR
SDR104 @ 120MHz: r:err [SAFE]  [BACK]
SDR104 @ 132MHz: r:60MB/s w:45MB/s  W:27MB/s R:ERR
SDR104 @ 132MHz: r:err [SAFE]  [BACK]
SDR104 @ 160MHz: r:71MB/s w:18MB/s  W:14MB/s R:ERR
SDR104 @ 160MHz: r:err [SAFE]  [BACK]
Best: r:36MB/s w:13MB/s  W:24MB/s R:36MB/s  ??? [best 33MB/s]
Best: r:36MB/s w:16MB/s  W:21MB/s R:36MB/s  ??? [best 33MB/s]

Done.
Please run THOROUGH tests before using!!!


SanDisk Ultra 64GB (red/gray) : 37 MB/s


Before the hack: r:22MB/s w:16MB/s  W:19MB/s R:22MB/s  8)  [best 16MB/s]
SDR50 @ 96MHz  : r:43MB/s w:22MB/s  W:19MB/s R:43MB/s  8)  [best 22MB/s]
SDR50 @ 96MHz  : r:43MB/s w:21MB/s  W:26MB/s R:43MB/s  ::) [best 22MB/s]
SDR50 @ 80MHz  : r:36MB/s w:20MB/s  W:26MB/s R:36MB/s  ::) [best 22MB/s]
SDR50 @ 80MHz  : r:36MB/s w:23MB/s  W:26MB/s R:36MB/s  :)  [best 23MB/s]
SDR50 @ 120MHz : r:54MB/s w:24MB/s  W:29MB/s R:54MB/s  :)  [best 24MB/s]
SDR50 @ 120MHz : r:54MB/s w:37MB/s  W:39MB/s R:54MB/s  8)  [best 37MB/s]
SDR104 @ 96MHz : r:43MB/s w:30MB/s  W:22MB/s R:43MB/s  meh [best 37MB/s]
SDR104 @ 96MHz : r:43MB/s w:26MB/s  W:27MB/s R:43MB/s  meh [best 37MB/s]
SDR104 @ 80MHz : r:36MB/s w:29MB/s  W:33MB/s R:36MB/s  meh [best 37MB/s]
SDR104 @ 80MHz : r:36MB/s w:36MB/s  W:26MB/s R:36MB/s  ::) [best 37MB/s]
SDR104 @ 120MHz: r:err [SAFE]  [BACK]
SDR104 @ 120MHz: r:err [SAFE]  [BACK]
SDR104 @ 132MHz: r:err [SAFE]  [BACK]
SDR104 @ 132MHz: r:err [SAFE]  [BACK]
SDR104 @ 160MHz: r:err [SAFE]  [BACK]
SDR104 @ 160MHz: r:err [SAFE]  [BACK]
Best: r:err [SAFE]  [BACK]
Best: r:err [SAFE]  [BACK]

Done.
Please run THOROUGH tests before using!!!


Lexar 633x 16GB : 19 MB/s


Before the hack: r:22MB/s w:18MB/s  W:16MB/s R:22MB/s  8)  [best 18MB/s]
SDR50 @ 96MHz  : r:43MB/s w:18MB/s  W:19MB/s R:43MB/s  :)  [best 18MB/s]
SDR50 @ 96MHz  : r:43MB/s w:18MB/s  W:19MB/s R:43MB/s  ::) [best 18MB/s]
SDR50 @ 80MHz  : r:36MB/s w:18MB/s  W:18MB/s R:36MB/s  ::) [best 18MB/s]
SDR50 @ 80MHz  : r:36MB/s w:18MB/s  W:18MB/s R:36MB/s  ::) [best 18MB/s]
SDR50 @ 120MHz : r:54MB/s w:19MB/s  W:19MB/s R:54MB/s  :)  [best 19MB/s]
SDR50 @ 120MHz : r:54MB/s w:19MB/s  W:19MB/s R:53MB/s  :)  [best 19MB/s]
SDR104 @ 96MHz : r:43MB/s w:18MB/s  W:19MB/s R:43MB/s  ::) [best 19MB/s]
SDR104 @ 96MHz : r:43MB/s w:19MB/s  W:18MB/s R:43MB/s  ::) [best 19MB/s]
SDR104 @ 80MHz : r:36MB/s w:17MB/s  W:17MB/s R:36MB/s  meh [best 19MB/s]
SDR104 @ 80MHz : r:36MB/s w:16MB/s  W:16MB/s R:36MB/s  meh [best 19MB/s]
SDR104 @ 120MHz: r:54MB/s w:18MB/s  W:18MB/s R:54MB/s  ::) [best 19MB/s]
SDR104 @ 120MHz: r:54MB/s w:18MB/s  W:18MB/s R:54MB/s  ::) [best 19MB/s]
SDR104 @ 132MHz: r:59MB/s w:18MB/s  W:18MB/s R:59MB/s  ::) [best 19MB/s]
SDR104 @ 132MHz: r:60MB/s w:18MB/s  W:18MB/s R:59MB/s  ::) [best 19MB/s]
SDR104 @ 160MHz: r:71MB/s w:18MB/s  W:18MB/s R:70MB/s  ::) [best 19MB/s]
SDR104 @ 160MHz: r:71MB/s w:18MB/s  W:18MB/s R:70MB/s  ::) [best 19MB/s]
Best: r:54MB/s w:18MB/s  W:18MB/s R:54MB/s  ::) [best 19MB/s]
Best: r:54MB/s w:18MB/s  W:18MB/s R:54MB/s  ::) [best 19MB/s]

Done.
Please run THOROUGH tests before using!!!


Kingston 64GB : 9 MB/s


Before the hack: r:22MB/s w:6.1MB/s  W:6.8MB/s R:22MB/s  8)  [best 6.1MB/s]
SDR50 @ 96MHz  : r:43MB/s w:9.2MB/s  W:8.2MB/s R:43MB/s  8)  [best 9.2MB/s]
SDR50 @ 96MHz  : r:43MB/s w:9.1MB/s  W:5.8MB/s R:43MB/s  ::) [best 9.2MB/s]
SDR50 @ 80MHz  : r:36MB/s w:8.9MB/s  W:12MB/s R:36MB/s  ::) [best 9.2MB/s]
SDR50 @ 80MHz  : r:36MB/s w:9.0MB/s  W:12MB/s R:36MB/s  ::) [best 9.2MB/s]
SDR50 @ 120MHz : r:err [SAFE]  [BACK]
SDR50 @ 120MHz : r:err [SAFE]  [BACK]
SDR104 @ 96MHz : r:43MB/s w:ERR [SAFE] !!! [BACK]
SDR104 @ 96MHz : r:35MB/s w:ERR [SAFE] !!! [BACK]
SDR104 @ 80MHz : r:33MB/s w:ERR [SAFE] !!! [BACK]
SDR104 @ 80MHz : r:33MB/s w:ERR [SAFE] !!! [BACK]
SDR104 @ 120MHz: r:err [SAFE]  [BACK]
SDR104 @ 120MHz: r:err [SAFE]  [BACK]
SDR104 @ 132MHz: r:err [SAFE]  [BACK]
SDR104 @ 132MHz: r:err [SAFE]  [BACK]
SDR104 @ 160MHz: r:err [SAFE]  [BACK]
SDR104 @ 160MHz: r:err [SAFE]  [BACK]
Best: r:34MB/s w:ERR [SAFE] !!! [BACK]
Best: r:34MB/s w:ERR [SAFE] !!! [BACK]

Done.
Please run THOROUGH tests before using!!!


Transcend 64GB : 11 MB/s


Before the hack: r:21MB/s w:11MB/s  W:20MB/s R:19MB/s  8)  [best 11MB/s]
SDR50 @ 96MHz  : r:22MB/s w:11MB/s  W:21MB/s R:21MB/s  :)  [best 11MB/s]
SDR50 @ 96MHz  : r:22MB/s w:11MB/s  W:10MB/s R:21MB/s  ::) [best 11MB/s]
SDR50 @ 80MHz  : r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  ::) [best 11MB/s]
SDR50 @ 80MHz  : r:22MB/s w:11MB/s  W:11MB/s R:20MB/s  ::) [best 11MB/s]
SDR50 @ 120MHz : r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  :)  [best 11MB/s]
SDR50 @ 120MHz : r:22MB/s w:11MB/s  W:11MB/s R:20MB/s  :)  [best 11MB/s]
SDR104 @ 96MHz : r:22MB/s w:11MB/s  W:11MB/s R:21MB/s  ::) [best 11MB/s]
SDR104 @ 96MHz : r:22MB/s w:11MB/s  W:21MB/s R:21MB/s  :)  [best 11MB/s]
SDR104 @ 80MHz : r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  ::) [best 11MB/s]
SDR104 @ 80MHz : r:22MB/s w:11MB/s  W:11MB/s R:20MB/s  ::) [best 11MB/s]
SDR104 @ 120MHz: r:22MB/s w:11MB/s  W:11MB/s R:20MB/s  ::) [best 11MB/s]
SDR104 @ 120MHz: r:22MB/s w:11MB/s  W:11MB/s R:20MB/s  ::) [best 11MB/s]
SDR104 @ 132MHz: r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  ::) [best 11MB/s]
SDR104 @ 132MHz: r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  ::) [best 11MB/s]
SDR104 @ 160MHz: r:22MB/s w:11MB/s  W:11MB/s R:21MB/s  ::) [best 11MB/s]
SDR104 @ 160MHz: r:22MB/s w:11MB/s  W:11MB/s R:20MB/s  ::) [best 11MB/s]
Best: r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  ::) [best 11MB/s]
Best: r:22MB/s w:11MB/s  W:21MB/s R:20MB/s  ::) [best 11MB/s]

Done.
Please run THOROUGH tests before using!!!

a1ex

Some of these cards had trouble enabling higher speeds. Mind running the diagnostic version (right above your post) on all these cards? You will need firmware 1.1.3 for that test. Just to check whether the card capabilities can predict the results, to some extent.

domasa

I downgraded firmware to 1.1.3. But I have problem with load module sd_uhs_d:




I have ML on CF card.

a1ex

That's weird; renaming the module to sd_uhs.mo solves the issue. Will check later to see why that happens.

domasa

SanDisk Ultra 64GB (white/gray)

Before the hack: r:22MB/s w:14MB/s  W:10MB/s R:22MB/s  8)  [best 14MB/s]
SDR50 @ 96MHz  : sd_check_function =>
00C8 8001 8001 800F 800F 8001 801F 0000
8001 800F 800F 8001 801F 0000 0100 0000
800F 8001 801F 0000 0100 0000 0000 0000
801F 0000 0100 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     1 (supported 0,1,2,3,4,F)
sd_set_function =>
0190 8001 8001 800F 800F 8001 801F 0000
8001 800F 800F 8001 801F 0000 0200 0000
800F 8001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 400 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:18MB/s  W:18MB/s R:43MB/s  8)  [best 18MB/s]
SDR50 @ 96MHz  : sd_set_function =>
0190 8001 8001 800F 800F 8001 801F 0000
8001 800F 800F 8001 801F 0000 0200 0000
800F 8001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 400 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:18MB/s  W:18MB/s R:43MB/s  :)  [best 18MB/s]
Best: sd_set_function =>
0190 8001 8001 800F 800F 8001 801F 0000
8001 800F 800F 8001 801F 0000 0200 0000
800F 8001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 400 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:18MB/s  W:17MB/s R:43MB/s  :)  [best 18MB/s]
Best: sd_set_function =>
0190 8001 8001 800F 800F 8001 801F 0000
8001 800F 800F 8001 801F 0000 0200 0000
800F 8001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 400 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:17MB/s  W:17MB/s R:43MB/s  ::) [best 18MB/s]

Done.
Please run THOROUGH tests before using!!!


SanDisk Ultra 64GB (red/gray)

Before the hack: r:22MB/s w:19MB/s  W:12MB/s R:22MB/s  8)  [best 19MB/s]
SDR50 @ 96MHz  : sd_check_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0100 0000
800F C001 801F 0000 0100 0000 0000 0000
801F 0000 0100 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     1 (supported 0,1,2,3,4,F)
sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:22MB/s  W:32MB/s R:43MB/s  8)  [best 22MB/s]
SDR50 @ 96MHz  : sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:33MB/s  W:24MB/s R:43MB/s  8)  [best 33MB/s]
Best: sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:21MB/s  W:25MB/s R:43MB/s  meh [best 33MB/s]
Best: sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:24MB/s  W:25MB/s R:43MB/s  meh [best 33MB/s]

Done.
Please run THOROUGH tests before using!!!


Kingston 64GB

Before the hack: r:22MB/s w:6.4MB/s  W:6.9MB/s R:22MB/s  8)  [best 6.4MB/s]
SDR50 @ 96MHz  : sd_check_function =>
0064 8001 8001 800F 800F 8001 8017 0000
8001 800F 800F 8001 8017 0000 0100 0000
800F 8001 8017 0000 0100 0000 0000 0000
8017 0000 0100 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 100 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     1 (supported 0,1,2,4,F)
sd_set_function =>
0064 8001 8001 800F 800F 8001 8017 0000
8001 800F 800F 8001 8017 0000 0200 0000
800F 8001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 100 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:39MB/s w:7.2MB/s  W:8.2MB/s R:43MB/s  8)  [best 7.2MB/s]
SDR50 @ 96MHz  : sd_set_function =>
0064 8001 8001 800F 800F 8001 8017 0000
8001 800F 800F 8001 8017 0000 0200 0000
800F 8001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 100 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:39MB/s w:7.2MB/s  W:5.7MB/s R:43MB/s  :)  [best 7.2MB/s]
Best: sd_set_function =>
0064 8001 8001 800F 800F 8001 8017 0000
8001 800F 800F 8001 8017 0000 0200 0000
800F 8001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 100 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:39MB/s w:7.2MB/s  W:13MB/s R:42MB/s  :)  [best 7.2MB/s]
Best: sd_set_function =>
0064 8001 8001 800F 800F 8001 8017 0000
8001 800F 800F 8001 8017 0000 0200 0000
800F 8001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 100 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:39MB/s w:7.2MB/s  W:13MB/s R:42MB/s  :)  [best 7.2MB/s]

Done.
Please run THOROUGH tests before using!!!


mk11174




===================
2018/04/07 18:22:55
===================
Before the hack: r:43MB/s w:42MB/s  W:40MB/s R:43MB/s  8)  [best 42MB/s]
SDR50 @ 96MHz  : sd_check_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0100 0000
800F C001 801F 0000 0100 0000 0000 0000
801F 0000 0100 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     1 (supported 0,1,2,3,4,F)
sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:39MB/s  W:41MB/s R:43MB/s  ::) [best 42MB/s]
SDR50 @ 96MHz  : sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:41MB/s  W:41MB/s R:43MB/s  ::) [best 42MB/s]
Best: sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:40MB/s  W:41MB/s R:43MB/s  ::) [best 42MB/s]
Best: sd_set_function =>
00C8 8001 8001 800F 800F C001 801F 0000
8001 800F 800F C001 801F 0000 0200 0000
800F C001 801F 0000 0200 0000 0000 0000
801F 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,2,3,F)
Function group 3 (Driver Strength) 0 (supported 0,1,2,3,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,3,4,F)
r:43MB/s w:40MB/s  W:41MB/s R:43MB/s  ::) [best 42MB/s]

Done.
Please run THOROUGH tests before using!!!





===================
2018/04/07 18:26:14
===================
Before the hack: r:43MB/s w:41MB/s  W:39MB/s R:44MB/s  8)  [best 41MB/s]
SDR50 @ 96MHz  : sd_check_function =>
00C8 8001 8001 8003 8001 C001 8017 0000
8001 8003 8001 C001 8017 0000 0100 0000
8001 C001 8017 0000 0100 0000 0000 0000
8017 0000 0100 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,F)
Function group 3 (Driver Strength) 0 (supported 0,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     1 (supported 0,1,2,4,F)
sd_set_function =>
00C8 8001 8001 8003 8001 C001 8017 0000
8001 8003 8001 C001 8017 0000 0200 0000
8001 C001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,F)
Function group 3 (Driver Strength) 0 (supported 0,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:42MB/s w:41MB/s  W:40MB/s R:43MB/s  ::) [best 41MB/s]
SDR50 @ 96MHz  : sd_set_function =>
00C8 8001 8001 8003 8001 C001 8017 0000
8001 8003 8001 C001 8017 0000 0200 0000
8001 C001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,F)
Function group 3 (Driver Strength) 0 (supported 0,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:43MB/s w:41MB/s  W:40MB/s R:43MB/s  ::) [best 41MB/s]
Best: sd_set_function =>
00C8 8001 8001 8003 8001 C001 8017 0000
8001 8003 8001 C001 8017 0000 0200 0000
8001 C001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,F)
Function group 3 (Driver Strength) 0 (supported 0,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:43MB/s w:41MB/s  W:40MB/s R:43MB/s  :)  [best 41MB/s]
Best: sd_set_function =>
00C8 8001 8001 8003 8001 C001 8017 0000
8001 8003 8001 C001 8017 0000 0200 0000
8001 C001 8017 0000 0200 0000 0000 0000
8017 0000 0200 0000 0000 0000 0000 0000
Switch Function Status version 0
Max current: 200 mA
Function group 6 (Reserved)        0 (supported 0,F)
Function group 5 (Reserved)        0 (supported 0,F)
Function group 4 (Power Limit)     0 (supported 0,1,F)
Function group 3 (Driver Strength) 0 (supported 0,F)
Function group 2 (Command System)  0 (supported 0,E,F)
Function group 1 (Access Mode)     2 (supported 0,1,2,4,F)
r:43MB/s w:41MB/s  W:40MB/s R:43MB/s  :)  [best 41MB/s]

Done.
Please run THOROUGH tests before using!!!
500D/T1i  550D/T2i  600D/T3i  700D/T5i

goldenchild9to5

Will it be possible to overclock the "CF" interface as well so we can get higher rez on the 5D Mark III?  Awesome work @a1ex & the whole magic lantern team. 

domasa

Quote from: goldenchild9to5 on April 08, 2018, 06:15:15 PM
Will it be possible to overclock the "CF" interface...?
I had same question ☺
Quote...what about brute force search registers for CompactFlash?  ;)

a1ex

Of course. Managed to get 130MB/s in benchmarks (compared to 110 in default configuration).

However, while running some low-level benchmarks (without overclocking), my CF card stopped working (I can no longer format it). I might have overwritten some important parts of the card firmware by mistake, as it no longer reports the correct version.

Before:

2.193.870   CSMgrTask:ff6aa2f8:22:05: [ID:Firmware Revision] = 20121203
2.193.882   CSMgrTask:ff6aa30c:22:05: [ID:Model Number] = SILICONMOTION SM2236AC   
2.193.904   CSMgrTask:ff6aa3b4:22:05: IDE = 4, PCMCIA = 80, UDMA = 7
2.193.927   CSMgrTask:ff6aa58c:22:05: 48-bit LBA:0x00000000_03ba3e70
2.193.953   CSMgrTask:ff6aa604:22:03: Cyl=62041, Hds=16, Trk=63, nSec=62537328


After (same card):

0.592.929   CSMgrTask:ff6aa2f8:22:05: [ID:Firmware Revision] =         
0.592.940   CSMgrTask:ff6aa30c:22:05: [ID:Model Number] = SM2236-AB                               
0.592.962   CSMgrTask:ff6aa3b4:22:05: IDE = 4, PCMCIA = 0, UDMA = 0
0.592.989   CSMgrTask:ff6aa604:22:03: Cyl=65, Hds=16, Trk=63, nSec=65520


The card still reacts somewhat to I/O requests, but reports bogus values when trying to read sectors from it. It simply repeats the LBA address modulo 256, 512 times.

Quote from: KB TechSupport on May 23, 2016, 10:47:19 AM
If the software reports that the card is less than 64MB (not GB) then the card is corrupted  and is unrecoverable using card reader.

65520*512 = 32MB => RIP KB 32GB 1000x.

If you have experience with reflashing CF card firmware, or other low-level diagnostics, please get in touch.

Camera still works fine with another (slower) CF card.

domasa

Quote from: a1ex on April 09, 2018, 10:52:26 PM
However, while running some low-level benchmarks (without overclocking), my CF card stopped working

I have broken KomputerBay 64GB 1000x. When I was recording to RAW a few years ago: camera crash and CF contains file with strange name... Slow format was not possible (stop after +-60%).

I tried program "SD Card Formatter" today... Result? Crash and cappacity is 31,9 MB... => absolute RIP

Kharak

Maybe this is as good a time as any to tell how I corrupted a 128 GB 1000x Lexar card.

This is about 3 years ago, I was looking in to doing Spanned recordings to increase recording time with Vanilla MLV in 1920x1280. I had tried it before, but it was a long time before. So I did the mistake of going in to Canon Menu and set record to CF+SD Card and did the same in ML RAW submenu, I should have set it only in ML Menu, this resulted in an immediate crash when I pressed record and the card was inaccessible via camera or card reader. But when you buy Lexar cards, you get free serial key for their Card Recovery program, with the program I managed to repair the card to function again. Some pictures and MLV's were corrupted, but I can still use the card today, until there is about 20 GB of space left, then recording times drop to a few seconds. the SD card was fine though.

Just a FYI tl:dr. Dont set Canon Menu to record to CF+SD combined with ML Menu Spanned Recording ON, this will ruin your CF card.
once you go raw you never go back

reddeercity

Sorry to go off topic a bit .
Quote from: goldenchild9to5 on April 08, 2018, 06:15:15 PM
Will it be possible to overclock the "CF" interface as well so we can get higher rez ......
Don't think so , I had a look at 5D2 log for CF action and notice it auto detect the UDMA mode , in my case UDMA 6
but that kind of puzzling at that mode , it's writes speed is max 133MB/s according to Wikipedia (bench marks says on 5d2 around 79MB/s on a udma7 card 1066x) can't believe there that much over head .
and udma7 writes at 167MB/s and I do think 5d3 is around 120MB/s .
Is the controller really limited or is there a software limit , being 5d2 never really needed high write speeds like the 5d3 for video (720p60 &1080p30)

dm_log from 5d2
825FE>  CSMgrTask:00095f98:00:00: *** register_interrupt("CFDriver", 0x82, 0xffb8b8cc, 0x0), from ffb8bb58
      .............
834A0>  CSMgrTask:ffb8a92c:22:05: [ID:Model Number] = LEXAR ATA FLASH CARD                   
834C8>  CSMgrTask:ffb8aabc:22:05: IDE = 4, PCMCIA = 80, UDMA = 6
      .............
83572>  CSMgrTask:ffbdb8a0:22:01: cfDecideTiming: UDMA Mode 6 (CFA4.0)
      .............
83592>  CSMgrTask:ffbdbb3c:22:03: CF_GetAccessTiming : DatTim = 3, DatMod = 6

can we fool the controller to switch to UDMA7 on D4 camera CF cards?
Can the "DatTim" be changed to 4? & "DatMod" to 7 ? assuming that means "UDMA"
or though some register in the "CFDriver" .  Thou I have no idea how to try and change it , just a few thoughts  :D



a1ex

I wouldn't be surprised if these were coincidental failures, except there's pretty much no way to tell.

Quote from: Kharak on April 10, 2018, 12:55:11 AM
Just a FYI tl:dr. Dont set Canon Menu to record to CF+SD combined with ML Menu Spanned Recording ON, this will ruin your CF card.

When card spanning is enabled (mlv_rec), it ignores Canon setting (main stream goes to CF, secondary stream goes to SD). ML cannot even tell whether CF+SD is selected in Canon menu (it only recognizes the card selected for playback), so I'm pretty sure it wasn't that. BTW, can you record H.264 on both SD and CF at the same time? (it doesn't seem to work here).

I also have a Lexar 512MB SD that now reports 256MB after a crash while copying something on it, some years ago. Maybe I should try SD Card Formatter on it.

With the dead CF, I was doing sector-level benchmarks with Canon routines from bootflags.c, filling the entire card with 0xFFFFFFFF, 0x00000000, 0x55555555, 0xAAAAAAAA, 0x5A5A5A5A etc, to see if that makes any difference in benchmarks. It didn't, but some blocks were written at ~120MB/s, others at ~85MB/s, and a very small percentage of them were written at lower speeds. That pattern wasn't exactly repeatable, but the histograms were pretty much the same. I've saved logs from 3 such runs, so here are some plots:



Right before the card died, I accidentally wrote something to sector -32768 (LBA underflow?)

@reddeercity: more details after I'll get a new card (it *is* possible to overclock the 5D2 CF interface).

goldenchild9to5