Renesas Introduces next-gen R32C MCUs

I'm posting this because I wanted to get the word out about the R32C. It is code compatible with R8C/M16C/M32C and runs faster with more peripherals and a built-in FPU.

http://america.renesas.com/fmwk.jsp?cnt=m16c_family_landing.jsp&fp=/products/mpumcu/m16c_family/

When will it be available through digikey?  And when will the hardware and opcode manuals be online?  So far all it has are shortsheets.  Also, the r8c and m32c are not code compatible; how can the r32c be compatible with both of them?  Do you mean source compatible?  (Yes, I've been looking forward to these chips for a while

Just to be picky:  Having written the gnu tools for r8c and m32c, the r8c codes are NOT binary compatible with the m32c codes.  I expect the R32C will also not be binary compatible, so you'd have to recompile at least.

Peripheral compatibility is wonderful, though

You are right. Only R8C and M16C are nearly the same (where R8C misses 2 instructions of M16C), but M32C and R32C are different things with a number of different instructions and different adressing modes. I think R32C will not have more in common with M32C than M32C has with M16C. The CPUs are quite similar with M32C being a bigger M16C, and R32C being a bigger M32C.

Pin configurations are compatible and peripherals are very much the same.

OK, OK....

Upward code compatible with the little * next to it.

(As anyone will tell you, the devil is in the details. Even moving from a 64k memory R8C to a 128K R8C can require a recompile - depending on how the original build was done.)

Hey All;

We are doing a port of the Unison RTOS to the R32 (rowebots.com/products/unison) .  Can you tell us what peripheral support you might like with it?

Kim