• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 178 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.

F29H850TU: Uniflash mistakenly CPU3.out in CPU1

Lawrence Wang
Prodigy 740 points
Part Number: F29H850TU
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi experts,

When my customer was using Uniflash, he mistakenly selected the CPU1 option to flash the .out file of CPU3. After the flash was completed, a warning was reported saying that CPU1 might be in a persistent fault state. I hope experts can help confirm this phenomenon and the cause of this warning.

  • 0
    TI__Genius 14780 points

    Hi Lawrence,

    I've also loaded the Flash config for CPU3.out and only see the "Program load completed successfully" message. Was the example modified in some way?

    Does the warning persist after reconnecting to the device?

    Thanks and regards,

    Charles

  • 0 in reply to Charles Roberson
    TI__Prodigy 740 points

    I  think that there are different configuration on ‘Run action’, if you tick this option, you may find this warning. So question is that, how about this option, what's influence.

  • +1 in reply to Lawrence Wang
    TI__Genius 14780 points

    When we are telling CPU1 to use the 'Run Action', after the load operation completes, it will run CPU1 target from CPU1 flash memory, so it makes sense that the warning is arriving. Can you check to confirm CPU1 Flash memory space as empty? If a CPU1.out was loaded to the target, then CPU1 could take advantage of the 'Run Action' button.

    Thanks and regards,

    Charles