Bit-banging features questions (aka MOFLAGS)
Posted: Sun Aug 16, 2009 8:25 pm
Ok, I like messing around with the Spectra and such, but don't need a doorstop (or an expensive one for that matter!)
I did some reading today, recorded my moflag strings and such. I seem to be having luck! I know that the Command Board feature string is ALWAYS between B681 and B690, with B691 and B692 being the check sums. The MLM I heard changes locations depending on the size of the codeplug, but mine did start at 6183 and went to 6192, with 6193 and 6194 being the check sums. I have a big codeplug too, with all 128 modes being used.
As with more "luck", my feature string happens to be exactly the same, byte for byte, as the "full feature string" on the Moflag page on batlabs. Really all i want to do is maybe disable features from being used or just seeing if the unused bits actually enable anything. My question is is it possible to brick the radio by messing with JUST the feature strings on the command board and MLM? I assume not, because any value would just change features used, which could possibly cause some fail codes, but I should be able to still bit bang with lab right?
Here is my example. Lets say in Moflag 5, bit 1 (which is MDC Emergency), I want to disable it completely and making it not available in the RSS. In B686 and 6188 (moflag 5), the hex is FF, which means 11111111 in binary which is everything enabled. So I would want 11111101, which would just disable the MDC emergency. In hex, that is FD. So from my readings, this is what I should do:
1: Go in lab, and bit bang B686 AND 6188 from FF to FD. Then Exit out of lab
2: I get a Fail 01/82. Go into the RSS. Read the radio, then write it back. Check sums fixed and all should be well right?
The only bit banging I did was increasing the modes on the Spectra at location 6128, which is 80 (128 decimal). So I assume this is the same thing as that gives the check sum error too.
Also I had another question regarding the differences between the MLM and the Command Board. I know the MLM is attached to the Command board but what I don't get is the bit banging. When I go to the bit bang menu, it says it is the MLM. However, when i see of editing the command board, it always starts with a Bxxx for the address. I thought that the MLM with its EEPROM was the only thing that ever gets written to (along with the A9 head if you have one, which i do). Is there a chip on the ACTUAL command board that gets edited as well using the MLM bit-banging menu? All I see on the command board is Motorola IC's, so that is why I am unsure. Or does that mean that the command board info (feature string, serial and model number) is stored on the MLM EEPROM as well, as well as the all the MLM info. Basically is it ALL stored on the 28C64 chip or is the actual command board info stored some where on the actual command board? If so where?
Sorry if that is a little confusing. Its just that I am not 100% sure on how to make the distinction. Also when bit-banging, how do you know if you are editing the actual command board (if that is the case)? Is it by the address starting with a "B"?
Thanks for the responses in advanced!
I did some reading today, recorded my moflag strings and such. I seem to be having luck! I know that the Command Board feature string is ALWAYS between B681 and B690, with B691 and B692 being the check sums. The MLM I heard changes locations depending on the size of the codeplug, but mine did start at 6183 and went to 6192, with 6193 and 6194 being the check sums. I have a big codeplug too, with all 128 modes being used.
As with more "luck", my feature string happens to be exactly the same, byte for byte, as the "full feature string" on the Moflag page on batlabs. Really all i want to do is maybe disable features from being used or just seeing if the unused bits actually enable anything. My question is is it possible to brick the radio by messing with JUST the feature strings on the command board and MLM? I assume not, because any value would just change features used, which could possibly cause some fail codes, but I should be able to still bit bang with lab right?
Here is my example. Lets say in Moflag 5, bit 1 (which is MDC Emergency), I want to disable it completely and making it not available in the RSS. In B686 and 6188 (moflag 5), the hex is FF, which means 11111111 in binary which is everything enabled. So I would want 11111101, which would just disable the MDC emergency. In hex, that is FD. So from my readings, this is what I should do:
1: Go in lab, and bit bang B686 AND 6188 from FF to FD. Then Exit out of lab
2: I get a Fail 01/82. Go into the RSS. Read the radio, then write it back. Check sums fixed and all should be well right?
The only bit banging I did was increasing the modes on the Spectra at location 6128, which is 80 (128 decimal). So I assume this is the same thing as that gives the check sum error too.
Also I had another question regarding the differences between the MLM and the Command Board. I know the MLM is attached to the Command board but what I don't get is the bit banging. When I go to the bit bang menu, it says it is the MLM. However, when i see of editing the command board, it always starts with a Bxxx for the address. I thought that the MLM with its EEPROM was the only thing that ever gets written to (along with the A9 head if you have one, which i do). Is there a chip on the ACTUAL command board that gets edited as well using the MLM bit-banging menu? All I see on the command board is Motorola IC's, so that is why I am unsure. Or does that mean that the command board info (feature string, serial and model number) is stored on the MLM EEPROM as well, as well as the all the MLM info. Basically is it ALL stored on the 28C64 chip or is the actual command board info stored some where on the actual command board? If so where?
Sorry if that is a little confusing. Its just that I am not 100% sure on how to make the distinction. Also when bit-banging, how do you know if you are editing the actual command board (if that is the case)? Is it by the address starting with a "B"?
Thanks for the responses in advanced!