• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 104 subscribers
  • Views 603 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Failed to run examples on ARM core of 66AK2E

Xiuwen Cai
Prodigy 10 points
Other Parts Discussed in Thread: 66AK2E05, SYSBIOS

Hi,

I am using CCS 6.1 to run some examples on XEVMK2EX board.

The example is from TI Resource Explorer. The path is SYSBIOS/Unclassified Devices/66AK2E05/C66XX [C6000]/TI Target Examples/Minimal. I set the boot mode switches to '1111', and the project runs OK.

But the example for the ARM core failed to run.

The error message is:

arm_A15_0: Trouble Reading Memory Block at 0x80000000 on Page 0 of Length 0x4: (Error -1205 @ 0x80000000) Device memory bus has an error and may be hung. 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 5.1.641.0)


The example is SYSBIOS/Unclassified Devices/66AK2E05/Cortex A [ARM]/GNU Target Examples/Minimal.

Then I tried set the boot mode switches to '0010', and pressed key to stop autoboot in the U-Boot. After that, I started debugging the Minimal project. It is able to connect the ARM core, but the CPU didn't stop at main function.

I opened the targetConfigs/66AK2E05.ccxml, and I noticed that there is a .gel file for C66xx_0 core, but there is no .gel file for the ARM core.

My question is: do I need a .gel file for the ARM core? If so, is there any example file?

I am using Windows 7 64-bit, Service Pack 1.

CCS version: 6.1.0.00104

XEVMK2EX board version: v1.0.2.2 and I am using the onboard debug probe.

Thanks,

Xiuwen Cai

  • 0
    TI__Guru* 81335 points

    Hi Xiuwen,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com). Please read all the links below my signature.

    My question is: do I need a .gel file for the ARM core? If so, is there any example file?

    No. We do not have gel file ARM. Its only for DSP.

    What is the MCSDK version used for testing? What example are trying to run on ARM cores? Could you please provide name and path to it?

    Option 1:

    Keystone II ARM bootloader examples are now available for download. Please refer below,

    Source code published to external git: 

    Documentation: 

    Software Features

    • Boot Utilities to create and format boot images
    • Examples that demonstrate booting K2H and K2E devices from SPI, I2C, UART, Ethernet and NAND. Examples also demonstrate the following features of the BootROM
      • Single and Multi-Stage booting.
      • Using Boot Parameter tables to speed up booting from a boot media.
      • Using Boot Configuration tables to initialize DDR.
    • Examples to demonstrate formatting uboot for above mentioned boot modes.

    Option 2:

    By default ARM core 0 is enabled. After u-boot prompt up, power up the other core using "mon_power" command and then connect it to CCS. Please refer the boot monitor source from MCSDK explore wiki page for more information.

    For example, ( for ARM core 3 )

    #tftpboot 0x0c5f0000 skern-keystone-evm.bin

#mon_install 0x0c5f0000

#mon_power 3 1

    Thank you.

  • 0
    TI__Mastermind 43955 points
    Hi Xiuwen Cai,


    The example is from TI Resource Explorer. The path is SYSBIOS/Unclassified Devices/66AK2E05/C66XX [C6000]/TI Target Examples/Minimal. I set the boot mode switches to '1111', and the project runs OK.

    But the example for the ARM core failed to run.

    The error message is:

    arm_A15_0: Trouble Reading Memory Block at 0x80000000 on Page 0 of Length 0x4: (Error -1205 @ 0x80000000) Device memory bus has an error and may be hung. 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 5.1.641.0)


    I suspect that memory conflict could happen between u-boot memory and example app memory.
    Check the app *.map file that whether memory conflict appears or not with u-boot(ARM Linux).


    Regards,
    Shankari.
  • 0
    TI__Guru** 116100 points
    Hi,
    Would you please help us to reproduce your problem.
    Provide the step by step procedure.