Changes

[[File:DIF-AT BINVIS.png|alt=binvis.io|center|thumb|BINVIS The little 'white line defined' area is where the pointer is viewing]]

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"

When I finally load the firmware (I still haven't at this point) I spend ages looking for what calls these strings. I find it difficult to navigate but fascinating. It is difficult to navigate any production firmware disassembly I expect. I have no prior experience, but it seems the H8300H is kind of a different level, a bit of an oddity. It's used a lot in Japanese electronics. It is in a lot of Roland devices. Apparently it interleaves code and data frequently which makes static disassembly trickier. ''Especially in Cutter, which won't decompile H8 instructions (it either links to Ghidra method, which does not support the H8, or JS, which can't de-compile either)''

One or two strings can be discovered, which have a different call system to the diagnostic strings (the ones I'm most interested in) especially because I have to repair so many subsystems, ICs, and traces.

I think that, the ADAT and TASCAM tape machines, will have had a video sync input, so they could be used to sync to video gear to score music for TV / video productions.  The video sync will input to those machines, and the DIF-AT sees the 'passed through' sync source from the ADAT tape machine or the DA88. It's not possible to sync the DIF-AT to video without it coming from a tape machine. I'm sure the manual for an ADAT machine will have this info. If I locate the info I will update this section.

===High Performance Embedded Workshop -===