2023-02-21 08:58 AM
Our product has a STM23MP151D, no security features (signed stuff or fuses blown) and the same QSPI NOR as the EV1 board.
We have run the microcontroller style DDR tester (STM32DDRFW-UTIL) which took a bit of bashing to run on the 151 but did show our memory (interface) is good..
But I cannot for the life of me get TF-A to load (along with U-Boot) via USB from the STCubeProgrammer. TF-A goes in and outputs stuff on the console but it's as if though the ROM knows how to drive the USB and get this far, TF-A does not on this device.
I have had to stop TF-A concerning itself with the monotonic counter and bsec_probe(). Things I think this device does not have.
What I would really like is confirmation that some version (which ?) of https://github.com/STMicroelectronics/arm-trusted-firmware.git works on the 151 and did you have to do anything to it ? Ideally its IOC and DTS files and anything else.
The problem is that there does not appear to be a single dev board or reference design with the 151 I can compare to.
Does anybody out there use the 151 booting with TF-A SP_MIN edition then U-Boot and is willing to share their know-how ?
2023-03-14 09:32 AM
Hi @JSchn.5 ,
Sorry to come late in this thread and bad time with your project.
Indeed we don't have MP151 ref design board and sw delivery but many customers used either MP151 or 153 quite smoothly.
As for any other custom design the method we recommand is to use CubeMX to generate project with your soc reference, setup your peripheral as requested.
Once DTS generated, take as reference DTS generated for a EV1 or DK2 board project ( the most close to your design) and comparing node by node fill the USER DEFINED section accordingly.
Following link provide some further tips and guidance for this:
FAQ : STM32MP1 - How to create a device tree adapted to your design with STM32CubeMx?
EDIT : refering to this link can also help to better understand Device Tree structure and the way 15x diversity is managed :
STM32MP15 device tree - stm32mpu-ecosystem-v3
Hope it help
Olivier
2023-03-23 02:03 AM
Yes I have been through this procedure.
I'd like to check my understanding of the USB_OTG_HS peripheral as presented in the STM32CubeMX tool. There is a dropdown for "High Speed". Initially I thought with this on "Disabled" it would work at 12Mb/s but I see that the pins (USB_DM2 and USB_DP2) are removed. Given that we have a micro USB socket and do not have PA10 wired I guess "Device_only" is the safe setting. So would I be right in thinking that "High Speed" set to "Disabled" actually disables OTG functionality as if the checkboxes were all unchecked ?