[Help] Bootloader Example CCS C don't work.

[tienchuan]

Hi all.
I have a trouble when try using bootloader of CCS.
I'm using CCS Ver 5.013, PIC16F877A to test it.
I compiled the (ex_bootload.c & ex_bootloader.c ) with change configs follow my hardware as below (for ex_bootload.c & ex_bootloader.c) with no errors:

*

[PCM programmer]

What board are you using to test it ? Post the manufacturer and name
of the board, and post a link to the website for it so we can look at the
board's schematic.

Or, if you made the board, or breadboard circuit by yourself, then post
the schematic on an image hosting website such as
http://www.imageshack.us and post a link to the schematic here.

[tienchuan]

Thanks for your repply!
I'm made the board with schematic as bellow:

Thanks u
_________________
Begin Begin Begin !!!

[PCM programmer]

Your schematic shows jumper J6 to enable a pull-up on Pin A4. You need
to install that jumper. Pin A4 must have a pull-up on it so that the
switch (called J7) can work properly.


Also, I notice you have two jumpers called J6. Is that a mistake ?
Should one of them be called J5 ?

[tienchuan]

Thanks u reply.
My schematic has error, which is double jumper J6, I copied it in Orcad Capture but it don't automatic change.
Yes, I enabled J6 ( jumper below connected with PortA), and enabled J7 to enter bootloader after reset.
I checked again my hardware is connect right follow instructions in exp code.
I don't know where errors excuted in my code.
I uploaded all project code on, Pls u check again for me, thanks u.
http://www.mediafire.com/download/kb95k2pcpeb13n2/bootloader_ccs.rar
_________________
Begin Begin Begin !!!

[PCM programmer]

I tested it, and the CCS bootloader example works on vs. 4.120 (from
the thread where I wrote my explanation). But it doesn't work with
vs. 5.013. I will try to find the problem.

I just compared the files between the two versions. CCS has made a
large number of changes. This will take a while.

I did some testing and vs. 5.013 works with the default PIC in
ex_bootloader.c which is the 16F887. So whatever changes CCS made,
they caused it not to work with a 16F877A. I'll try to find out why.

[tienchuan]

Thanks u
I'm waiting from here to known what errors excuted in code.
..
_________________
Begin Begin Begin !!!

[PCM programmer]

I found the problem. The bootloader doesn't work with the 16F877A with
vs. 5.013 because the program_memory_write() function is buggy. It also
fails with vs. 5.014. I'll wait for comments and then I'll report it to CCS.

Here is the test program:

[Ttelmah]

They seem to have destroyed the memory settings in the device database for several chips.
If you look at the thread about bootloader problems with the 16F1827:

<http://www.ccsinfo.com/forum/viewtopic.php?t=51450>

Here the chip had the memory type set in the database as 64/64, where it needs to be 16/64.

The same has happened with the 877, and the 877A, with the new compilers having the type set as 8/8, when it needs to be 2/2.

It seems to date from a few releases before the V5 compilers. I suspect they rewrote the tables when they added quite a few new chips at this point, and seem to have got a very large percentage of the settings wrong....

Best Wishes

[PCM programmer]

Thanks. I wondered if that was it, but I couldn't check it because I only
have the command line compilers. I just now emailed CCS support and
referred them to this thread and especially to your comment at the end.

[Ttelmah]

Can you verify that your compiler does actually say it is 5.014, 12940 in the listing?....

I've found something odd about the downloads.

I have 4.014, downloaded October 25th.
Lo and behold, look at the listing, and it says it is still 5.013.

Your code fails.

Just pulled a new copy of 5.014, and re-compiled, and your code runs.

This gives 5.014 in the listing.....

It looks as if they may initially put up a 5.014 download, that was actually 5.013. The CCSC file is exactly the same size, but version changes from 5.0.0.423 to 5.0.0.425
The new version still has the database error for the 16F1827.

Aargh.....

[PCM programmer]

Starting with vs. 5, the compiler takes over version control. CCS has a
utility program called "Compiler Version" that you can access in Windows
by going to: Start button / Programs / PIC-C / Compiler version

If run it, and then click the "View other versions" button in the lower right
corner, it will list all versions installed in the c:\Program Files\PICC
directory. You can click on the version that you want to use and it will
be slightly highlighted in bold. Then click the Close Version List button
and then exit by clicking the X box in the upper right corner.

I don't like this feature because it's not always reliable for me. Sometimes,
if I want to revert to some vs. 4.xxx version, I have to open a Command
prompt window and manually wipe out most of the PICC directory.
(Everything except my .crg files, and the Projects folder). I really dislike
how the compiler takes over the version control. I used to be able to
reliably change the version just by re-installing the version I want.
Now, I can no longer trust it. This is a whole topic in itself, and maybe
deserves its own thread. My problems may be due to using the
command line compilers. You have the full IDE.


With regard to vs. 5.014, I downloaded it again just now (for command
line compilers pcm and pch) and did a binary file compare in a Command
prompt window with the files I downloaded on November 6, 2013. They
match. There are no differences.

I re-installed pcm vs. 5.014 and looked at the Compiler Version utility
and it says only vs. 5.014 is installed. That's as expected. I then compiled
and ran my test program in MPLAB vs. 8.91. It works in the MPSIM
simulator. That's unexpected. So I ran it on a PicDem2-Plus board
and it failed as noted in my previous post. Only the 4th word is written.
I don't normally use MPSIM to test hardware processes. I am a little
surprised that it works there. The .LST file shows vs. 5.014.

Are you testing in MPLAB simulator or in hardware ?

[PCM programmer]

CCS just emailed me and said they have fixed the problem with
write_program_memory() and it will be in the next release, vs. 5.015.

[Ttelmah]

Just as an update to this, on the 16F1827 at least we can blame Microchip....

Their original data sheet for the chip has the settings 'right', but the current version lists the chip as having 32word write latches, not 8. However the example program correctly only writes 8....

Talk about making it easy.

CCS have said they have also corrected this one now.

Best Wishes

[PCM programmer]

I installed the new version, vs. 5.015, and tested it with Exbootloader.c
with a 16F877A and it works.

It also works with my test program above. Both these tests were done
on a PicDem2-Plus board.