Re: [Amforth] measuring time

[Matthias T. <mt...@we...>]

Hi,

> But here we go:
> Whats wrong with the following simple test code:

looks innocent (haven't tried it however)

> The result on my arduino uno is quite inconsistent, but mostly I see:
> 
> 3 TCCR0B c!
> does not hang the system, but does not tick either.
> 
> 4 TCCR0B c!
> hangs system, had to re-flash amforth
> often also takes my /dev/ttyACM0 down and I have to reboot linux
> (which looks to me like a linux kernel issue).
> 
> 5 TCCR0B c!
> reset?
> The system starts to print the boot message interruptet by some
> bytes of garbage and endlessly repeats that.

Are the numbers behind the T-labels correct (memory mapped addresses,
somewhere around $40ff) for the Atmega328p? I did something
similiar for the atmega16 without any trouble.

Otherwise it looks like you're programming
the wrong controller. Loosing the ACM device is really
strange, need-to-reflash by writing a single byte is
very unusual as well.


Matthias