• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 97 subscribers
  • Views 785 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.

CCS/PROCESSOR-SDK-DRA7X: debugging MLO on DRA7xx EVM board

Devendra T
Intellectual 320 points
Part Number: PROCESSOR-SDK-DRA7X

Tool/software: Code Composer Studio

We are using DRA7XX VAYU board and CCS version 7.4. I am trying to set the hardware break point at 0x40300000 where ROM boot loader is loading the MLO from SD card. But, when we connect the CCS, processor is PC is setting to some random address and break point is not working. I, already tried the patch set mentioned in the "review.omapzoom.org/38670" and "http://review.omapzoom.org/38671"

We are stuck here and timely response will be highly appreciated.

  • 0
    TI__Mastermind 42515 points

    Hi Devendra,

    can you check if wait_for_debugger() function is enabled in board_init_f() in the "hwinit-common.c", I see it is added with "#if 0 ... #endif" in the patch.

    (I guess you already checked chapter "3.1.2 Debugging MLO" in )

    Regards,
    Yordan

  • 0 in reply to Yordan Kamenov
    Intellectual 320 points

    Hi Yordan,

    >>can you check if wait_for_debugger() function is enabled in board_init_f() in the "hwinit-common.c", I see it is added with "#if 0 ... #endif" in the patch

    Yes, function is enabled. What I am doing is:

    Let debugger connect to target. Put hardware break point either on 0x40300000 (MLO entry point) or 0x80800000 (u-boot entry point). Reset the target and I am expecting that ROM boot loader will load the MLO in OCRAM and will halt. But after connecting to A15 and after resetting the target, code seems to stop at 0x0003800c ( RBL pre-fetch ABORT exception).

  • Former Member
    0 Former Member in reply to Devendra T
    Hi,
    Is this issue resolved? Can you check if any other boot mode works fine and this is not an issue with boot-media?

    Regards,
    Somnath
  • 0 in reply to Former Member
    Intellectual 320 points

    Hi,

    This issue is not solved yet. Waiting for earliest response on the same.

    Regards,

    Devendra

  • Former Member
    0 Former Member in reply to Devendra T

    Hi,

    I am assuming you are using TI EVM. And the SD card you are booting from is known to work.

    If you have already applied the debug patch with infinite debug loop, can you let the device boot and connect via CCS to the device, without using any gel file.

    If it had boot-ed successfully, you should see it the PC is stuck in the debug loop. Can you check that and let me know what happens.

    Regards,

    Somnath

  • 0 in reply to Former Member
    Intellectual 320 points
    Hi,
    >>If you have already applied the debug patch with infinite debug loop, can you let the device boot and connect via CCS to the device, without using any gel file.

    what is the procedure to connect to board (A15-0) without using any GEL file?
  • Former Member
    0 Former Member in reply to Devendra T

    Hi,

    You can do a "Save As" of your current configuration file and name "..._debug". Then remove the .gel files from every core in that configuration file (especially A15 in your case). Follow the link  and you can locate the gel file for a particular core and save the configuration.

    Next time, disconnect the CCS target connection, power-cycle the device, let the device boot and then launch the configuration, connect to A15 core. If everything goes fine, it should be stuck at your debug loop.

    Regards,

    Somnath