Do you have access to an oscilloscope? If so, I would connect to the
pc->micro data line, and look to see if the pc is sending anything.
If it is not, then I would look at the handshake lines.
If the pc is sending characters but the micro is not seeing them, that is
a different problem.
But firs
>
> Dear AmForthers,
>
>
> I'm quite certain, that many of you have noticed...
Ah, that explains the silence, and I'm s glad someone is picking up
the torch! We'll miss Matthias, but life goes on.
___
Amforth-devel mailing list for http://amforth.
I would say that your idea is feasible with the existing toolchain, if
your business model is adjusted a little bit:
1) You must sell the user TWO programmed chips, with instructions making
it very clear a chip can be bricked by a bug.
2) Along with the two chips, the instructions "when you brick
I think people mainly use the atmel studio tools, either under windows,
windows in a VM, or maybe under wine. We're past the days when an
XP-or-better machine costs used car money, after all. 50 bux will get you
something that still runs, even if linux is your first love.
> Message: 2
> Date: Mon,
I've thought about this issue, and have concluded that it's rather simple,
if you are building your own hardware, and you are willing to be a little
bit tricky.
Receiving data too fast from an atmel generally isn't the problem, as I'm
assuming your PC can handle incoming data as fast as it can tra
