WIP libusbhsfs - USB Mass Storage Class Host + Filesystem Mounter static library.

Are there a lot of people who use external hard drives formatted to EXT*?

I uploaded snippets of the MBR/GPT code I wrote for Tinfoil, I hope it saves you some time if you intend to parse the MBR/GPT manually: https://gist.github.com/blawar/98635098baa9ae8ba502dfd62a5c8417

note that EXFAT and NTFS both share the same partition code (annoying). The only way to differentiate them is to actually read from the partition itself ti try to figure out the file system.

 

Where were you during the WiiU days ? I still don't think we have proper WiiU hdd support for HB lol

 

oof yeah that'll do it but if you ever do find yourself with a WiiU we could really use your talents heh

 

Love you DKM - sending positive vibes to you <3

 

Could you please implement SX's USB api on the backend, so developers who use this library will automatically work on both atmosphere and sxos with no code changes? The relevant code is here: https://github.com/blawar/tinleaf/blob/master/source/nx/usbhdd.cpp

It is not currently working in SXOS though because the code in Tinleaf is low quality, and I do not believe their API supports relative paths.

 

I was gong to say, their license is pretty permissive. So I downloaded those files from the website years ago, and then I ported them to the latest libnx when they did that big service api rewrite. However any code that I wrote in that tinleaf repo you are free to use and re-license in any way you see fit.

— Posts automatically merged - Please don't double post! —

Also, ensure it is actually SXOS and not reinx or AMS before you try to initialize TX services or it will crash the user's switch. The code used for detecting SXOS on that file I linked works.

 

I just tested it, and no, tx.h, tx.c, txInitialize(), and txExit() do not appear to be needed.

 

I compiled it and ran your example app in SXOS with USBHDD attached and got this:

USB MAss Storage status change event triggered!
Mounted USB Mass Storage device count: 1
Failed to list mounted USB Mass Storage devices!

 

This fixes the error, there was a logic error

Code:

u32 usbHsFsListMountedDevices(UsbHsFsDevice *out, u32 max_count)
{
    mutexLock(&g_managerMutex);
 
    u32 device_count = 0, ret = 0;
 
    if (g_isSXOS)
    {
        if(g_sxOSDeviceAvailable)
        {
            /* Copy device data, update return value and jump to the end. */
            memcpy(out, &g_sxOSDevice, sizeof(UsbHsFsDevice));
            ret = 1;
        }
        goto end;
    }
 
    if (!g_usbHsFsInitialized || !g_driveCount || !g_driveContexts || (!g_isSXOS && !(device_count = usbHsFsMountGetDevoptabDeviceCount())) || !out || !max_count)
    {
        USBHSFS_LOG("Invalid parameters!");
        goto end;
    }
 
    for(u32 i = 0; i < g_driveCount; i++)
    {
        UsbHsFsDriveContext *drive_ctx = &(g_driveContexts);
    
        for(u8 j = 0; j < drive_ctx->lun_count; j++)
        {
            UsbHsFsDriveLogicalUnitContext *lun_ctx = &(drive_ctx->lun_ctx[j]);
        
            for(u32 k = 0; k < lun_ctx->fs_count; k++)
            {
                UsbHsFsDriveLogicalUnitFileSystemContext *fs_ctx = &(lun_ctx->fs_ctx[k]);
            
                /* Fill device element. */
                UsbHsFsDevice *device = &(out[ret++]);  /* Increase return value. */
                usbHsFsFillDeviceElement(drive_ctx, lun_ctx, fs_ctx, device);
            
                /* Jump out of the loops if we have reached a limit */
                if (ret >= max_count || ret >= device_count) goto end;
            }
        }
    }
 
end:
    mutexUnlock(&g_managerMutex);
 
    return ret;
}

— Posts automatically merged - Please don't double post! —

This is the output from your test program on SXOS. IIRC SX's api does not support renaming files on the hard drive which may be the cause of that error.

 

I updated Tinleaf to use use your dev branch, and released a binary: https://github.com/blawar/tinleaf/releases/tag/1.4.1

I tested it on both SXOS and AMS, works great.

 

It might be a bug with SXOS's driver. I remember when they first released the homebrew library, I had a graph at the top for hdd free space but it was very buggy and locked up my app for like 30 seconds so I removed it.

Perhaps a further down the road thing (since it is 99% there already), however SXOS' server lets you read and write directly from the storage. It is possible for you to just issue raw storage read/write commands and unify the code even more. Then you could implement the things you stubbed.

Thanks for the quick work. This is a really great thing that there is a standard interface for accessing HDD's on all CFW's.