dtc on OSD32MP1-RED
Forums › Devices › OSD32MP15x › dtc on OSD32MP1-RED
- This topic has 2 replies, 2 voices, and was last updated 1 week, 4 days ago by
Budimir Miljkovic.
- AuthorPosts
- November 5, 2024 at 5:07 am #15373
Hello,
I installed dtc on the RED board with Debian, it is looking good converting /sys/firmware/fdt to fdt.dts. I did conversion in another directory over copy of fdt file. Reverse conversion did not give same binary fdt – there were differences both in size and in data. Also, fdt file is read only, so I couldn’t replace original fdt with new one. Is it possible to modify fdt file, or I need to create new image? I’m experienced with embedded systems, but new to Linux.
Attachments:
- November 7, 2024 at 1:26 pm #15388
Budimir,
There are better ways for device tree modification:
1. Developer Package: https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package (Keep track of kernel version you are using and match the developer package kernel version)
2. Distribution Package: https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Distribution_Package
3. Use the Debian SDK: https://github.com/octavosystems/osd32mp1-build-tools/blob/master/Makefile#L148
I am not sure whether this is happening on OSD32MP1-RED, but bootloader and kernel can modify the device tree at runtime.
Best,
Neeraj
- November 9, 2024 at 4:34 pm #15395
Thanks Neeraj,
I’m using the Debian SDK with a docker. It produced a SD image which works fine, but I’m now trying to find which file I should edit to enable access of m4 core to peripherals (2 SPIs , 2 external interrupts and few GPIO lines). As I understand, initial SD image has device tree which takes almost all peripherals – couldn’t find one pin which is accessible to m4 core.
I thought that editing device tree in runtime is not possible, can you point me to some manuals how to do that?
Thanks for your help, I appreciate very much your efforts!
Best,
Budimir
- AuthorPosts
- You must be logged in to reply to this topic.