> On Mon, May 02, 2005 at 12:56:31PM +0100, Dave Turner wrote:
>> Okays, well I would do this, except whatever I try to send, the
>> computer only recieves lots and lots of ones, which it decodes as 
>> 03h
>> (111), and FF (11111111).  I think there's probably some other 
>> problem
>> than the baud rate.

> Can you take a minute and describe the entire setup please?
>
> What is the clock source? Both type and speed?
> What is the interface between the PIC and the PC?
> How is hyperterm setup?
>
> Then we'll get to the software...

What he says.
But can you also tell us how you are determining that it is sending 
all 1's or whatever?
Have you got an oscilloscope? and
Are you using it to look at the output? and
What do you see.

Also.

Are you sending single bytes, or strings terminated in CR + LF or ... 
?


The more we know about what you are REALLY doing and REALLY seeing the 
better we are liable to be able to help.
My questions tend to be following a slightly different track to those 
relating to software settings.
Knowing the basics of your system is UTTERLY ESSENTIAL to getting 
consistent results, so the software setting line of questioning takes 
precedence to mine of you are after full understanding. My line of 
questions may help you get going faster (maybe not) but then you'll 
still have to go back and find out why it worked.

IF you have an oscilloscope you can work out clock speed either by 
measuring clock output or by toggling a pin low/high/low and then 
working out how low the toggle should take at a given clock speed. 
But, working it all out properly is even better.

If you have a crystal or resonator available that could easily be used 
to control the clock, now may be a good time to use it. You can always 
go back to RC with all its joys once you get things going.

Always remember - this is fun you are having :-) !



        RM 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist