Neeraj Dantu
Forum Replies Created
-
AuthorPosts
-
Akshay,
The procedure to compile custom device trees with the Developer Package is shown here: https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package/.
Best,
Neeraj
Rishi,
Please make sure you have cpu clock frequencies defined in your custom device trees like here:
https://github.com/STMicroelectronics/linux/blob/v5.4-stm32mp/arch/arm/boot/dts/stm32mp151.dtsi#L27 and OPP table here:
https://github.com/STMicroelectronics/linux/blob/v5.4-stm32mp/arch/arm/boot/dts/stm32mp15xa.dtsi#L7
Do you see that the board boots completely with no issues logging in and executing commands?
Best,
Neeraj
Anton,
We are wrapping up the finishing touched on the SDK. It should be officially released by the end of next week 3/26.
Best,
Neeraj
Carel,
The SDK should be officially released by the end of next week 3/26.
Best,
Neeraj
bduke,
Currently, there is no CubeMX project for OSD32MP1-RED. We will generate a CubeMX project after we upgrade support from OpenSTLinux V1.2 to OpenSTLinux V2.x.
An alternate way of using CubeMX would be to generate specific parts of the CubeMX device tree you need and copy it over to the appropriate place in OSD32MP1-RED device tree. The sources for OSD32MP1-RED device tree are provided here: https://github.com/octavosystems/OSD32MP1-RED-Device-tree. As noted earlier, this device tree is generated for OpenSTLinux V1.2. Note that ST has changes how device trees are organized between OpenSTLinux V1.2 to V2.x. So, you will have to install CubeMX 5.x that is compatible with OpenSTLInux V1.2.
Developer Package can be used to cross compile: https://wiki.st.com/stm32mpu-ecosystem-v1/wiki/How_to_cross-compile_with_the_Developer_Package.
Best,
Neeraj
Bastien,
An eMMC is already integrated inside OSD335x C-SiP on the MMC1 interface. So, if you want to add an SD card, you can add it on MMC0 and have dual boot interfaces. You will have to implement a boot button to change boot order. Please take a look at the schematics for OSD335x C-SiP RED board here for an example implementation of eMMC and SD card with C-SiP: https://octavosystems.com/docs/osd3358-sm-red-c-sip-schematics-pdf/.
Best,
Neeraj
Karl & Leox,
The source code should be online in the next week.
Best,
Neeraj
March 5, 2021 at 1:08 pm in reply to: Working custom design works great for 6 months – now dead #11335Hey Matt,
It looks like the fault is intermittent. Most likely this is a mechanical issue. Please look for any hardware connectivity issues between SiP pins and the PCB. Cold solder joints for example can cause unreliable connections and could progressively get worse with time. We recommend doing an X-Ray on the boards to determine whether there is a connectivity issue.
Please take a look at sections 9.1, 9.2 and 9.3 on the datasheet(https://octavosystems.com/docs/osd335x-sm-datasheet/) to make sure you have the correct landing pad sizes and reflow profiles.
Please let us know when you have an update.
Best,
Neeraj
bduke,
Glad you were able to get it working. Distribution Package support for BRK board is in the works. In the meantime, if you can, please feel free share your knowledge for the community.
Please let us know if you have any more questions.
Best,
Neeraj
mlarkin,
It looks like there is a misconfiguration in the device tree. Exceptions at TF-A occur mainly because there is a clock tree issue. Please take a look at https://github.com/octavosystems/OSD32MP1-BRK-device-tree for a working device tree. You can compare the device tree you generated with the minimal config project and see where there is a difference in configuration.
The developer package provides a nice way to develop the initial image because it is easy to modify each of the components of the image. Once validated, these can be transferred over to the distribution package to generate image from scratch and make necessary image level configurations.
Direct support for Distribution Package for the BRK board is in the works.
Best,
Neeraj
Jack,
The AM335x SoC is able to generate a 50MHz clock from RMII1_REF_CLK. But, it cannot be used to supply clock to external PHYs because it does not satisfy the clock requirements for them. Please take a look at Advisory 1.0.16 of AM335x errata: https://www.ti.com/lit/er/sprz360i/sprz360i.pdf. You can configure the clock pin as an input by modifying the gmii_sel register.
We have not tested this ourselves. But, modifying the pinmux settings in Kernel device tree should change the pin configuration. Please take a look at https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/am335x-icev2.dts#L215 for example.
Best,
Neeraj
Karl,
Can you please check the boot configuration on the board? The boot configuration for SD card is described here: https://octavosystems.com/app_notes/osd32mp1-brk-getting-started/#boot. You can verify the switch positions are working correctly by probing the boot signals on the board. The layout files for the board are available here: https://octavosystems.com/octavo_products/osd32mp1-brk/#Design%20Files.
Best,
Neeraj
Stravos,
Please expect a release of the Debian SDK in the following weeks.
For now, please take a look at the device tree sources for OSD32MP1-RED here: https://github.com/octavosystems/OSD32MP1-RED-Device-tree.
Because the OSD32MP1 RED is configured to generate internal clock for Ethernet MAC, the device tree setup is different from STM32MP1-DK2 boards.
Please take a look at https://community.st.com/s/question/0D50X0000B8iBSB/stm32mp157-ethernet-problem for more information on Ethernet configuration.
Please make sure you are generating right clocks for both HDMI and Ethernet in CubeMX. Clock tree needs to be configured in 2 places:
1. TF-A: https://github.com/octavosystems/OSD32MP1-RED-Device-tree/blob/main/tf-a-v2.0/osd32mp1-red.dts#L168
Best,
Neeraj
Jac,
There are no modifications required for the commands themselves. You can ignore any part that involves cloud9 and run the commands.
Best,
Neeraj
Sylvian,
The device tree in the repository has not been created with CubeMX. So, it does not have an .ioc file associated with it.
However, you can take a look at the CubeMX application note we created for your development here: https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/.
You can also use the CubeMX tool to create device tree snippets of a particular peripheral and copy those snippets into the base working device tree. You will have to use a tool like diff to compare the difference between the old and new device trees from CubeMX and then export those snippets over to the base device tree in the git repository.
Best,
Neeraj
-
AuthorPosts