135
edits
Changes
Jump to navigation
Jump to search
=== Video Sync Pal/NTSC - ===This 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 interesting oneoddity. The DIFIt'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-AT syncing to video?!compile either)''
I think that, the ADAT and TASCAM tape machinesOne or two strings can be discovered, will which have had a video sync input, so they could be used to sync to video gear different call system 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 diagnostic strings (the DIF-AT to video without it coming from a tape machine. ones I'm sure the manual for an ADAT machine will most interested in) especially because I have this infoto repair so many subsystems, ICs, and traces. If I locate the info I will update this section.
When I finally load the firmware (I still havendon't know at this point) I spend ages looking for what calls that these diagnostic strings. I find it difficult are highly likely to navigate but fascinatingbe called by the Monitor Version 1. It is difficult to navigate any production firmware disassembly I expect. I have no prior experience00, but it seems the H8300H which is kind of a different level, highly likely 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 Machine Language diagnostic tool which makes static disassembly trickiermust operate over UART.
I have studied the datasheet for the CPU, and found out the boot modes, what pins are active in which boot mode, timer set up, SCI (serial) interface===Video Sync Pal/NTSC -===This is an interesting one. Most pins of the CPU are mapped in the excel sheet above and the notes belowe. The DIF-AT syncing to video?!
One or two strings can be discoveredI think that, the ADAT and TASCAM tape machines, which will have had a different call system 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 diagnostic strings (DA88. It's not possible to sync the ones DIF-AT to video without it coming from a tape machine. I'm most interested in) especially because I sure the manual for an ADAT machine will have to repair so many subsystems, ICs, and tracesthis info. If I locate the info I don't know at will update this point that these diagnostic strings are highly likely to be called by the Monitor Version 1.00, which is highly likely a Machine Language diagnostic tool which must operate over UARTsection.
→Video Sync Pal/NTSC -: layout
The **Roland xx looks like a boot banner and is called differently in the firmware. I'm sure that's why it has different start and stop markers. Ditto for the early Version string. Interestingly, the early Version is way at the other end of the addresses in the code. This adds to the DFU / Bank swap theory.
===High Performance Embedded Workshop -===
