• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 1463 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/TMS320F28379S: Question about Boot Mode selection while debugging via XDS100V3 Emulator

Mengchao Yang
Prodigy 70 points
Part Number: TMS320F28379S
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

HI,

I have a control board based on a TMS320F28379S. which Boot Mode select module like this:

As this SchDoc title describes, this boot mode select modue hardware design based on the LAUNCHPAD_F28379D Board.

When I start to debug an example program, the S1's status is: TRST to 1, GPIO72 to 1, GPIO84 to 1. After i launch the Target Configurations file, and click the "Connect The Target" button，then errors come out ：

C28xx_CPU1: Trouble Writing Memory Block at 0x5f452 on Page 1 of Length 0x1: (Error -1041 @ 0x5F453) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.903.2) 
C28xx_CPU1: GEL: Error while executing OnTargetConnect(): Target failed to write 0x0005F452@Data
	 at *((int *) 0x5F452)=0xFFFF [f28379s.gel:79]
	 at OnTargetConnect()
C28xx_CPU1: Trouble Reading Register ST1: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.903.2) 
C28xx_CPU1: Trouble Reading Register ST1: (Error -1156 @ 0x6) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 8.0.903.2) 
C28xx_CPU1: Trouble Reading Register ST1: (Error -1156 @ 0x6) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 8.0.903.2) 
C28xx_CPU1: Trouble Reading Register ST1: (Error -1156 @ 0x6) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 8.0.903.2) 
C28xx_CPU1: Error occurred during flash operation: Earlier errors prevented reading 0x0005F800@Data
C28xx_CPU1: 2 other operation(s) were automatically canceled as a result 
C28xx_CPU1: Trouble Reading Register ST1: (Error -1156 @ 0x6) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 8.0.903.2) 
C28xx_CPU1: Error occurred during flash operation: Earlier errors prevented reading 0x70268@Program
C28xx_CPU1: 2 other operation(s) were automatically canceled as a result 
C28xx_CPU1: Error: (Error -1135 @ 0x806E) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.903.2) 
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: Error occurred during flash operation: Could not write 0x5FB00@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.

But when I set S1's status to:TRST to 1, GPIO72 to 0, GPIO84 to 1,or TRST to 1, GPIO72 to 1, GPIO84 to 0. The debugging process is all good. (Both run at RAM and Flash.)

 

Question:

1) Is there a specific Boot Mode when debugging via an emulator? 

2) If 1) is Yes, then, Why the S1 all to 1(TRST to 1, GPIO72 to 1, GPIO84 to 1) works good at the LaunchPad?

  • 0
    Prodigy 70 points
    And when S1's status to:TRST to 1, GPIO72 to 0, GPIO84 to 0, errors also come out , which is the same with status 1,1,1.
  • 0 in reply to Mengchao Yang
    TI__Guru** 113565 points

    Hi,

    Can you check the status of XRSn pin on your board. Look like device is going through reset cycle when you are getting the error. On fresh device, it's not recommended to use 1/1 on both BOOTMODE pins because in that case device will BOOT to flash and since it's ALL_1, it'll ITRAP and issue WD reset.

    Value 0/0 is for parallel boot and if on your board you don't have parallel boot setup then that should also work. Best option is to use 1/0 value on BOOTMODE pins (GPIO72/GPIO84) which is wait boot.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Prodigy 70 points

    Hi, Vivek

    I checked the  XRSn pin via oscilloscope, it hold "1" all the time when I click the "Connect Target" button.(S1:1/1/1, errors still)

     

    I have flashed the program to flash, device  BOOT to flash is ok.

    Every time when I  donwload a new program or debug a program, I have to power off the device  first and switch S1 to 1/1/0(Wait) or  1/0/1(SCI) .

    But on the LaunchPad F28379D board, why S1 status 1/1/1(Get) works OK both at running a program and debugging ?

    In order to keep S1 status 1/1/1 all the time. Is there any register that I have missed to configure?

     

    Regards,

    Mengchao Yang

  • 0 in reply to Mengchao Yang
    TI__Guru** 113565 points
    Hi Yang,

    On both the boards, are you downloading same program ? In your application, are you putting CPU in low power mode by executing "IDLE" instruction? Can you try loading a simple example from C2000Ware on your custom board and see if you still face same issue.

    Regards,

    Vivek Singh
  • 0 in reply to Vivek Singh
    TI__Guru** 113565 points
    Hi Yang,

    Any further debug info on this one?

    Vivek Singh