Simple ideas and proposals Assumptions based on : Tentative to limit the triplications where strictly needed In criticality order. “ abcnasic ” SEU strategies. Protection about the “ DCL ” functions. An soft error on DCL may result in one or a few packets loss , if properly protected.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
An soft error on DCL may result in one or a few packets loss, if properly protected.
One option would be the use of a watchdog synchronized to DCL_BUSY
This has to be evaluated by model and simulation
(Applying full triplication on the DCL logic would be a killer, because of the peak current activity)
Readout Port FIFO
Actually the “Readout” is the most “”unknown” part for concerns about soft errors, but the function is critical (serializer has to be able to send packets)
An option is to provide a “minimal” mode (after soft error or by addressable command) which is :
BYPASS (to adjacent chip data : ie only passing data through w/o local chip interruption)
This BYPASS mode should be fully soft error protected
Bypass (soft error or command)