MTP responder, SDcard reader, and other compatability

[Dark Akuma]

This thread is for general compatability with transfering files to your Switchs SD card. Basically, anything where CaVE would “connect” to a device for Syncing and Save management.

Right now CaVE v1.5 is not compatible with the latest DBI. This is on my TODO list though.

CaVE requires at least v506 or before, but I am not sure on an exact version.

FTP support or whatever Wireless transfer I can do is also something I hope to work on, but is on the back burner right now.

Non-DBI MTP responders are… of a lesser concern. I am hesitant to support Tinfoil since in general, its crap and causes other issues. I don’t want to encourage people to use a known bad option.

[Dark Akuma]

While it does not exactly need “testing”, I added support for the more modern DBI. I have tested it with the latest, which off the top of my head I think is v598? If anyone can confirm it works, that would be fine. But if not, that's fine too. Its a relatively minor change, and the bulk of the DBI MTP responder code is version independent. Simply, at some point DBI made a change with 2 pieces of text.

Switch -> Nintendo Switch

External SD Card -> SD Card

---

In other news, just to disclose what I have researched… I'm less certain about FTP support.

I figured that any FTP homebrew app would naturally support providing access to the NAND like DBI does, so Save access would go along with it. But FTPD and sys-ftp (based of FTPD) both do not as far as I can tell. I found Checkpoint, which is said to support providing access to saves via FTP, but I have not confirmed myself yet.

I know I would like a wireless option. And the more options available, the less it will sting forcing people to use CaVE for file transfers. Yea, technically you can still manually copy databases yourself. But I will no longer be officially supporting that. Thus I want to provide support for as many automatic transfer options as I can.

SD Card Reader support is of course not the ideal method. But even that I still need to provide. DBI MTP is the recommended version. I guess after that, Memloader v3 / UMS Tool (Basically SD Card reader support). But that lacks Save management support. Hopefully Checkpoint pans out.

Anyway, for now I am just testing some FTP code to see how to work with it. It wont easily plug into the existing MTP/SD Card Reader support I have done now. It makes less sense considering the connection setup for Save syncing. Am I going to have to ping the Switch’s local IP every few seconds to detect when the FTP server code is running? I’m probably going to have to enable the Saves tab at all times, and put a button in the middle of it to press and try to connect to a FTP server.

---

Oh yea. For SD Card reader support, currently… it “should” work, but I have not changed anything to make it work better since the last report that it did not. It does for me. That’s all I know.

All I can do for now is, I have added debug messages to provide me some info when it fails. But only if it fails in the way I think it fails. Sucks that I cant test this myself outside of UMS Tool, which works fine. My 2 SD card readers are ancient. My phone wont work as one when linked to my PC. But still, I don’t think I would have the same issue if they did.

---

Well anyway, use this issue thread to inform me of homebrew apps and file transfer options I could/should support. I cant make promises. Just I don't assume to know all of them to properly consider them.

[Dark Akuma]

Just learned of Haze as a MTP option.

It currently does not work, even with the manual UMS Device code, since it uses the same device info as DBI, but lacks NAND access.

This is just further reason that I need to rewrite some of code. Rewrite being to base the device identification off probing the file structure too. Or rather, base things less off specific devices and more off “SDCard” and “SDCard+NAND”. Figuring that out right away on connection.