View previous topic :: View next topic |
Author |
Message |
emon
Joined: 05 May 2006 Posts: 5 Location: Colorado
|
Hi, any advice for me? |
Posted: Fri May 05, 2006 1:51 pm |
|
|
I am a total newbie:) to C language and am looking at the PIC16F877A Development Kit plus a bunch of books! I have a couple of questions maybes omebody could point me in the right direction...
I want to get the dev board with the plcc pack for my first trys and then move to a better developement board with more options before I go shooting my own board... so,
Is this kit compatable with the picdem 2 board from microchip? I would like to use it for the LCD functionality as well as the ability to use DIP pics.
Can the in circuit programmer program the pics through the picdem board or will i need to use mplab to upload the hex code?
How easy is this to learn for someone who has minimal programming experience with any language but a firm grasp in electronics and microprocessors? I have used Basic a bit and years ago some fortran, but never more than simple intro programs.
Will you guys be nice to me with my stupid question posts!?
Thanks for any advice!! |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Fri May 05, 2006 1:59 pm |
|
|
Here are the two most common choices that you can take
for a development environment with the CCS compiler:
CCS
Compiler with IDE: PCW or PCWH
Hardware Debugger: ICDU-40
Microchip
Compiler: CCS command line (PCM and/or PCH)
IDE: MPLAB
Hardware Debugger: ICD2 |
|
|
emon
Joined: 05 May 2006 Posts: 5 Location: Colorado
|
|
Posted: Fri May 05, 2006 3:45 pm |
|
|
how compatible are they? IE can I buy the whole suite from CCS and then use the Mplab programmer?
I typically would think that using all from one manufactor would be the ideal solution... but am clueless on either product. |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Fri May 05, 2006 3:50 pm |
|
|
The CCS IDE only supports the CCS ICD debugger.
Microchip MPLAB only supports their ICD2 debugger.
You can't use a debugger with the other company's IDE.
Edit:
Now you can use ICD2 with the CCS IDE. See this page for instructions:
http://www.ccsinfo.com/faq.php?page=icd2_real_ice
Last edited by PCM programmer on Mon Sep 15, 2008 1:55 pm; edited 1 time in total |
|
|
emon
Joined: 05 May 2006 Posts: 5 Location: Colorado
|
|
Posted: Fri May 05, 2006 3:54 pm |
|
|
ok Thanks!!
Last quick question... the demo board from microchip should be compatible with CCS right? It appears the same physical connections should be made regardless of which software version you use.
I would like to have both the MC picdemo 2 plus board and the CCS board included with their kit. I just don't want to buy it if it would be useless. And I do want to be able to use something where I can program dip packages or at least program them on an old epic we have and then test in the demo board. |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Fri May 05, 2006 4:11 pm |
|
|
The ICD connector pinout is essentially the same for both boards.
CCS doesn't make their product manuals available for download,
so I can't look at a schematic of their 16F877A development board.
But I think it's likely that pin B3 on the PIC goes to pin 6 on the ICD
connector on that board. The CCS tools use that pin for a software
UART for optional terminal output during debugging.
Microchip doesn't have that feature and there's no connection
between pin B3 of the PIC sockets and the ICD2 connector
on the PICDem2-Plus board. However, you could easily add
a jumper on the back of the board to add support.
But I don't think this back-channel debug terminal output feature
is very important. I wouldn't make a decision just based on it. |
|
|
emon
Joined: 05 May 2006 Posts: 5 Location: Colorado
|
|
Posted: Fri May 05, 2006 5:10 pm |
|
|
sorry more questions...
does CCS C include built in libraries so you can do simple coding such as:
I2CWRITE or LCDOUT for example whereas you do not need to program the specific function each time. I am looking at picbasicpro or this product.
picbasic seems so easy it is hard to imagine it is very powerful. It seems CCS would be a better way to go long term?? Is this an accurate read?
It does seem nice to have the built in libraries... right? |
|
|
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
Posted: Fri May 05, 2006 5:23 pm |
|
|
For a list of all built-in functions, driver source code, and example files,
go to this CCS website page:
http://www.ccsinfo.com/content.php?page=compilers
Click on the links for "built-in functions" and "example programs". |
|
|
Mark
Joined: 07 Sep 2003 Posts: 2838 Location: Atlanta, GA
|
|
Posted: Sat May 06, 2006 8:53 am |
|
|
Also, there is no need to program with the epic programmer. The ICD will program the chip for you. |
|
|
emon
Joined: 05 May 2006 Posts: 5 Location: Colorado
|
|
Posted: Sun May 07, 2006 8:33 am |
|
|
Cool I hadn't found that page!
Thanks a lot for your help. I am placing my order today. |
|
|
Darren Rook
Joined: 06 Sep 2003 Posts: 287 Location: Milwaukee, WI
|
|
Posted: Tue Oct 17, 2006 6:35 am |
|
|
PCM programmer wrote: | Here are the two most common choices that you can take
for a development environment with the CCS compiler:
CCS
Compiler with IDE: PCW or PCWH
Hardware Debugger: ICDU-40
Microchip
Compiler: CCS command line (PCM and/or PCH)
IDE: MPLAB
Hardware Debugger: ICD2 |
Sorry to bring up an old post, but:
Be aware that if you buy just the command line compiler you do not get the RTOS or the ability to create relocatable objects. (The command line compiler can link other objects, but can not create them). _________________ I came, I saw, I compiled. |
|
|
|