Groups > comp.lang.forth > #30977 > unrolled thread

MSP430-Stamp

Started by	rickman <gnuarm@gmail.com>
First post	2014-05-29 21:35 -0400
Last post	2014-07-17 16:09 -0400
Articles	20 on this page of 190 — 24 participants

Back to article view | Back to comp.lang.forth

  MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-29 21:35 -0400
    Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-29 19:09 -0700
      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-29 19:13 -0700
        Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-29 23:00 -0400
          Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-29 20:25 -0700
        Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-29 20:23 -0700
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-29 22:15 -0700
          Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-05-30 15:13 +0200
            Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-30 13:51 -0400
              Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-05-30 21:08 +0200
            Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-30 12:22 -0700
              Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-05-30 21:41 +0200
                Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-30 13:28 -0700
                  Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-30 17:55 -0400
              Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-30 16:29 -0400
                Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-30 14:18 -0700
                  Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-30 18:07 -0400
                    Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-30 17:24 -0700
        Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-02 11:10 +0200
          Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-02 10:57 +0000
            Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-02 13:34 +0200
      Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-29 20:10 -0700
        Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-29 20:29 -0700
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-29 21:02 -0700
      Re: MSP430-Stamp "Rod Pemberton" <dont_use_email@xnothavet.cqm> - 2014-05-30 04:05 -0400
      Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-05-30 15:13 +0200
    Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-29 19:57 -0700
      Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-29 23:32 -0400
        Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-29 21:07 -0700
    Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-05-30 02:39 -0700
      Re: MSP430-Stamp visualforth@rocketmail.com - 2014-07-17 12:40 -0700
        Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-07-17 16:08 -0400
        Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-07-18 00:06 +0200
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-07-18 08:22 -0700
            Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-07-18 23:42 +0200
              Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-07-18 18:28 -0400
                Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-07-19 01:41 +0200
                  Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-07-18 19:48 -0400
                    Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-07-18 16:59 -0700
                    Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-07-19 14:30 +0200
                      Re: MSP430-Stamp Gary Bergstrom <forthprgrmr@gmail.com> - 2014-07-19 08:23 -0700
                    Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-07-21 10:42 +0200
    Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-05-30 03:03 -0700
      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 07:47 -0700
        Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-31 11:36 -0400
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-31 09:34 -0700
            Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 10:09 -0700
              Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-31 10:52 -0700
            Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 01:28 -0400
              Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 22:41 -0700
                Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 02:00 -0400
                  Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 23:07 -0700
                    Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 03:13 -0400
                      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-01 07:15 -0700
                        Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 12:33 -0400
                          Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-01 09:45 -0700
                            Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 13:10 -0400
                        Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-06-01 18:38 +0200
                          Re: MSP430-Stamp babruehl@gmail.com - 2014-06-01 11:40 -0700
              Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-06-01 11:13 +0200
                Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-01 09:50 +0000
                  Re: MSP430-Stamp HaveANiceDay <HaveANiceDay@NoSpam.invalid> - 2014-06-01 12:47 +0200
                    Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-01 04:05 -0700
                Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 12:39 -0400
                  Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-01 10:00 -0700
                    Re: MSP430-Stamp babruehl@gmail.com - 2014-06-01 11:45 -0700
                      Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 14:57 -0400
              Re: MSP430-Stamp "VisualForth.com" <babruehl@gmail.com> - 2014-06-01 12:01 -0700
                Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-01 15:12 -0400
    Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-05-30 03:12 -0700
      Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-30 14:02 -0400
        Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-05-31 03:33 -0700
          Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 07:19 -0700
          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-05-31 12:01 -0400
          Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 09:15 -0700
            Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 13:51 -0700
              Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-05-31 14:20 -0700
                Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 14:51 -0700
                Re: MSP430-Stamp "VisualForth.com" <babruehl@gmail.com> - 2014-05-31 16:22 -0700
            Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-06-01 01:33 +0200
              Re: MSP430-Stamp "Elizabeth D. Rather" <erather@forth.com> - 2014-05-31 17:31 -1000
                Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 21:48 -0700
                  Re: MSP430-Stamp "Elizabeth D. Rather" <erather@forth.com> - 2014-05-31 19:12 -1000
                    Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 22:25 -0700
                  Re: MSP430-Stamp stephenXXX@mpeforth.com (Stephen Pelc) - 2014-06-01 09:45 +0000
                    Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-01 04:16 -0700
                      Re: MSP430-Stamp "Elizabeth D. Rather" <erather@forth.com> - 2014-06-01 08:51 -1000
              Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-05-31 21:03 -0700
                Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-06-01 21:17 +0200
                  Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-04 22:46 -0700
                    Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-05 13:27 +0000
                      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-05 08:39 -0700
                        Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-05 16:10 +0000
                          Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-05 11:10 -0700
                            Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-05 19:52 +0000
                            Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-06-05 23:25 +0200
                              Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-05 15:02 -0700
                              Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-06 10:56 +0000
                            Correct Software and Specifications (was Re: MSP430-Stamp) Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2014-06-09 09:59 +0100
                      Re: MSP430-Stamp mhx@iae.nl - 2014-06-05 14:30 -0700
                        Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-06 10:59 +0000
                    Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-06-05 15:57 +0200
                      Formal specifications etc. (was: MSP430-Stamp) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-06-05 15:34 +0000
                        Re: Formal specifications etc. Paul Rubin <no.email@nospam.invalid> - 2014-06-05 11:48 -0700
                          Re: Formal specifications etc. anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2014-06-05 19:46 +0000
                        Re: Formal specifications etc. (was: MSP430-Stamp) Bernd Paysan <bernd.paysan@gmx.de> - 2014-06-05 23:02 +0200
                          Re: Formal specifications etc. Paul Rubin <no.email@nospam.invalid> - 2014-06-05 14:15 -0700
                            Re: Formal specifications etc. rickman <gnuarm@gmail.com> - 2014-06-05 17:33 -0400
                              Re: Formal specifications etc. Paul Rubin <no.email@nospam.invalid> - 2014-06-05 15:32 -0700
                            Re: Formal specifications etc. Andrew Haley <andrew29@littlepinkcloud.invalid> - 2014-06-06 04:00 -0500
                          Re: Formal specifications etc. (was: MSP430-Stamp) albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-06 11:05 +0000
                      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-05 11:01 -0700
                        Re: MSP430-Stamp Bernd Paysan <bernd.paysan@gmx.de> - 2014-06-06 01:09 +0200
                          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-05 22:01 -0400
          Re: MSP430-Stamp stephenXXX@mpeforth.com (Stephen Pelc) - 2014-05-31 16:47 +0000
      Re: MSP430-Stamp visualforth@rocketmail.com - 2014-05-30 12:11 -0700
      Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-06 12:54 +0200
    Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-02 11:39 +0200
      Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-02 12:15 -0400
        Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-03 10:26 +0200
          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-03 12:18 -0400
      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-02 10:04 -0700
        Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-03 11:51 +0200
          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-03 13:33 -0400
            Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-06 13:02 +0200
              Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-06 17:31 -0400
                Re: MSP430-Stamp "Elizabeth D. Rather" <erather@forth.com> - 2014-06-06 16:30 -1000
                  Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-06 22:52 -0400
                  Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-07 11:58 +0000
                Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-07 11:40 -0700
                  Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-07 20:01 -0400
                    Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-08 16:05 -0700
                      Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-08 22:28 -0400
                        Re: MSP430-Stamp Gary Bergstrom <forthprgrmr@gmail.com> - 2014-06-08 20:36 -0700
                        Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-08 21:38 -0700
                          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-09 14:36 -0400
                        Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-09 02:45 -0700
                          Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-09 03:18 -0700
                          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-09 15:57 -0400
                    Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-08 16:20 -0700
          Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-03 20:42 -0700
            Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-03 21:05 -0700
              Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-04 10:43 +0000
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-03 21:28 -0700
          Re: MSP430-Stamp "VisualForth.com" <babruehl@gmail.com> - 2014-06-03 22:43 -0700
            Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-03 23:31 -0700
              Re: MSP430-Stamp "VisualForth.com" <babruehl@gmail.com> - 2014-06-04 04:13 -0700
      Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-03 01:41 -0700
        Re: MSP430-Stamp Paul Rubin <no.email@nospam.invalid> - 2014-06-03 01:51 -0700
          Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-03 16:19 +0100
            Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-03 09:14 -0700
            Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-03 13:19 -0400
              Re: MSP430-Stamp "Elizabeth D. Rather" <erather@forth.com> - 2014-06-03 07:43 -1000
                Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-03 20:56 -0700
                  Re: MSP430-Stamp albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-06-04 10:51 +0000
                    Re: MSP430-Stamp VisualForth <babruehl@gmail.com> - 2014-06-04 04:06 -0700
    Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-06 21:26 -0400
      Re: MSP430-Stamp "VisualForth.com" <babruehl@gmail.com> - 2014-06-06 20:40 -0700
        Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-07 03:18 -0700
    Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-07 04:35 -0700
      Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-07 12:01 -0700
        Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-09 03:47 -0700
          Re: MSP430-Stamp Mikael Nordman <oh2aun@gmail.com> - 2014-06-09 09:28 -0700
            Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-11 07:35 -0700
              Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-11 10:43 -0700
                Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-11 15:52 -0700
                  Re: MSP430-Stamp Coos Haak <chforth@hccnet.nl> - 2014-06-12 02:06 +0200
                    Re: MSP430-Stamp "Elizabeth D. Rather" <erather@forth.com> - 2014-06-11 15:13 -1000
                    Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-12 02:16 -0700
              Re: MSP430-Stamp Mikael Nordman <oh2aun@gmail.com> - 2014-06-11 12:56 -0700
          Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-09 16:46 -0400
        Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-09 03:49 -0700
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-09 09:47 -0700
      Re: MSP430-Stamp Rikard Lang <rikard.lang@gmail.com> - 2014-06-09 23:16 +0200
        Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-10 07:48 -0700
          Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-11 07:23 -0700
            Re: MSP430-Stamp David Schultz <abuse@127.0.0.1> - 2014-06-11 18:00 -0500
              Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-12 02:14 -0400
                Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-12 02:13 -0700
                  Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-12 13:04 -0400
                    Re: MSP430-Stamp David Schultz <abuse@127.0.0.1> - 2014-06-12 18:06 -0500
                      Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-12 19:29 -0400
                        Re: MSP430-Stamp David Schultz <abuse@127.0.0.1> - 2014-06-13 18:48 -0500
        Re: MSP430-Stamp Mark Wills <markwills1970@gmail.com> - 2014-06-11 07:26 -0700
          Re: MSP430-Stamp visualforth@rocketmail.com - 2014-06-11 10:45 -0700
    Re: MSP430-Stamp JUERGEN <epldfpga@aol.com> - 2014-06-13 00:03 -0700
      Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-18 11:11 +0200
        Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-06-18 05:27 -0400
          Re: MSP430-Stamp Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-06-18 12:29 +0200
            Re: MSP430-Stamp rickman <gnuarm@gmail.com> - 2014-07-17 16:09 -0400

Page 8 of 10 — ← Prev page 1 … 6 7 [8] 9 10 Next page →

#31182

From	Paul Rubin <no.email@nospam.invalid>
Date	2014-06-03 20:42 -0700
Message-ID	<7xoay9z6fk.fsf@ruckus.brouhaha.com>
In reply to	#31172

Matthias Koch <matthias.koch@hot.uni-hannover.de> writes:
> Mecrisp contains Ledcomm sources both in assembly and Forth,

Oh that is very interesting, I had a similar idea a while back and
wondered whether it could work.  Yes it seems worth implementing.

> I want to introduce "Visolate" and its "Voronoi Toolpaths" to give a
> pleasant looking board:

That is neat too!  I guess it could be done with conventional photo
etching.  Presumably you want to use a regular board shop.

> * Who is writing basic commented Forth and inlined assembly examples ?
> Mecrisp already contains an assembler, but this doesn't fit into
> G2553.

You mentioned using the 2955 but if SMT and slightly higher cost is ok,
I suggest considering the MSP430FR5969 whose unique feature is 64k of
FRAM.  It also has DSP extensions which would allow teaching a bit about
signal processing.  Plus it has a 32x32 hw multiplier and AES extension
so it can be used for public and secret key cryptography.

> I am offering hints on board schematic design and I volunteer in
> porting Mecrisp to the board arriving in my snail mail giving Forth a
> launch.

I think one main idea of 4e4th is to work with Dirk's IDE, which may
also rely on Camelforth at the target.

[toc] | [prev] | [next] | [standalone]

#31185

From	visualforth@rocketmail.com
Date	2014-06-03 21:05 -0700
Message-ID	<3fc107a7-94dd-4814-9682-a1f992dfe456@googlegroups.com>
In reply to	#31182

On Tuesday, June 3, 2014 11:42:39 PM UTC-4, Paul Rubin wrote:

> I think one main idea of 4e4th is to work with Dirk's IDE, 

Thanks, Paul! I would be delighted to support these boards with the 4E4th-IDE!

> which may
> also rely on Camelforth at the target.

The 4E4th-IDE can be used as a general terminal, especially for command oriented microprocessor targets. All Forth are welcome. To get most of it, there should be support from the target, and that is 4e4th doing (CamelForth doesn't support special 4E4th-IDE features). The main feature 4e4th has is a special prompt enhanced with a base (hex, decimal, etc.) coding to synchronize the 4E4th-IDE to the 4e4th base. This is necessary for support of Constants and the cross-assembler to send values to the target using the right base.

[toc] | [prev] | [next] | [standalone]

#31194

From	albert@spenarnc.xs4all.nl (Albert van der Horst)
Date	2014-06-04 10:43 +0000
Message-ID	<538ef834$0$4687$e4fe514c@dreader36.news.xs4all.nl>
In reply to	#31185

In article <3fc107a7-94dd-4814-9682-a1f992dfe456@googlegroups.com>,
 <visualforth@rocketmail.com> wrote:
>On Tuesday, June 3, 2014 11:42:39 PM UTC-4, Paul Rubin wrote:
>
>> I think one main idea of 4e4th is to work with Dirk's IDE,
>
>Thanks, Paul! I would be delighted to support these boards with the 4E4th-IDE!
>
>> which may
>> also rely on Camelforth at the target.
>
>The 4E4th-IDE can be used as a general terminal, especially for command
>oriented microprocessor targets. All Forth are welcome. To get most of
>it, there should be support from the target, and that is 4e4th doing
>(CamelForth doesn't support special 4E4th-IDE features). The main
>feature 4e4th has is a special prompt enhanced with a base (hex,
>decimal, etc.) coding to synchronize the 4E4th-IDE to the 4e4th base.
>This is necessary for support of Constants and the cross-assembler to
>send values to the target using the right base.

The alternative noforth has the assembler running right on the board.
http://home.hccnet.nl/anij/nof/noforth.html
(There is a separate document .pdf about the assembler, but it is fair
to say it is frugal.)
The new "C&V" version accomodates larger and newer versions of the
MSP430.

Groetjes Albert
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

[toc] | [prev] | [next] | [standalone]

#31188

From	visualforth@rocketmail.com
Date	2014-06-03 21:28 -0700
Message-ID	<3a2b6e7f-7172-4c29-83d8-db561434d404@googlegroups.com>
In reply to	#31172

On Tuesday, June 3, 2014 5:51:29 AM UTC-4, Matthias Koch wrote:
> > Can you say what the optical link is for?
> 
> Together with a coil and a large capacitor you can seal your project for underwater usage and still have a communications channel even in heavy electrical noise. It can also serve as an ESD-proof debug terminal remaining in projects that have no electrical communication connector otherwise in their final form and use the LED for human signaling at the same time. It is time to introduce the uncommon feature that a LED connected with both anode and cathode to a microcontroller can serve for communication. It won't increase the board cost, but gives one interesting example to try out of the box. If not used for communication, a LED connected with both wires can serve as ambient light sensor.

Looks like this LED Interface is the cheapest Interface possible!
Am I right?

> Exactly. But we need a chip we are comfortable with to finally get this board off the ground with the people available.
> Let's settle for MSP430 for now. To continue, we need to get organisation done. Open Hardware and GPL3 licenced software only. We start when all seats are filled.

Volunteers requested!

> Board design:
> * We need to collect what parts need to be included. Goodfet is a good start. The Tinkerlog headers are a convenient idea.
> * Who is doing schematic design ?
> * Who is doing hardware design and board layout ? Needs an eye for beauty, too.

That's my volunteering offer: hardware design and board layout.
Recently I had the idea to start an exhibition with my 25 years of pcb layouts (through hole, SMT, single, double, multi layer) - to me they look like artwork.

> * Who volunteers to do a prototype run ? 

A prototype run is no problem for me, as long as there are through hole parts only (lack of infrastructure on the country side) and a range of 3 to 15 prototypes.

> Maybe we can contact http://43oh.com/ for help in this step.
> * Who is responsible for manufacturing later ?

Best wishes,
Dirk

P.S.: If we make a bunch of boards, these will be boards always operate by themselves or boards operation in concert. The latter can be established by this LED-Interface (like a bunch of Fireflies) or with a Bus System. There are several Bus-Systems available. My favorite is the Universal EXTension (UEXT) Bus which is an open-project that is royalty-free: 
http://en.wikipedia.org/wiki/UEXT

[toc] | [prev] | [next] | [standalone]

#31190

From	"VisualForth.com" <babruehl@gmail.com>
Date	2014-06-03 22:43 -0700
Message-ID	<badd0382-4498-41fe-9404-3de3d85baae8@googlegroups.com>
In reply to	#31172

On Tuesday, June 3, 2014 5:51:29 AM UTC-4, Matthias Koch wrote:
> To continue, we need to get organization done.

What about self-organization?

That works!
I am in production of a little gadget - bookkeeping and special parts support is done in China by a Chinese Citizen, public relations and sales is done in Texas by an American, and production is done in Pennsylvania by a German Citizen. A "multinational company", connected through the Internet.

My suggestion:
We call our MSP430-Stamp TOPIC now "MSP430-Task-Forth".
Members of our MSP430-Task-Forth are Makers or Thinkers.
The Makers do all the development work, designing, hardware, software - the Thinkers do suggestions, critics, testing.

Using these divisions, everybody is able to participate, no one left behind.
If somebody changes lines, no problem.

The only rule to observe: everybody who has made a commitment, should stay with his commitment, to stabilize our "business". If somebody recognizes that for whatever reason he/she is not able to fulfill his commitment, he/she has to announce this, and it would be helpful if he/she helps to find another person to fill in.

When our first board is done as a prototype, our business will grow. May be there will be some revenue even. In my "multinational business" we do the following: the salesperson prepays the material, and the difference between sales price and material is divided by the number of participants. This is how it works with us three. These lines here are only to report about a functioning "business model", it has been selected to show that we are all equal. And it works, since three years now.

[toc] | [prev] | [next] | [standalone]

#31192

From	Paul Rubin <no.email@nospam.invalid>
Date	2014-06-03 23:31 -0700
Message-ID	<7x4n01xk17.fsf@ruckus.brouhaha.com>
In reply to	#31190

"VisualForth.com" <babruehl@gmail.com> writes:
> We call our MSP430-Stamp TOPIC now "MSP430-Task-Forth".
> Members of our MSP430-Task-Forth are Makers or Thinkers.
> The Makers do all the development work, designing, hardware, software ...

Wait, what happened to Simon's board?  Wasn't that how this got started?

[toc] | [prev] | [next] | [standalone]

#31197

From	"VisualForth.com" <babruehl@gmail.com>
Date	2014-06-04 04:13 -0700
Message-ID	<9974534d-54eb-4b1c-86f8-44b65bcd898f@googlegroups.com>
In reply to	#31192

On Wednesday, June 4, 2014 2:31:48 AM UTC-4, Paul Rubin wrote:
> "VisualForth.com" writes:

> > We call our MSP430-Stamp TOPIC now "MSP430-Task-Forth".
> > Members of our MSP430-Task-Forth are Makers or Thinkers.
> > The Makers do all the development work, designing, hardware, software ...
> 
> Wait, what happened to Simon's board?  Wasn't that how this got started?

Simon's board is still there, at TOPIC "Go Forth and Prosper", and there are waiting still the same donors for your support at https://www.indiegogo.com/projects/go-forth-and-prosper

This thread is named "MSP430-Stamp", even if words don't matter.
Are you with us?

[toc] | [prev] | [next] | [standalone]

#31169

From	Paul Rubin <no.email@nospam.invalid>
Date	2014-06-03 01:41 -0700
Message-ID	<7xmwdujsgp.fsf@ruckus.brouhaha.com>
In reply to	#31147

Matthias Koch <matthias.koch@hot.uni-hannover.de> writes:
> MSP430G... - either socketed DIP MSP430G2553 or stronger SMD MSP430G2955.

This might be of interest, a small $5.00 MSP430G2955 board (Launchpad
booster pack):

 http://store.43oh.com/index.php?route=product/product&product_id=115

[toc] | [prev] | [next] | [standalone]

#31170

From	Paul Rubin <no.email@nospam.invalid>
Date	2014-06-03 01:51 -0700
Message-ID	<7x4n021im8.fsf@ruckus.brouhaha.com>
In reply to	#31169

Paul Rubin <no.email@nospam.invalid> writes:
>  http://store.43oh.com/index.php?route=product/product&product_id=115

Note it is just the PCB, you have to supply your own cpu and other parts
and solder them on.

[toc] | [prev] | [next] | [standalone]

#31173

From	Mark Wills <markwills1970@gmail.com>
Date	2014-06-03 16:19 +0100
Message-ID	<lmkp29$qpd$1@dont-email.me>
In reply to	#31170

On 03/06/2014 09:51, Paul Rubin wrote:
> Paul Rubin <no.email@nospam.invalid> writes:
>>   http://store.43oh.com/index.php?route=product/product&product_id=115
>
> Note it is just the PCB, you have to supply your own cpu and other parts
> and solder them on.
>

I think I'm losing track of this thread! Can anyone in the know 
attempt a summary of where we are? Is any kind of consensus 
developing?

[toc] | [prev] | [next] | [standalone]

#31174

From	visualforth@rocketmail.com
Date	2014-06-03 09:14 -0700
Message-ID	<24c09dcc-aff0-4091-a299-ee7d616c0b74@googlegroups.com>
In reply to	#31173

On Tuesday, June 3, 2014 11:19:38 AM UTC-4, Mark Wills wrote:
> On 03/06/2014 09:51, Paul Rubin wrote:
> > Paul Rubin <no.email@nospam.invalid> writes:
> >>   http://store.43oh.com/index.php?route=product/product&product_id=115

> > Note it is just the PCB, you have to supply your own cpu and other parts
> > and solder them on.

> I think I'm losing track of this thread! Can anyone in the know 
> attempt a summary of where we are? Is any kind of consensus 
> developing?

Read Matthias posting  5:51 AM (6 hours ago)- that shows the way!
Did you find a seat for yourself?
I found some - I will report later.

[toc] | [prev] | [next] | [standalone]

#31176

From	rickman <gnuarm@gmail.com>
Date	2014-06-03 13:19 -0400
Message-ID	<lml02b$noh$1@dont-email.me>
In reply to	#31173

On 6/3/2014 11:19 AM, Mark Wills wrote:
> On 03/06/2014 09:51, Paul Rubin wrote:
>> Paul Rubin <no.email@nospam.invalid> writes:
>>>   http://store.43oh.com/index.php?route=product/product&product_id=115
>>
>> Note it is just the PCB, you have to supply your own cpu and other parts
>> and solder them on.
>>
>
> I think I'm losing track of this thread! Can anyone in the know attempt
> a summary of where we are? Is any kind of consensus developing?

That is the problem with this thread.  We have not agreed on the 
starting goals and features we want in a board or even if a board is 
needed.  So there is not much point in discussing alternatives.

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#31178

From	"Elizabeth D. Rather" <erather@forth.com>
Date	2014-06-03 07:43 -1000
Message-ID	<KoSdnaadzui4lBPOnZ2dnUVZ_tGdnZ2d@supernews.com>
In reply to	#31176

On 6/3/14 7:19 AM, rickman wrote:
> On 6/3/2014 11:19 AM, Mark Wills wrote:
>> On 03/06/2014 09:51, Paul Rubin wrote:
>>> Paul Rubin <no.email@nospam.invalid> writes:
>>>>   http://store.43oh.com/index.php?route=product/product&product_id=115
>>>
>>> Note it is just the PCB, you have to supply your own cpu and other parts
>>> and solder them on.
>>>
>>
>> I think I'm losing track of this thread! Can anyone in the know attempt
>> a summary of where we are? Is any kind of consensus developing?
> 
> That is the problem with this thread.  We have not agreed on the 
> starting goals and features we want in a board or even if a board is 
> needed.  So there is not much point in discussing alternatives.
> 

Exactly. To be successful, you need goals, strategy, and marketing plan.
Describe your target customers, what their needs and interests are, and
how you will reach them with your message. With that definition in hand,
you can then determine what technology you need (hardware, software,
documentation).

Technology-driven projects ("I want to build this cool thing because
surely other people will love it!") are doomed. In this case, you
started out with a goal to "popularize Forth" and then focussed entirely
on hardware. A sales proposition "Forth on board" will not sell, because
there is no demand. "An easy-to-program, inexpensive board with great
instructional materials" is potentially a much more salable proposition,
but keep your eye on the user-perceived value.

Cheers,
Elizabeth

-- 
==================================================
Elizabeth D. Rather   (US & Canada)   800-55-FORTH
FORTH Inc.                         +1 310.999.6784
5959 West Century Blvd. Suite 700
Los Angeles, CA 90045
http://www.forth.com

"Forth-based products and Services for real-time
applications since 1973."
==================================================

[toc] | [prev] | [next] | [standalone]

#31184

From	visualforth@rocketmail.com
Date	2014-06-03 20:56 -0700
Message-ID	<90cb2881-5144-48a4-810d-a017f4ae5826@googlegroups.com>
In reply to	#31178

On Tuesday, June 3, 2014 1:43:02 PM UTC-4, Elizabeth D. Rather wrote:

> Technology-driven projects ("I want to build this cool thing because
> surely other people will love it!") are doomed.

Somebody should have told this to the Maker Movement Freaks.
I am sure they didn't know, like the Bumblebee doesn't know that she can't fly - aero dynamics say this.

I am wondering how companies like SparkFun, Olimex, Energia, Adafruit (the Maker Lady) and others do exist. They shouldn't - they did everything wrong.

> In this case, you
> started out with a goal to "popularize Forth" and then focussed entirely
> on hardware. 

This is a discussion. Different people have different views.

> A sales proposition "Forth on board" will not sell, because
> there is no demand.

There is no demand for all the stuff that ThinkGeek is selling: http://www.thinkgeek.com/
There was neither another company nor demand, so they started producing and selling that stuff.

> "An easy-to-program, inexpensive board with great
> instructional materials" is potentially a much more salable proposition,
> but keep your eye on the user-perceived value.

Great! 
Let's start with users like us.

[toc] | [prev] | [next] | [standalone]

#31195

From	albert@spenarnc.xs4all.nl (Albert van der Horst)
Date	2014-06-04 10:51 +0000
Message-ID	<538efa31$0$4687$e4fe514c@dreader36.news.xs4all.nl>
In reply to	#31184

In article <90cb2881-5144-48a4-810d-a017f4ae5826@googlegroups.com>,
 <visualforth@rocketmail.com> wrote:
>On Tuesday, June 3, 2014 1:43:02 PM UTC-4, Elizabeth D. Rather wrote:
>
>> Technology-driven projects ("I want to build this cool thing because
>> surely other people will love it!") are doomed.
>
>Somebody should have told this to the Maker Movement Freaks.
>I am sure they didn't know, like the Bumblebee doesn't know that she
>can't fly - aero dynamics say this.
>
>I am wondering how companies like SparkFun, Olimex, Energia, Adafruit
>(the Maker Lady) and others do exist. They shouldn't - they did
>everything wrong.

You don't interpret the remark correctly.
Probably Elizabeth is right in the sense that capitalism has reached
an end point. Renovation efforts will actively be thwarted by how the
market place works nowadays. In the Netherlands we have a
farmaceutical industry closed down. Some hedge funds had enough money
to buy the whole stuff for "intellectual property" and closed down the
facility that generated ip for decennia.
Talking about killing the goose that lays the golden eggs...

But the internet gives interesting opportunities, like crowd funding
and small groups finding each other, producing at a very minimal
scale and still have world wide distribution.
A new horizon opens, that is where *you* are right.

Groetjes Albert
-- 
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- being exponential -- ultimately falters.
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

[toc] | [prev] | [next] | [standalone]

#31196

From	VisualForth <babruehl@gmail.com>
Date	2014-06-04 04:06 -0700
Message-ID	<2f48ad6b-6e26-4631-8f0b-9310d2f1a4ad@googlegroups.com>
In reply to	#31195

On Wednesday, June 4, 2014 6:51:29 AM UTC-4, Albert van der Horst wrote:
>  <visualforth.com> wrote:
> >On Tuesday, June 3, 2014 1:43:02 PM UTC-4, Elizabeth D. Rather wrote:
> 
> >> Technology-driven projects ("I want to build this cool thing because
> >> surely other people will love it!") are doomed.

> >Somebody should have told this to the Maker Movement Freaks.
> >I am sure they didn't know, like the Bumblebee doesn't know that she
> >can't fly - aero dynamics say this.
> >I am wondering how companies like SparkFun, Olimex, Energia, Adafruit
> >(the Maker Lady) and others do exist. They shouldn't - they did
> >everything wrong.
> 
> You don't interpret the remark correctly.
> Probably Elizabeth is right in the sense that capitalism has reached
> an end point. Renovation efforts will actively be thwarted by how the
> market place works nowadays. In the Netherlands we have a
> farmaceutical industry closed down. Some hedge funds had enough money
> to buy the whole stuff for "intellectual property" and closed down the
> facility that generated ip for decennia.
> Talking about killing the goose that lays the golden eggs...

I don't care.
I am using and promoting Forth because one day people will be happy that they can understand important software instead of trying to decipher cryptographic mesh.

> But the internet gives interesting opportunities, like crowd funding
> and small groups finding each other, producing at a very minimal
> scale and still have world wide distribution.
> A new horizon opens, that is where *you* are right.

Thanks for your support, Albert!
Herzliche Gruesse, 
Dirk.

[toc] | [prev] | [next] | [standalone]

#31253

From	rickman <gnuarm@gmail.com>
Date	2014-06-06 21:26 -0400
Message-ID	<lmtpse$26o$1@dont-email.me>
In reply to	#30977

On 5/29/2014 9:35 PM, rickman wrote:
> The thread "Go Forth And Prosper" has gotten quite long and this is a
> diversion, so I am discussing it here.
>
> Perhaps Dirk can explain a bit what the purpose of this board is and why
> each of the features is important, especially the $4 price tag.  I
> honestly can't think how any board, even as a kit, could be sold for $4.
>   But I just want to hear the basis for the feature set of the board.

This has been batted around a bit and a number of divergent subthreads 
popped up and I still am not clear on the purpose of this idea.

I think before we discuss any details of the design or even if we are 
going to design a board, I think we should figure out the purpose we are 
trying to fill.

I believe Dirk would like this to be an educational project.  I assume 
to teach programming, in particular Forth programming.  Others seem to 
want the project to be about providing some hardware they can't 
otherwise find.  Others yet seem to feel it is about making some "cool" 
hardware.  What part of this can we agree on or can we do all of the 
above?  Are there other goals?

-- 

Rick

[toc] | [prev] | [next] | [standalone]

#31257

From	"VisualForth.com" <babruehl@gmail.com>
Date	2014-06-06 20:40 -0700
Message-ID	<dc042fb7-80f4-41cc-af4c-af7a4b69fa54@googlegroups.com>
In reply to	#31253

On Friday, June 6, 2014 9:26:35 PM UTC-4, rickman wrote:
> 
> I believe Dirk would like this to be an educational project.  I assume 
> to teach programming, in particular Forth programming.  

That's true. For two reasons: we can only spread the use of Forth if there are more Forth programmers who like what they are doing - for this education is needed. Second, some day people will be happy that software code is readable and understandable in the first place, being sure what these commands are doing - for this education is needed.

Let's treat your next arguments the Forth way with some factoring, to have smaller chunks which are easier to digest!

> Others seem to 
> want the project to be about providing some hardware they can't 
> otherwise find.  

Great idea, that may be done with the same effort, and as a plus, it's a demo about what Forth is good for.

> Others yet seem to feel it is about making some "cool" 
> hardware.  

Great idea, that may be done with the same effort, and as a plus, it's a demo about what Forth is good for.

> What part of this can we agree on or can we do all of the 
> above?  

To me this seems to be all one task.
If the result is showing that several boards are asked for, the more the better. 
Let's do it.
Let's diversify.
We are enough people to get a lot of stuff done. 
Let's start with one part, let's learn from this, others will follow.

> Are there other goals?

Good question to the audience ...
Don't hesitate to answer!

Cheers,
Dirk.

[toc] | [prev] | [next] | [standalone]

#31262

From	Mark Wills <markwills1970@gmail.com>
Date	2014-06-07 03:18 -0700
Message-ID	<37687bfe-6751-4f75-b829-ffe02256a195@googlegroups.com>
In reply to	#31257

On Saturday, 7 June 2014 04:40:24 UTC+1, VisualForth.com  wrote:
> On Friday, June 6, 2014 9:26:35 PM UTC-4, rickman wrote:
> 
> > 
> 
> > I believe Dirk would like this to be an educational project.  I assume 
> 
> > to teach programming, in particular Forth programming.  
> 
> 
> 
> That's true. For two reasons: we can only spread the use of Forth if there are more Forth programmers who like what they are doing - for this education is needed. Second, some day people will be happy that software code is readable and understandable in the first place, being sure what these commands are doing - for this education is needed.
> 
Agreed.
> 
> 
> Let's treat your next arguments the Forth way with some factoring, to have smaller chunks which are easier to digest!
> 
> 
> 
> > Others seem to  
> > want the project to be about providing some hardware they can't 
> > otherwise find.  
> 
> 
> 
> Great idea, that may be done with the same effort, and as a plus, it's a demo about what Forth is good for.
> 
Agreed.
> 
> 
> > Others yet seem to feel it is about making some "cool" 
> 
> > hardware.  
> 
> 
> 
> Great idea, that may be done with the same effort, and as a plus, it's a demo about what Forth is good for.
> 
Agreed
> 
> 
> > What part of this can we agree on or can we do all of the 
> 
> > above?  
> 
> 
> 
> To me this seems to be all one task.
> 
> If the result is showing that several boards are asked for, the more the better. 
> 
That's the key to it, IMO.

> Let's do it.
> 
> Let's diversify.
> 
> We are enough people to get a lot of stuff done. 
> 
> Let's start with one part, let's learn from this, others will follow.
> 
EXACTLY!
> 
> 
> > Are there other goals?
> 
> 
> 
> Good question to the audience ...
> 
> Don't hesitate to answer!
> 
> 
> 
> Cheers,
> 
> Dirk.

[toc] | [prev] | [next] | [standalone]

#31265

From	Mark Wills <markwills1970@gmail.com>
Date	2014-06-07 04:35 -0700
Message-ID	<77b540af-fc64-4caa-8d90-46645daf0d4c@googlegroups.com>
In reply to	#30977

After spinning this around in my head for a few days, I'm going 
to go ahead and post my thoughts re the feature set of the board.

The principle I have in my head is of a "main-board" that can
support a number of daughter-boards. The type of the daughter
boards (their function etc) is not of importance right now.
They can be determined much later (if at all/ever).

For the main board, I envisage the following:

Main Board Specification
========================
* MSP430 based CPU (I like the part with 16K ram*)
* 1 off Serial port (RS232) for connection to PC/terminal
* 1 off Serial port (RS232) for connection to other devices
* 1 off connector for connection to a 16-key hex key-pad
* 1 off connector for connection to a LCD display 
  (e.g. 20x2, 20x4 Hitachi type)
* 1 off I2C connector for daisy-chaining daughter boards
* 1 off red LED
* 1 off green LED (the colours aren't important, I'm just
  specifying two LEDs of different colours)
* 1 off 2 position switch
* 1 off power connector/battery connector

Rationale
=========
I'll describe where I'm coming from with the above specification.

MSP430 CPU: The central tenet of all discussions so far. Low 
cost, good instruction set. One aspect of the discussion I would
to instroduce here is the FRAM part. Could we please have a 
discussion about using the FRAM version of the MSP430. I know
they are available in a number of specifications, but I don't
recall specifics any more. I was on top of this a couple of years
back when I was in regular contact with a TI sales rep, but
not anyore, and the MSP430 product line is developing very fast.

The FRAM version of the part offers a number of advantages, 
particularly in a educational type environment. Specifically,
one may write to FRAM with complete impunity, and not worry 
about the complications of wearing out flash. And of course, it
retains it's state after power off. All of the conveniences of
flash, and none of the complications. This is very handy for us
in an educational environment. It means that:

* We don't have to have complex solutions for things like 
  CREATE/DOES> (for example, in a Flash environment you might 
  want the PFA (or whatever you want to call it - the thing that
  children of CREATE returns to the stack) in RAM, whilst the
  compiled code goes in flash. This is because one may want to
  write to the PFA (consider the classical implementation of 
  CONSTANT). With FRAM, we simply don't need to go there.
* We wouldn't need special words for ! where ! needs to write to
  flash. For example, if ! is writing to an area of "true" RAM
  then no special action is required. If ! needs to write to 
  Flash, then the appropriate block/page needs to be unlocked, 
  the value written, and locked again etc. With FRAM, we just 
  don't need to go there.
* FRAM, as shown in the above two point, simplifies the Forth
  system running on the chip, but, crucially, simplifies the life
  of the student, meaning we can avoid having to describe to the
  student the architectural constraints of a Flash based system.
  
Serial Port - for connection to host
------------------------------------
This would be for general communication with the board. The 
student would upload source code (a simple text file) to the 
board via an RS232 connection. The code would be compiled on
the board, not on the host PC. We want real-time, interactive
Forth. Not a host-based cross-compiler (IMO). The student should
be encouraged to (and the accompanying tutorial documentation
will) type stuff right at the keyboard of the PC, and see results
instantly, as has been the Forth way for decades.

Serial Port - for connection to other devices
---------------------------------------------
Part of the tutorial syllabus shall include connecting the board
to other devices (or, perhaps another main board) and exchanging
data using a very simple protocol. Of course, it's possible to 
do this using the first serial port, but students may want to see
what their code is doing by sending output to the "PC" serial 
port, so they can see their program communicating in real-time.

16-key Hex Keypad Port
----------------------
The Hex keypad will form part of the ability (along with an LCD)
to allow the board to be used by a student for stand-alone 
projects, away from a PC. For example, the syllabus can include
a clock project that displays the time on the LCD, and allows
the setting of the time via the keypad. The Forth system will 
include words for scanning the keypad.

LCD Display Port
----------------
For displaying output in a stand-alone configuration. Eg time in
a clock project.

I2C Port
--------
This will allow multiple daughter-boards to be connected to the
main board. For example, in the future, an SD card reader/writer
board could be developed for saving code/data. 
Ideas for daughter boards:
 * Analogue input boards (simple voltage reading, not current 
   loop);
 * Analogue output boards;
 * Digital input/output boards;
 * SD card reader writer.
 
LEDs
----
For general use. For example, in a clock project, they could be
the alarm, in the absence of a buzzer.

Two Position Switch
-------------------
The two position switch shall determine what action the board
takes upon power-up. In one position, the board shall simply 
initialise itself and send its welcome message to the terminal
via the host serial port.
In the second position, the board shall begin executing a users
program upon power-up. This would be implemented using simple
vectored execution. E.g.

' my_prog on_power_up !



Other things to consider:
=========================
* Including digital input/output (buffered) on the board, for 
  reading switches etc. Depends on how much I/O is available;
* A pezio buzzer.

My Contribution:
================
I would be willing to commit to the following:

* Financial input (e.g. procurement of MSP430's or contribution
  towards same if (for example) they can be obtained cheaper in 
  the USA rather than the UK;
  
* Financial input towards board prototyping.
  
* Documentation development:
  * User reference manual;
  * Tutorial syllabus - a complete Forth course, starting from
    first principles and taking the student right through Forth,
    using Forth best-practices. Targeted specifically to the 
    board. 

Comments?
=========
Your comments are welcome. Upon initial reading, this probably 
comes over as being way over-the-top. However, I would encourage
some thought, rather than (respectfully) knee-jerk reaction.
The system I have described above is, in my opinion, a very good
compromise between a purely education board for Forth students 
and a board that could be put into general use (perhaps along
with a daughter-board or two).

For example, I could envisage using such a board to teach Forth
to students. However, I could equally envisage using the same
board, un-modified, along with, say, one digital input board and
one analog input board as a home burgler alarm system. Or perhaps
as an RTU in the field somewhere, maybe monitoring a block-valve
on a pipeline block-valve station.

[toc] | [prev] | [next] | [standalone]

Page 8 of 10 — ← Prev page 1 … 6 7 [8] 9 10 Next page →

csiph-web

MSP430-Stamp

Contents

#31182

#31185

#31194

#31188

#31190

#31192

#31197

#31169

#31170

#31173

#31174

#31176

#31178

#31184

#31195

#31196

#31253

#31257

#31262

#31265