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

AM5728: CCS debug issue

Nijin P
Intellectual 1050 points
Part Number: AM5728

Hello,

We are using AM572x Rev 1.3B board in which a valid QSPI bootloader and application are flashed (this application gets launched when the board is powered on). But we are facing issues while connecting to A15 core from CCS via JTAG. Error message in CCS are as shown below:

CortexA15_0: Trouble Reading Memory Block at 0x58820000 on Page 0 of Length 0x4: (Error -1205 @ 0x58820000) Device memory bus has an error and may be hung. Verify that the memory address is in valid memory.

What is the recommended approach to debug via JTAG in this scenario?

Regards,
Nijin P

  • 0
    TI__Guru**** 393215 points
    Hi,

    This address in in IPU1 RAM space. Is IPU1 initialized?
  • 0 in reply to Biser Gatchev-XID
    TI__Intellectual 1050 points

    Hi Biser,

    We are using AM572x IDK (TMDXIDK5728) in this case . This scenario is similar to what documented for AM335x at here

    Following are our questions:

    • Is there any way to prevent the execution of QSPI bootloader/application (say, using some hardware breakpoints from CCS?)
    • As per  Known Deficiencies entry A.13, CCS JTAG connectivity will be lost once we do a system reset. Is this issue resolved in latest version of CCS?
    • How can we erase the QSPI contents if that is the only option?

    Regards,
    Nijin P

  • 0 in reply to Nijin P
    TI__Guru**** 393215 points
    You could change the SYSBOOT configuration instead of erasing the flash.
  • 0 in reply to Biser Gatchev-XID
    TI__Intellectual 1050 points
    Hi Biser,

    Changing the SYSBOOT configuration to alter the boot sequence will not work for us (SD boot->QSPI boot is the current boot order). Do you mean to say that the first or third option in my previous post won't work?

    Regards,
    Nijin
  • 0 in reply to Nijin P
    TI__Guru**** 393215 points
    I have notified the RTOS team. They will post here any suggestions they have.
  • 0
    TI__Guru** 116170 points
    Nijin,

    Can you specify which version of CCS are you using. Also is the application that you are loading consist of ARM,, IPU and DSP binary or just the ARM binary? If the bootloader is bringing up secondary cores. Can you connect to any other cores on the device ?

    If the slave cores aare not enabled. One way to prevent ARM core from booting from QSPI is to put an MLO file in an SD card. the IDK is configured to boot first from SD card so if it finds an MLO in the SD card, it will not go to QSPI boot. This way you can then connect to the ARM core and re-run the QSPI writer to reporgram or erase the QSPI flash.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    TI__Intellectual 1050 points

    Hi Rahul,

    We are using CCS 6.2.0.00050 currently. We will be migrating to CCS 7.0.0.00043 soon. The application I am trying to load consists of ARM binary only.

    The suggestion to insert an SD card to AM572x 1.B board is good. It resolves the mentioned issue (CCS throws errors while connecting to A15 core) temporarily. Also I observed that we need to use an SD card which does not have a valid SD card bootloader (MLO) file. I was getting the same error when the SD card contained a valid MLO(there was no 'app' in the SD card). Can you please confirm whether this is the recommended solution to handle this scenario or just a workaround?

    Rahul Prabhu said:
    re-run the QSPI writer to reporgram or erase the QSPI flash

    I couldn't find the option to erase the QSPI flash using the 'qspi_flash_writer.out' available at {PDK_INSTALL_PATH}\ti\boot\sbl\tools\flashWriter\qspi\bin\idkAM572x

    How can we erase the QSPI bootloader and QSPI application explicitly using qspi_flash_writer.out?

    Best Regards,
    Nijin P