mtwieg
Advanced Member level 6
Hello, for my research I've been using an ATmega168 for control, but I've pretty much reached its limitations so I'm looking for a more powerful solution. I'm already pretty comfortable with Atmel, so I was looking at the AT32UC3 family as an upgrade. I'm not to savvy on embedded design, which is why I'm not jumping for something more powerful like an ARM. But I'm looking over the documentation and am kind of uncertain as to whether it meets my specs or not.
The MCU will be executing routines in which it controls and reads from peripherals with accurate timing (100ns would be nice). In particular it needs to have a fast SPI interface (preferably at least 25MHz). The main clock on these devices generally goes up to 66MHz, but can the SPI clock actually go that fast? I've read in the Errata for some of the devices that it clock to the SPI and UART is limited to 33MHz. But is that the same as the actual data rate of the interface, or is it half the peripheral clock speed (like it is in the ATmega devices)?
Second, I see that there a few revisions available, A B and C. The A devices seem to have incredible amounts of Errata, so I'd like to avoid that, but the C devices seem very new, and there doesn't seem to be any dev boards available yet. Is the B revision a good place to start?
I do have more questions, but those are the two main ones for now.
Thanks,
-Mike
The MCU will be executing routines in which it controls and reads from peripherals with accurate timing (100ns would be nice). In particular it needs to have a fast SPI interface (preferably at least 25MHz). The main clock on these devices generally goes up to 66MHz, but can the SPI clock actually go that fast? I've read in the Errata for some of the devices that it clock to the SPI and UART is limited to 33MHz. But is that the same as the actual data rate of the interface, or is it half the peripheral clock speed (like it is in the ATmega devices)?
Second, I see that there a few revisions available, A B and C. The A devices seem to have incredible amounts of Errata, so I'd like to avoid that, but the C devices seem very new, and there doesn't seem to be any dev boards available yet. Is the B revision a good place to start?
I do have more questions, but those are the two main ones for now.
Thanks,
-Mike