Prev: RTOS brands
Next: Low cost GPIB-USB controller
From: Jim Granville on 5 Mar 2006 19:03 rickman wrote: > Isn't that a pretty large battery for a clock backup? But the self > discharge is the real issue. I just find it odd that they would design > the power circuit for a real time clock to be anything other than > compaitble with 1.5 volt Silver Oxide found in watches or 3 volt > lithium cells found in pretty much all the other stuff that needs a > backup battery. If it needs an LDO to work with standard batteries, > then shove that inside the chip. Isn't integration what these chips > are all about? The data says this: ? VDDCORE pins: Power the core, including the processor, the memories and the peripherals; voltage ranges from 1.08V and 1.32V, 1.2V nominal. ? VDDBU pin: Powers the Slow Clock oscillator and a part of the System Controller; voltage ranges from 1.08V and 1.32V, 1.2V nominal. So, seems it powers not just the OSC, but some other stuff as well, and that will be in the same process as the core - thus the tight VddBU Spec. Wonder what the ESD rating on the VddBU is ? - this could need care, if designing to replace batteries in the field. If you do find a uA region regulator, that is happy with Vin=1.5V, and Vo = 1.2V, AND continues to draw the low uA whilst in dropout, let us know. -jg
From: rickman on 5 Mar 2006 23:28 Ulf Samuelsson wrote: > Since it is in a 0,13u process, the core voltage is limited to 1.2V. > The integrated LDO has 30-40uA inherent power consumption. > The external voltage regulator has 1 uA power consumption. > Different processes you know. I understand about processes, but a regulator that powers a 70 mA core would draw more current than one that powers a 2.5 uA RTC. I can't imagine that you could not have put a regulator in the circuit for a 1.5 volt cell with a decent power consumption. This sort of attention to detail is what makes a good design great. If I have to add a bunch of different small parts to an MCU like this, it can make me want to use a different MCU. I can actually get an RTC for the same price as a typical LDO. BTW, as long as I have your attention, am I correct in thinking that this part can not boot from NAND flash? The data sheet seems to say that I have to use either standard NOR flash (or some other directly addressable memory) or a serial SPI flash. I have not read the entire data sheet yet. In particular I have not real all about the memory interface. If I let the CPU boot from memory, will it handle the NAND flash interface so that it looks like random access NOR flash and the CPU can boot from it? I am used to treating NAND flash like a block memory device that is not directly executable and must be copied to RAM memory.
From: Ulf Samuelsson on 6 Mar 2006 05:08 rickman wrote: > I understand about processes, but a regulator that powers a 70 mA core > would draw more current than one that powers a 2.5 uA RTC. I can't > imagine that you could not have put a regulator in the circuit for a > 1.5 volt cell with a decent power consumption. This sort of attention > to detail is what makes a good design great. If I have to add a bunch > of different small parts to an MCU like this, it can make me want to > use a different MCU. I can actually get an RTC for the same price as a > typical LDO. > Maybe there is no suitable LDO available in that specific process... The 0.13u has not been around for that long inside Atmel. > BTW, as long as I have your attention, am I correct in thinking that > this part can not boot from NAND flash? No, You can put U-Boot in a *small* serial flash (1-2 Mbit), and then you continue from there. NAND flash boot is a possibility for future chips. -- Best Regards, Ulf Samuelsson ulf(a)a-t-m-e-l.com This message is intended to be my own personal view and it may or may not be shared by my employer Atmel Nordic AB
From: Jim Granville on 6 Mar 2006 13:40 Ulf Samuelsson wrote: > rickman wrote: > > >>I understand about processes, but a regulator that powers a 70 mA core >>would draw more current than one that powers a 2.5 uA RTC. I can't >>imagine that you could not have put a regulator in the circuit for a >>1.5 volt cell with a decent power consumption. This sort of attention >>to detail is what makes a good design great. If I have to add a bunch >>of different small parts to an MCU like this, it can make me want to >>use a different MCU. I can actually get an RTC for the same price as a >>typical LDO. >> > > > Maybe there is no suitable LDO available in that specific process... > The 0.13u has not been around for that long inside Atmel. Perhaps Atmel should characterize a Series Diode + Watch battery solution, and publish that as a practical battery solution ? Or a PNP transistor, and two resistors ? - fine control over the voltage drop & more current tolerance, at the expense of some static current. Some ESD comments would be good too :) -jg
From: rickman on 6 Mar 2006 13:43
Ulf Samuelsson wrote: > rickman wrote: > > > I understand about processes, but a regulator that powers a 70 mA core > > would draw more current than one that powers a 2.5 uA RTC. I can't > > imagine that you could not have put a regulator in the circuit for a > > 1.5 volt cell with a decent power consumption. This sort of attention > > to detail is what makes a good design great. If I have to add a bunch > > of different small parts to an MCU like this, it can make me want to > > use a different MCU. I can actually get an RTC for the same price as a > > typical LDO. > > > > Maybe there is no suitable LDO available in that specific process... > The 0.13u has not been around for that long inside Atmel. > > > > BTW, as long as I have your attention, am I correct in thinking that > > this part can not boot from NAND flash? > > No, You can put U-Boot in a *small* serial flash (1-2 Mbit), and then you > continue from there. > NAND flash boot is a possibility for future chips. I understand that the processor can boot from the serial flash. So it can not boot from a NAND flash. Again, I consider this a shortcoming of the chip that requires yet another small chip to be placed around the CPU to make it functional. The list grows... |