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

Original question:

MSPM0G1507: About "TGTSUPPLYOUT" of XDS110

UNIFLASH: "Remove power at final disconnect" in UNIFLASH does not work

O.H
Mastermind 6330 points
Part Number: UNIFLASH
Other Parts Discussed in Thread: LP-MSPM0G3507

Tool/software:

Hi expert,

Continuing from the original thread.

Q1: When using "Remove power at final disconnect" in UNIFLASH, it doesn't seem to be applied at the first connection (power supply is maintained).
Could you tell me a workaround?

I have confirmed the operation with CCS v12.x and v20.x, and used a .ccxml file created with CCS and LP-MSPM0G3507, but the operation is unstable.
- Start a new session with Uniflash and flash as is. Power continues to be supplied after flashing.
- After flashing, physically disconnect the USB cable. If I reconnect it as is, power supply will stop after flashing.
- Start a new session with Uniflash, start and finish a Debug session from CCS. If I return to Uniflash and flash, power supply will stop after flashing.
- If power supply is stopped after flashing and another session is started with Uniflash, the problem returns.

I have tried restarting the PC, replacing the XDS110, and replacing the USB cable, but no change has been made.
The objective is to safely stop the power. If physically disconnecting the USB cable does not change anything, that's fine.

Best regards,
O.H

  • 0
    TI__Guru**** 463961 points

    Hello,

    In the other thread:

    In my environment, with CCSv20, the power is cut off as soon as Debug mode ends.
    With Uniflash v9.2, the flashed program starts after "Program Load" and power continues to be supplied.

    I assume you wish to have UniFlash have the same behavior of CCS. 

    For CCS, you mention "Debug mode ends". What exactly is meant by this? Is this when the CCS debug session is terminated? 

    For UniFlash, are you expecting power to stop being supplied when UniFlash is closed or is it when the flashing is complete (but GUI is still running)? 

    Thank you

    ki

  • 0 in reply to Ki
    Mastermind 6330 points

    Hello ki,

    Thank you for your reply.

    Ki said:
    For CCS, you mention "Debug mode ends". What exactly is meant by this? Is this when the CCS debug session is terminated? 

    Pressing the "STOP" button in the image below is called "end of debugging".

    Ki said:
    when the flashing is complete (but GUI is still running)

    This is after flashing is complete.

    Q2: If the USB cable is disconnected after writing from UNIFLASH and then reconnected, is there a possibility that some kind of damage will be caused to the board by noise from the XDS110 when the USB cable is disconnected/connected?
    If there is no problem, I would like to deal with it using the above method.

    Best regards,
    O.H

  • 0 in reply to O.H
    TI__Guru**** 463961 points
    O.H said:
    Pressing the "STOP" button in the image below is called "end of debugging".

    Yes, this would be complete termination of the debugger.

    O.H said:
    This is after flashing is complete.

    I believe the debugger is still running under the hood hence why the behavior is different than terminating a CCS debug session. If you close the UniFlash GUI after flash, then do you see that power stops being supplied?

    O.H said:
    Q2: If the USB cable is disconnected after writing from UNIFLASH and then reconnected, is there a possibility that some kind of damage will be caused to the board by noise from the XDS110 when the USB cable is disconnected/connected?

    There should not be any problem. Not that by default, UniFlash will disconnect from the target CPU after any target action. So If you flash the target and then physically disconnect the USB cable and then connect it back, there should be no impact to the target. Of course it is not recommend to detach the cable DURING any target action like program load or memory access.

  • 0 in reply to Ki
    Mastermind 6330 points

    Hi Ki,

    Thank you for your reply.

    Ki said:
    I believe the debugger is still running under the hood hence why the behavior is different than terminating a CCS debug session. If you close the UniFlash GUI after flash, then do you see that power stops being supplied?

    As you point out, closing Uniflash or returning to the new session creation screen will stop the power supply.

    Ki said:
    There should not be any problem. Not that by default, UniFlash will disconnect from the target CPU after any target action. So If you flash the target and then physically disconnect the USB cable and then connect it back, there should be no impact to the target. Of course it is not recommend to detach the cable DURING any target action like program load or memory access.

    For the time being I will deal with this by unplugging and replugging the USB cable. If there are any firmware updates for XDS or Uniflash I would appreciate it if you could let me know.

    Best regards,
    O.H

  • +1 in reply to O.H
    TI__Guru**** 463961 points
    O.H said:
    As you point out, closing Uniflash or returning to the new session creation screen will stop the power supply.

    Yes, at this point the debugger for the UniFlash session would get terminated just like pressing the terminate button in CCS.

    O.H said:
    If there are any firmware updates for XDS or Uniflash I would appreciate it if you could let me know.

    The firmware version required will be dependent on the CCS/UniFlash being used. If CCS/UniFlash is not updated, then a firmware update would not be needed.

    Thank you

    ki