We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Dear All Expert,
I am thinking of programming a PIC MCU for my application as it uses 3V supply which can be power up with 2xAAA batteries. I am using Keil C uVision4 and therefore would like to know any user of PIC had already written the assoicated SFR in a <PIC.h> file. Is it possible to provide me with this file as I am totally new to PIC. Should you have a simple interrupt enabled routine and go_to_sleep routine, it will be great if you can share.
My application need to be low power during sleep and will only wake up through external interrupt. I need 4 external interrupts and a RS232 serial communication for my PIC and DIL package is preferred. Anyone had any recommendation on the model number to use?
Thanks a lot for all your advise. Have a good day ahead.
It is funny that some FAE from one of our distributors insisted and tried to convince me that, you can use the internal flash of MSP430 for frequent counter value saving. (100 times per day, 20 years.) Not to mention the Erase/Write cycles, and the Power Consumption, the MSP430 would freeze for 23ms while doing the Flash Erase/Write, but he sees no problem.
Thats probably why he is an FAE and not a programmer/developer :)
It's just a question of time scale for the application.
23 ms lockup while erasing the flash doesn't matter for a device that controls equipment in 1-second timing resolution. And since many embedded designs can sleep the processor for 99% or more, it can matter a lot to go all the way down to the deepest power mode, potentially turning off the core and RAM power and not just stopping the clocks.
This MSP430 device is in charge to decode Low-Frequency signal. The FAE knows this. 23 ms lockup could be considered as 23 bits loss.
since many embedded designs can sleep the processor for 99% or more, it can matter a lot to go all the way down to the deepest power mode, potentially turning off the core and RAM power and not just stopping the clocks.
Per, thanks for your explanation.
I would do something for my MSP430 project to (try to) reduce power consumption; and would ignore issues that I can not handle. For those traditional PIC products, I would stay away from them.
Got an email from management to most software engineers, saying that every software engineer should do a good job, otherwise the company may sue you for professional negligence.
This is really encouraging.
I think I should concentrate on the major functionalities, and ignore all the minor issues like power consumption.
Why do I suddenly think about Dilbert?
WTF?!?!!?!?!? Are you serious?
=> Are you serious?
Yes.
-----
Use Google translator to do a direct translation:
You should have seen the company has already begun on the Software Bug loss requirements, I hope (YOU ALL) not in the punishment of the list. Each software must be reviewed and approved, Do not issue or a problem, the company may pursue professional negligence, please bear in mind.
NOW!!