Joep Suijs wrote:
> Hi Wayne,
> 
> It seems that we have to dig deeper into this.
> The only cause I can think of is the bit calculation overhead that adds to
> each bit. Hower to verify this, I need time and my tools, which both are
> currently unavailable due to some serious redecoration at home ;)
> However, if you create an issue on googlecode, I'll look into
> serial_software baudrates at lower clock rates some day.
> 

I understand  :-)  Been there done that.

I will create an issue.

> And about INTCON_GIE. This is used to disable interrutps. If your pic
> doesn't have interrupts or you don't use them, you can just define a bit var
> with this name. If your pic has interrupts and you use them, they have to be
> disabled. You can do this yourself (and define the var) or use the
> pseudo-var construct. I can provide you with some sample code if you want.

I looked at the data sheets and 'thought' that I might be able to do 
what you say.  I wasn't sure but 'hoped' that if I mentioned it you 
would suggest a workaround, you are very good at that you know. :-)))

Thanks for your help, again!

Have a nice weekend

Best Regards

Wayne

> 
> Joep
> 
> 2009/11/28 Wayne <[email protected]>
> 
>>  Joep Suijs wrote:
>>> 2009/11/24 Wayne [email protected]
>>>
>>>> Because I did not find any samples of how to use print.jal or format.jal
>>>> with serial_sw_write.  I don't really understand enough to figure that
>> out.
>>>> I would like to know if they would work though.
>>>>
>>> Just init the serial software comms like you do now and use
>> serial_sw_data
>>> as the first param in stead of serial_hw_data.
>>> Haven't tested this, but it should work...
>>>
>> Joep
>>
>>   I am integrating a Maxim DS18B20 into my application and asked on
>> jallist if anyone had a jallib lib they were working on.  I got a
>> response, with a link, to one that Helge<[email protected]> had
>> modified from on that Stef had written back in 2002/4.
>>
>>   In looking at the application I noticed that Helge also had a problem
>> getting 9600 baud with a 4 MHZ clock on a 16c84. He had this in the code
>> const serial_sw_baudrate = 10400 (this is really 9600 baud).
>>
>> I just tried that with the 16f628a_lcd_k107sample.jal. What do you know,
>> the k107 communicates with LCD now with a 4 MHZ Crystal.
>>
>> I am reporting this but wish I had the answer as to why this works.  I
>> also hope that someone else wanting to work at 9600 baud can use the
>> information above.
>>
>>   I still can't use it on the 12f509 due to the lack of INTCON_GIE
>> which is required by the serial_software.jal lib but sure would like to.
>>  :-)
>>
>> Best Regards
>>
>> Wayne
>>
>> --
>>
>> You received this message because you are subscribed to the Google Groups
>> "jallib" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected]<jallib%[email protected]>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/jallib?hl=en.
>>
>>
>>
> 
> --
> 
> You received this message because you are subscribed to the Google Groups 
> "jallib" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/jallib?hl=en.
> 
> 
> 

--

You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en.


Reply via email to