2022-08-14 05:39 AM
Hi,
Currently i am looking for an easy way:
to change the device tree, to assign peripherals to the M4 Coprocessor for quasi real time applications.
i do have a STM32MP157F-DK2 board for testing and also a board with Debian, which i purchased from a different vendor who has built it´s own Linux image, which i want to use.
The vendor does not provide any CubeMX files for his design, or any other information regarding his design.
So... do i need to built everything from scratch myself ?
2022-09-01 02:44 AM
Hi @STrat.1
For DK2 board for sure you can use CubeMX to generate DTS assigning peripherals to M4.
Can you please give the reference of the other board you are talking about ?
Olivier
2024-01-16 05:30 AM
Hi,
here is the topic creator once again.
The problem:
i stopped some time ago with this and now more people are interested in resolving this.
The reference board is, which can enter production or engineering mode.
https://www.olimex.com/Products/OLinuXino/STMP1/STMP157-OLinuXino-LIME2/open-source-hardware
to which i sucessfully connected with st link and got some response of the board.
olimex has its own image called Olimage, and has a guide to change the device tree blob:
https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf
Goals:
Extract the information to generate an ioc file for cubemx to built my own STlinux Yocto image.
or
simply program the M4 core with .elf files, for realtime tasks and i do not want the A7 to interfere somewhow with the M4 through shared resources. They should work independently from each other and only communicate via remoteproc.
How can i accomplish this?
Thanks & BR