Thread: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

amforth is an extendible interpreter on microcontrollers

Brought to you by: erwaelde, mtrute

amforth-devel

[Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-13 22:01:15

Hello folks!

I have an Arduino Uno that, as far as I can tell, works fine; it's run a
few sample sketches from the Arduino IDE, although I've not tested it
hard enough to entirely rule out a chip failure.

Anyway, from a freshly downloaded and extracted amforth 4.8 zip file, I
have run the following commands:

avrdude -c usbtiny -p atmega328p -U efuse:w:0x5:m

avrdude -c usbtiny -p atmega328p -U hfuse:w:0xd9:m

avrdude -c usbtiny -p atmega328p -U lfuse:w:0xff:m

avrdude -c usbtiny -p atmega328p -U
flash:w:amforth-4.8/appl/arduino/duemilanove.hex

avrdude -c usbtiny -p atmega328p -U
eeprom:w:amforth-4.8/appl/arduino/duemilanove.eep.hex

These have all programmed and verified, although the eeprom write has
the following worrying message:


-------------------------------B<-------------------------------
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e950f
avrdude: reading input file "amforth-4.8/appl/arduino/duemilanove.eep.hex"
avrdude: input file amforth-4.8/appl/arduino/duemilanove.eep.hex auto
detected as Intel Hex
avrdude: writing eeprom (82 bytes):

Writing |                                                    | 0% 0.00s
avrdude: error: usbtiny_send: Connection timed out (expected 82, got -110)
Writing | ################################################## | 100% 1.11s

avrdude: 82 bytes of eeprom written
avrdude: verifying eeprom memory against
amforth-4.8/appl/arduino/duemilanove.eep.hex:
avrdude: load data eeprom data from input file
amforth-4.8/appl/arduino/duemilanove.eep.hex:
avrdude: input file amforth-4.8/appl/arduino/duemilanove.eep.hex auto
detected as Intel Hex
avrdude: input file amforth-4.8/appl/arduino/duemilanove.eep.hex
contains 82 bytes
avrdude: reading on-chip eeprom data:

Reading | ################################################## | 100% 0.10s



avrdude: verifying ...
avrdude: 82 bytes of eeprom verified

avrdude: safemode: Fuses OK

avrdude done.  Thank you.
-------------------------------B<-------------------------------

What's with the "avrdude: error: usbtiny_send: Connection timed out
(expected 82, got -110)" that then seems to work fine the second time?
It verifies OK in the end, however...

So, I run up a minicom on the USB serial port at 9600 baud and when I
press reset on the arduino board I see:

amforth 4.8 ATmega328P Forthduino
 >

If I press enter I get ok prompts:

 >
  ok
 >
  ok
 >
  ok
 >
  ok
 >
  ok
 >
  ok
 >

All working, right? So I try my standard FORTH test:

 > 1 1 + .

...and it hangs. No result comes back and the serial link stops echoing.

Press reset and I get the prompt again. COLD works:

amforth 4.8 ATmega328P Forthduino
 > cold
amforth 4.8 ATmega328P Forthduino
 >

If I try "words" I get a mixture of valid-looking output and garbage
characters, then a hang.

Let's try defining a word:

 > : hi ." Hello world " cr ;
: ??

...and the system is again hanging, with no serial echo.

Have I done something wrong? Should I try and rebuild duemilanove.hex
and the eeprom file from scratch? Does anybody have any idea what the
problem could be?

Thanks,

ABS

--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-14 20:21:29

On 06/13/12 23:01, Alaric Snell-Pym wrote:

> Have I done something wrong? Should I try and rebuild duemilanove.hex
> and the eeprom file from scratch? Does anybody have any idea what the
> problem could be?

Gah, I proudly fired up avra and found that it doesn't exactly work out
of the box :-)

However, with the latest avra from git and the latest amforth from svn,
I have managed to assemble an image... there's even a uno.asm now - much
easier to type!

However, it doesn't even get me a prompt now. No serial output when I
reset the AVR...

Does anyone have a *known working* uno.hex and uno.eep.hex that I can try?!?

>
> Thanks,
>
> ABS
>

ABS

--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Jan K. <kro...@ho...> - 2012-06-15 12:12:28

Dear Alaric,

There is a working version in the download of the 4.8 version.
I have try this one before I started to compile my own running version.
When you look into mailing list I had a lot of questions.
With the aswers of the frendly guys on this forum and a lot of patiance I had luck.

The name is not unu but du.....?

If this is not working I will send you my running version.
One thing, I have bought the mkii programmer, and after that I got a running by my own compiled version.

Cheers,

Jan kromhout
Sacharovlaan 3
3223HM Hellevoetsluis-NL

Op 14 jun. 2012 om 22:21 heeft Alaric Snell-Pym <al...@sn...> het volgende geschreven:

> On 06/13/12 23:01, Alaric Snell-Pym wrote:
> 
>> Have I done something wrong? Should I try and rebuild duemilanove.hex
>> and the eeprom file from scratch? Does anybody have any idea what the
>> problem could be?
> 
> Gah, I proudly fired up avra and found that it doesn't exactly work out
> of the box :-)
> 
> However, with the latest avra from git and the latest amforth from svn,
> I have managed to assemble an image... there's even a uno.asm now - much
> easier to type!
> 
> However, it doesn't even get me a prompt now. No serial output when I
> reset the AVR...
> 
> Does anyone have a *known working* uno.hex and uno.eep.hex that I can try?!?
> 
>> 
>> Thanks,
>> 
>> ABS
>> 
> 
> ABS
> 
> --
> Alaric Snell-Pym
> http://www.snell-pym.org.uk/alaric/
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-15 13:01:56

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/15/2012 01:12 PM, Jan Kromhout wrote:
> Dear Alaric,
>
> There is a working version in the download of the 4.8 version.
> I have try this one before I started to compile my own running version.

The one from the 4.8 zipfile works for you? Damn... it must be a problem
with my hardware, then :-)

Exactly what hardware do you have? I have an Arduino Uno, which uses the
same CPU (ATmega328p) as the Duemilanove; the readme.txt in the
appl/arduino directory suggests I use the duemilanove.hex and
corresponding EEPROM, along with the suggested fuse settings.

The duemilanove.hex from amforth-4.8.zip *almost* works; I get a nice
prompt, but it's easily crashed. I think the fact that "words" works
but prints a mixture of garbage and names of words to the screen (always
exactly the same garbage) is telling; it feels to me like the dictionary
is somehow corrupted.

The flash files flashed perfectly to the AVR, and verified back, so my
first thought was a problem in the .hex file, perhaps snuck through if
it was just automatically built as part of the 4.8 release but hadn't
been tested.

I wanted to do my own build with avra to test this hypothesis, and also
to give me a base to work from in diagnosing the problem - if my own
build did exactly the same things, I could extend TURNKEY to call WORDS,
perhaps put a small delay in the loop that prints the words in case the
corruption is actually a serial problem caused by the high speed, and
work from there. But getting a build with avra required me to update to
the latest svn release of amforth for various reasons, and the resulting
code didn't even get me to a prompt...

I think I see two paths going forwards:

 * Dig out a Windows system (or WINE?) and run AVR Studio and thereby
get the official AVR assembler running and try building form the 4.8
release sources, check I get an identical resulting .hex/.eep.hex file,
and then add diagnosis tools to it and investigate from there

 * Sticking with my avra setup, write my own device tests in assembly
(checksum the contents of flash, saturate the serial port, and so on),
and/or put debugging code into COLD and WARM and friends that will flash
the LED on the Arduino board in different patterns, so I can see where
the avra-built hex file hangs by seeing what the last pattern I see
flashed is.

> If this is not working I will send you my running version.

Any known-working .hex and .eep.hex files I can try will be gratefully
recevied, as even if they don't work for me, how far they get may give
me useful clues :-)

> One thing, I have bought the mkii programmer, and after that I got a running by my own compiled version.

Mine's a USBtinyISP. I built it myself from a kit, so it's slightly
suspect (it might not be working properly), but the fact that the flash
and eeprom and fuses read *back* correctly for verification makes me
think it's probably OK.

Thanks for the response :-)

ABS

- --
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/bMjoACgkQRgz/WHNxCGr10ACfSCn9acfKuJFmND+DuejNnTH1
/sMAn1vLuYN/jWFPzhe2i78hH8QLkyf5
=J6Sa
-----END PGP SIGNATURE-----

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Charles S. <sum...@gm...> - 2012-06-15 13:07:06

Personally, I couldn't get avra to work correctly for the uno. It doesn't
seem to be very well supported. I was able to use wine to run the atmel
compiler from avrstudio 4.

On Fri, Jun 15, 2012 at 8:01 AM, Alaric Snell-Pym
<al...@sn...>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06/15/2012 01:12 PM, Jan Kromhout wrote:
> > Dear Alaric,
> >
> > There is a working version in the download of the 4.8 version.
> > I have try this one before I started to compile my own running version.
>
> The one from the 4.8 zipfile works for you? Damn... it must be a problem
> with my hardware, then :-)
>
> Exactly what hardware do you have? I have an Arduino Uno, which uses the
> same CPU (ATmega328p) as the Duemilanove; the readme.txt in the
> appl/arduino directory suggests I use the duemilanove.hex and
> corresponding EEPROM, along with the suggested fuse settings.
>
> The duemilanove.hex from amforth-4.8.zip *almost* works; I get a nice
> prompt, but it's easily crashed. I think the fact that "words" works
> but prints a mixture of garbage and names of words to the screen (always
> exactly the same garbage) is telling; it feels to me like the dictionary
> is somehow corrupted.
>
> The flash files flashed perfectly to the AVR, and verified back, so my
> first thought was a problem in the .hex file, perhaps snuck through if
> it was just automatically built as part of the 4.8 release but hadn't
> been tested.
>
> I wanted to do my own build with avra to test this hypothesis, and also
> to give me a base to work from in diagnosing the problem - if my own
> build did exactly the same things, I could extend TURNKEY to call WORDS,
> perhaps put a small delay in the loop that prints the words in case the
> corruption is actually a serial problem caused by the high speed, and
> work from there. But getting a build with avra required me to update to
> the latest svn release of amforth for various reasons, and the resulting
> code didn't even get me to a prompt...
>
> I think I see two paths going forwards:
>
>  * Dig out a Windows system (or WINE?) and run AVR Studio and thereby
> get the official AVR assembler running and try building form the 4.8
> release sources, check I get an identical resulting .hex/.eep.hex file,
> and then add diagnosis tools to it and investigate from there
>
>  * Sticking with my avra setup, write my own device tests in assembly
> (checksum the contents of flash, saturate the serial port, and so on),
> and/or put debugging code into COLD and WARM and friends that will flash
> the LED on the Arduino board in different patterns, so I can see where
> the avra-built hex file hangs by seeing what the last pattern I see
> flashed is.
>
> > If this is not working I will send you my running version.
>
> Any known-working .hex and .eep.hex files I can try will be gratefully
> recevied, as even if they don't work for me, how far they get may give
> me useful clues :-)
>
> > One thing, I have bought the mkii programmer, and after that I got a
> running by my own compiled version.
>
> Mine's a USBtinyISP. I built it myself from a kit, so it's slightly
> suspect (it might not be working properly), but the fact that the flash
> and eeprom and fuses read *back* correctly for verification makes me
> think it's probably OK.
>
> Thanks for the response :-)
>
> ABS
>
> - --
> Alaric Snell-Pym
> http://www.snell-pym.org.uk/alaric/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk/bMjoACgkQRgz/WHNxCGr10ACfSCn9acfKuJFmND+DuejNnTH1
> /sMAn1vLuYN/jWFPzhe2i78hH8QLkyf5
> =J6Sa
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>



-- 
-chuck
* This sig intentionally left blank *

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-15 13:13:01

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/15/2012 02:06 PM, Charles Summers wrote:
> Personally, I couldn't get avra to work correctly for the uno. It doesn't
> seem to be very well supported. I was able to use wine to run the atmel
> compiler from avrstudio 4.

Interesting... I'd hoped to be able to use avra to avoid downloading a
giant Windows closed-source IDE. Ah well :-)

I'll try the AVRStudio route, then, I think! But it might be interesting
to compare the .hex files it generates and try to find the difference...

ABS

- --
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/bNNEACgkQRgz/WHNxCGrD3QCffJ9grgbQgUN513D+MBvNYMqD
GT4An1G7XyeIipHhPVa1MFSLSlT4f2Ca
=rvYP
-----END PGP SIGNATURE-----

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-15 13:15:06

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Also, I've been pointed at
http://strotmann.de/~cas/download/amforth/hexfiles/ as a source of
prebuilt hexes - I'll try those and see if they tell me anything.

ABS

- --
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/bNU4ACgkQRgz/WHNxCGrK4QCfU9yWjvGMT8T+5aGTmdDI3Uc4
m2wAniD86nnSfZlyVj10vr16OXmOmY7s
=5LuX
-----END PGP SIGNATURE-----

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-18 20:34:16

On 15/06/12 14:14, Alaric Snell-Pym wrote:
> Also, I've been pointed at
> http://strotmann.de/~cas/download/amforth/hexfiles/ as a source of
> prebuilt hexes - I'll try those and see if they tell me anything.

I got the 4.8 hexfile from there working fine!

But I can't let it go without finding out what went wrong before :-) One
clue is that when I first tried flashing the hexes from there I got a
LOT of errors from avrude, about SPI problems, then a verify failure.
Swapping the USB cables over (I use two, one to power the arduino and
one to drive the USBtinyISP) made it a lot better, but I still needed a
few tries before I got one without verify failures. I didn't have any
verify failures when I tried before, but now I think about it, I used a
different USB *port* on my laptop... I will experiment some more.

I'd still like to get avra running and build my own hexes, but that
might be a pipe dream!

Anyway, I've been playing a bit with the amforth I have installed -
making the arduino's debug LED flash, mainly ;-)

I plan to customise it a bit (I've written up a bunch of portpin:
declarations that match the arduino pin names, and I'm working on
adapting the demonstration PWM and ADC code from lib/ into something
that, along with the TWI and SPI drivers, might be a useful wordset for
a "bus pirate" tool, letting me quickly hack around with random devices;
if I get it working to my satisfaction, I'd like to publish my .frt file
and the resulting .hexes for folks to poke into their arduinos to make
SUPER PROGRAMMABLE bus pirate clones. Woo!

ABS

--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Matthias T. <mt...@we...> - 2012-06-19 18:13:37

Hi Alaric,

> But I can't let it go without finding out what went wrong before :-) One
> clue is that when I first tried flashing the hexes from there I got a
> LOT of errors from avrude, about SPI problems, then a verify failure.

Sounds like that you have some SPI devices (SD-Card) connected while
programming the controller.

> I'd still like to get avra running and build my own hexes, but that
> might be a pipe dream!

That would be great indeed.

> Anyway, I've been playing a bit with the amforth I have installed -
> making the arduino's debug LED flash, mainly ;-)
> 
> I plan to customise it a bit (I've written up a bunch of portpin:
> declarations that match the arduino pin names, and I'm working on
> adapting the demonstration PWM and ADC code from lib/ into something
> that,

Erich has written a lot of code for the danger shield. Maybe you
two could collaborate?

Matthias

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-19 20:25:42

On 19/06/12 19:13, Matthias Trute wrote:
> Hi Alaric,
>
>> But I can't let it go without finding out what went wrong before :-) One
>> clue is that when I first tried flashing the hexes from there I got a
>> LOT of errors from avrude, about SPI problems, then a verify failure.
>
> Sounds like that you have some SPI devices (SD-Card) connected while
> programming the controller.

The Arduino itself puts an LED on the SCK line, but isolated from it by
an op-amp buffer, so it shouldn't be a problem - I have nothing else in
parallel with it...

>> I plan to customise it a bit (I've written up a bunch of portpin:
>> declarations that match the arduino pin names, and I'm working on
>> adapting the demonstration PWM and ADC code from lib/ into something
>> that,
>
> Erich has written a lot of code for the danger shield. Maybe you
> two could collaborate?

Sounds good to me!

>
> Matthias
>

ABS

--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/

Re: [Amforth] Problem running amforth 4.8 on an Arduino Uno - am I doing this right?

From: Alaric Snell-P. <al...@sn...> - 2012-06-19 20:40:43

On 19/06/12 21:25, Alaric Snell-Pym wrote:
> On 19/06/12 19:13, Matthias Trute wrote:
>> Hi Alaric,
>>
>>> But I can't let it go without finding out what went wrong before :-) One
>>> clue is that when I first tried flashing the hexes from there I got a
>>> LOT of errors from avrude, about SPI problems, then a verify failure.
>>
>> Sounds like that you have some SPI devices (SD-Card) connected while
>> programming the controller.
>
> The Arduino itself puts an LED on the SCK line, but isolated from it by
> an op-amp buffer, so it shouldn't be a problem - I have nothing else in
> parallel with it...

Having said that, I can easily pop a raw AVR chip into a breadboard and
wire it up to the programmer directly, taking the Arduino board out of
the equation altogether. I might try that.

ABS


--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/

Re: [Amforth] arduino danger shield

From: Erich W. <ew....@na...> - 2012-06-26 16:50:19

Hi Alaric,

On 06/19/2012 10:25 PM, Alaric Snell-Pym wrote:
>>> I plan to customise it a bit (I've written up a bunch of portpin:
>>> >>  declarations that match the arduino pin names, and I'm working on
>>> >>  adapting the demonstration PWM and ADC code from lib/ into something
>>> >>  that,
>> >
>> >  Erich has written a lot of code for the danger shield. Maybe you
>> >  two could collaborate?
> Sounds good to me!
> 

I have used the code below to run a simple test script on newly assembled
danger shields. Missing parts and/or known "bad" code"
a. not properly debouncing the switches
b. the menu logic
c. I have not bothered to properly convert the temperature sensor readings
   into Celsius or so. Please note that the connection details of this sensor
   have changed between board revisions!


Have the appropriate amount of fun.
Erich

-----------------------------------------------------------------------------------
\ 2011-03-06  EW
\ test arduino duemilanove + danger shield rev. 14
\ 2012-02-15  EW  changed for dangershield rev. 16

\ hw layout
\ arduino | atmega328p                | danger shield
\      D0 |        PD0   rx	      | 
\      D1 |        PD1   tx	      |
\      D2 |        PD2   int0	      |
\      D3 |        PD3   int1  oc2b   |   bz      (buzzer)
\      D4 |        PD4   t0	      |   sr_in   (shift register DS)
\      D5 |        PD5   t1    oc0b   |   led1
\      D6 |        PD6         oc0a   |   led2
\      D7 |        PD7		      |   sr_latch (shift register /OE)
\ 				      |
\      D8 |        PB0    icp	      |   sr_clk  (shift register SH_CP)
\      D9 |        PB1         oc1a   |
\     D10 |        PB2    /ss  oc1b   |   sw1     (switch)
\     D11 |        PB3    mosi oc2a   |   sw2     (switch)
\     D12 |        PB4    miso	      |   sw3     (switch)
\     D13 |        PB5    sck	      |
\ 				      |
\      A0 |        PC0    adc0	      |   sl3     (slider)
\      A1 |        PC1    adc1	      |   sl2     (slider)
\      A2 |        PC2    adc2	      |   sl1     (slider)
\      A3 |        PC3    adc3	      |   light   (photo cell)
\      A4 |        PC4    adc4  scl   |   temp    (temperature)
\      A5 |        PC5    adc5  sda   |

\ make marker

marker --start--

decimal

PORTB 2 portpin: sw1
PORTB 3 portpin: sw2
PORTB 4 portpin: sw3

PORTD 5 portpin: led1
PORTD 6 portpin: led2

PORTD 3 portpin: bz

PORTC 2 portpin: sl1
PORTC 1 portpin: sl2
PORTC 0 portpin: sl3

PORTC 3 portpin: photocell
PORTC 4 portpin: thermometer

PORTD 4 portpin: sr_in
PORTD 7 portpin: sr_oe \ output enable
PORTB 0 portpin: sr_cl

variable 1delay  20 1delay !
: msg_quit
  ." press switch 1 (D10) to quit" cr
;


\ --- switches -----------------------------------------------
: sw1? ( -- true|false )
  sw1 pin_low? if       \ if switch1 pressed
    &20 ms              \ { wait a little
    sw1 pin_low? if     \   if switch1 still pressed
      -1                \   { "true" on stack
    else                \   }else
      0                 \   { "false on stack
    then                \   }
  else                  \ }else
    0                   \ { "false" on stack
  then                  \ }
;

\ --- buzzer -------------------------------------------------

\ 2 ms T_period =^= 500 Hz
: buzz ( cycles -- )
  0 ?do bz low 1ms bz high 1ms loop
;

\ --- analog digital converter -------------------------------
\ --- adc ---

: or!   dup c@ rot or swap c! ;

\ pin>pos
\     convert bitmask of portpin: back to value (bitposition)
: pin>pos       ( pinmask portaddr -- pos )
  drop          ( -- pinmask )
  log2          ( -- pos_of_most_significant_bit )
;

: adc.init ( -- )
  \ ADMUX
  \ A_ref is NOT connected externally
  \ ==> need to set bit REFS0 in register ADMUX
  [ 1 5 lshift      \ ADLAR
    1 6 lshift or   \ REFS0
  ] literal ADMUX c!
  \ ADCSRA
  [ 1 7 lshift      \ ADEN   ADC enabled
    1 2 lshift or   \ ADPS2  prescaler = 128
    1 1 lshift or   \ ADPS1  .
    1          or   \ ADPS0  .
  ] literal ADCSRA c!
;
: adc.init.pin ( bitmask portaddr -- )
  over over high
  pin_input
;
  
1 6 lshift constant ADSC_MSK \ ADStartConversion bitmask
: adc.start
  \ start conversion
  ADSC_MSK ADCSRA or!
;
: adc.wait
  \ wait for completion of conversion
  begin
    ADCSRA c@ ADSC_MSK and 0=
  until
;
: adc.channel! ( channel -- )
  7 and                 \ clip channel to 0..7
  ADMUX c@ 7 invert and \ read ADMUX, clear old channel
  or                    \ add new channel
  ADMUX c!              \ write
;
: adc.get10 ( channel -- a )
  adc.channel! adc.start adc.wait
\ 10 bit
  ADCL c@
  ADCH c@ 8 lshift + 6 rshift
;
: adc.get ( channel -- a )
  adc.channel! adc.start adc.wait
\ 8 bit
  ADCH c@
;

\ --- shift register -----------------------------------------

: bit>sr ( bit -- )
  if sr_in high else sr_in low then
  sr_cl high noop sr_cl low noop
;

: get.bit ( byte pos -- bit )
  1 swap lshift    \ -- byte bitmask
  and              \ -- bit
;

\ clock one byte out, MSB first!
: byte>sr ( byte -- )
  8 0 do
    dup 7 i -  \ 7 6 5 ... 0: MSB first!
    get.bit
    bit>sr
  loop
  drop
;

: >7seg
  invert
  byte>sr
  sr_oe low noop sr_oe high
;


create HexDigits
$3f ,  \ 0
$06 ,  \ 1
$5b ,  \ 2
$4f ,  \ 3
$66 ,  \ 4
$6d ,  \ 5
$7d ,  \ 6
$07 ,  \ 7
$7f ,  \ 8
$6f ,  \ 9
$77 ,  \ A
$7c ,  \ b
$58 ,  \ c
$5e ,  \ d
$79 ,  \ E
$71 ,  \ F

$80 constant dec.point
: emit.7seg ( n -- )
  dup 0 $F within if
    HexDigits + @i >7seg
  else
    drop
  then
;

\ --- convert thermometer reading --------------------------


: .T
  thermometer pin>pos adc.get10  . cr
;


\ --- test functions ---------------------------------------
: test_switches
  ." press switch 2,3 to light up led 1,2" cr
  msg_quit

  begin
    sw2 pin_low? if led1 high else led1 low then
    sw3 pin_low? if led2 high else led2 low then
  sw1? until
;

: test_buzzer
  ." press switch 2 (D11) to test buzzer" cr
  msg_quit
  begin
    sw2 pin_low? if 500 buzz then
  sw1? until
;

: test_sliders
  ." move sliders" cr
  msg_quit
  begin
    sl1 pin>pos adc.get 4 u0.r space space
    sl2 pin>pos adc.get 4 u0.r space space
    sl3 pin>pos adc.get 4 u0.r    $0d emit
    1delay @ ms
  sw1? until
  cr
;

: test_photocell
  ." light/shadow photocell" cr
  msg_quit
  begin
    photocell pin>pos adc.get 4 u0.r    $0d emit
    1delay @ ms
  sw1? until
  cr
;

: test_thermometer
  ." warm/cool thermometer" cr
  msg_quit
  begin
    thermometer pin>pos adc.get10 4 u0.r    $0d emit
    1delay @ ms
  sw1? until
  cr
;


: test_bits.7seg
  8 0 do
    1 i lshift >7seg
    500 ms
  loop
;
: test_emit.7seg
  $10 0 do
    i emit.7seg
    500 ms
  loop
;
: test_7seg
  ." show single segments on 7seg" cr
  test_bits.7seg
  1000 ms
  ." show hex numbers on 7seg" cr
  test_emit.7seg
  1000 ms
;

\ --- main: init, run --------------------------------------
: init
  led1 pin_output
  led2 pin_output
  bz   pin_output

  \ set pins to high (internal pullup)
  sw1 high sw1 pin_input
  sw2 high sw2 pin_input
  sw3 high sw3 pin_input
  
  adc.init
  sl1 adc.init.pin
  sl2 adc.init.pin
  sl3 adc.init.pin
  photocell adc.init.pin
  thermometer adc.init.pin

  sr_in high sr_in pin_output
  sr_oe high sr_oe pin_output
  sr_cl low  sr_cl pin_output
  $ff >7seg
;


\ --- pwm: timer/counter0, led1,2 ---
\ D5 | PD5  t1  oc0b | led1
\ D6 | PD6      oc0a | led2
\ timer/counter0
\ fast pwm mode
\ TCCR0A bits
\ .  COM0A[1,0] = 1,0    (non inverted mode)
\ .  COM0B[1,0] = 1,0    (non inverted mode)
\ .  WGM0[1,0]  = 1,1    (mode3: fast pwm)
\ TCCR0B bits
\ .  CS[2,1,0]  = 0,1,1  (clk_io/64)

\ TIMSK0 TIFR0 TCNT0 TCCR0B TCCR0A OCR0B OCR0A

: pwm.leds.init
  0 TCNT0 c! \ clear counter
  led1 high led1 pin_output
  led2 high led2 pin_output
  \ TCCR0A = COM0A1 | COM0B1 | WGM01 | WGM00
  %10100011 TCCR0A c!
  \ TCCR0B = CS1 | CS0
  %00000011 TCCR0B c!
;
\ control brightness via registers
\ OCR0A  (D6)
\ OCR0B  (D5)

: pwm.leds.off
  led1 low led2 low
  0 TCCR0A c!
  0 TCCR0B c!
  0 OCR0A  c!
  0 OCR0B  c!
  0 TCNT0  c!
;

: test_leds_pwm_slider
  ." move sliders to control leds (pwm)" cr
  msg_quit
  pwm.leds.init
  begin
    sl1 pin>pos adc.get 5 -  0 max  OCR0B c!
    sl2 pin>pos adc.get 5 -  0 max  OCR0A c!
    1ms
  sw1? until
  pwm.leds.off
  cr
;


\ --- pwm: timer/counter2, buzzer ---
\ D3 | PD3 int1 oc2b | bz

\ timer/counter2
\ clear timer on compare match, ctc mode
\ TCCR2A bits
\ .  COM2B[1,0] = 0,1    (non inverted mode)
\ .  WGM2[1,0]  = 1,0    (mode2: ctc)
\ TCCR2B bits
\ .  CS[2,1,0]  = 1,1,1  (clk_t2s/256)

\ TIMSK0 TIFR0 TCNT0 TCCR0B TCCR0A OCR0B OCR0A

: pwm.bz.init
  0 TCNT2 c! \ clear counter
  bz high bz pin_output

  \ TCCR2A =  COM0B0 | WGM01 
  %00010010 TCCR2A c!
  \ TCCR2B = CS1 | CS0
  %00000110 TCCR2B c!
;
\ control frequency via register
\ OCR2A
: pwm.bz.off
  0 TCNT2  c!
  0 TCCR2A c!
  0 TCCR2B c!
  0 OCR2A  c!
  0 OCR2B  c!
;
: buzzer_pwm_once
  pwm.bz.init
  $20 OCR2A c!  200 ms
  $30 OCR2A c!  200 ms
  $40 OCR2A c!  200 ms
  $0  OCR2A c!  200 ms
;
: test_buzzer_pwm
  ." press switch 2 (D11) to test buzzer (pwm)" cr
  msg_quit
  begin
    sw2 pin_low? if 500 buzzer_pwm_once then
  sw1? until
  pwm.bz.off
;

: test_bz_pwm_slider
  ." move slider1 to control buzzer (pwm)" cr
  msg_quit
  pwm.bz.init
  begin
    sl1 pin>pos adc.get 5 -  0 max  OCR2A c!
    1ms
  sw1? until
  pwm.bz.off
  cr
;


\ --- --- ---

variable state
9 constant max_state

: run

  init
  0 state !
  20 1delay !

  ." press switch 1 (D10) for next test" cr
  begin

    sw1? if
      state @ 1+
      dup max_state > if drop 0 then 
      dup state !
      . cr
    then

\   state @ 0 =   ( do nothing )

    state @ 1 = if test_switches    then
    state @ 2 = if test_buzzer      then
    state @ 3 = if test_buzzer_pwm  then
    state @ 4 = if test_sliders     then
    state @ 5 = if test_leds_pwm_slider then
    state @ 6 = if test_photocell   then
    state @ 7 = if test_thermometer then
    state @ 8 = if test_7seg  1 state +! then

    \ wait some
    1delay @ 5 * ms

  key? until
  key drop
;

\ fin