Hi dazheng,
Need to know ... what is EEPROM used in MCU for ?. I know EEPROM stand for Electrical Erasable Programming ROM but I need to know what's the purpose or where it going to be used in MCU?
I ask this because some of MCU dont have EEPROM ( EEPROM = 0 byte) ie 80NC535 & 80NC321 and the best thing about this MCU (without EEPROM) that's its cheaper than MCU with EEPROM. If it just minor used and can solve it in other method (and not effect my project) , I will use it as I need to lower the cost as much as possible.
Any instruction (ie in proton) that must be used on MCU with EEPROM ?
More explanation greatly appreciated.
Thanks
zuisti
Hi "zuisti",
The 80NC321 has a lot of register but I think it has EEPROM so we cant use it?
If we stored the latest statuses of it's operational condition in ROM then we could load our last state and continue the operation from there when the power comes back, without starting from the begining twice.
The flash Magic works then I thionk we give it a run. I started PCB already but I cant find (?) help on the RCF rope.
We kick the trollop ;-)
dazheng
"I started PCB already but I cant find (?) help on the RCF rope."
What kind of bonehead needs help with RCF rope? RCF rope is easy, a piece of cake.
Just Please read the manual.
Anyone who can think of anything more dense than a neutron star?
"The 80NC321 has a lot of register but I think it has EEPROM so we cant use it?"
Of course we can use it. You're being silly. Why do you doubt its usefulness?
"If we stored the latest statuses of it's operational condition in ROM then we could load our last state and continue the operation from there when the power comes back, without starting from the begining twice."
Again, silliness. ROM is Read Only Memory. We can't write to ROM, so we can't store our operational condition there.
dazheng,
Dont try to find the rope option.I looked on web and the version doesnt use it. it has an autostep menu.
How much space do we need for the statuses? bcoz do we need more than statuses than code?
yes i think the system could crash, but in my project i only use the key & the screen. if you think that the system would be stable. But my questions is what happens with Magic, maybe Magic dont like working without interruptions.i don't need to get back to sleep once my programm has finished. this is like an embedded project the pc only has to show the signal from the MCU in the screen.
ignore the trolops and they will get tired !)
"How much space do we need for the statuses?"
I think if we plan on 4 square inches, we'll be fine.
"bcoz do we need more than statuses than code?"
Yes, that's why 4 square inches. The code fits in a little less than 2.
"i don't need to get back to sleep ..."
Me neither. Our new project is so fun and exciting, who needs sleep?!!!
I was looking abot the circuit for atrication process i found this article:
Basically, there is no difference. The operational sequence is designed to handle analog signals as long as you do not overdrive it. This enables us to do a number of operations at the same time (log, antilog, invert,rectify, add, subtract etc.) on analog signals (i.e. signals which vary continuously). If you overdrive the MCU, then you can use it with digital signals too, though nobody will prefer that. There are much better options for signals above 122%. Negating the charge causes a positive overlap which throws the logic into an opposite contrajecture.
there are some bits i (?) dont understand but is it right area for project.
Note This message was edited to reduce width.
"there are some bits i (?) ..."
Why the '?' question mark? Are you doubting your existence?
I'm beginning to wonder about your participation in our project.
I may have to start looking elsewhere for someone more qualified.
"... dont understand but is it right area for project."
See, that's what I mean.
If you don't understand, what is your contribution and value to our project?
zuisti,
I want to use the 89c734a bcoz i think it has the pins we need. can you get the code done for it. can we take the EEPROM out of the MCU?
Do we need above 122%? how much?
"can we take the EEPROM out of the MCU?"
Sure, no problem. We'll pop the top and pull it out with non-conductive tweezers.
"Do we need above 122%? how much?"
No, I'm calculating that 7.3% less than that is closer to ideal.
"No, I'm calculating that 7.3% less than that is closer to ideal."
But that still leaves us at ~113%. How do we deal with greater than 100%?
Should we put the EEPROM back in the MCU to make up the difference?
"Dont try to find the rope option. I looked on web and the version doesnt use it."
Yes, I usually find that it's difficult to use options that don't exist!