On 06/05/2011 01:45 PM, Erich Waelde wrote:
>
>> Thanks, Neal! Nice if there were one for the Uno. ;(
>>
> The only difference in handling between the duemilanove
> and the uno is the name of the serial device, on Linux
> at least:
>
> /dev/ttyUSB (duemilanove)
> /dev/ttyACM (uno)
>
> as I hav
On 06/05/2011 01:45 PM, Erich Waelde wrote:
>
>> Thanks, Neal! Nice if there were one for the Uno. ;(
>>
> The only difference in handling between the duemilanove
> and the uno is the name of the serial device, on Linux
> at least:
>
> /dev/ttyUSB (duemilanove)
> /dev/ttyACM (uno)
>
> as I hav
> Thanks, Neal! Nice if there were one for the Uno. ;(
>
The only difference in handling between the duemilanove
and the uno is the name of the serial device, on Linux
at least:
/dev/ttyUSB (duemilanove)
/dev/ttyACM (uno)
as I have posted to the list before (21.March.2011)
Cheers,
Erich
--
On 05/31/2011 05:56 PM, Neal Crook wrote:
>
> How to build amforth-4.4 images for an arduino using AVR Studio 5.0
>
> 12. locate the file appl/arduino/duemilanove.asm (or the correct name for your
> target arduino) and copy it to the project folder; rename it to
Thanks, Neal! Nice if there were
> It was my understanding that you want to
> check the proper working of the inner interpreter
> in a watchdog like manner.
no watchdog
> That is a profiling system. What do you want to
> profile? Number of calls? Time? Both? Something
> else?
To start simple I wanted to see the inner interprete
Hi Pito,
>> You could use the timer interrupt since any
>> (forth-written) ISR is handled by it.
>
> Could you clarify a little bit?
It was my understanding that you want to
check the proper working of the inner interpreter
in a watchdog like manner.
> Currently my leds are switched on/off in
