Hi,
I am also very interested in the Yocto Layer for the RED board! Any scheduled release date?
Thanks
Thanks Neeraj!
Hi,
I have checked that you have included a new yocto and Debian Image for the osd32mp1-brk:
Any news about the update of the manual to this BSP 1.2 version? I would like to have access to the steps that you have followed to create the yocto and the Debian Images. It is also important to have access to the tf-a, u-boot and kernel sources that you have used, just in case any modification in the DT files or sources is needed. And also the access to the .ioc used configuration for the CubeMX.
Thanks
Alberto
Thanks Neeraj! The problem has been solved thanks to your indication!
Best Regards
Alberto
Thanks Erik!
Thanks Neeraj
There is no problem to edit manually the device tree. Do you know where ST is setting the PC13 pin that is being used by the PMIC_WAKEUP?
I would like to know if it is possible to configure some pins with specific pad setting in the early boot stages, for example during TF-A booting.
Thanks
Thanks Neeraj! it is clear now!
Hi,
i would like to follow the STM32MP1 CubeMX Tutorial for OSD32MP15x app note https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/
using the STM32MP157C-DK2 development platform from ST. The idea is to work with the ST board until there is an Octavo board available, but that my SW solution can be valid for my custom HW even if it is developed using the ST board.
There is something that is not clear to me. The OCTAVO PART NUMBER>_MinimalConfig.ioc configuration is using some fixed settings mainly for the Ocatvo SiP DDR configuration. But can an Octavo SiP DDR configuration with specific settings used in the STM32MP157C-DK2 board (that will probably have different DDR memory settings)? Is this possible?? Can the processor boot?
Thanks
Alberto
Octavo Systems LLC all rights reserved
OCTAVO is registered in the U.S. Patent and Trademark Office. OSD, C-SiP, and the Octavo Logo are trademarks of Octavo Systems LLC.
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields
"*" indicates required fields