# Hardware Update through Digital TV Signals
## 6 Simulation Results
However, the rates between 1000 ms and 1500 ms presented the best average performance during the hardware core remounting procedure. It is worth noticing that the mentioned rates provided similar remounting times but with a clear upward trend regarding this merit figure. The other experiments were based on a private section rate of 1000 ms, with a UIT rate set to 1000 ms. The mentioned USB 2.0-based multi-standard modulator was used to perform TS broadcasting. Some results were generated for validating the correct operation of the entire scheme. The metrics evaluated here were the remounting time (RMT) (i.e., the time for downloading reconfiguration data) and the reconfiguration time (RCT), which is the period employed to parse the related SVF file and to reconfigure a target FPGA, with the latter occurring if an RMT process has occurred, as well as the sum of the checksum verification time necessary to check all sections and the download time for all sections (remounting). RCT is the total time needed to reconfigure an FPGA device using the implemented JTAG host/target mode. Table 9 shows the obtained results when the broadcast and reception tests were performed using this reconfiguration scheme. The HWname table column represents the pre-synthesized core file name. Column CRsize shows the pre-synthesized core size, followed by TSname, which is the generated TS file name. Finally, the RMT and RCT fields show the obtained average remounting time and average reconfiguration time values, respectively. \begin{table}
\begin{tabular}{c c c} \hline \hline \(\mathbf{TS_{NAME}}\) & **Private Section Repetition Rate** & **RMT** \\ \hline Ex01\_500 ms.ts & 500 ms & 29.20 s \\ Ex01\_750 ms.ts & 750 ms & 17.76 s \\ Ex01\_1000 ms.ts & 1000 ms & 9.87 s \\ Ex01\_1250 ms.ts & 1250 ms & 12.70 s \\ Ex01\_1500 ms.ts & 1500 ms & 13.60 s \\ Ex01\_1750 ms.ts & 1750 ms & 14.26 s \\ Ex01\_2000 ms.ts & 2000 ms & 14.84 s \\ \hline \hline \end{tabular}
\end{table} 
Table 8: Remounting time (RMT) values obtained for the first pre-synthesized example using different repetition rates. \begin{table}
\begin{tabular}{c c c c c} \hline \hline \(\mathbf{HW_{NAME}}\) & \(\mathbf{CR_{SIZE}}\) & \(\mathbf{TS_{NAME}}\) & **RMT** & **RCT** \\ \hline Ex01\_svf & 900,845 bytes & Ex01.ts & 9.87 s & 20.36 s \\ Ex02\_svf & 900,945 bytes & Ex02.ts & 10.89 s & 20.34 s \\ Ex03\_svf & 900,923 bytes & Ex03.ts & 9.95 s & 20.29 s \\ Ex04\_svf & 900,951 bytes & Ex04.ts & 10.25 s & 20.26 s \\ \hline \hline \end{tabular}
\end{table} 
Table 9: Remounting and reconfiguration time values obtained for all the employed pre-synthesized examples using a repetition rate of 1000 ms. The performed experiments showed that pre-synthesized cores could be signaled, multiplexed, and broadcast with DTV content. The achieved RMTs in each test were satisfactory, considering that the proposed scheme's task was performed in concurrency with other DTV tasks (e.g., application retrieval, table filtering, and electronic program guide construction). The RCTs were also satisfactory, considering that the employed reference receiver presented low processing power. Indeed, the developed SVF parser took most of the elapsed time. The reconfiguration JTAG mode is generic and ideal for this PoC, but that can be improved if FPGA devices are integrated into the receiver boards, which would be the case in a complete commercial solution. The RMT value associated with Ex02.svf was larger than what was obtained even with Ex04.svf, which was due to the platform conditions and scheduling at that time (other processes were running). Although all the test files presented nearly the same size, the resulting RMT depended on factors such as the start point related to the private sections, signal strength, and corrupted private sections. Regarding final users, those periods were not perceived, given that the associated tasks were performed in parallel with other receiver tasks. However, if a reconfigured FPGA device was being used (e.g., for media decoding), momentary service interruption may have been noticed.