CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to CCS Technical Support
v3.200 Confirmed Bugs

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
prwatCCS



Joined: 10 Dec 2003
Posts: 70
Location: West Sussex, UK

View user's profile Send private message

v3.200 Confirmed Bugs
PostPosted: Tue May 25, 2004 5:18 am     Reply with quote
This topic is a place to post summary details of CONFIRMED bugs in the v3.200 release.

PLEASE only post summaries here when you have a problem CONFIRMED by CCS. It might be usefull to include the CCS reference number in your post.

PLEASE post details of the version (PCW/PCWH) your are using, together with the PIC your are compiling for (PIC12F627 / PIC18F6621 / PIC18F877 etc).

PLEASE keep discussions on the details of any problems in other topics - this thread should be more like the index to any known problems.

thanks
_________________
Peter Willis
Development Director
Howard Eaton Lighting Ltd UK
prwatCCS



Joined: 10 Dec 2003
Posts: 70
Location: West Sussex, UK

View user's profile Send private message

PostPosted: Thu May 27, 2004 11:19 am     Reply with quote
AS yet CCS have not responded in any detail to my bug reports for v3.200.

However they have released a new version.
Quote:

A new release of the CCS C compiler for PICmicro(r) microcontrollers
has been released. The new version is: 3.201

Recent changes include:
3.201 New infrastructure added in 3.200 to support new chips and families has
3.201 caused a large number of problems, The reported problems are fixed in 3.201
3.201 Use with caution, expect a 3.202 on Friday. 3.191 is stable.


They dont specify which Friday, and I dont know what they mean by stable. Once again they fail to detail what the reported problems were. I have not tried v3.191.
_________________
Peter Willis
Development Director
Howard Eaton Lighting Ltd UK
prwatCCS



Joined: 10 Dec 2003
Posts: 70
Location: West Sussex, UK

View user's profile Send private message

PostPosted: Fri May 28, 2004 2:04 am     Reply with quote
v3.200 fails to correctly set BSR register (seen on PIC18F6621)

I have now had my problem with v3.200 confirmed as a bug by CCS

the problem was described in this post
[url]
http://www.ccsinfo.com/forum/viewtopic.php?t=19380
[/url]

Quote:

This message is a reply to CCS e-mail id: 4E6511

The problem you reported has been fixed and will be in the
next compiler release.


Once again, CCS fail to be specific - they dont quote a release number. As my report was sent BEFORE v3.201 was released, and they replied AFTER it was released, and they DONT mention this (or any) problems specifically in the release notes for v3.201, I've no idea which version is worth trying .... Twisted Evil
_________________
Peter Willis
Development Director
Howard Eaton Lighting Ltd UK
C-H Wu
Guest
PostPosted: Fri May 28, 2004 3:34 am     Reply with quote
3.200 confirmed bug: delay_us() for 18F458

Code:
0000                00431 .................... #use delay(clock= 40000000)
0004 0E02           00432 MOVLW  02
0006 5E09           00433 SUBWF  09,F
0008 E20B           00434 BC    0020  <-- 'BC' is now 'BNC' in 3.201.
000A 6AEA           00435 CLRF   FEA


Well, this is not important any more since 3.200 is only a 'beta'.

p.s. Considering the BSR register bug, try 3.187 with #opt 10, its algorithm is different from 3.188 ~ 3.201. They made that mistake since 3.188, and now 3.187 is the only hope! However, 3.187 might have "Problems with very large PIC18 data structures (fixed in 3.189)". Does anyone have a test code for this bug ?
prwatCCS



Joined: 10 Dec 2003
Posts: 70
Location: West Sussex, UK

View user's profile Send private message

PostPosted: Fri May 28, 2004 5:40 am     Reply with quote
v3.200 fails to correctly set BSR register (seen on PIC18F6621)

It would appear that this problem is still seen on v3.201
_________________
Peter Willis
Development Director
Howard Eaton Lighting Ltd UK
Guest
a bug hunter program for 3.201, actually 3.188 ~ 3.201
PostPosted: Sat May 29, 2004 12:10 pm     Reply with quote
Hi, guys:

I finally made a small bug hunter program to show you this bug.

Try it and have fun !

Code:
/* bug_3201_BSR.c          by C-H Wu                        2004/05/30

   This bug exist in PCWH 3.201, 3.200 with default optimization level,
   which is #opt 9, and also 3.188 ~ 3.191 with #opt 10
   
   press '0' or '1' with keyboard using Hyperterminal, then ...
   you will see the BUG pops out !

   After pressing the keyboard with either '0' or '1', due to the
   BSR setting bug when returning from either fun_A() or fun_B(),
   the instruction ... printf(" BUG ! "); ... will be executed,
   
   Using #opt 7 or lower with 3.201 can stop this bug.
*/

#include <18F458.H>

//#opt 10   // for 3.188 ~ 3.191

#fuses HS, PUT, NOLVP, NODEBUG

#use delay(clock= 20000000)
#use rs232(baud = 115200, xmit= PIN_C6, rcv= PIN_C7)

int8    x, y, z;

#locate x = 0x056
#locate y = 0x256
#locate z = 0x356

void fun_A() { x = 1; z = 4; }
void fun_B() { x = 2; z = 5; }
void fun_C() { x = 3; z = 6; }

void main()
{
   int8 mode;

   printf("\r\n\n If you press '0' or '1', then you will see the BUG ! ");

   while ( TRUE )
   {
      x = 7;
      y = 8;
     
      if ( kbhit() )
      {
         putc( mode = getc() );

         if      ( mode == '0' ) fun_A();
         else if ( mode == '1' ) fun_B();
         else if ( mode == '2' ) fun_C();
      }

      y = 0; // making 'x' become ZERO if returning from fun_A() or fun_B()!

      if ( x == 0 ) printf(" BUG ! "); // How can this line be executed ?
   }
}


The good news is 3.187 does not have this bug even with #opt 10.

You can find out what went wrong from the LST file.

Best regards

C-H Wu

p.s. Sorry for violating the guide line for this topic because now I am confident in this finding and there will be of no need waiting for the confirmation from CCS.
C-H Wu
Guest
BSR bug confirmed by CCS, waiting for 3.202 on Tuesday !
PostPosted: Mon May 31, 2004 9:27 pm     Reply with quote
Good news:

Got CCS's reply in less than 48 hours, excellent ! Very Happy

Let's wait and see ... 3.202 is coming in less than 24 hours. Cool

Quote:
This message is a reply to CCS e-mail id: 4E7950

The problem you reported has been fixed and will be in the
next compiler release. 3.202 is expected out Tuesday.

>
> Dear CCS:
>
> Enclosed to you is a demo program to show you the BSR setting bug in PCWH 3.201 with default optimization level,
> and also for the PCWH 3.191 with #opt 10.
>
> Some details are written in the demo program and you can find out what went wrong in the LST file.
>
> Thanks a lot for your careful consideration and support.
>
> Sincerely,
>
> C-H Wu
>
> http://www.ccsinfo.com/forum/viewtopic.php?t=19417&sid=a3bd618aeecfb06a6902ec2cc2fb000a
>
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group