Playing With PIC Pack
Contents
Starting Off
Pic Pack is an interesting library of PIC C code for BoostC and has an accompanying set of tutorials. I can be found using the links below. I have wanted to try it out for a while, here is my experience ( so far )
Author russ_hensel
I recording some experiences playing with pic pack.
Not linked into Open Circuits may do so later.
could not find beginning of blog, best I got was part 13, googling let me find welcome finally got the archive for 08 to open,
I am using BoostC 6.90 unlimited non-commercial on a pretty much up to date XP system
First 4 parts
07 April 2008 -- 1. Introduction
07 April 2008 -- 2. Microcontrollers
07 April 2008 -- 3. Take your pic
Make sense to me, just read them.
07 April 2008 -- 5. Your first pic program
Jan 11 2009:
- text said: adventures\flasher: try instead: demos\flasher think this it was moved.
- no mention of target, i left it at: 16f88 ( target is part of the project, so of course it was right for the text.
- I tried to build, IDE said building... but then nothing? I am using 6.90
tried compile and got error locating the compiler, so I pointed the IDE to mine. Problem was I do not keep my compiler in the normal location, all users shuld check this setting if the build just seems to hang.
- Then had error finding: C:\Source\Electronics\MicroController\Pic\PicPack\demoCopy\flasher\flasher.c(7): Unable to open include file: pic_utils.h
This is because I had moved the project, need to keep the relative locations of... demos and ...pic_pack_lib unchanged so I put a copy in the right relative location.
- Now compiles successfully.
but got the warning
#ifndef GOT_CLOCK #warning "Don't know about your clock. See pic_utils.h" #endif
This seems to be related to lack of definition of PLATFORM_CLOCK == 12000000. Perhaps this is what should be in flasher.c instead of ( or in addition to ) #pragma CLOCK_FREQ 8000000 Or perhaps it is just a warning to be ignored.
- note that
/* */
in the code denotes a comment ( and that the contents is ignored by the compiler).
6. Chip Programming
I am going to try an 18f2550 so looking up the config for it
I am confused about config1, 2.... and the high and low so how do I read the .h file?
seems that for the 18F2550 we need
_CONFIG1L, _CONFIG1H, _CONFIG2L, ....
this seems at least to compile .... but the linker fails with
Error: .obj or .lib file wrong target type
Error: Failed to process:pic_utils.obj
perhaps i am still missing some sort of config or #define switch
Problem fixed by removing all but ._c .c and .h files and recompiling, changing target from 16F to 18F was probably the problem.
This took me a long time, 16 config locations, not sure I have them right, perhaps if i copied from some bootloader that worked on my chip?
7. Bootloading
do not want to use 16f88, do not have one, will use either the 18f2550 or if I have to the 16F877 which I have a lot of and have used a lot.
Good night for now....
8
9
[http://embeddedadventures.blogspot.com/2008/04/8-its-about-time.html
14 April 2008 9. It's about time
19 April 2008 11. It's hot in here
22 April 2008 13. It's about time
[ part1x]
[ part1x]
