Can you help with questions in regards to USBmap tutorial sticky?

[DASBOOT5]

Can you explain how the T command corrects incorrect port type naming or is it just a port type discovery based on what the USBMAP guesses or what the OS guesses the port type is?
Is there a way to edit port types with USBMAP before creating the kext?
This seems to be a better way to may correctly it is a hybrid of USBmap usable in Windows where all of the parts are visible before starting the install process of opencore. It is called UBBToolkit, the kext or map (really a Plist) can be created in Windows. https://github.com/USBToolBox/tool

https://www.reddit.com/r/hackintosh/comments/n2udl3

What I do not understand about the tool is the Kext or Map creation with the tool which is used in conjunction with his downloadable kext is after ports are selected under the magic 15 in the kext creation process if the guesses are incorrect how do you correct port types? Also if there are 2 separate USB controllers is the magic 15 MAX apply to each controller or combined? (such as B550 chipset board)

5. Once all the ports are discovered, press Q to quit the ports discovery, and then press P to edit the plist.

USB Types

Type	Connector Info	Notes
0	USB 2.0 Type-A connector
3	USB 3.0 Type-A connector
8	Type C connector, USB 2.0 only
9	Type C connector, with USB 2.0 and USB 3.0 switch
10	Type C connector - USB 2.0 and USB 3.0 without Switch
255	Proprietary connector	For Internal USB Ports such as Bluetooth. macOS always expects Bluetooth as Internal.

Now, use T:x, x:3. Where,

• x represents your discovered port.
• 3 represents the connector type.

Type:


Code:

T:x:255


The x is the Bluetooth Controller and it has to be internal

 

[EliteMacx86]

Can you explain how the T command corrects incorrect port type naming or is it just a port type discovery based on what the USBMAP guesses or what the OS guesses the port type is?
Is there a way to edit port types with USBMAP before creating the kext?
This seems to be a better way to may correctly it is a hybrid of USBmap usable in Windows where all of the parts are visible before starting the install process of opencore. It is called UBBToolkit, the kext or map (really a Plist) can be created in Windows. https://github.com/USBToolBox/tool

https://www.reddit.com/r/hackintosh/comments/n2udl3

What I do not understand about the tool is the Kext or Map creation with the tool which is used in conjunction with his downloadable kext is after ports are selected under the magic 15 in the kext creation process if the guesses are incorrect how do you correct port types? Also if there are 2 separate USB controllers is the magic 15 MAX apply to each controller or combined? (such as B550 chipset board)

5. Once all the ports are discovered, press Q to quit the ports discovery, and then press P to edit the plist.

USB Types

Type	Connector Info	Notes
0	USB 2.0 Type-A connector
3	USB 3.0 Type-A connector
8	Type C connector, USB 2.0 only
9	Type C connector, with USB 2.0 and USB 3.0 switch
10	Type C connector - USB 2.0 and USB 3.0 without Switch
255	Proprietary connector	For Internal USB Ports such as Bluetooth. macOS always expects Bluetooth as Internal.

Now, use T:x, x:3. Where,

• x represents your discovered port.
• 3 represents the connector type.

Type:


Code:

T:x:255


The x is the Bluetooth Controller and it has to be internal

USBMap and USB Tool are two different ways to map the USB ports. A new guide is coming soon. Can you clarify your questions more simply?

 

[DASBOOT5]

Now, use T:x, x:3. Where,

• x represents your discovered port.
• 3 represents the connector type.

Type:


Code:

T:x:255

I believe I have it (the method of renaming port types I wish to map in)for the USBtoolbox you turn off the companion/guess feature and then the T:X:X command will be initiated for each port number used in with the command before making the Kext final?

If you have two USB controllers showing with either USBMap or Toolbox IS the 15 max per controller, as the port numbering sequence starts over when using the toolbox in Windows? ie 1-8 for controller one. 1-14 for controller 2. (2 separate controllers on the motherboard AMD motherboard I am working on (Gigabyte B550I Aorus Pro AX) Here is an example:

 

[EliteMacx86]

I believe I have it (the method of renaming port types I wish to map in)for the USBtoolbox you turn off the companion/guess feature and then the T:X:X command will be initiated for each port number used in with the command before making the Kext final?

Really not sure about USBToolBox. This guide is limited to USBMap.

No, that's one single command, for mapping and setting the port type.

If you have two USB controllers showing with either USBMap or Toolbox IS the 15 max per controller, as the port numbering sequence starts over when using the toolbox in Windows? ie 1-8 for controller one. 1-14 for controller 2. (2 separate controllers on the motherboard AMD motherboard I am working on (Gigabyte B550I Aorus Pro AX) Here is an example:

Yes, is limited to 15 only. There is a new method. The guide will be here very soon.

 

[DASBOOT5]

Really not sure about USBToolBox. This guide is limited to USBMap.

No, that's one single command, for mapping and setting the port type.

Yes, is limited to 15 only. There is a new method. The guide will be here very soon.

You should take a look at the toolbox before you write a new Tutorial. 90% of the time all of the ports do not show using the USBMap under terminal in the MacOS. If you want all the ports to show and guarantee all of the ports are showing before Mapping it must be done under Windows 10/11. The executable of the Toolbox is written from the original from u/CorpNewt with additional features which can be toggled on or off. The T:x:x command is identical to the USBMap version other than it just does not rename the port type if the auto guess feature and companion binding are turned on. These features only work under windows, they are not present in the Mac version of the toolbox or the original USBMap from u/CorpNewt,
Here is the author's comment on the differences between the windows and Mac versions of the Toolbox:

From macOS​

macOS is not recommended for several reasons. You won't have features like guessing port types (as there simply isn't enough info for this) as well as binding companion ports (again, no info). However, there are also port limits to deal with, and in macOS 11.3, XhciPortLimit is broken, resulting in a lot more hoops to go through.

 

[EliteMacx86]

You should take a look at the toolbox before you write a new Tutorial. 90% of the time all of the ports do not show using the USBMap under terminal in the MacOS. If you want all the ports to show and guarantee all of the ports are showing before Mapping it must be done under Windows 10/11.

Well, not sure about USBToolBox. But I have used USBMap and Hackintool and they work as expected. Of course, I never tried it on an AMD system. Although, I have one. Hopefully, this time, I'll write a guide for both. Intel and AMD, together.

The T:x:x command is identical to the USBMap version other than it just does not rename the port type if the auto guess feature and companion binding are turned on. These features only work under windows, they are not present in the Mac version of the toolbox or the original USBMap from u/CorpNewt,

I guess so.

original USBMap from u/CorpNewt,
Here is the author's comment on the differences between the windows and Mac versions of the Toolbox:

From macOS​

macOS is not recommended for several reasons. You won't have features like guessing port types (as there simply isn't enough info for this) as well as binding companion ports (again, no info). However, there are also port limits to deal with, and in macOS 11.3, XhciPortLimit is broken, resulting in a lot more hoops to go through.

Yes, he is right. Although, there is a new way, where I have been able to achieve more than 28ports and it works as expected.

Still not sure what your actual question is

 

[DASBOOT5]

Yes, is limited to 15 only. There is a new method. The guide will be here very soon.

This answer does not make sense based on these quotes taken from 2 different instructions on USB mapping (one from Dortania's guide) can you please elaborate?

"One extra note: if your Z370 board has a couple USB3.1 Gen 2 ports like mine does (a red type A and a type C port), they’re probably not part of the XHCI bus, but are provided by a different, separate controller on another branch. You can confirm this in IORegistryExplorer by plugging something into them and seeing that the device pops up in a completely different place. That means those ports DON’T count towards your 15 port limit."

"This meant it was just cleaner to stop at 15 than to say expand the port limit to 255(0xFF), and in Apple's eyes it made little sense to have anything above 15 ports as no Macs they supported went over this limit. And if a Mac Pro user added a USB expansion card, it would get it's own 15 port limit."

 

[EliteMacx86]

This answer does not make sense based on these quotes taken from 2 different instructions on USB mapping (one from Dortania's guide) can you please elaborate?

What I mean is, normally, when mapping, it only works up to 15 ports, if there is more, it will not work. However, with the new method, it's possible to have more ports and is not limited to 15 ports only.

"One extra note: if your Z370 board has a couple USB3.1 Gen 2 ports like mine does (a red type A and a type C port), they’re probably not part of the XHCI bus, but are provided by a different, separate controller on another branch. You can confirm this in IORegistryExplorer by plugging something into them and seeing that the device pops up in a completely different place. That means those ports DON’T count towards your 15 port limit."

Yes, I tested the new method while mapping on an RKL. That has a bunch of USB ports.

"This meant it was just cleaner to stop at 15 than to say expand the port limit to 255(0xFF), and in Apple's eyes it made little sense to have anything above 15 ports as no Macs they supported went over this limit. And if a Mac Pro user added a USB expansion card, it would get it's own 15 port limit."

Exactly. In short, there is a way to bypass this limit, even with the new version i.e macOS Big Sur 11.3 and later.