AS3 Codeplug in an AS2?

[fogster]

I have two related, hypothetical questions regarding the extent of 'backwards compatibility' with codeplugs between an ASTRO Saber 2 and an AS3.

- Suppose an AS2 somehow ended up with an AS3 codeplug in it. (But nothing else weird was going on; i.e., same bandsplit, not changing from VSELP to IMBE, and not messing with software encryption.) Am I correct in my understanding that DTMF is the only difference? Provided I didn't use any DTMF features, would it matter at all? (And, for that matter, will an AS2 codeplug work in an AS3, short of DTMF functionality?)

- If a codeplug from a 512KB radio ended up in a 1MB radio, would it work? (And actually, for that matter, do the codeplugs actually depend on the size of the controller board? In other words, what happens if a codeplug from a 1MB radio were put in a 512KB radio? Is this different if dealing with S-records instead of normal codeplugs?)

Thanks!

[MattSR]

Yes, Yes, Yes.

No - the codeplugs has nothing to do with the controllers memroy - that memory is only used to hold the Firmware, not the codeplug. The codeplug is held in separate memory.

[wavetar]

- Suppose an AS2 somehow ended up with an AS3 codeplug in it. (But nothing else weird was going on; i.e., same bandsplit, not changing from VSELP to IMBE, and not messing with software encryption.) Am I correct in my understanding that DTMF is the only difference? Provided I didn't use any DTMF features, would it matter at all? (And, for that matter, will an AS2 codeplug work in an AS3, short of DTMF functionality?)

Yes, your understanding is essentially correct.

- If a codeplug from a 512KB radio ended up in a 1MB radio, would it work? (And actually, for that matter, do the codeplugs actually depend on the size of the controller board? In other words, what happens if a codeplug from a 1MB radio were put in a 512KB radio? Is this different if dealing with S-records instead of normal codeplugs?)

The 512KB vs 1MB is actually referring to firmware memory size, not the codeplug. So, you can jam a codeplug from a 1MB to a 512KB & vice-versa. What options actually end up working (or not) will depend on the firmware version. For 9600bps Astro25 trunking, a 1MB firmware with version 6.xx.xx is required. The 1MB is required for something else too...I just can't recall what.

Todd

[MattSR]

Its needed for DSP > 7 and Host > 5

512KB means you miss out on DSP 8.xx.xx

[akardam]

Since the DSP is stored in a seperate 256k ROM, seperate from the 512k or 1m HOST ROM, I believe you can have an 8 series DSP with an older HOST, though of course the older HOST may not be able to access all the features of the newer DSP, and your radio may or may not behave correctly with such a HOST/DSP mismatch.

[MattSR]

HOST/DSP mismatch is a bad idea. I think it requires some bodgy hacks to do as well.

[akardam]

Never claimed it was a good idea, but it is doable if you absolutely positively have to.

[fogster]

Excellent, thanks for everyone's help. (Now, too bad I missed the auction that spurred this question... But there'll be more.)

As far as the Host/DSP mismatch... I hadn't heard much about it. Definitely a bad idea, I agree, but given that the context it came up in was mixing codeplugs between radios, it's not necessarily an unreasonable risk.

BTW, not to get too astray (or too into potentially illegal activities), but how would one end up with a host/DSP mismatch? I'm assuming Motorola wouldn't do it. Am I reading too far into this by assuming that it's somehow possible to clone/hack host/DSP from one radio to another?

[mr.syntrx]

The 512KB vs 1MB is actually referring to firmware memory size, not the codeplug. So, you can jam a codeplug from a 1MB to a 512KB & vice-versa. What options actually end up working (or not) will depend on the firmware version. For 9600bps Astro25 trunking, a 1MB firmware with version 6.xx.xx is required. The 1MB is required for something else too...I just can't recall what.

Todd

APCO Packet Data lives in the upper memory.