• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 2995 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.

BeagleBone black with CCS 6

Daniele Montesi
Prodigy 100 points

Hi, I've a problem debugging an example project  with a beaglebone black board, using CCS 6.

This is the project I chose (TI-RTOS for Sitara-> AM33x-Cortex A8-> BeagleBone_Black-> Cortex A-> Kernel Examples-> TI Target Examples-> Generic Examples-> Hello Examples).

At the end of the debug process I read this error on the consolle:

CortxA8: GEL: Error while executing OnTargetConnect(): Target failed to read 0x44E10040 at (*((unsigned int *) (0x44E10000+0x40))>>22) [beagleboneblack.gel:362] at GetInputClockFrequency() [beagleboneblack.gel:433] at ARM_OPP100_Config() [beagleboneblack.gel:353] at AM335x_BeagleBlack_Initialization() [beagleboneblack.gel:339] at OnTargetConnect() .
CortxA8: Trouble Writing Memory Block at 0x80000000 on Page 0 of Length 0x7ff0: (Error -1065 @ 0x3D5A) 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 5.1.507.0)
CortxA8: Unable to terminate memory download: NULL buffer pointer at 0x3a9f
CortxA8: GEL: File: C:\Users\Filippo\workspace_v6_0\hello_BeagleBone_Black_CortexA\Debug\hello_BeagleBone_Black_CortexA.out: Load failed.

I connected my beaglebone to the PC through a XDS100 v3, using the JTAG connector (P2 - 20pin).

  • 0
    TI__Guru**** 171044 points

    Hi,

    The error you are seeing is not related to the project itself, but instead the GEL file is being prevented from accessing specific registers on the device. 

    This can happen due to some reasons:

    - the GEL file you are using is incompatible with the board - (this would be true if the GEL file was modified in any way, as the stock GEL file supplied with CCS works fine on BBB.

    - there is code already running on the target (Linux or any other flashed code), which may prevent access to some memory protected areas. Usually removing a SD/µSD card solves this problem.

    - the core/device is being reset or is suffering power fluctuations from an external source. This would require a deeper investigation, as the issue may stem from several sources - replacing/testing the power supply or monitoring test points on the board usually help diagnose this.

    These are the most common scenarios, but I will reply to this thread if I have any additional insights, ok?

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 100 points

    Thank you Rafael,

    Finally I solve this problem:

    I just pressed the "boot button" (S2)  before switching-on the board and kept the button pressed for 2 seconds after the board was powered!

    In this way everything work right!