Hello - I have been working with the l051 for 2+ years now on a product, using i2c-1 as slave to outside world and i2c-2 as master for local board downstream devices. while my interrupt-driven code "works," I continue to have bugs filed about both ma...
In regular kernel and application development, does ST Linux running on the STM32MP15x series MPU allow booting over the network to a remote developer host, i.e. nfs-boot or similar so that "in-place" debugging can be performed?thanks, -pete u.
Hi. I have generated a full device tree for the EV1 to add I2C5 pins PA11/PA12 for external connector hookup to some of my I2C widgets using STM32CubeMX. I've place the generated .dts file from the kernel/ folder into <linux-source>/arch/arm/boot/dts...
Running Ubuntu-18.0.4LTS native on Dell latitude 5480. Using STM32MP157A-EV1, Following instructions (still), Ch6@https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Populate_the_target_and_boot_the_image#P...
Following these instructions:https://wiki.st.com/stm32mpu/wiki/Getting_started/STM32MP1_boards/STM32MP157x-EV1/Let%27s_start/Populate_the_target_and_boot_the_imagePlease see the attached screen shot, and advise.thanks.
SOLVED (I believe)I think my previous post was not needed because in fact my cube-mx generated .dts ==> kernel /boot/.dtb process was working in the first place. Thanks again for your suggestions on compilation, those helped.With the ev1 distribution...
using yes '' | make oldconfig ... does allow the build to continue and complete, even thought I'm not sure ALL the new configurations are really applicable. At any rate, here I am:I have completed building the .dtb from my cube-mx generated .dts. I h...
SOLVED:the answer is in the question. In my haste to recover a corrupted weston stack on the EV1 I failed to recognize my misreading of the instructions that clearly point out the use of the CN7/OTG port on the EV1, NOT the STM-Link port on the MP1 b...
Good afternoon (here at least), I have the device tree that now looks like it has a chance of giving me I2C5 on the I2C_EXT connector of the EV1. However I am now stuck on not being able to find details on how to move the STMCubeMX device tree files ...
