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.

LP-AM243: Boot error.

Part Number: LP-AM243
Other Parts Discussed in Thread: AM2434, UNIFLASH

Tool/software:

Hi Ti-experts,

I am stuck at this point, while i am try to upload the code in Am243x-lp

MAIN_Cortex_R5_0_1: AM2434_ALX
MAIN_Cortex_R5_0_1: GEL Output: CPU reset (soft reset) has been issued through GEL.
MAIN_Cortex_R5_0_1: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x140: (Error -1065 @ 0x140) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.8.0.00189)
MAIN_Cortex_R5_0_1: File Loader: Verification failed: Target failed to write 0x00000000
MAIN_Cortex_R5_0_1: GEL: File: D:\27-09-2024-2\hello_world_am243x-lp_m4fss0-0_freertos_ti-arm-clang\Debug\hello_world_am243x-lp_m4fss0-0_freertos_ti-arm-clang.out: Load failed.


I tried with 2 diff. Power supply which have 5v 3A.


My debug point,
1) Green light working:- Means power done
2) xds110 uart port shows in device manager 
3) Targe set :-AM243x_LAUNCHPAD in target configuration

4) I tried with pin set 11100000(UART mode),USB-dfu 01010000  and 01000100(QSPI mode). All cases got same error.
(pin set 12345678).
 

Considered Ref. URL :-
1)https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EVM_SETUP_PAGE.html#EVM_CABLES
2)https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EXAMPLES_DRIVERS_SBL_DFU_UNIFLASH.html
3) https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EXAMPLES_USB_DFU.html
4)https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EVM_SETUP_PAGE.html#CCS_UART_TERMINAL
5)https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/EVM_SETUP_PAGE.html#EVM_FLASH_SOC_INIT
6)https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/TOOLS_FLASH.html#TOOLS_FLASH_ERROR_MESSAGES


Thanks in Advance.

  • Hi, I am assuming you are using CCS. Did you try DEV BOOT MODE (11110000)? If so same issue?

    If DEV BOOT MODE works then you can follow steps to load DMSC FW and initialize the SOC (loadJSFile "C:/ti/mcu_plus_sdk_{soc}_{sdk version}/tools/ccs_load/am243x/load_dmsc_hsfs.js"

    Or, you can follow AM243x MCU+ SDK: EVM Setup (ti.com) to flash SBL NULL, and after successfully flashing it, boot from QSPI and load your application *.out from CCS without running load_dmsc_hsfs.js

    thank you,

    Paula

  • Hi,

    Can you please tell which core are you connected to?

    I assume that you have connected to R5F core and trying to load the M4F *.out binary on it.

    Please connect to the correct core and try to load the example binary.

    Regards,

    Tushar

  • Hi Tushar,

    Thanks for your response. 

    Good Morning

    I also getting error while  running the bellow command (Pin 11100000)

    "python uart_uniflash.py -p COM6 --cfg=sbl_prebuilt/am243x-lp/default_sbl_null.cfg:"



    (I forgot to mention in 1st msg)

    I assume that you have connected to R5F core and trying to load the M4F *.out binary on it.




    Regards,
    D J

  • Hi D J,

    I also getting error while  running the bellow command (Pin 11100000)

    Can you please confirm which device type are you using? Is it a GP or HSFS?

    Please refer faq-am6xx-how-to-check-if-device-type-is-hs-se-hs-fs-or-gp for details.

    Please connect to the M4F core and then try to load the program.

    Regards,

    Tushar

  • Hi Tushar,
    Please check below screenshot

  • Hi D J,

    From the above screenshot, I can see that you are using a GP device. The support for GP device had been revoked from the MCU+SDK v09.00 release. 

    You can use the MCU+SDK v08.06.00.45 which has support for GP devices.

    Please visit https://www.ti.com/tool/download/MCU-PLUS-SDK-AM243X/08.06.00.45 

    Regards,

    Tushar

  • Hi Tushar,

    Thanks for the quick response, 

    I think this the sdk issue And I resolved the previous error.

    But I am stuck at load js file 
    I added the environment variable and passing the am243x 8.xx.xx .js file but considering  the previous one


    Thanks & regards,
    D J

  • Hi D J,

    I added the environment variable and passing the am243x 8.xx.xx .js file but considering  the previous on

    Which boot mode are you using?

    Also I can see that you are trying to run the load_dmsc_hsfs.js file. This file will not work as this is meant to be run for HSFS device. 

    You are currently using GP device, please try to run the load_dmsc.js file.

    Regards,

    Tushar

  • Hi Tushar,

    Still same error



    path not found error

    pin set 01000100

  • Hi D J,

    The above script is failing because it is not able to find the files used inside the script. The path you are setting above for the variable MCU_PLUS_SDK_AM243X_PATH is incorrect.

    You should only provide path till root directory of MCU+SDK.

    The correct path should be C:\ti\mcu_plus_sdk_am243x_08_06_00_45.

    Regards,

    Tushar

  • Hi Tushar, 


    1) when i build 1st I got error like this. if i rebuild same code error was solved. what is the issue.

    Generating certificate for D:/08-10-2024/gpio_led_blink_am243x-lp_r5fss0-0_nortos_ti-arm-clang/Debug/gpio_led_blink_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage ...
    makefile_ccs_bootimage_gen:75: recipe for target 'all' failed
    'openssl' is not recognized as an internal or external command,
    operable program or batch file.
    Traceback (most recent call last):
    File "C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot\signing\appimage_x509_cert_gen.py", line 244, in <module>
    cert_str = get_cert(args)
    ^^^^^^^^^^^^^^
    File "C:\ti\mcu_plus_sdk_am243x_08_06_00_45\tools\boot\signing\appimage_x509_cert_gen.py", line 179, in get_cert
    sha_val = subprocess.check_output('openssl dgst -{} -hex {}'.format(g_sha_to_use, bin_file), shell=True).decode()
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "C:\Python312\Lib\subprocess.py", line 466, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "C:\Python312\Lib\subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
    subprocess.CalledProcessError: Command 'openssl dgst -sha512 -hex D:/08-10-2024/gpio_led_blink_am243x-lp_r5fss0-0_nortos_ti-arm-clang/Debug/gpio_led_blink_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage' returned non-zero exit status 1.
    gmake[3]: *** [all] Error 1


    2) Hello-word example is running perfectly. but in case i restart mcu then, mcu not printing the hello world in serial port. for this case which parameter require to change?

    3) I saw the 2 type of example in this board  r5fss0-0_nortos and m4fss0-0_nortos. What is the diff. between r5 and m4 ?

    Thanks.. 

  • Hi D J,

    when i build 1st I got error like this. if i rebuild same code error was solved. what is the issue.

    You are getting this issue because you might not have installed openssl on your system.

    Hello-word example is running perfectly. but in case i restart mcu then, mcu not printing the hello world in serial port. for this case which parameter require to change?

    What do you mean by restarting the MCU? How are you restarting the MCU?

    I saw the 2 type of example in this board  r5fss0-0_nortos and m4fss0-0_nortos. What is the diff. between r5 and m4 ?

    Yes, We have R5F and M4F core present on the SoC. The two examples you are referring above tells which core the application is supposed to be built for.

    Regards,

    Tushar

  • Hi Tushar,

    Power restart or press mcu-pro button.

    What do you mean by restarting the MCU? How are you restarting the MCU?




    What is the meaning of this error?


    MAIN_Cortex_R5_0_0: AM2434_ALX
    MAIN_Cortex_R5_0_1: AM2434_ALX
    MAIN_Cortex_R5_0_1: GEL Output: CPU reset (soft reset) has been issued through GEL.
    MAIN_Cortex_R5_1_0: AM2434_ALX
    MAIN_Cortex_R5_1_0: GEL Output: CPU reset (soft reset) has been issued through GEL.
    MAIN_Cortex_R5_1_1: AM2434_ALX
    MAIN_Cortex_R5_1_1: GEL Output: CPU reset (soft reset) has been issued through GEL.
    DMSC_Cortex_M3_0: GEL Output: This GEL is currently only supported for use from the Cortex-M3 inside the DMSC.
    DMSC_Cortex_M3_0: GEL Output: Do not run this GEL from any other CPU on the SoC.
    DMSC_Cortex_M3_0: GEL Output: This script sets the first address translation region to [0x8000_0000, 0x0000_0000].
    DMSC_Cortex_M3_0: GEL Output: It also sets the second address translation region to [0x6000_0000, 0x4000_0000].
    DMSC_Cortex_M3_0: GEL Output: This is consistent with the SoC DV assumptions.
    DMSC_Cortex_M3_0: GEL Output: Configuring ATCM for the R5Fs
    DMSC_Cortex_M3_0: GEL Output: ATCM Configured.
    DMSC_Cortex_M3_0: GEL Output: R5F Halt bits set.
    DMSC_Cortex_M3_0: GEL Output: Configuring bootvectors
    DMSC_Cortex_M3_0: GEL Output: Bootvectors configured.
    DMSC_Cortex_M3_0: GEL Output: Programming all PLLs.
    DMSC_Cortex_M3_0: GEL Output: Programming Main PLL 0 (Main PLL)
    DMSC_Cortex_M3_0: GEL Output: Main PLL 0 (Main PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: Programming Main PLL 1 (Peripheral 0 PLL)
    DMSC_Cortex_M3_0: GEL Output: Main PLL 1 (Peripheral 0 PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: Programming Main PLL 2 (Peripheral 1 PLL)
    DMSC_Cortex_M3_0: GEL Output: Main PLL 2 (Peripheral 1 PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: Programming Main PLL 8 (ARM0 PLL)
    DMSC_Cortex_M3_0: GEL Output: Main PLL 8 (ARM0 PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: Programming Main PLL 12 (DDR PLL)
    DMSC_Cortex_M3_0: GEL Output: Main PLL 12 (DDR PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: Programming Main PLL 14 (Main Domain Pulsar) PLL)
    DMSC_Cortex_M3_0: GEL Output: Main PLL 14 (Main Domain Pulsar PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: Programming MCU PLL 0 (MCU PLL)
    DMSC_Cortex_M3_0: GEL Output: MCU PLL 0 (MCU PLL) Set.
    DMSC_Cortex_M3_0: GEL Output: All PLLs programmed.
    DMSC_Cortex_M3_0: GEL Output: Powering up all PSC power domains in progress...
    DMSC_Cortex_M3_0: GEL Output: Powering up MAIN domain peripherals...
    DMSC_Cortex_M3_0: GEL Output: Powering up GP_CORE_CTL.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_DMSC
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_MAIN_TEST
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_MAIN_PBIST
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_EMMC_4B
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_EMMC_8B
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_USB
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_ADC
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_DEBUGSS
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_GPMC
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_EMIF_CFG
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_EMIF_DATA
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_MCAN_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_MCAN_1
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_SA2UL
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_SERDES_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PCIE_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up GP_CORE_CTL done.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_PULSAR_0.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PULSAR_0_R5_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PULSAR_0_R5_1
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PULSAR_PBIST_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_PULSAR_0 done.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_PULSAR_1.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PULSAR_1_R5_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PULSAR_1_R5_1
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_PULSAR_PBIST_1
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_PULSAR_1 done.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_ICSSG_0.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_ICSSG_0
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_ICSSG_0 done.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_ICSSG_1.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_ICSSG_1
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_ICSSG_1 done.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_CPSW.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_CPSW3G
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_CPSW done.
    DMSC_Cortex_M3_0: GEL Output: Powering up all MAIN domain peripherals done.
    DMSC_Cortex_M3_0: GEL Output: Powering up MCU Domain peripherals.
    DMSC_Cortex_M3_0: GEL Output: Powering up GP_CORE_CTL_MCU.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_TEST
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_MAIN2MCU
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_MCU2MAIN
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up GP_CORE_CTL_MCU done.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_M4F.
    DMSC_Cortex_M3_0: GEL Output: Powering up LPSC_M4F
    DMSC_Cortex_M3_0: GEL Output: No change needed.
    DMSC_Cortex_M3_0: GEL Output: Powering up PD_M4F done.
    DMSC_Cortex_M3_0: GEL Output: Powering up MCU Domain peripherals done.
    DMSC_Cortex_M3_0: GEL Output: Powering up all PSC power domains done!
    DMSC_Cortex_M3_0: GEL Output:
    DMSC_Cortex_M3_0: File Loader: Verification failed: Values at address 0x00000000 do not match Please verify target memory and memory map.
    DMSC_Cortex_M3_0: GEL: File: D:\08-10-2024\hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang\Debug\hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang.out: a data verification error occurred, file load failed.

  • Hi D J, 

    Are you trying to load the binary on M3 core?

    This is not allowed. If you are building application for M4F core then please connect to M4F core and load the application on it.

    Don't connect to M3 core.

    Regards,

    Tushar

  • Hi Tushar,

    Good Morning.


    What is the meaning of this error?

    this error solved. I tried the 1st load AM2434_ALX.ccxml 2nd load the main_example. out file. using this step error solved.



    Power restart or press mcu-pro button.

    What do you mean by restarting the MCU? How are you restarting the MCU?

    How to run application while power on? currently every time rebuild and reload example in mcu.

    Thank you.

  • Hello D J,

    How to run application while power on?

    For this, you will need to flash the application binary to the EVM. Please refer FLASH_APPLICATION for details.

    Regards,

    Tushar

  • Hi Tushar,

    Thanks for your support and guidance.

    It's very helpful for me to solve this error.

    You can close this thread.

    Thanks & Regards,
    D J