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 <jimlux@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 HDMI or DVI monitor.. > > >_______________________________________________ >time-nuts mailing list -- time-nuts@febo.com >To unsubscribe, go to >https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >and follow the instructions there. -- Sent from my Motorola Droid Razr 4G LTE wireless tracker while I do other things.

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 <herbert@13thfloor.at> wrote: > 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 eprom programmer that >> I'm hoping I can use. > > Microchip has good product selection tools like this one: > http://www.microchip.com/maps/microcontroller.aspx > (note the plus signs on the right side of each section) > >> I don't know what all the features PICs have, but for my first >> project I would like to have it connected to a serial port on >> one of my Soekris' where it can grab info (i.e. the current >> time, or NTP/GPS info) and output that on a little LED display. > > Depending on the type of LED display you have in mind, you > want to have PWM capabilities (multiplexing) and high > current source/sink, as well as an (E)U(S)ART for the serial > communication. > > A four digit LED display can be easily controlled by a > PIC16F1503 (price about 0.8 USD, 14 pins) and the required > documents are available on the Microchip site: > http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en553475 > > You can do the UART part in software for low data rates > or simply take the PIC16F1508/9 which already includes > an EUSART (price about 1.3 USD, 20 pins) > > One programmer for many PIC chips (8 bit to 32 bit) is > the PICkit2 which can be bought for less than 30 USD > (via usb, works fine on Linux and MacOS as well) > > HTH, > Herbert > >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there.

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 the PICkit 3, although there was/is an efford to make the 'new' PICkit 3 compatible with the PICkit 2. (as usualy, marketing decisions ... :) And the PICkit 2 can do all the debugging the PICkit 3 does plus it can work as UART and Logic Analyzer as well. > Having breakpoints and debug is a *good* thing. Depends, using breakpoints and/or debug on time critical stuff (like software PWM or UART) usually results in unexpected results, more often it is simpler to add one or more LEDs to display a state or do 'printf' style debugging via serial (UART/I2C/SPI). But as always, YMMV. best, Herbert > Bob > On May 25, 2013, at 9:44 PM, Herbert Poetzl <herbert@13thfloor.at> wrote: >> 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 eprom programmer that >>> I'm hoping I can use. >> Microchip has good product selection tools like this one: >> http://www.microchip.com/maps/microcontroller.aspx >> (note the plus signs on the right side of each section) >>> I don't know what all the features PICs have, but for my first >>> project I would like to have it connected to a serial port on >>> one of my Soekris' where it can grab info (i.e. the current >>> time, or NTP/GPS info) and output that on a little LED display. >> Depending on the type of LED display you have in mind, you >> want to have PWM capabilities (multiplexing) and high >> current source/sink, as well as an (E)U(S)ART for the serial >> communication. >> A four digit LED display can be easily controlled by a >> PIC16F1503 (price about 0.8 USD, 14 pins) and the required >> documents are available on the Microchip site: >> http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en553475 >> You can do the UART part in software for low data rates >> or simply take the PIC16F1508/9 which already includes >> an EUSART (price about 1.3 USD, 20 pins) >> One programmer for many PIC chips (8 bit to 32 bit) is >> the PICkit2 which can be bought for less than 30 USD >> (via usb, works fine on Linux and MacOS as well) >> HTH, >> Herbert >>> _______________________________________________ >>> time-nuts mailing list -- time-nuts@febo.com >>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there.

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 Hardly "virtually no IOs", and some of the pins can be re-assigned. Cheers, David -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk

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 <herbert@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 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 the > PICkit 3, although there was/is an efford to make the 'new' > PICkit 3 compatible with the PICkit 2. > (as usualy, marketing decisions ... :) > > And the PICkit 2 can do all the debugging the PICkit 3 > does plus it can work as UART and Logic Analyzer as well. > >> Having breakpoints and debug is a *good* thing. > > Depends, using breakpoints and/or debug on time critical > stuff (like software PWM or UART) usually results in > unexpected results, more often it is simpler to add one > or more LEDs to display a state or do 'printf' style > debugging via serial (UART/I2C/SPI). > > But as always, YMMV. > > best, > Herbert > >> Bob > >> On May 25, 2013, at 9:44 PM, Herbert Poetzl <herbert@13thfloor.at> wrote: > >>> 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 eprom programmer that >>>> I'm hoping I can use. > >>> Microchip has good product selection tools like this one: >>> http://www.microchip.com/maps/microcontroller.aspx >>> (note the plus signs on the right side of each section) > >>>> I don't know what all the features PICs have, but for my first >>>> project I would like to have it connected to a serial port on >>>> one of my Soekris' where it can grab info (i.e. the current >>>> time, or NTP/GPS info) and output that on a little LED display. > >>> Depending on the type of LED display you have in mind, you >>> want to have PWM capabilities (multiplexing) and high >>> current source/sink, as well as an (E)U(S)ART for the serial >>> communication. > >>> A four digit LED display can be easily controlled by a >>> PIC16F1503 (price about 0.8 USD, 14 pins) and the required >>> documents are available on the Microchip site: >>> http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en553475 > >>> You can do the UART part in software for low data rates >>> or simply take the PIC16F1508/9 which already includes >>> an EUSART (price about 1.3 USD, 20 pins) > >>> One programmer for many PIC chips (8 bit to 32 bit) is >>> the PICkit2 which can be bought for less than 30 USD >>> (via usb, works fine on Linux and MacOS as well) > >>> HTH, >>> Herbert > >>>> _______________________________________________ >>>> time-nuts mailing list -- time-nuts@febo.com >>>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>> and follow the instructions there. >>> _______________________________________________ >>> time-nuts mailing list -- time-nuts@febo.com >>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. > >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there.

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 marketed as an 'improved' version, and all new software was geared toward the 'new' PICkit 3, despite the fact that it is inferior to the PICkit 2 in almost all regards Recent updates to the PICkit 3 made it more and more compatible with the PICkit 2 but it is still missing certain features like the uart or logic analyzer. Just google for a comparison (PICkit 2 vs PICkit 3) to get an idea :) Best, Herbert > Bob > On May 25, 2013, at 10:20 PM, Herbert Poetzl <herbert@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 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 the >> PICkit 3, although there was/is an efford to make the 'new' >> PICkit 3 compatible with the PICkit 2. >> (as usualy, marketing decisions ... :) >> And the PICkit 2 can do all the debugging the PICkit 3 >> does plus it can work as UART and Logic Analyzer as well. >>> Having breakpoints and debug is a *good* thing. >> Depends, using breakpoints and/or debug on time critical >> stuff (like software PWM or UART) usually results in >> unexpected results, more often it is simpler to add one >> or more LEDs to display a state or do 'printf' style >> debugging via serial (UART/I2C/SPI). >> But as always, YMMV. >> best, >> Herbert >>> Bob >>> On May 25, 2013, at 9:44 PM, Herbert Poetzl <herbert@13thfloor.at> wrote: >>>> 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 eprom programmer that >>>>> I'm hoping I can use. >>>> Microchip has good product selection tools like this one: >>>> http://www.microchip.com/maps/microcontroller.aspx >>>> (note the plus signs on the right side of each section) >>>>> I don't know what all the features PICs have, but for my first >>>>> project I would like to have it connected to a serial port on >>>>> one of my Soekris' where it can grab info (i.e. the current >>>>> time, or NTP/GPS info) and output that on a little LED display. >>>> Depending on the type of LED display you have in mind, you >>>> want to have PWM capabilities (multiplexing) and high >>>> current source/sink, as well as an (E)U(S)ART for the serial >>>> communication. >>>> A four digit LED display can be easily controlled by a >>>> PIC16F1503 (price about 0.8 USD, 14 pins) and the required >>>> documents are available on the Microchip site: >>>> http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en553475 >>>> You can do the UART part in software for low data rates >>>> or simply take the PIC16F1508/9 which already includes >>>> an EUSART (price about 1.3 USD, 20 pins) >>>> One programmer for many PIC chips (8 bit to 32 bit) is >>>> the PICkit2 which can be bought for less than 30 USD >>>> (via usb, works fine on Linux and MacOS as well) >>>> HTH, >>>> Herbert >>>>> _______________________________________________ >>>>> time-nuts mailing list -- time-nuts@febo.com >>>>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>>> and follow the instructions there. >>>> _______________________________________________ >>>> time-nuts mailing list -- time-nuts@febo.com >>>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>> and follow the instructions there. >>> _______________________________________________ >>> time-nuts mailing list -- time-nuts@febo.com >>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions 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 like the Pi is a better toy if one wants to hook up a keyboard and monitor, but the BBB is a better tool for embedded systems. I am also bothered by the closed nature of the RPi while the BBB is completely open. The RPi has sold many times more units, so there is more info and more resources also on the net. For a beginner wanting to learn, the RPi is probably a better choice. Didier David J Taylor <david-taylor@blueyonder.co.uk> wrote: >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 > >Hardly "virtually no IOs", and some of the pins can be re-assigned. > >Cheers, >David >-- >SatSignal Software - Quality software written to your requirements >Web: http://www.satsignal.eu >Email: david-taylor@blueyonder.co.uk > >_______________________________________________ >time-nuts mailing list -- time-nuts@febo.com >To unsubscribe, go to >https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >and follow the instructions there. -- Sent from my Motorola Droid Razr 4G LTE wireless tracker while I do other things.

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 there's less to learn. Here's an example of a circuit that has 12 LEDs all driven from 4 PIC pins. http://www.prc68.com/I/PRC68COM.shtml#12LED This is an LCD clock and it uses the PIC 16F88 and is interrupt based, where assembly coding is mandatory because every machine cycle is critical in how the interrupts are handled. This is a "time nuts" clock where the external frequency reference is the heartbeat of the micro controller. The time can be set to a millisecond (the 1 PPS output is as good as the reference oscillator) and the date functions go back to fifteen hundred something as well as day of the week. http://www.prc68.com/I/PRC68COM.shtml#07092006 Have Fun, Brooke Clarke http://www.PRC68.com http://www.end2partygovernment.com/2012Issues.html 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 eprom programmer that I'm hoping I > can use. > > I don't know what all the features PICs have, but for my first project I would like to have it connected to a serial port on one of > my Soekris' where it can grab info (i.e. the current time, or NTP/GPS info) and output that on a little LED display. > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > >

-- Kenton A. Hoover kenton@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 the other hand, the BeagleBone Black has 96 IOs including several UARTs. I have one of each at the moment, and it seems like the Pi is a better toy if one wants to hook up a keyboard and monitor, but the BBB is a better tool for embedded systems. > > I am also bothered by the closed nature of the RPi while the BBB is completely open. > > The RPi has sold many times more units, so there is more info and more resources also on the net. For a beginner wanting to learn, the RPi is probably a better choice. > > Didier > > > David J Taylor <david-taylor@blueyonder.co.uk> wrote: > > > 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 > > > > Hardly "virtually no IOs", and some of the pins can be re-assigned. > > > > Cheers, > > David > > -- > > SatSignal Software - Quality software written to your requirements > > Web: http://www.satsignal.eu > > Email: david-taylor@blueyonder.co.uk > > > > _______________________________________________ > > time-nuts mailing list -- time-nuts@febo.com > > To unsubscribe, go to > > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > 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@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions 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 like the Pi is a better toy if one wants to hook up a keyboard and monitor, but the BBB is a better tool for embedded systems. I am also bothered by the closed nature of the RPi while the BBB is completely open. The RPi has sold many times more units, so there is more info and more resources also on the net. For a beginner wanting to learn, the RPi is probably a better choice. Didier ================================== Didier, It's easy to use the UART on the RPi for other work, e.g. GPS NMEA, as shown in the descriptions I've previously referenced. Edit a couple of files. Using SSH you can easily access the RPi over the network for test and, if you need it, graphics. I don't think that my latest two have ever had a keyboard or monitor attached. Of course there /are/ differences, and one would choose the device most suited to the task in use. Cheers, David -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk