Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac-OS wiki update | How to connect to configurator #10279

Merged
merged 5 commits into from
Aug 9, 2024
Merged

Mac-OS wiki update | How to connect to configurator #10279

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a53c303
Update USB Flashing.md
KY-S0ong Aug 5, 2024
e8f9503
Update USB Flashing.md
KY-S0ong Aug 5, 2024
a548bc6
Update USB Flashing.md
KY-S0ong Aug 5, 2024
98bc9f0
Connecting to Configurator via USB-C cable
KY-S0ong Aug 9, 2024
fc8aa0d
Update USB Flashing.md
mmosca Aug 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/USB Flashing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,13 +49,21 @@ With the board connected and in bootloader mode (reset it by sending the charact
* Choose Options > List All Devices
* Select `STM32 BOOTLOADER` in the device list
* Choose `WinUSB (v6.x.x.x)` in the right hand box

![Zadig Driver Procedure](assets/images/zadig-dfu.png)

* Click Replace Driver
* Restart the Configurator (make sure it is completely closed, logout and login if unsure)
* Now the DFU device should be seen by Configurator

## Platoform: Mac-OS
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be fair, I think this is a general USB-C issue, not a MacOS issue. It just so happens that macs only have USB-C ports.

USB-C cable is the same on both ends, so some extra bits on the devices is required to let themselves be auto detected as devices, instead of hosts.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a really good point that I did not think of 😃. Should I just delete the branch or rephrase it from Mac-OS to something along the lines of “while using USB-C”

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just edit it. :)

Copy link
Contributor Author

@KY-S0ong KY-S0ong Aug 9, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mmosca by any chance do you connect your USB-C to C to a USB a dongle or hub? I did some research and found out USB-C only sends power when the device requests it while USB-A essentially always sends power.

I have tried using a USbC to C cable with a USBC dongle but it does not work. (Wow that was a lot of USB)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

USB-C can be used on both the host and device side. It can also support other (higher) voltages and power levels, so it needs a bit more complicated stuff on both sides of the connection to successfully negotiate the type of connection (host/device) and power levels.


Configuator devices can have a problem accesing USB devices on Mac-OS. This is *ussaly* solved by a cable change.

* The official Apple USB-C to USB-C will not work no matter orentation.
* Make sure the cable you are using support data transfer
* For best results, use a USB-C to USB-A cable (And a dongle if your computer does not have an USB-A port)
* Dongle side pluged into the computer

## Using `dfu-util`

Expand Down