Oops - After rereading your post, I have no idea - my apologies for the false hope
Paul Borgmeier
Salt Lake City, Utah
USA
Oops - After rereading your post, I have no idea - my apologies for the false hope
Paul Borgmeier
Salt Lake City, Utah
USA
Last edited by paul borgmeier; - 12th June 2006 at 20:24.
But, recently, I had a similar problem with the baud rate on a different chip. I had the prototype working consistently and everytime on every board I built. But, all the other chips I managed to program did not work. I thought I had bad chips and tried to reconfigure and play with the settings. Everytime the result was just the same. The very first chip(proto) worked well irrespective of the code changes, the others wouldn't. Finally, I narrowed it down to the baud rate. The divider count was off by 1 count. Since you said that you changed the clock to 40MHz, perhaps you could check on the baud rate settings. Perhaps the 40MHz is off???
Jerson
Hi, Steve
few weeks ago,I read on this forum the PLL clock of the PICs was not working so well ... and was very sensitive to power variations.
...
Alain
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
Does the new one work if you switch from 40MHz to 20MHz?
Thanks Guys
I have come to the conclusion that faster is not necessarily better. I have read and re-read the 18F452 data sheet and my impression is that at 40Mhz I should be using a higher baud rate but years of using GSM modems at 9600 has taught me that this is a safe reliable connection speed.
Bruce I have ordered a 20Mhz Flash Lab and in due course all will be revealed.
Cheers
Gents
The 20Mhz Flash Lab does not work either.
Hmmmmm.
I can make it work, and the 40Mhz also, by entering the telephone number into the HSEROUT instruction.
HSEROUT[34,"0123456789",34,13]
but the way I want it to work and the way it did work was by using a string variable.
HSEROUT[34,STR TelephoneNo\16,34]
The reason I need it to work this way is because a keypad is used to enter or change the telephone numbers to text and also to store them in the onboard EEPROM.
The real curiosity to me is that both of the above instruction work when connected to hyperterminal.
I have upgraded to the latest version of PBP.
This is all very curious.
Has your string TelephoneNo been converted to ASCII first?
Except for the first example being terminated with CR, ASCII conversion
handled in-line, and the number of digits dialed, it looks like both should
work the same.
Does something like his work?
Code:STRING VAR BYTE[6] X VAR BYTE MAIN: FOR X = 0 TO 5 STRING[X] = X + "0" ' convert digits to ASCII NEXT X HSEROUT [34,STR STRING\6,34] DONE: GOTO DONE
Bookmarks