STPM4RasPI for STM32MP135F-DK - SPI timeout error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-28 4:31 AM - edited ‎2023-11-28 4:38 AM
Hi,
I would like to integrate the STPM4RasPI with MP135F-dk. After following the https://wiki.st.com/stm32mpu/wiki/STPM4RasPI_expansion_board tutorial, I am receiving an error.
Driver is enabled:
STPM4RasPI module is properly attached.
Do you have any possible solutions?
Best,
Jacek
Solved! Go to Solution.
- Labels:
-
Bug-report
-
STM32MP13 Lines
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-29 2:35 AM
Hi @Olivier GALLIEN ,
Instruction given in https://wiki.st.com/stm32mpu/wiki/X-LINUX-TPM_expansion_package was helpful. I had to adjust arch/arm/boot/dts/stm32mp135f-dk.dts as:
&spi5{
pinctrl-names = "default", "sleep";
pinctrl-0 = <&spi5_pins_a>;
pinctrl-1 = <&spi5_sleep_pins_a>;
cs-gpios = <&gpioh 11 0>;
status = "okay";
st33htpm0: st33htpm@0{
status="okay";
compatible = "st,st33htpm-spi";
#address-cells = <1>;
#size-cells = <0>;
reg = <0>; /* CS #0 */
spi-max-frequency = <10000000>;
};
};
And then the module was successfully detected.
Going back into the https://wiki.st.com/stm32mpu/wiki/STPM4RasPI_expansion_board there is a significant difference in configuration:
&spi5{ cs-gpios = <&gpioh 11 0>; status = "okay"; st33htpm0: st33htpm@0{ status="okay"; compatible = "st,st33htpm-spi"; #address-cells = <1>; #size-cells = <0>; reg = <0>; /* CS #0 */ spi-max-frequency = <10000000>; }; };
It is wrong and should be changed.
Best,
Jacek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-28 4:55 AM
Hi @jschneider
,
Please confirm you are on top of release V5.
For this last release you may also try https://wiki.st.com/stm32mpu/wiki/X-LINUX-TPM_expansion_package which have been validated on DK 135F.
Cross-checking both article and solution may help to find the missing piece
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-28 4:59 AM
Hi @jschneider
I also add a big warning : any wrong side connection of the TPM to RasPI connector likely lead to kill the TPM. ( high probability)
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2023-11-29 2:35 AM
Hi @Olivier GALLIEN ,
Instruction given in https://wiki.st.com/stm32mpu/wiki/X-LINUX-TPM_expansion_package was helpful. I had to adjust arch/arm/boot/dts/stm32mp135f-dk.dts as:
&spi5{
pinctrl-names = "default", "sleep";
pinctrl-0 = <&spi5_pins_a>;
pinctrl-1 = <&spi5_sleep_pins_a>;
cs-gpios = <&gpioh 11 0>;
status = "okay";
st33htpm0: st33htpm@0{
status="okay";
compatible = "st,st33htpm-spi";
#address-cells = <1>;
#size-cells = <0>;
reg = <0>; /* CS #0 */
spi-max-frequency = <10000000>;
};
};
And then the module was successfully detected.
Going back into the https://wiki.st.com/stm32mpu/wiki/STPM4RasPI_expansion_board there is a significant difference in configuration:
&spi5{ cs-gpios = <&gpioh 11 0>; status = "okay"; st33htpm0: st33htpm@0{ status="okay"; compatible = "st,st33htpm-spi"; #address-cells = <1>; #size-cells = <0>; reg = <0>; /* CS #0 */ spi-max-frequency = <10000000>; }; };
It is wrong and should be changed.
Best,
Jacek
