|
From: <an...@ki...> - 2010-07-08 10:09:41
|
Excellent, well done. I am just doing a first trial build of my design for a single sided 644 board. Got the wrong 40 pin dil package width. I guess this is why we do trial builds. I am using 16Mhz crystal though. Something that the arduino folk found ages ago was that certain clock frequencys don't divide down correctly with the provided options to give baud rates that are close enough to the established usuals in terms of error factor. I did'nt follow the discussion in their forums that closely but reference to the issues may still be there. Funnily enough 16Mhz the frequency that the arduino's use was found to be a good match. I have had acceptable results with 20Mhz xtals as well. Cheers Andy Kirby On 08/07/10 05:33, Leon Nathaniel Maurer wrote: > It looks like I've got amforth working (photographic evidence: > http://tinyurl.com/2d7cddx) -- thanks for your help! > > To avoid future problems, I do have a couple related quick questions. The FAQ > notes the default 1MHz clock (8 MHz internal RC clock divided by 8) can be > unreliable and suggests: "Try to maximize the CPU frequency." What are the > symptoms of this problem? Just not being able to get the serial communication > to work? Does it help to use the internal clock but not divide by 8 (giving an > 8MHz clock), or is inaccuracy with the internal clock part of the problem? > > Thanks. > -Leon > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Amforth-devel mailing list > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |