Hello xArt.
Hi, I can hardly believe you could get a compiled version for Linux.
It's posted on Github here: https://github.com/raburton/evoplus_cid
I just duplicated that source using Microchip's MDDFS library (for USB keys & SD Cards).
I used the same SD card for both platforms, so can verify evoplus_cid for Linux worked ok.
I don't expect any problem with any platform ->reading<- the CID.
Really I don't understand exactly what you have just written above.
I have evoplus_cid working on linux and android and I'm pretty sure I'm not the only one.
What do you mean?
And surely there can be no problem reading the cid with linux, android or anything else.
Evoplus_cid bails for any command leading up to CMD26 that doesn't give an expected reply.
Just like that program, I didn't push it any further.
CMD26 is never sent if the card doesn't reply properly to the vendor mode command.
Over an SPI interface, it doesn't.
Being a backdoor it works just like you wrote, of course, but it isn't true that in SPI it doesn't work.
Executing a cmd26 directly on the card while in SPI mode, then error 0x04 (illegal command) is issued, while always in SPI mode executing cmd62 0xEFAC62EC cmd62 0xEF50 cmd26 there is no error at all.
So it works.
The sequence cmd62 0xEFAC62EC cmd62 0xEF50 cmd26 can be used to check if the card supports the back door or not.
No errors it does, some error, generally 0x04 (illegal command), it doesn't, rather easy.