- Joined
- May 30, 2009
- Messages
- 1,292
- Trophies
- 1
- Age
- 28
- Location
- Madrid, Spain
- Website
- github.com
- XP
- 2,606
- Country
Yes and yes.Thank you. Is is for 11.0.1? Does this apply to usb:ds as well?
Yes and yes.Thank you. Is is for 11.0.1? Does this apply to usb:ds as well?
Not really, nope. The boot2 reimplementation from Atmosphère is launched after both USB and FS - all it does is call LaunchPostSdCardBootPrograms() and return right away.Just a question - why to patch usb module directly, if boot2 loads and hooks settings before usb. Why not patch there setting, not the module itself?
It is called by PM, not boot2 (even though it's part of the boot2 class). The first comment states this fact.In that case I do not understand what this function does and when it is called:
https://github.com/Atmosphere-NX/At...bstratosphere/source/boot2/boot2_api.cpp#L314
Patch locations 0x8718 and 0x87A8 in the uncompressed NSO with 05000014 (unconditional branch).
This will make the "usb30_force_enabled" checks always return 1.
Meh, I should just integrate usb 3.0 enable shit into ams. I'll do that today.
Thank you for going out of your way and making it easier for anyone to enable this flag. I truly appreciate it.Merged usb 3.0 enable stuff into ams-master, from next release onwards usb!usb30_force_enabled in system_settings.ini will work as expected when booting via fusee.
Hekate will need to get support for this to work when booting via hekate, I'll contact CTCaer about it.
Even if it chainload into fusee-primary?Hekate will need to get support for this to work when booting via hekate
Not necessary in that case.Even if it chainload into fusee-primary?
Are you properly setting USB3 device, configuration, interface and endpoint descriptors? Are you sure you're using a USB3-capable USB-C cable?I see
--------------------- MERGED ---------------------------
How can I check that setting applied at correct time?
Atmosphere with latest commit, usb30_force_enabled in config, loaded through fusee, but USBView still shows:
Is Port User Connectable: yes
Is Port Debug Capable: no
Companion Port Number: 1
Companion Hub Symbolic Link Name: USB#ROOT_HUB30#5&4087d53&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
Protocols Supported:
USB 1.1: yes
USB 2.0: yes
USB 3.0: no
int main(int argc, char **argv)
{
consoleInit(NULL);
usbCommsInitialize();
// Main loop
while(appletMainLoop())
{
//Scan all the inputs. This should be done once for each frame
hidScanInput();
//hidKeysDown returns information about which buttons have been just pressed (and they weren't in the previous frame)
u64 kDown = hidKeysDown(CONTROLLER_P1_AUTO);
if (kDown & KEY_PLUS) break; // break in order to return to hbmenu
consoleUpdate(NULL);
}
consoleExit(NULL);
return 0;
}
This flag set only on initial preUSB config parsing, right?new SMC config item via splGetConfigItem().
You can access it at any moment from HOS via spl.This flag set only on initial preUSB config parsing, right?
setting device through latest libnx usb_comms.
the same cable and port shows usb3: yes for external drive.
--------------------- MERGED ---------------------------
Also, AFAIK system first selects highest available speed reported by device and only after that asks for descriptors.
--------------------- MERGED ---------------------------
Test also simpliest:
Code:int main(int argc, char **argv) { consoleInit(NULL); usbCommsInitialize(); // Main loop while(appletMainLoop()) { //Scan all the inputs. This should be done once for each frame hidScanInput(); //hidKeysDown returns information about which buttons have been just pressed (and they weren't in the previous frame) u64 kDown = hidKeysDown(CONTROLLER_P1_AUTO); if (kDown & KEY_PLUS) break; // break in order to return to hbmenu consoleUpdate(NULL); } consoleExit(NULL); return 0; }
I mean, then this flag reflect this value read while boot2 process, not later by set.mitm.You can access it at any moment from HOS via spl.
I know that. I think it enough just to test USB3 capabilities.You should not use libnx usbcomms, for multiple reasons. I see it as really just proof of concept code.
You should not use libnx usbcomms, for multiple reasons. I see it as really just proof of concept code.
So, is it bad even for test initialize?as the author of the libnx usbcomms code, pretty much this. I don't recommend using it.