From: Mark M. <m.m...@gm...> - 2011-10-05 12:35:10
|
Thanks for that suggestion! Obvious next step. As it turns out, there's nothing "stable" coming out of the TXD(pin 3) - in fact on some resets it latches to vcc... ? although I also got a nice pulse train on another reset - but mostly I see nothing! So need to investigate those issues. I assembled a plain vanilla amforth 4.5 using the example template and appturnkey files... assume if all is well that will give me a simple forth prompt so further assuming my issue is hardware or the fuse bytes. On Tue, Oct 4, 2011 at 8:44 PM, D Nyberg <dny...@at...> wrote: > On 10/4/2011 10:43:00 AM, Mark Malmros (m.m...@gm...) wrote: > > What am I missing? > > > > I am attempting to put amforth on a Atmega328p following more or less > the > > Amforth Users Guide (which was written for Amforth 4.2). I am working > > from > > Linux. > ... > > Can you put a scope or even just a logic probe in capture mode on the > uart pins, to see if they're being wiggled at all? If so, then the speed > field of the fuse bits may be where you should be looking. I had some > difficulty with this on a 324. I eventually brute forced it by trying > many settings until I got console I/O that looked right. I still have > no idea why the value I settled on is the correct one. > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amf...@li... > https://lists.sourceforge.net/lists/listinfo/amforth-devel > |