2018-11-02 11:51 PM
Hello there,
I am currently analyzing the STUSB1602 chip and the P-NUCLEO-USB002 eval kit. I have come across a topic I am not fully certain about. Its the SPI interface for the BMC communication. I cannot understand either it is necessary in all applications, or only if I want to exchange some specific data between devices over CC line? For example, if I intend to create a sink only device, so I have to connect the SPI lines and provide any data from the MCU? I would appreciate all help.
Solved! Go to Solution.
2018-11-16 06:49 AM
2018-11-16 07:06 AM
so, if both boards (which use different devices) reject the original attach, it means there could be an issue with the SOURCE (VBUS different from vSafe 5V, discharge issue, not cold socket etc...) or with the Type-C cable (please use the one from P-NUCLEO-USB002 pack when possible). Do you confirm both boards still work with STEVAL-ISC004V1? If you can't find the issue, I'm interested to borrow your AC adapter to have a look at it (and ship back of course). Did you perform some trials with your DELL laptop?
2018-11-16 07:15 AM
2018-11-16 08:38 AM
Benoit,
Unfortunetally, I left the at the P-NUCLEO-USB002 office and cannot check either I can get better voltages from the dell PC... I will check that asap at monday and let you know.
As for the mentioned charger, it consists of 2 ports: USB A and USB C:
If I connect my android phone to the USB C (USB C ,-> USB C cable), I get a system message that fast charging is in progress:
While if I connect it to the USB A ports (using USB C to USB A plug cable), I get regular charging:
This would suggest that the phone made a handshake with the charger over USB C. I wonder why didnt this work with the eval boards.
2018-11-19 01:48 AM
Hi Lukasz,
To check what is happening with STEVAL-ISC004V1, I recommend to use the associated GUI (STSW-STUSB001) (STM32 NUCLEO board required to run it). The GUI include a Dashboard that collects the SINK profile, so that you can check consistency with the SOURCE profile. It also report the agreed contract between the 2 devices.
Also please note that your charger also support former Qualcomm QC3.0 on top of USB PD, which is likely the fast charge protocol also implemented in your smartphone. This protocol is not implemented on the eval board you have.
bye,
Benoit
2018-11-19 11:57 AM
2018-11-19 12:06 PM
2018-11-20 12:45 AM
Hi Lukasz,
there is a .bin file into STSW-STUSB001 software package that you need to drag and drop into the Nucleo + an .exe (GUI). the User Manual is called: "UM2254: STSW-STUSB001 quick installation guide"
rgds,
Benoit
2018-11-20 12:46 AM
2018-11-25 08:58 AM
Hello Benoit,
I should have the needed Nucleo tommorow. As for now, I have some results on connecting the P-NUCLEO-USB002 to the Dell precision 7730 machine. I would consider this one a pretty "high end", but it seems that it can only provide 5V... Please take a look:
P-NUCLEO-USB00x Demo v1.0.4
Console v0.4
Type help for a list of commands.
STMicroelectronics
Copyright (c) 2017 - All Rights Reserved.
>
*** [1] attached on CC2 (Sink)
*** [1] selected cap #1
>s 1
Role: Sink - Explicit contract CC2 Profile 1 5.00V
>r 1 1
Requested 1 : 5.00V 3.00A
>
*** [1] selected cap #1
r 1 2
Request failed: wrong index param '2' specified.
>r 1 1
Requested 1 : 5.00V 3.00A
>
*** [1] selected cap #1
r 2 1
Error: invalid parameter port '2 1'
>r 1 2
Request failed: wrong index param '2' specified.
>r 1 3
Request failed: wrong index param '3' specified.
>r 1 1
Requested 1 : 5.00V 3.00A
Does this piece:
>r 1 2
Request failed: wrong index param '2' specified.
means that it does not support the second profile? Looking forward to your answer.