I'm currently working on developing M33 for the i.mx8ULP platform. Unfortunately, the Evaluation Kit (EVK) provided by our solutions provider lacks a JTAG interface, requiring me to use the serial download mode for firmware updates.
To give you an overview of my debugging process for M33: I start by downloading the official SDK and using the MCUXpresso VSCode plugin to compile sdk20-app.bin. Following this, I rename sdk20-app.bin to m33_image.bin, as per the instructions provided by our solutions provider, and use the make SOC=iMX8ULP REV=A1 flash_singleboot_m33 command within the imx-boot tarball to package it into flash.bin. The final step involves burning this flash.bin to the M33 using UUU in serial download mode.
This workflow, however, seems highly inefficient to me. I'm curious if it's possible to streamline the debugging process by utilizing GDB within MCUXpresso for VSCode?
As someone new to 8ULP development, I'm in search of comprehensive learning materials specific to M33. Despite having reviewed various resources such as Industrial Products, the Reference Manual, and the Getting Started with MCUXpresso SDK for EVK, I still find myself uncertain about the origins of the programming and compiling techniques I'm currently employing.
For reference, I'm using SDK version SDK_2_15_000_MIMX8UD7xxx08 and the arm-gnu-toolchain-12.2.rel1-x86_64-arm-none-eabi toolchain.
