Today's stream began with analysis of the last glitching run, went on to discover whether the working PLC looks for the same file name as the bricked one, and then worked on adding auto-reset functionality to the glitching experiment.
Bookmarks for Easy Browsing:
1:58 - Summary of recent work & context
2:53 - Beginning glitching run analysis
11:16 - Background on SD Card experiment & explanation of next experiment, finding out if behavior unique to bricked PLC or common to all
21:47 - Explanation of SD card emulator interaction
27:55 - Attaching an SD card reader to the SD card emulator
30:41 - Attaching the SD card emulator to the working PLC
43:50 - Running the SD card emulation experiment on the working PLC
54:54 - Getting a closer look at working PLC operations
1:00:00 - Recap on file name discovery and next plans
1:09:17 - Adding a new GPIO pin from the Raspberry Pi to the microcontroller running the ethernet proxy so the Pi can send a hardware reset when there are repeated errors
1:58:41 - Almost there, just a few more changes necessary
2:16:33 - Recap on today's work
Bookmarks for Easy Browsing:
1:58 - Summary of recent work & context
2:53 - Beginning glitching run analysis
11:16 - Background on SD Card experiment & explanation of next experiment, finding out if behavior unique to bricked PLC or common to all
21:47 - Explanation of SD card emulator interaction
27:55 - Attaching an SD card reader to the SD card emulator
30:41 - Attaching the SD card emulator to the working PLC
43:50 - Running the SD card emulation experiment on the working PLC
54:54 - Getting a closer look at working PLC operations
1:00:00 - Recap on file name discovery and next plans
1:09:17 - Adding a new GPIO pin from the Raspberry Pi to the microcontroller running the ethernet proxy so the Pi can send a hardware reset when there are repeated errors
1:58:41 - Almost there, just a few more changes necessary
2:16:33 - Recap on today's work
RSS Feed