[00:01.080 --> 00:02.140]  Challenge 4
[00:03.340 --> 00:09.100]  Here's what we know. We've restored communication with the payload module, but we still can't operate it.
[00:09.100 --> 00:14.900]  The challenge? Now teams must restore normal operations of the payload module so we can access the imager.
[00:15.220 --> 00:20.020]  Here's how they do it. Teams discover that the payload module bootloader has been corrupted,
[00:20.020 --> 00:23.000]  which is why the payload module is not operating normally.
[00:23.000 --> 00:25.700]  The teams discover a system console to the payload module
[00:25.700 --> 00:28.740]  and the ability to access the payload module system console
[00:28.740 --> 00:34.340]  by controlling an undocumented GPIO and multiplexer on the CNDH board.
[00:34.340 --> 00:38.380]  The teams must write a custom flight software application that can control the GPIO
[00:38.380 --> 00:41.500]  and enable access to the payload system console.
[00:41.500 --> 00:46.400]  After writing the application, the teams must upload it to the CNDH and execute it.
[00:46.400 --> 00:51.400]  Once the teams have access to the system console, they will identify that it has been corrupted.
[00:51.400 --> 00:54.780]  The teams will need to research nominal kubos bootloader configuration
[00:54.780 --> 00:59.340]  and repair the payload module's bootloader to resume proper operation of the payload module.