Critical section in OSPI driver is not optimized and includes data transfer

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Medium
    • PDK
    • PDK-17547
    • PROCESSOR_SDK_10.01.00
    • PROCESSOR_SDK_12.00.00
    • Hide
      j721e-evm
      j721e-hsevm
      j721e-hsfs-evm
      j7200-evm
      j7200-hsevm
      j7200-hsfs-evm
      j721s2-evm
      j721s2-hsevm
      j721s2-hsfs-evm
      j784s4-evm
      j784s4-hsevm
      j742s2-hsfs-evm
      j784s4-hsfs-evm
      j742s2-hsevm
      j722s-hsevm
      j722s-hsfs-evm
      Show
      j721e-evm j721e-hsevm j721e-hsfs-evm j7200-evm j7200-hsevm j7200-hsfs-evm j721s2-evm j721s2-hsevm j721s2-hsfs-evm j784s4-evm j784s4-hsevm j742s2-hsfs-evm j784s4-hsfs-evm j742s2-hsevm j722s-hsevm j722s-hsfs-evm

      In the API OSPI_transfer_v0, the code disables the interrupts of the R5F to protect obj->transaction variable. but this does not get enabled until the entire transfer is complete by calling OSPI_primeTransfer_v0.

            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-5925 - Critical section in OSPI driver is ...
                SYNCHRONIZED
                • Last Sync Date: