• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 343 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.

AM2634: Debug sbl_qspi: error occurred after loading symbols

Wenkai
Prodigy 180 points
Part Number: AM2634
Other Parts Discussed in Thread: UNIFLASH

Hello,

I was trying to debug sbl_qspi example code and following the instruction from the link: How to debug sbl_qspi 

However after I loaded the symbols, I got following errors:

Cortex_R5_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x7000ebf4: (Error -1066 @ 0x7000EBF4) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.9.0.00040) 
Cortex_R5_0: Breakpoint Manager: Retrying with a AET breakpoint

What would cause such errors?  Please help! 

Thanks,

Wenkai

  • 0
    Prodigy 180 points

    Updates the issue:

    If I also flashed application image, previous errors went away, but after symbols were loaded the debugger still showed message: "No source available for _vector_sbl() at ....." Please refer to below captured image

    Also the SDK version I used is: mcu_plus_sdk_am263x_08_04_00_17

    CCS version is: ccs1210

  • 0 in reply to Wenkai
    TI__Mastermind 29778 points

    HI Wenkai,

    I'm looking into this and will get back with you shortly.

    Regards,
    Frank

  • 0 in reply to Wenkai
    TI__Mastermind 29778 points

    Hi Wenkai,

    Our expert on this topic is currently out of office. Please expect a delayed response.

    Regards,
    Frank

  • 0 in reply to Wenkai
    TI__Mastermind 26145 points

    Hi Wenkai,

    Ideally you should not have flashed the program. You might be overwriting the data. You just need symbols for debugging purpose.

    Questions -

    1. Is your device in QSPI boot mode ?

    2. SBL_QSPI is already flashed on the device via SBL_UNIFLASH examples ?

    3. Are you seeing any prints with the OOB example ? (ofcourse don't add loop_forever)

    This is to make sure SBL_QSPI is working on the device. Also, if QSPI fails, you will see "C" prints on the screen by ROM to recover the device by putting it in UART boot mode.

    Let me know if you have any observations as such.

    Best Regards,
    Aakash

  • +1 in reply to Aakash Kedia
    Prodigy 180 points

    Hi Aakash,

    Ah, I set the device at NOBOOT mode like regular debugging and that caused the issue. After using QSPI mode, it worked!

    Thanks for your help!

    Wenkai