I've been tasked with a project at work that is fairly outside my scope of knowledge and hoping others might have any potential advice.
- Is it possible to communicate with a TUSB2036 USB chip to poll if a port is actively providing a charge to a downstream connection (a wireless charger in this example)? We are hoping to detect when the wireless charger begins pulling a charge and run some logic when that is detected.
- When I utilize libusb (technically gousb as we are a Go shop) to communicate with the chip, I can send a few Control commands and Read commands, but not Write commands. The documentation indicates that it should support Write commands. Does this mean the custom board that the chip is integrated into was improperly set up?
- Additionally, is there a list of byte commands that can be run successfully with the TUSB2036 device? I have referenced these links: Microchip Developer Help and the TUSB2036 Data Sheet, but many of these commands simply return a `pipe error -9` when issued.
- Using Go and gousb, the only successful communication I have found so far is:
// Allocate a byte slice to receive the hub status data := make([]byte, 64) // Send a control command numBytes, err := dev.Control(0xA0, 0x06, 0x00, 0x00, data) if err != nil { panic(err) } // Data returns a slice of: 9,41,3,13,0,0,100,14,14 // I am unsure what these values correspond to and have struggled to locate a resource to help me parse it.
- Using Go and gousb, the only successful communication I have found so far is:
- Additionally, is there a list of byte commands that can be run successfully with the TUSB2036 device? I have referenced these links: Microchip Developer Help and the TUSB2036 Data Sheet, but many of these commands simply return a `pipe error -9` when issued.
I have a custom board that has some integrated USB chips on it (TUSB2036 from Texas Instruments). Each chip then connects to a three USB-C's that connects to a wireless charging board (we're testing a few different models). My background is coding in Golang, and I have no experience with circuitry.