Hi there,
I am currently working on upgrading our EV charging solution from OpenSTLinux Ecosystem v4 (Linux kernel 5.15) to Ecosystem v6 (Linux kernel 6.6).
As part of the process to ensure we are on the right track, I have successfully upgraded to the minor release: OpenSTLinux release v4.1.0 (Linux 5.15-stm32mp-r2.2), and it is functioning as expected. The next step is to proceed with the upgrade to Ecosystem v6 (Linux kernel 6.6).
In preparation for this, I regenerated the DTS files using STM32CubeMX_6.13.0 and loaded the existing .ioc file. While regenerating the DTS files using STM32CubeMX_6.1.3 and loading the existing .ioc file, I selected the Migrate option when prompted by the tool. Could you please confirm if this is the correct choice, or would selecting Continue be more appropriate in this case?
Current Setup:
I am now attempting to recompile the following components with updated versions:
- TF-A: v2.8-stm32mp
- OP-TEE: 3.19.0-stm32mp
- U-Boot: v2023.10-stm32mp
Issue Encountered:
In the process, I mistakenly compiled OP-TEE with the older version of TF-A and flashed it onto the board, which resulted in the board becoming unresponsive after few initial prints on the console ("bricked"). I am concerned that a similar situation may arise even with a new board if there are mismatches or issues with any of the components (TF-A, OP-TEE, or U-Boot). I get the following on the console:
NOTICE: Early console setup
PANIC at PC : 0x2ffe8b55
Request for Assistance:
Debugging Process: Could you provide guidance on the proper mechanism to debug TF-A, OP-TEE, and U-Boot?
- I am open to turning off TF-A and focusing on bringing up the new U-Boot first, but I am unsure how to debug the board effectively in case something goes wrong during the process. Particularly if anything goes wrong in uboot I do not have a mechanism to even talk via usb (stm32prog usb 0 - that's what we use to connect to the CubeMx Programmer).
- What tools or techniques are recommended to recover and debug the board if it becomes unresponsive?
We are using Buildroot for this project. Please let me know if any additional information is needed to assist with debugging or recovery. Your guidance would be highly appreciated to ensure a smooth upgrade process and avoid bricking the board again.
I am already referring to this post: https://community.st.com/t5/stm32-mpus/faq-stm32mpus-how-to-migrate-stm32cubemx-project-from-a-previous/ta-p/49262
But doesn't talk about the debugging part mentioned above.
Many thanks for your assistance.
Best regards,
Vivek
