1 ACCEPTED SOLUTION
Accepted Solutions
Hello @Tom�? Ju?ena ,
After looking at your DTS/DTB, I didn't found the error yet, but I have a question and some remarks. Maybe they will help you.
Which usb port are you trying to use? Is it the USB C port CN7?
Because if this is the USB-C port, I advise you to follow this chapter in the wiki:
This is what is implemented in the stm32mp157c-dk2.dts delivered with the developer package of ecosystem v3.1.
If you want to use the USB C port, you have to add it in your i2c and add the port in the usbotg_hs node.
This example is in host and device mode.
----------
The other point is about the "phys" configuration of your usbotg_hs config:
In your DTB/DTS, we can see:
phys = <0x2d 0x00>;
phy-names = "usb2-phy";which means:
phys = <&usbphyc_port1 0>;
phy-names = "usb2-phy";If you want to use the usboth_hs in host mode, you have to set the phys port like this:
phys = <&usbphyc_port1 1>;The second parameter indicates if you want to use the OTG controller or the Host controller. This is explained here with a great ascii-art :
So if extra parameter of &usbphyc_port1 is 0, OTG controller uses DP2/DM2, if it is 1, HOST (USBH) controller uses DP2/DM2.
Since you want to configure the "usbotg_hs" node as a host, you must put 1 in extra parameter of &usbphyc_port1.
And regarding the phys port that you used for usbh-ehci and ohci, I don't think you must use the port0:
phys = <&usbphyc_port0>;
phy-names = "usb";Because if you look at the wiki page:
You can see that to configure the UTMI switch (like for the OTG) in USB Host controller, you have to use the port #2:
/* Use USBPHYC HS PHY port #2, configure UTMI switch to select USBH controller */
<&usbphyc_port1 1>;------------
If you still are blocked, please can I have the complete bootlog traces related to the latest DTB/DTS that you sent? Because the first traces that you put in your first post is from your previous test. It will help me and the community to help you :).
Hope it helps,
Regards,
Kevin
Hi @Tom�? Ju?ena ,
I think I finally found the problem! (I hope)
If you look at the wiki page of the regulator: https://wiki.st.com/stm32mpu/wiki/Regulator_overview#Consumers
The USBPHY is supplied by vdd_usb:
&usbphyc {
vdd-supply = <&vdd_usb>;
};And in the chapter 6.1 of the same page: https://wiki.st.com/stm32mpu/wiki/Regulator_overview#How_to_trace
You can see that vdd_usb is configured to 3300mV
- Your DTS
You were right, vdd-supply and vdd_3v3_usbfs-supply were missing in your DTS, so you added:
vdd-supply = <&vdd>;
vdd_3v3_usbfs-supply = <&vdd_usb>;This is nice, but if we look at the latest dts that you sent, the node related to vdd is:
buck3 {
regulator-name = "vdd";
regulator-min-microvolt = <0x1b7740>;
regulator-max-microvolt = <0x1b7740>;
regulator-always-on;
st,mask-reset;
regulator-initial-mode = <0x00>;
regulator-over-current-protection;
};and the vdd voltage is 0x1b7740 microvolt (1 800mv) and it must be 3300mv as visibile in the wiki.
When I look at the DTB that I compiled for my STM32MP157C-DK2 board, I can see in the pwr node that
vdd-supply = <0x4f>;
and 0x4f is:
buck3 {
regulator-name = "vdd";
regulator-min-microvolt = <0x325aa0>;
regulator-max-microvolt = <0x325aa0>;
regulator-always-on;
st,mask-reset;
regulator-initial-mode = <0x00>;
regulator-over-current-protection;
phandle = <0x4f>;
};with 0x325aa0 microvolt (3 300 mv) as visible in the consumers example of the wiki.
Please can you make a test to set the "vdd-supply" property to a BUCKs configured to 3300mv ?
Hope it helps,
Regards,
Kevin
