STM32MP1 ECO 5.0.0. CubeProgrammer flashing image 0x1 result in no USB response after download

[debugging]

After compiling TF-A, uboot and optee, the flashing of the first mage xxx-usb.stm2 using the CLI tool ends with a wait for completion of the download this fails. The UART report a panic. Any idea how to look further. is this a problems with TF-A device tree or could it be from uboot or optee as the binaries in and output pf those build depend on each other ? Any way to reduce or isolate where it it going wrong to reduce the effort for looking around and trial and errors ? Could it just  be .dtb file TF-A generated  ?

This board ran fine with a previous ECO system.

CubeProgrammer:

File download complete
Time elapsed during download operation: 00:00:03.039

RUNNING Program ...
Address: : 0x1
DFU status = 0
DFU State = 5
bwPollTimeout = 1
sending a dfu end of download request
DFU status = 0
DFU State = 7
bwPollTimeout = 1
libusb get status error [-7] : LIBUSB_ERROR_TIMEOUT
libusb get status error [-7] : LIBUSB_ERROR_TIMEOUT
libusb control transfer error [-7] : LIBUSB_ERROR_TIMEOUT
Reconnecting...
Error:
Unable to reconnect the target device: time out expired
Error: Start operation failed

UARTS:

PANIC at PC : 0x2fff1a71

Exception mode=0x00000016 at: 0x2fff1a71

[debugging]

After changing the build method without using makefile.sdk :

unset LDFLAGS;
unset CFLAGS;

make ARM_ARCH_MAJOR=7 ARCH=aarch32 PLAT=stm32mp1 STM32MP_SDMMC=1 STM32MP15=1 DTB_FILE_NAME=stm32mp157a-board-mx.dtb DEBUG=1 all

it generated build/stm32mp1/release/tf-a-stm32mp157a-board-mx.stm32 file.

The panic went ways but now there is a message

NOTICE: CPU: STM32MP157AAA Rev.B
NOTICE: Model: STMicroelectronics custom STM32CubeMX board - openstlinux-6.1-yocto-mickledore-mp1-v23.06.21

And from there it stops. The same result as when using this file in the first partition on an SD card when booting from the SD card socket. Where is this stuck ? How to get more debug information to understand the cause ?

[debugging · Accepted solution]

Reason and solution are here. The workshop information for TF-A DT caused this problem

https://community.st.com/t5/stm32-mpus-other-tools/stm32mp15-eco-5-0-0-tf-a-device-tree-build-fails-for-discrete/td-p/587185#M160