OSPI_flashExecCmd has a couple of checks where the code may get stuck

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: High
    • SITSW-8036
    • 11.01.00
    • Hide
      11.01.01
      11.02.00
      Show
      11.01.01 11.02.00
    • Hide
      am62xx-sk
      am62xx-sk-lp
      am62x-sip-sk
      am62a-sk
      am62p-sk
      am62d-evm
      am62l-evm
      am275x-evm
      Show
      am62xx-sk am62xx-sk-lp am62x-sip-sk am62a-sk am62p-sk am62d-evm am62l-evm am275x-evm

      In the OSPI_flashExecCmd function call, the first and third loops do not have timeout mechanism added to it. This makes it one of the points where the code may hang.

      To make it more robust, there should be timeout mechanisms introduced to the first and third loops, the second loop already has this.

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Connection: Intermediate to External PROD System
                EXTSYNC-6003 - OSPI_flashExecCmd has a couple of c...
                SYNCHRONIZED
                • Last Sync Date: