• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 121 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.

AM2732: Unable to write using XDS200

K.Z
Expert 2490 points
Part Number: AM2732
Other Parts Discussed in Thread: TMDS273EVM,

Tool/software:

Hi All,

I tried connecting and writing using XDS200, but I couldn't connect properly.
Please tell me the settings necessary to connect and write correctly.

The EVM's AM273x is Revision A, but I think it is currently Revision C.

Is it necessary to support secure areas?
1. Import the initial connection verification environment (hello_world_am273x-evm_r5fss0-0_nortos_ti-arm-clang)

2. Click evmAM273x.ccxml, change Connection to XDS2xx USB Debug Probe from the Basic tab.
Change Board on Device from evmAM273x to AM273x.
When you perform Test Connection, the following OK message is displayed.
The JTAG IR Integrity scan-test has succeeded.
　　　The JTAG DR Integrity scan-test has succeeded.
3. Set the SOP to NOBOOT MODE and perform Debug. The following error will be displayed.

Cortex_R5_0: AM273x
Cortex_R5_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x40: (Error -1065 @ 0x0) 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 12.7.0.00130) 
Cortex_R5_0: File Loader: Verification failed: Target failed to write 0x00000000
Cortex_R5_0: GEL: File: C:\work\Rader\mid_radar_mainboard_test\ipc_notify_echo_am273x-evm_r5fss0-0_freertos_ti-arm-clang\Debug\ipc_notify_echo_am273x-evm_r5fss0-0_freertos_ti-arm-clang.out: Load failed.

4. Even when SOP is set to QSPI Boot, “C” is not sent to the serial port used by XDS200. Python for QPSI writing cannot be used.

5. When the SOP is set to MODE6 (SOP0=0, SOP1=1, SOP2=1) and debugging is performed, execution is not possible, but the error message changes as follows.
*This mode is only available for Secure-compatible chips.

Cortex_R5_0: AM273x
Cortex_R5_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x10281588: (Error -1066 @ 0x10281588) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 12.7.0.00130) 
Cortex_R5_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_R5_0: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x10280100: (Error -1066 @ 0x10280100) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 12.7.0.00130) 
Cortex_R5_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_R5_1: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00130)

Could you please advise on a solution based on this information?

Best Regards,

Ito

  • 0
    TI__Mastermind 22685 points

    Hi Ito,

    A couple of questions:

    1. Which AM273 EVM are you using?  The older TMDS273GPEVM (that is no longer sold) or the current TMDS273EVM?
    2. Which exact AM273 device is on the EVM?  I.e. what is the full OPN marked on the device (i.e. AM 2732ADRFGQZCWQ1)
    3. Are you trying to use the onboard emulator or an external XDS200 emulator?
      1. Note that the emulator on the AM273 EVM (both the older version and the newer version) are XDS110, not XDS200

    From here, we can recommend the best path forwards.

    Thanks,
    Mike

  • 0 in reply to Mike Pridgen
    Expert 2490 points

    Hi Mike,

    Thank you for your reply.

    The customer is creating a Mass-produced board, not an EVM.

    The board has an AM2732CDRFHAZCER mounted on it.
    The board is also being written to using the XDS200.

    K.Z said:
    4. Even when SOP is set to QSPI Boot, “C” is not sent to the serial port used by XDS200. Python for QPSI writing cannot be used.

    This problem has now been fixed.
    However, the current situation remains that the XDS200 and AM2732 cannot be connected when the SOP is set to mode2 (=Noboot mode) or mode6.
    Since there is a response from QSPI Boot, we are trying to see if it is possible to write using python, but have not been successful so far.

    In the EVM environment, the QSPI Flash was GD25B64, but this has been changed to MX25L51245 as it is no longer in production.
    It is highly likely that the flash settings have not been changed.
    The manual states that if you run the qspi_diag project, you will obtain a json file containing the values required for settings.
    Since it is not possible to start in Noboot mode, I am unable to try this, and am instead figuring out what settings are likely to be correct from the datasheet.

    Please tell me the settings to access the MX25L51245 from the AM2732.

    Best Regards,

    Ito

  • +1 in reply to K.Z
    TI__Mastermind 22685 points

    Ito,

    Ok, I think there are a couple things that we need to start with here.

    First, in the ccxml file, you should leave the Board or Devices as evmAM273x.  Using the board file will include a lot of the device initialization gel files that is not included in the device only selection.  If you want to use the AM273x device selection here, you need to include all the device initialization in your boot loader.

    Also, I think you have the wrong SOP line selection.  Per the AM273 datasheet:

    If you are trying to connect to the AM273 device via the XDS200, you need the device to be in SOP_MODE2 - Development Mode.  This means you need SOP2 = 0, SOP1 = 1, and SOP0 = 1.

    There may be some issues with changing the QSPI device, but lets get the XDS200 fully functional with the AM273 first, then determine what problems exist with the QSPI device.

    Thanks,
    Mike

  • 0 in reply to Mike Pridgen
    Expert 2490 points

    Hi Mike,

    This problem has been resolved

    Thank you.

    Ito

  • 0 in reply to K.Z
    TI__Mastermind 22685 points

    Hi Ito,

    Do you mind sharing what the resolution was?  Was it related to the SOP pins selecting the correct bootmode?

    Thanks,
    Mike

  • 0 in reply to Mike Pridgen
    Expert 2490 points

    Hi All,

    The solution was to change the EVM board file and change the SOP.

    Best Regards,

    Ito