Okay, I am old and fat, my mother is 84'ish and still kicking and dancing, even with people telling her she is old enough to take it easy and behave like an old woman. Buying a new car doesn't mean I can't drive it because I'm old, nor will force me to keep the old car just to drive mother around.
I saw ATMEL born, I saw all the new chips born, and for some reason I still use At90S2313 for simple projects. Perhaps because I have few thousands of them around, from old inventory. Writing lean assembly gives me the advantage to not need huge flash memory. Of course I use AtMegas when needed. But I love the 90S2313 and 8515, what can I do? get rid of mother and replace her with a 22 yrs old, brand new young lady? well, shush, lets not think about it.
When the AS4 came without the programming support for AT90S2313 and 8515/35 we found a way to make them being recognized by AVRISP MKII and Dragon, and works pretty well. Save the neck of several friends around.
Now, AS5 came with a different kind of 'device'.xml files. On AS4 they were at the assembly2 folder.
Last night I was able to trick AS5 to accept the AT90S2313 as its own device, compile (build), etc.
Mother, the very old lady, is back racing around in a brand new sparkling yellow 12 cylinders Lambourghini. :)
What I basically did, was copy and rename the AtTiny2313 xml file to At90S2313 and change some contents to reflect this new name and functions, change PORTA to PORTB, and its I/O addresses, clocks, etc. I also deleted several text area relative to the Tiny2313 that doesn't exist on 90S2313. But there is much more to do.
Basically I am "creating a new AVR device", with the characteristics of the At90S2313.
What I did NOT make yet (lack of time), is changing the programming ISP commands, so the xml file continue with the Tiny2313 commands, and of course, when trying to program the 90S2313 via the AVRISP MKII, it can read the signature byte, it can READ flash and eeprom, it can erase it, but can not program it, YET, I tried all of it.
Interesting enough, now the new .xml files carry information about the programming of each individual chip. That's neat and smart, since it eliminate the need to keep updating the AVRISP and Dragon firmware all the time for new chips, just tell them the new protocol, the different commands, on the fly, and keep going.
Also, I was not crazy enough to run any simulation, several Tiny2313 DNA molecular segments still there in the xml file, will take time to change.
The reason of this post, is to make people think that it is possible to use legacy chips with AS5, why not? Just because Atmel doesn't produce them any longer is no reason to cut them out of the software platforms.
Mother may be old, but she is not dead yet.
So I ask: Is there someone out there trying to do the same? Maybe we could share results.
If I am incorrect thinking to find a way to "allow mother to enjoy riding a new car", then why Atmel left INCLUDE files for those legacy chips at some folder of the AS5 ? yes, they are there. They forgot to remove them? hmmm.
I am pretty sure that some people will benefit for being able to use legacy chips in AS5, so I will continue the job and will post news here.