Background:

Both Linux and ROM implementation to pick the read capture delay value for Tap mode is the same. It basically picks the middle(or median value). This makes sure that the data captured from the flash is robust enough across PVT.

Problem Statement:

Currently, the MCU PLUS SDK implementation, picks the largest value by going from a baud rate divisor(which user configures in SysConfig) to 0. For example, if we go from 8 until 0, and if 6 passes, we pick 6. But it should be the middle value out of all the passing values.

More explanation on what sort of Logic needs to be implemented:

• Pick middle read delay capture value
  • If odd number, pick middle
  • If even, pick either middle value
    • We don’t good evidence for which middle value to pick yet (upper or lower middle)
• Read actual data{}
  • More than 4 bytes
  • Reading from actual flash array instead of a flash register
  • Can read the PHY data for “known” good assumed to be in flash
  • 128 bytes