Neeraj Dantu
Forum Replies Created
-
AuthorPosts
-
gregor613,
We are working on updating the board support to OpenSTLinux 3.0(latest). Please check back in a few weeks.
Best,
Neeraj
Rishi,
This question may be better suited for STM32MP1 forum as it involves core driver setup and ST’s team would be better able to answer.
From our side, we would suggest taking a look at the driver source code: https://github.com/STMicroelectronics/linux/tree/v5.10-stm32mp/drivers/usb/dwc2/, although the documentation on this driver is not great. Enabling traces would also give you more debug messaging to understand where the setup is failing: https://wiki.st.com/stm32mpu/wiki/USB_overview.
Best,
Neeraj
Carlos,
Thanks for closing the loop. We will test for this use case when we update the software.
Best,
Neeraj
Matthew,
Because the hardware configuration for DK2 and RED are different, you will not be able to use the DK2 device tree to implement the M4 demo. You will need to include the device tree nodes in the stm32mp157c-dk2-m4-examples.dts file in osd32mp1-red.dts and recompile the device tree to be able to exercise the M4 peripherals.
Please take a look at https://wiki.st.com/stm32mpu-ecosystem-v1/wiki/How_to_compile_the_device_tree_with_the_Developer_Package.
Best
Neeraj
Audrain,
Please refer to Buildroot documentation for this: https://buildroot.org/downloads/manual/manual.html#adding-board-support. We are working on adding more build system support for OSD32MP1 dev boards. Currently, we recommend working with OpenSTLinux.
Best,
Neeraj
Matthew,
This happens because of the device tree configuration for the BRK. You will encounter the same error if you use the DK2 if you boot with the default device tree: ‘stm32mp157c-dk2.dtb’. If you use stm32mp157c-dk2-m4-examples.dtb, you will be able to run the example without errors. Please take a look at the device tree here: https://github.com/STMicroelectronics/linux/blob/v5.10-stm32mp/arch/arm/boot/dts/stm32mp157c-dk2-m4-examples.dts.
Best,
Neeraj
mkleox,
We are currently putting together Debian support for BRK. The binary image for Debian is available in the BRK page here: https://octavosystems.com/octavo_products/osd32mp1-brk/#Software. You can use the Device tree sources(https://github.com/octavosystems/OSD32MP1-BRK-device-tree/tree/v1.2) if you want to make changes to the hardware configuration. For compilation of the device tree please take a look at how to use the developer package: https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package. Please note that you will need to use OpenSTLinux V1.2 linked here: https://wiki.st.com/stm32mpu-ecosystem-v1/wiki/Main_Page.
Best,
Neeraj
SylvianB,
As shown in Section 4.4 of Boot Chain Overview(https://wiki.st.com/stm32mpu/wiki/STM32MP15_ROM_code_overview#Boot_from_e-E2-80-A2MMC-E2-84-A2), only CK, CMD and D0 are utilized for eMMC boot by the ROM code. So, you can use PC7 for the D7 bit of the eMMC interface as you can setup the pin in device tree for the bootloader. You will not need to change any OTP parameter for eMMC boot. OSD32MP1-RED does not come with any OTP pre-programmed.
Best,
Neeraj
Carlos,
Can you take a look at the troubleshooting steps described here: https://octavosystems.com/app_notes/osd32mp1-brk-getting-started/#trouble.
Another thing to try would be to use a USB hub connected to your laptop to power the BRK. Trying a different port or a different machine(we recommend Ubuntu for development) are also viable options. RED and BRK have different configurations for USB OTG port. Both should work just fine. Although it does not look related to your issue, it looks like there are other people reporting problems with the RNDIS functionality: https://community.st.com/s/question/0D50X0000B5H4dHSQS/windows-10-does-not-recognise-ethernet-over-usb-for-stm32mp157cdk2. We will monitor this thread to see if there are similar reports and update the image if needed.
Please update here if you have one.
Best,
Neeraj
Arthur,
The low power modes were not supported in OpenSTLinux V1.0, which is what was used to develop the Debian image. They will be supported in the next release of Debian as we plan to upgrade to Kernel 5.10 with OpenSTLinux v3.0.
Best,
Neeraj
Hey Artthur.
Please take a look at https://community.st.com/s/question/0D53W00000cxRieSAE/wakeup-on-gpio-in-linux-on-stm32mp1 and https://www.st.com/resource/en/application_note/dm00449434-stm32mp1-series-using-low-power-modes-stmicroelectronics.pdf. https://octavosystems.com/forums/topic/wake-up-through-gpio/#post-11532 is also useful.
Best,
Neeraj
Hey Rishi,
My apologies for the delayed response.
It turns out, GPIO wakeup is already implemented in the core device tree for stm32mp1 here: https://github.com/STMicroelectronics/linux/blob/v5.4-stm32mp-r2/arch/arm/boot/dts/stm32mp151.dtsi#L1313. You are right that CubeMX does not generate any wakeup specific device tree nodes to facilitate GPIO wake-up. But, as the pwr_irq nodes are already declared in stm32mp151.dtsi, all GPIO wake-up pins are enabled by default. You should not have to modify device tree in order to be able to implement wake-up. However, note that you will need to make sure that the pin that you are using for wake-up is not configured in the device tree for some other function. I was able to test this with DK2 on Kernel 5.4 with PA0.
For using the ponkey, please also compare your TF-A and U-Boot device trees to the BRK. It looks like there is a proper low power mode entry and wake-up detection. But, the TF-A is running into an error while initializing the board.
Best,
Neeraj
PMZ,
We do not have a CubeMX project for the BRK. However. we offer a minimal CubeMX project that can be modified for the BRK her: https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/. We also offer the device tree source for the BRK: https://github.com/octavosystems/OSD32MP1-BRK-device-tree as well as the patches for OpenSTLinux Developer Package here: https://github.com/octavosystems/BRK_Developer_Package_patches. We are assessing whether a CubeMX project is needed for the BRK.
Best,
Neeraj
orocle,
As you said, the SPI devices are available on both the OpenSTLinux image and Debian images for the BRK.
If you are referring to the minimal CubeMX project, you are right that there are not SPI devices enabled in that project as it was intended to create a minimal bootable system.
There are several resources for doing custom builds. Please take a look at the BRK Developer Package patches here: https://github.com/octavosystems/BRK_Developer_Package_patches. You can use them to build a custom OpenSTLinux image based on OpenSTLinux Developer Package(https://wiki.st.com/stm32mpu/wiki/STM32MP1_Developer_Package).
For Debian, we have made the SDK available here: https://github.com/octavosystems/osd32mp1-debian. Note however that the Debian SDK is built on an older version of the OpenSTLinux distro.
Best,
Neeraj
-
AuthorPosts