Resolve "Decoder crash with new error pattern (which starts with a lost frame) 2"
requested to merge 1293-decoder-crash-with-new-error-pattern-which-starts-with-a-lost-frame into main
- Related issues: #1293 (closed)
- Requested reviewers: @tyagiri
Reason why this change is needed
- Addition to NONBE_1293_CRASH_FIRST_FRAME_LOST.
Description of the change
- Fix
-fr 5/10outputs when the first frame is lost - Changes are within NONBE_1293_CRASH_FIRST_FRAME_LOST
Affected operating points
- Not-BE for
-fr 5/10outputs when the first frame is lost