MCU-PLUS-SDK-AM263PX: AM263Px – How to make flash-based program bootable

Hi Thank you for your query, Please allow me to get back here by tomorrow.

yes sure

Thank you for your reply.

I've completed the previous step. The code now builds successfully, and I am able to flash it. However, after flashing, the board appears to revert to QSPI boot mode, but in the logs, I see the same output as when it's in UART boot mode, as shown in the attached screenshot.

#-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVM
# - The application image points to relative path of the ipc echo application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify if you just want to verify the flash contents and not flash the file.
#

# First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
--flash-writer=sbl_prebuilt/am263px-lp/sbl_uart_uniflash.release.tiimage

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# Program the OSPI PHY tuning attack vector
--operation=flash-phy-tuning-data

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
--file=sbl_prebuilt/am263px-lp/sbl_ospi_fastboot.release.tiimage --operation=flash --flash-offset=0x0

# When sending application image, make sure to flash at offset 0x80000 (default) or to whatever offset your bootloader is configured for
--file=../../../../Users/a.salem/workspace_v12/project/Debug/project.appimage --operation=flash --flash-offset=0x80000

# send the XIP image for this application, no need to specify flash offset since flash offset is specified within the image itself
--file=../../../../Users/a.salem/workspace_v12/project/Debug/project.appimage_xip --operation=flash-xip

Do I need to modify something in the flash configuration file (which I've shared)? Also, could you advise on how to debug the code?

Thanks

Tested. I have same problem

What is boot switch configuration?Is it OSPI or QSPI?

I tested it on my end with MCU PLUS SDK 10.2 it works fine.

OSPI BOOT MODE 

BOOTMODE [ 1 : 4 ] = 0011

Well, I am not able to understand why it is not working for you?

Can you tell me which revision of board you are uaing E1/E2 or RevA? You can attach a picture of the board, I can figure out from that.

Yes Sure. 
This is the board 


And this is the memory allocations

Do you power reset the board after flashing?

yes

Thanks for your support issue resolved