Results 1 to 1 of 1

Thread: MCS2000 S-Record Mapping

  1. #1
    Join Date
    Sep 04, 2015
    Location
    In the Corn
    Posts
    405
    Thanks
    211
    Thanked 333 Times in 129 Posts
    Country: United States

    Default MCS2000 S-Record Mapping

    In my quest to change my model II MCS2000 to a model III, I had a running excel sheet highlighting various parts of the s-record I needed to change. Then I just said, what the heck, I'll highlight and annotate the whole thing. A few hours later, here it is. It's not 100% complete, because I used the block ID's found in this thread for the Astro Spectra codeplug, so every feature that the MCS has isn't listed.

    I've created a Google Sheets Document where anyone can comment with their suggestions and tell me anything I might've missed.

    MCS2000 S-Record Mapping - Google Sheets

    Hopefully this is of use to someone. I'll be referring to it a lot in upcoming experiments, and I might even start mapping out individual bytes and what they do depending on how much time I'm willing to waste.

    In the coming weeks I might map out a few more S-Records for things like the Astro Spectra, and maybe some portables too.

    Ending thought: thanks to FDBTool we known we can write to the S-Record, and we can also map out the entire byte structure of the S-record. Could this not lead to something along the lines of a 3rd-party CPS?


  2. The Following 5 Users Say Thank You to axel For This Useful Post:

    kobit (Dec 16, 2018),Mogman (May 13, 2019),p47r4ck (Jun 18, 2016),QBFreak (Jun 21, 2016),WX9EMS (Nov 04, 2016)