The fact that the MS2 chip is running out of room has been a topic for occasional discussion for rather some time. In the past few days, a user reported an overflow error caused by the processor slamming hard into the limits of the device's memory. Something Must Be Done (tm).
From what I can tell, the single greatest waste of space is having all the wheel decoders loaded at once. No matter what trigger type you are using, your processor also has the EDIS, Renix 44-2-2, and the YZF1000 patterns, and and and ... The suggestion was made several weeks ago about stripping out the trigger patterns, and only including the pattern you wanted in the compiler build. This was rejected as it would require EVERY MS2 user to understand how to install and operate the compiler, which is a fairly non-trivial task and an unsuitable expectation.
Is it possible, and how hard would it be, to modify the code such that the main compiled .s19, when loaded and run, gives you the option of loading one of a selection of precompiled 'special' .s19 trigger modules? The standard load would be Basic Trigger and Toothed Wheel, but you would have the option of loading "Honda VTR1000", or "Subaru 6/7", or "UJM 1 long+3 short" (*ahem* *ahem*
) from a menu in TS. Is this possible? Is it practical?
A simpler, more brute force method might be to simply divide the list of trigger modules in half; MS2/Extra_pre3.3.2beta9(A) has first ... 17 ..., while MS2/Extra_pre3.3.2beta9(B) has the other 16 trigger modules, all compiled and ready to load. I have no idea what the compiled memory size of the trigger modules are, but I have to assume this would free up a fair amount of memory - particularly when the code is so desperately poor for memory. "Rollin' dimes for gas money poor," as the man said ...
Thoughts? Comments?
