This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM263P4: [ERROR] Issue flashing on launchpad - QSPI controller not accessible

Part Number: AM263P4
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG, LP-AM263P

Tool/software:

Hi

I'm using mcu_plus_sdk_am263x_10_00_00_35 with CCS THEIA  Version: 1.5.1.3 on a AM263P launchpad.

I was having issues trying to flash a program in QSPI and boot from it.

First in the flashing process, I'm getting and error loading the SBL after loading the flash writer with the uart_uniflash.py script.

The flash writer loads ok but hangs when it comes to load the sbl.

Issue is similar as in this thread :

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1158291/am2634-sbl-and-uart-uniflash-of-sdk-when-built-and-flash-shows-error-error-xmodem-send-failed-no-response-or-incorrect-response-from-evm-or-cancelled-by-user

or this one:

AWR2944: [ERROR] Cortex_R5_0: XMODEM send failed, no response OR incorrect response from EVM OR cancelled by user, power cycle EVM and run this script again !!! - Sensors forum - Sensors - TI E2E support forums

From other threads I came across trying to debug the issue, I have imported the qspi_flash_diag_am263x-lp_r5fss0-0_nortos_ti-arm-clang project to check the flash on the board.

I selected the right board and checked the SysConfig setup. Rebuilt the project and tried to run. Note, the board is configured in CCS(DEV) BOOT mode to run the test.

The SW execution runs into an exception.

The exception is triggered when trying to read the content of register QSPI0.SysConfig at address 0x48200010 within the following function :

In the debugger, the QSPI0 controller is not accessible either and the contents cannot be read:

I'm a stuck with this issue and can't find anybody reporting the same problem. I also tried on 2 boards but boths are displaying the same issue.

I might have missed something here but can't figure out what.

Would greatly appreciate your support here to 1/ get the flash diag example to work to ensure the sanity of the flash on my boards, 2/ to resolve my issue flashing the memory to boot from the application which 1/ will hopefully facilitate.

Thanks

Regards

Seb