[time-nuts] Good (cheap) PIC chip choice for project?
lists at rtty.us
Sat May 25 22:01:13 EDT 2013
I have had several conversations with 16 bit chip designers over the past couple of years. Each time the M0 or similar ARM parts has come up. The consensus seems to be that getting (internal) funding for future 16 bit parts is going to be tough. The tiny 8 bit parts will survive and move forward. Getting the money for "the next big thing" in 16 bits - not likely.
On May 25, 2013, at 9:39 PM, Didier Juges <shalimr9 at gmail.com> wrote:
> While I have often said that I have more time than money, I still consider that my time is too scarce (or valuable) for assembly language.
> My opinion is that the language for small embedded devices is C. Some may disagree, but after over 40 years of writing software for a whole bunch of platforms (obviously not all in C), I see no reason to switch to something else for small embedded systems.
> Therefore make sure you select a chip/family/architecture for which you can get a decent C compiler.
> Friends don't let friends write in assembly.
> Nowadays, the Cortex M0 is on par price-wise with 8 bit controllers. If I had to start over today, I would probably start there.
> Didier KO4BB
> Jason Rabel <jason at extremeoverclocking.com> wrote:
>> My reasoning for using a PIC (or similar) is mostly two factors.
>> First, simplicity... The few things I have in my head that I've wanted
>> to do aren't complicated or require special busses. It is
>> things that you could *probably* do with a whole pile of logic chips,
>> or keep it simple with just one PIC. ;)
>> Second, cost... Spending $30-$40 for a one time project is fine. But
>> say after 10 or so, the cost savings of a $2 chip vs $30
>> embedded system starts to add up.
>> I agree with you that I need to figure out the project details first
>> and what I'm trying to integrate with and work backwards. I'm
>> really glad people are giving me feedback though I didn't know so many
>> different options existed (and at so many different price
>> points). If you don't ask, you will never learn. ;) Both the Arduino
>> and TI Launchpad offerings look very intriguing.
>> I'm on no deadline, so time is not an issue. I just wanted a new
>> challenge and this is something I've wanted to dive into for a long
>> Learning a programming language is not an issue. While I mostly write
>> code in PHP, Perl, and shell scripts these days, I used to and
>> am still somewhat familiar with C/C++. Most other programming languages
>> I've used in the past are now probably considered archaic or
>> defunct. ;)
>> Looks like I have a lot of reading to do now. Everyone's responses have
>> been most helpful!
>>> How did you decide to use a PIC and not one of the others such as the
>>> AVR MSP or whatever? I don't want to argue for any of the others
>>> if you can't list 5 or 6 good reasons to use a PIC and you are not
>>> able to say why the oters cn't work for you then you've just selected
>>> something at random without thinking. SO as a check, see if you can
>>> list pros and cons.
>>> You have to decide what you are going to USE the device for first.
>>> Some are bets for different purposes. And also how much time you are
>>> willing to invest in learning. How much programming experience do
>>> you have?
>> time-nuts mailing list -- time-nuts at febo.com
>> To unsubscribe, go to
>> and follow the instructions there.
> Sent from my Motorola Droid Razr 4G LTE wireless tracker while I do other things.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
More information about the time-nuts