MCF5213 UART Scrams -- Also is tech support on a holiday??

[JimD]

This is the message that I sent to tech support 5 days ago (10/26/06).  I have not been assigned anyone to at least answer acknowledge this problem.  I have been told that other compiler error that I found may be rectified in version. It better the problem is that while loops have a problem changing values that they shouldn't.   That could be a major problem with the three projects that I am working on.   I think that we should be able to at least look at a bug list of codewarrior problems so we can make sure they don't jump up and bite someone in the a??.  

My Current Problem is the following.

While UART(0) is outputting I am looking for a kyeboard input on UART(0) to change to the next calibration routine. During this period the program scrams and leave the program in an error loop. (Output: Registered #5) I don't know what causes it all the routines are very very basic. I have included a project that has everything needed to cause this problem.

The value comes from the asm exception handler.  Registered #5 IS NOT MUCH information to go on.  Anyone else have this problem let me know.   I will owe you a dinner.

Just enter the key '?' a few time and it will scram.

I made a video of what happens. 

http://www.dgroup.com/onavi/index.html


Chip: Coldfire 5213

Codewarrior 6.3 build 14
CPU set to 64Mhz
Baud Rate 9600

[lambtron]

Are you using uart interrupts?  If so, is there a separate isr for char transmit and receive?  Also, is your application multi-threaded?

[JimD]

No, Just the regular prinf routines. I turns off all the interrupts. I can see losing characters but scramming is not workable. Tech support has looked at the problem and has sent it to a higher level. This allways happens to me. I can find the problem in any product.

[lambtron]

It sounds like you are running a single-thread that runs a loop that (1) does a printf, and then (2) checks for keypress.  When a keypress is detected, the key is immediately fetched and processed so that it will not pend while you are doing other things with uarts.  No other threads are running that have anything to do with uart activity.  Is this correct?

[JimD]

Yes that is what is happening? 

[Nouchi]

Hello,

I have a look to your video, and it seems to be caused by a Divide by 0 exception (exception #5), thanks to mcf5xxx_exception_handler.


Emmanuel

[JimD]

You are RIGHT!!!   Give that man a silver dollar !!!   DIVIDE BY ZERO-ERROR was the problem.       I owe you a beer or dinner your choice.  If you are ever in San Diego, CA  send me an email.

I called a function that had a division in it that was zero because the sensor that I am using is not attached to the ADC.   Wow that was really stupid.  !!!  Thanks for your help again.

[Nouchi]

Hi,

I'll take a beer..... a virtual beer, because San Diego it's a little bit far from home (france).


Emmanuel