Re: [PIC] Seeking advice fpr 14-pin PIC

Dwayne Reid <[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.pic
Message-ID <[email protected]>
Hi there, Joel.

Many thanks for suggesting the 16f182x family.  It turns out that I 
have several ICD headers for both 12f1840 and 16f1829.  Although I 
have to rewrite the initialization stuff, I can debug using a PICkit 
3 and not have to re-assign pins for RA0 & RA1.

I will give this a try.

I can then either switch back to the 16f676 or drop in the 14-pin 
variant of the 16f182x family.

Everyone else: I am still seeking suggestions!

Thanks again!

dwayne


At 02:15 PM 12/3/2024, [email protected] wrote:
>Dwayne, I don't have a lot of debugging or emulation tools,
>I prefer to put my chips on boards, start with a simple program, 
>make sure everything works, and work to the final program in steps.
>
>I have ICD3 and PICkit3, PICkit4. But I seldom use them. I started 
>with PICs and other microprocessors decades ago when few of the now
>common tools were available. Most of my chips are 8-bit chips, so I 
>can usually get by without emulation tools.
>My first microprocessor was the RCA CDP1802 almost 50 years ago.
>I like the PIC 16F182x chips. They have built-in debug capabilities, 
>and I can use basically the same chip in 8-pin, 14-pin, or 20-pin chips.
>The same chip with more in-out pins.
>
>good luck with your project.
>
>Joel
>
>On 2024-12-03 14:44, Dwayne Reid wrote:
>>Hi there, Joel.
>>What debug tools work with these chips?  Emulator?
>>Many thanks!
>>dwayne
>>At 01:16 PM 12/3/2024, [email protected] wrote:
>>
>>>Good day Dwayne,
>>>For something more capable than the PIC 16F676, but not much more
>>>complicated, I have been using the PIC 16F1823,4,or 5 chips.
>>>They are 14 pin chips with different amounts of memory.
>>>16F1823       16F1824      16F1825
>>>Flash       2k words      4k words     8k words
>>>EEPROM         246          256          256
>>>RAM            128          256         1024
>>>I have been using these chips for a number of years, I also have a
>>>problem working with "C".
>>>Good luck.
>>>Joel
>>>On 2024-12-03 13:42, Dwayne Reid wrote:
>>>
>>>>Good day to all.
>>>>I am working on a project that currently uses the PIC16F676.
>>>>Although this is a very old PIC, I've done dozens of projects with
>>>>it and I am comfortable with it.
>>>>Unfortunately, it looks like I have pooched my emulator.  I've got
>>>>one pin (RC3) that always reads HI in MPLAB, no matter what the
>>>>actual level is at the pin.  And I do not have any spares of the
>>>>emulator pod nor the DVA module.
>>>>So now this is a good reason to check out modern PIC
>>>>microcontrollers.
>>>>I need something that is easy to emulate and debug.  I write
>>>>pretty much everything in PIC Assembly - I'm sufficiently old that
>>>>my brain simply will not grok "C".
>>>>I have several MPLAB ICE 2000 units and a couple of Real ICE
>>>>units, along with the usual smattering of ICD2, ICD3, PICkit 3.
>>>>Does anyone have any suggestions?  14 pins (this project), 2k
>>>>words, 256 bytes RAM.
>>>>I can't ask this on Stack Exchange because I'm asking for opinions
>>>>and suggestions.
>>>>Many thanks!
>>>>dwayne
>>>>--
>>>>Dwayne Reid   <[email protected]>
>>>>Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
>>>>780-489-3199 voice   780-487-6397 fax   888-489-3199 Toll Free
>>>>www.trinity-electronics.com [1]
>>>>Custom Electronics Design and Manufacturing
>>--
>>Dwayne Reid   <[email protected]>
>>Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
>>780-489-3199 voice   780-487-6397 fax   888-489-3199 Toll Free
>>  www.trinity-electronics.com [1] Custom Electronics Design and
>>Manufacturing
>>Links:
>>------
>>[1] http://www.trinity-electronics.com/


-- 
Dwayne Reid   <[email protected]>
Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
780-489-3199 voice   780-487-6397 fax   888-489-3199 Toll Free
www.trinity-electronics.com
Custom Electronics Design and Manufacturing
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.