I slowed down a bit here because I had no idea how to actually load the file I'd dumped to look at it. First I used [https://github.com/ReFirmLabs/binwalk Binwalk], which I *think* is more suited to SOC work (at least, I think Binwalk is able to find files and systems within bin images, which this firmware does not contain) Anyway Binwalk was able to provide an informative image showing the entropy of the file - low entropy = low chance of corruption or encryption.
=== Binvis - ===
I also had a look at [https://binvis.io/ Binvis]. Binvis makes for a stunning visual representation, regardless of anything else at all. I love it. It was fun to see the strings represented in coloured pixels. Also, very apparent to see in Binvis, are the firmware banks. [[File:DIF-AT BINVIS.png|alt=binvis.io|thumb|BINVIS The little 'white line defined' area is where the pointer is viewing]][[File:Binwalk entropy image.png|thumb|Binwalk entropy image looking good - encouraging at least|alt=|none]]
===Firmware Banks -===
==Firmware Strings -==
Alright we've heard enough about them; here is the list - '''''strings -n 6 INTEL_HEX_DIF_AT_LH28F400BVE@TSOP48_byte_swapped.bin'''''
{| class="wikitable sortable"
|+
|
|}
=== Strings - ===
Alright we've heard enough about them; here is the list - '''''strings -n 6 INTEL_HEX_DIF_AT_LH28F400BVE@TSOP48_byte_swapped.bin'''''
I removed all the strings returned which are over n6 but not really strings - and - There are also two blank strings which the above table has optimised away. These seem to have a function, unclear at present.