D64 vs D128

[D64]

I plan to immigrate from D128 to D64 due to a significant code optimization. I already sent out prototype with D128. And I really don't want to keep two release software, one for D64 and one for D128. Is there any way I could make the S19 code compatible to both MCUs?

By the way, I couldn't find S12 D-family memory map organization.

[kef]

Yes, that's possible. You just compile for smallest D64 and keep in mind what boundaries RAM and EEPROM blocks are mappable to. D64 4k RAM block is mappable to any 4k boundary 0-FFF,1000-1FFF etc. D128 8k RAM block is mappable to any 8k boundary 0-1FFF, 2000-3FFF etc. So if 4k RAM is mapped to <$2000, then EEPROM should be mapped to >=$2000. If 4k RAM is mapped to 2000-2fff or 3000-3fff, then EEPROM should be mapped to <$2000 or to >=$4000. Etc.

[D64]

Thanks for your kindly response, Kef.

Some of the concern might be related to the flash logic address difference between those two MCUs. I mean the ppage register. I am not sure D64 is able to tolerant 7F address and map it to 3F pagers by discarding the MSb. Otherwise the program could jump out of the micro. That's gona be fun.

[kef]

I'm not sure I understand you. It's not clear what's the nature of your mentioned 7F. D64 has 4 pages of flash 3C-3F. D128 has 8 pages 38-3F. If you compile for smaller D64, then it will fit D128.

[D64]

sorry. My mistake. I mixed with S12X

[kef]

Wow. Did you mean S12D64 vs S12XD128 or S12XD64 vs S12XD128? I thought you were talkig about S12D64 vs S12D128.

S12D64 vs S12XD128. Too big differences. I would not bother trying to do binary that works on both. Something is possible, but not easy and won't work with all tools.

S12XD64 vs S12XD128. That's easier than S12D64 vs S12D128. Just compile for smaller XD64.

[D64]

still D64 vs D128. there is nothing with XD128. only documents mixed.

Thanks your info. It is good I didn't provide misleading information to management team.