• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 199 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR2E44PEVM: Error running hello_world

Gregory Sadowy
Prodigy 30 points
Part Number: AWR2E44PEVM
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

I'm just getting started with the EVM and CCS. I tried to build and debug run hello_world. I get the following errors on the debug console:

Cortex_R5_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x40: (Error -1065 @ 0x40) 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 20.0.0.3344)
Cortex_R5_0: File Loader: Verification failed: Target failed to write 0x00000000
Cortex_R5_0: GEL: File: C:\Users\gregas\AppData\Local\Temp\ti_cloud_storage\hello_world_awr2x44p-evm_r5fss0-0_nortos_ti-arm-clang.out: Load failed.

I have already power cycled and tried again. I'm not sure how to lower the TCLK (or whether it should be lowered. I am using the USB cable that cable with the kit and a good 12V supply.

  • 0
    TI__Mastermind 37575 points

    Hello Gregory,

    Can you provide me the following information:

    1) Is this happening on a single EVM or multiple EVM?
    2) Which SDK you are using?
    3) Have you flashed the SBL app image and CCS debug/application image on the EVM before trying this out?
    4) Please mention your exact process of things you are doing.

    Regards,
    Saswat Kumar

  • 0 in reply to Saswat Kumar
    Prodigy 30 points

    1) This is a single EVM but I only have one to test

    2) mmwave_mcuplus_sdk_04_07_00_01

    3) I followed the instruction in the SDK docs: file:///C:/ti/mmwave_mcuplus_sdk_04_07_00_01/mcu_plus_sdk_awr2x44p_10_00_00_07/docs/api_guide_awr2x44p/EVM_SETUP_PAGE.html#EVM_FLASH_SOC_INIT

    It told me to flash according to:

    python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/awr2x44p-evm/default_sbl_null.cfg

    This installs the following images:

    # First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
    --flash-writer=sbl/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

    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
    --file=sbl/sbl_qspi.release.tiimage --operation=flash --flash-offset=0x0

    # send the application image to flash. Flash it at 0xA0000 as the SBL expects it at this location
    # To connect to C66x core and load the program using CCS we should provide a valid appimage with while loop.
    --file=appimage/sbl_multicore_app_system.release.appimage_qspi --operation=flash --flash-offset=0xA0000


    But I notice in the boot directory, that there are images labeled "debug" rather than "release". Perhaps that is the problem.

    4) For hello_world in CCS, I am following: file:///C:/ti/mmwave_mcuplus_sdk_04_07_00_01/mcu_plus_sdk_awr2x44p_10_00_00_07/docs/api_guide_awr2x44p/GETTING_STARTED_BUILD.html

    But now that I see the "debug" images, I suspect that may be the issue. Can you confirm all three of the images that I should be flashing?

    Thank you for your help.

  • 0 in reply to Gregory Sadowy
    TI__Mastermind 37575 points

    Hello Gregory,

    The appimage you need to use the following image: C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\utils\ccsdebug
    pick up the right appimage for your device and flash it.

    After that I assume you are switching to functional SOP mode, connect to R5 in CCS and then load the .out file for hello world?

    Regards,
    Saswat Kumar