[Sdcc-user] Too stupid for C515C, frust....

[Georg R. <geo...@ui...>]

Good evening!

After a frustrating day I'm looking for some hints and advice. So If you
ever used a SAB80C5XX you might be a good victim ;-).

I tried to get things running on my Phytec dev. board (utilizing a
SAB80C515C, fosc=10Mhz). 

First point: Baud rate. 
I cannot get baud rates above 4800 running using the internal baud rate
generator. How far can the real baud rate be off the desired val so that
it still works? With f_osc=10Mhz I get e.g. 18939 instead of 19200, too
much probably. Ok. But: the Flashtool (the Phytec tool to program the
eeprom from DOS) says it does communication with 19200. How do they
manage?

Second point:
Has a bit diffuse appearance, I don't know exactly what's going on.
Things first work when adding new code fragments or some more complex
code (using not only sfrs and char vars or even a isr routine) things
stop working.
 
I can blink with a port. No problem. 
I added a putchar fn (implemented: a wait for TI flag and setting SBUF);
in the program start initialization for the baud rate generator and
switching on everything.
Strange enough the ser.h or serial.h (with changing the timer rates of
course) didn't work out of the box. 
So characters come out of the thing, using putchar('x'). I also can use
a printf_fast("bla"); fine. (BTW what is the code to make a terminal go
to the *begining* of the next line? "\n" is not enough in my terminal,
it only moves the cursor one line down)
Using printf I only get garbage on the serial port. I vaguely can
remember that I used this fn a long time ago without problems.

So I kept using printf_fast. Trying to write out some numbers with
("%4u", uIntNumber) gives strange results. (or is it %d or %i?) Seems
only to work for chars maximum I get is 255.  I guess it's a small
variant of printf. 

Any ideas. I think all the code in the libs works more or less
flawlessly. So the printf definitely is ok (although not documented, or
is it? ;-)). But what could be my the problem?

I use a compile command:
 sdcc test1.c -I/opt/sdcc-2.3.0/share/sdcc/include/
-L/opt/sdcc-2.3.0/share/sdcc/lib/
And get a nice .ihx file.

I also tried to run the example code that Michael Schmitt has put to
OKR. I also get only garbage output.  (he used --stack-after-data
--large-...) (settings to 4800 baud, which I go working before.)


So long, 

	Georg