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.

[FAQ] AM2634-Q1: How to debug applications without GEL Script and using SBL NULL

Part Number: AM2634-Q1
Other Parts Discussed in Thread: UNIFLASH

Hi expert, 

Can you explain the procedure to debug applications using SBL NULL

  • Hi, 

    There are three steps here mainly

    Step 1: Prepare and Flash the SBL NULL

    Step 2: Prepare Target Configuration

    Step 3: Load the application

    Step 1:

    - Locate the prebuilt image: Navigate to the MCU+ SDK directory and retrieve the sbl_null binary file (sbl_null.release.tiimage) from your specific local path: /mcu_plus_sdk_am263x_26_01_00_08/tools/boot/sbl_prebuilt/am263x-lp/

    - Flash the binary: Write the image to the device flash memory using your preferred tool, such as UniFlash, UART Uniflash, or SBL JTAG Uniflash.

    - Configure boot pins: Switch the hardware boot mode pins on the device to OSPI/QSPI boot mode.

    - Power cycle and verify: Perform a Power-On Reset (POR) on the device, open your terminal emulator, and verify the initialization by checking the UART logs.

    Step 2

    - Open CCS and go to Debug Menu

    - Click on the + icon in Target Configuration tab

    - Provide it a suitable name

    - Select the device name

    - Remove Initialization Script from each core. Select the contents in Initialization Script tab and hit backspace

    - Make sure this is done for all cores from Cortex R5_0 to Cortex R5_3. Select each cores from the Debuggable CPU drop down and repeat the above step.

    Step 3

    - Now launch the newly created target configuration by right clicking on the ccxml file > Start Project less Debug

    - Now connect to core and load the program, for example connect to core 0 and core 2 and load the corresponding out files.

    Now debugging will be possible.

    Thanks & Regards,

    Aswin