I can recommend the Pic24/dspic33 series chips. I spent a bunch of time
looking at different options, and ended up with the pic family. There
are a lot of really nice micros out there now. Not like years ago.
The Pic's aren't the fastest chips out there, they aren't the newest
chips out there,
Well, its a matter of opinions I guess. The RPi has one UART which is also
the console port, so so much for that, and 17 IOs in total from the link in
the message below.
On the other hand, the BeagleBone Black has 96 IOs including several UARTs.
I have one of each at the moment, and it seems
On Sun, 26 May 2013 00:12:58 +
li...@lazygranch.com wrote:
If you go arm cortex
A little note here: Arm Cortex are multiple families of processors for
different uses. And they vary a lot!
Cortex-M:
This family is ment to replace the old ARM7TDMI chips that are so ubiquitous.
They are
John, for guys like us who grew up with basic, there is an excellent
(compiled) pic basic from
http://www.protonbasic.co.uk/
I had a look at c, but decided at my time of life I wanted to produce
working projects not learn new (cryptic to me) languages so I stuck with
what I was comfortable with.
Hi
At least with the newer versions ( the X stuff), they really seem to want to
see the PIC Kit 3.
Bob
On May 25, 2013, at 10:20 PM, Herbert Poetzl herb...@13thfloor.at wrote:
On Sat, May 25, 2013 at 10:04:59PM -0400, Bob Camp wrote:
Hi
If you are putting money into a Microchip
Hi
One of the original starting points was a free tool chain. Paying major money
for a compiler is moving a bit far from that. You would have to do a *lot* of
home projects to justify that cost.
Bob
On May 25, 2013, at 10:17 PM, Clint Turner tur...@ussc.com wrote:
Having used PICs since
Hi
I started out loading Unix via tape on a PDP-11 back in 1974. C has been around
for a while. It's also got a bit of baggage from those roots. I do indeed code
quite a bit in C, I just don't use it for everything. Different tools for
different jobs.
Bob
On May 25, 2013, at 10:52 PM, Orin
you really need their
capabilities.
Robert G8RPI.
From: Jason Rabel ja...@extremeoverclocking.com
To: time-nuts@febo.com
Sent: Saturday, 25 May 2013, 20:08
Subject: Re: [time-nuts] Good (cheap) PIC chip choice for project?
My reasoning for using a PIC
On Sun, May 26, 2013 at 07:48:08AM -0400, Bob Camp wrote:
Hi
At least with the newer versions ( the X stuff), they
really seem to want to see the PIC Kit 3.
As I said, it's a marketing move: the PICkit 2 was
declared obsolete after the main developer left
Microchip and the PICkit 3 was
On Sun, May 26, 2013 at 4:50 AM, Bob Camp li...@rtty.us wrote:
Hi
One of the original starting points was a free tool chain. Paying major
money for a compiler is moving a bit far from that. You would have to do a
*lot* of home projects to justify that cost.
Indeed. I wouldn't pay
Probably, one of the best advantages of AVR over PIC is that with avr you
can use the GCC compiler. Gcc of course is the compiler used everywhere
and supports real ANSI C and has a good optimizer and it's free. So if
you use AVR you can port most C code you find that was written for UNIX
Well, its a matter of opinions I guess. The RPi has one UART which is also the
console port, so so much for that, and 17 IOs in total from the link in the
message below.
On the other hand, the BeagleBone Black has 96 IOs including several UARTs. I
have one of each at the moment, and it seems
In message CABbxVHvP0JmXo=ObnZUmtTH=7-ohixswixa0hy3svgo4gqd...@mail.gmail.com
, Chris Albertson writes:
Probably, one of the best advantages of AVR over PIC is that with avr you
can use the GCC compiler.
I recently had enough of all the trouble with both AVR and PIC chips
and went ARM, which
Hi
Actually GCC does support *some* of the PICs. I'd prefer to go with a = PIC24
and run the free version of the Microchip compiler rather than GCC in this
case. The optimization isn't quite as neat in the free Microchip compiler, but
the price is right and the thing does work.
Bob
On May
Hi
It is interesting how the various outfits sneak around the flash loader issue
on their low end boards. Some of the dual CPU approaches I've seen actually
have as much horsepower in the loader CPU as they do in the target. I'm not
complaining about getting 2 usable cpu's for a bit over $10….
In message eed8cc97-4c42-4eed-93fa-b52073051...@rtty.us, Bob Camp writes:
It is interesting how the various outfits sneak around the flash loader issue
on their low end boards. Some of the dual CPU approaches I've seen actually
have as much horsepower in the loader CPU as they do in the target.
Hi Jason:
I've done a number of PIC projects in assembly language because it like it.
I like the 8 pin parts where they are all that's needed. But if you want to have USB or LAN connections then you'll
need one of the much bigger parts or better already assembled boards.
With a simpler part
For some of the TI and NXP boards I have seen, the debug chip is clearly bigger
than the target, probably due to the fact that the debut chip has USB and USB
is typically only supported in the bigger chips.
Didier
Bob Camp li...@rtty.us wrote:
Hi
It is interesting how the various outfits
--
Kenton A. Hoover
ken...@nemersonhoover.org
+14158305843
On Sunday, May 26, 2013 at 12:35, Didier Juges wrote:
Well, its a matter of opinions I guess. The RPi has one UART which is also
the console port, so so much for that, and 17 IOs in total from the link in
the message below.
On
Hi
PIC's have been around for a *long* time. The PIC16's came early on and were
followed by the PIC18's. Both are a bit dated at this point. The PIC24's and
dsPIC33's are actually very similar parts. The PIC33's form a third family
pretty much on their own. A modern version of the Microchip
I started with just the PIC datasheet to learn about the hardware
architecture and the MPASM to write (in assembler) the first try at a
PIC16C84 (at that time the PIC16F84 was not yet available). There are
plenty of sites about PICs and relative projects. The Shera controller
is based on PICs.
On
Hi
I started out with the PIC16's as well, I did projects using a number of them,
and moved to the PIC18's long ago. If you were starting out today - which
family would you start with?
Bob
On May 25, 2013, at 10:03 AM, Azelio Boriani azelio.bori...@screen.it wrote:
I started with just the
On 5/25/13 7:22 AM, Bob Camp wrote:
Hi
PIC's have been around for a *long* time. The PIC16's came early on and were
followed by the PIC18's. Both are a bit dated at this point. The PIC24's and
dsPIC33's are actually very similar parts. The PIC33's form a third family
pretty much on their
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 but
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
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
If you have enough software development experience then maybe you
don't need the Arduino. It is best if you have none. And as you say,
you need to spend $30 per project.
But you might still consider some kind of flash based chip. These can
download new revisions of your software nearly
Hi
If you are going to code on a cheap PIC (the PIC16 series) you will likely need
to learn PIC assembler. All my coding on those parts was in assembly language.
They are old enough / slow enough / small RAM enough that things like C (or the
other high level languages you listed) really don't
On 5/25/13 10:55 AM, Chris Albertson wrote:
3) the Pi is almost PC-like and very easy to use. Costs about $40
and requires a HDMI or DVI monitor..
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
*Jim Lux*
S*at May 25 16:53:50 EDT 2013*
* 3) the Pi is almost PC-like and very easy to use. Costs about $40***and
requires a HDMI or DVI monitor..
A $9 USB to 3.3V serial adapter connects to
the serial console unless you prefer ssh or VNC.
Likewise the Beaglebone.
Le 25 mai 2013 à 22:53, Jim Lux a écrit :
On 5/25/13 10:55 AM, Chris Albertson wrote:
3) the Pi is almost PC-like and very easy to use. Costs about $40
and requires a HDMI or DVI monitor..
If you don't need graphics it runs fine headless using putty to ssh into.
(http://www.pololu.com/catalog/product/1300).
Bob LaJeunesse
From: Chris Albertson albertson.ch...@gmail.com
To: Discussion of precise time and frequency measurement time-nuts@febo.com
Sent: Sat, May 25, 2013 4:15:33 PM
Subject: Re: [time-nuts] Good (cheap) PIC
3) the Pi is almost PC-like and very easy to use. Costs about $40
and requires a HDMI or DVI monitor..
It's got an ethernet. You can ssh in to it from your PC. Headless is the
buzzword.
It may be easier to get started if you plug in a display and keyboard.
Even with graphics it works fine (I think it works better) headless using X or
VNC
Sent from my iPhone
On May 25, 2013, at 17:05, mike cook mc235...@gmail.com wrote:
Le 25 mai 2013 à 22:53, Jim Lux a écrit :
On 5/25/13 10:55 AM, Chris Albertson wrote:
3) the Pi is almost PC-like
I agree with everything below. It is a good argument for AVR. The
AVR was designed specifically wit the needs of the compliter writer in
mind. Because of this C compilers can generate very good AVR code and
there is rarely a good reason to program an AVR in assembly, although
you can.
The
On 5/25/2013 1:22 PM, Bob Camp wrote:
If you are going to code on a cheap PIC (the PIC16 series) you will likely need
to learn PIC assembler. All my coding on those parts was in assembly language.
They are old enough / slow enough / small RAM enough that things like C (or the
other high level
On 25 May 2013, at 15:22, Bob Camp wrote:
If you are going to code on a cheap PIC (the PIC16 series) you will likely
need to learn PIC assembler. All my coding on those parts was in assembly
language. They are old enough / slow enough / small RAM enough that things
like C (or the other
In general PICs need assembly language for many things. AVRs almost
never need assembly. The reason is that the AVR designers studied C
compilers and made the AVR an easy compiler target.
A compiler writer like to have an orthogonal instruction set and
some other features. So the AVR compirrs
Hi
At least on the code I've tried both ways, there's about a 2:1 difference in
what you can get done on a low end PIC with assembly vs C. There are a lot of
things you can get away with in assembler that drive a C compiler a bit nuts….
Bob
On May 25, 2013, at 5:24 PM, Rex r...@sonic.net
Hi
It always depends on what you are trying to do and what you are happy with as a
result. Back when packing lots of stuff into a PIC mattered, the only way I
could get it done (literally millions of lines of code spread across many
dozens of projects) was with assembler. The C compilers that
If you go arm cortex and linux, you will need to make your code a service.
You will want it to start up by itself and if for some reason it crashes, you
will want it to restart itself. The buzzword is harden and the techniques
vary depending on the distribution.
You should check the
On 5/25/13 2:10 PM, Paul wrote:
*Jim Lux*
S*at May 25 16:53:50 EDT 2013*
* 3) the Pi is almost PC-like and very easy to use. Costs about $40***and
requires a HDMI or DVI monitor..
A $9 USB to 3.3V serial adapter connects to
the serial console unless you prefer ssh or VNC.
Once you have
Hi
If you want Linux, you probably also want something like an A9 or better. The
M0 and even the M4's MCU's are not really targeted at Linux. Can you pack it
into a big M4 - sure, it'll be a tight fit and you may not have everything you
really wanted to have. Oddly enough some of the M4's have
I suspect Linux based systems are a few sigma away from the original goal of a
cheap pic choice...:)
But to get back to the original point, you can get samples of most of the PIC
chips from MicroChip for free. I think the limit is 3 per week. Or 30 days, I
don't remember.
Bob
On May 25,
On Sat, May 25, 2013 at 04:03:36PM -0700, Chris Albertson wrote:
In general PICs need assembly language for many things.
AVRs almost never need assembly.
I've done quite a number of PIC projects, from low end
8 bit up to the high end 32 bit controllers, and except
for a really time critical
On Sat May 25 20:18:20 EDT 2013
A $9 USB to 3.3V serial adapter connects to
the serial console unless you prefer ssh or VNC.
Once you have it up and running, sure...
Or maybe, someone has a SD image that you can just dump onto an SD
The Pi, unlike the the Beaglebone Black (BBB) doesn't come
Hi
To *maybe* bring this back to a bit more timing related region of internet
space:
To make any of these parts really do timing stuff (as opposed to simply
display strings) you need some glue. A CPLD or better yet an FPGA can give you
a *lot* of glue for the money. A board with a Cyclone V
On Sat, May 25, 2013 at 08:46:03AM -0500, Jason Rabel wrote:
I've decided I finally want to tackle learning how to use a PIC
chip for some smaller projects. Can someone recommend me a good
(and cheap) PIC, and possible some literature (be it a book or
website)? I have a fairly recent willem
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
The Pi has virtually no IOs, not good for any embedded system.
The BeagleBone Black on the other hand has plentt of IOs
Didier
Jim Lux jim...@earthlink.net wrote:
On 5/25/13 10:55 AM, Chris Albertson wrote:
3) the Pi is almost PC-like and very easy to use. Costs about $40
and requires a
Hi
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
Hi
If you are putting money into a Microchip programmer, I'd probably head over to
the PIC Kit 3 rather than the 2. It will do debug as well as programming on the
range of parts. Having breakpoints and debug is a *good* thing.
Bob
On May 25, 2013, at 9:44 PM, Herbert Poetzl
Having used PICs since 1990, I've designed them into projects rather
than getting a board like a Parallax or Arduino (either of which are far
more expensive than the chip and the few components required to make it
work) and then shoehorning someone else's board into my project.
Since the late
On Sat, May 25, 2013 at 10:04:59PM -0400, Bob Camp wrote:
Hi
If you are putting money into a Microchip programmer, I'd
probably head over to the PIC Kit 3 rather than the 2. It will
do debug as well as programming on the range of parts.
Unfortunately the command line support is missing in
On Sat, May 25, 2013 at 6:39 PM, Didier Juges shali...@gmail.com wrote:
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
On Sat, May 25, 2013 at 6:39 PM, Didier Juges shali...@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
Nice topic. I learned at bit. One source of info on the PIC is a course book
and
programming kit, programmer, prototype board and components set up by the ARRL.
www.arrl.org
You get all the stuff you need to get going. Software and a integrated
development environment is provided. All in one
I'm surprised not to have seen the picaxe(s) mentioned. cheap enough,
easily programmed, large amount of re-useable code chunks, etc. Not for
production, but good enough for a few-off or individual projects,
cheaper than Arduinos...
Of course, I like New Micros. expensive (relatively) but directly
The Pi has virtually no IOs, not good for any embedded system.
The BeagleBone Black on the other hand has plentt of IOs
Didier
You can see the RPi I/O connections here:
http://elinux.org/RPi_Low-level_peripherals#General_Purpose_Input.2FOutput_.28GPIO.29
58 matches
Mail list logo
