2024-11-25 01:22 PM - edited 2024-11-25 01:37 PM
Hello,
We have produced a board using the STM32MP257FAI3 that we are trying to bring up. I previously had followed the following guide: Getting started - stm32mpu To bring up the STM32MP257F-EV1 development board; I applied the same process to the debug/run configurations for my own board and we are unable to connect to the processor using the STLink-V3 nor program the eMMC over USB. We have checked the ST-Link connections to the processor, and all appears to be correct (i.e., matching the EV1 board). We also texted the voltages going to the processor and those appear as expected.
1. Should we expect to be able to connect to the STM32MP2 processor using the ST-Link alone? We're seeing that "Examination Failed" when the ST-Link is trying to connect to the processor. We are able to get past this step with the EV1 board, though we've not really been able to do anything useful with the CubeIDE at this point.
2. Since we are unable to connect to the STM32MP2, we are unable to program the STPMIC25 via I2C to configure the power rails properly (this is primarily important for the DDRs). We assume that connecting to the STM32MP2 to run some basic software is a preliminary requirement to bringing up the board. Is that correct?
3. Our new board has a boot fail LED that flashes when the board is powered on without the USB plugged in (nothing is programmed in the flash currently); the LED light does not flash if you plug the USB cable in. Therefore, the STM32MP2 is aware that the debugging computer is connected to it. However, we are unable to connect to the processor via the USB to program the flash (the STM32MP2 does not appear as a device on the Ubuntu computer that it is plugged into whereas the EV1 does), and thus, we are unable to program the flash. Are there any steps that we have missed that would enable the STM32MP2 to show up as a device on the Linux/Ubuntu development machine and allow the flash to be programmed?
Overall, it seems like the STM32MP2 is missing information about booting from USB and/or the ST-Link is missing information about how to connect to a bare-metal STM32MP2. We noticed that support for "bare-metal" STM32MP1 was a feature added to CubeIDE, so perhaps this is missing in the current CubeIDE build (even though it says that STM32MP2* is supported).
Any insight would be greatly appreciated.
Thank you
PS - Your DDR reference design schematics that are currently on your website are incorrect as it shows a 5V input connection to LDO3 using a DDR4 instead of the output of Buck 6.