Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #47046

Re: How to write a compile documentation

From Cecil Bayona <cbayona@cbayona.com>
Newsgroups comp.lang.forth
Subject Re: How to write a compile documentation
Date 2016-05-12 12:23 -0500
Organization A noiseless patient Spider
Message-ID <nh2e04$fb3$1@dont-email.me> (permalink)
References (2 earlier) <f44e1266-d307-4646-9cba-227afced1918@googlegroups.com> <slrnni431s.dgp.albert@cherry.spenarnc.xs4all.nl> <ngt51p$2bh$1@dont-email.me> <ngu2vq$7c8$1@dont-email.me> <1e26eaba-322a-47a7-b070-0c1925056624@googlegroups.com>

Show all headers | View raw

On 5/10/2016 10:32 PM, Mikael Nordman wrote:
> Cecil,
> You could start with FlashForth.
> It works directly on pic24 and dsPic.
> It has been developed for 5 years and supports almost all pic24 and dsPic variants.
>
> I think mecrisp is written for vonNeumann architecture. FlashForth is written for Harvard architecture like the PICs.
>
> OH2AUN / Mikael
>
I had a question for you on FlashForth.

On the dsPIC version how much FLASH can the compiler handle?

I ask as I'm getting ready to put in an order on Mouser and I didn't 
want to order chips that will not work or use all the FLASH.

I was looking at the following SPDIP chips;

DSPIC33EP128GP502-I/SP with 128K of FLASH and 16KB of RAM

DSPIC33EP128MC202-I/SP with 128K of FLASH and 16KB of RAM This one is 
the #1 choice for most projects due to cost and capability.

DSPIC33EP512MC202-I/SP with 512K of FLASH and 48KB of RAM

Thanks
-- 
Cecil - k5nwa

Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

How to write a compile documentation Cecil - k5nwa <cecil.bayona@k5nwa.com> - 2016-04-26 08:40 -0700
  Re: How to write a compile documentation foxaudioresearch@gmail.com - 2016-04-27 11:47 -0700
    Re: How to write a compile documentation Cecil - k5nwa <cecil.bayona@k5nwa.com> - 2016-04-27 14:02 -0700
      Re: How to write a compile documentation Paul Rubin <no.email@nospam.invalid> - 2016-04-27 17:05 -0700
      Re: How to write a compile documentation Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-04-28 12:12 +0000
        Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-04-28 06:54 -0700
        Re: How to write a compile documentation Cecil - k5nwa <cecil.bayona@k5nwa.com> - 2016-04-28 20:10 -0700
        Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-10 12:20 -0500
          Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-10 20:51 -0500
            Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-10 20:32 -0700
            Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-10 20:32 -0700
              Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-11 00:11 -0500
                Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-10 22:39 -0700
              Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-12 12:23 -0500
                Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-12 12:50 -0700
                Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-12 16:19 -0500
                Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-13 06:36 -0700
                Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-13 09:44 -0500
                Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-13 08:01 -0700
                Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-13 13:00 -0500
                Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-13 12:51 -0700
                Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-13 17:15 -0500
                Re: How to write a compile documentation Mikael Nordman <oh2aun@gmail.com> - 2016-05-13 21:31 -0700
                Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-14 10:19 -0500
                Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-21 19:29 -0500
    Re: How to write a compile documentation "HAA" <someone@microsoft.com> - 2016-04-28 12:34 +1000
      Re: How to write a compile documentation foxaudioresearch@gmail.com - 2016-04-28 06:14 -0700
  Re: How to write a compile documentation Cecil - k5nwa <cecil.bayona@k5nwa.com> - 2016-05-02 13:36 -0700
    Re: How to write a compile documentation Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> - 2016-05-02 22:25 +0100
      Re: How to write a compile documentation Cecil - k5nwa <cecil.bayona@k5nwa.com> - 2016-05-02 16:00 -0700
        Re: How to write a compile documentation Paul Rubin <no.email@nospam.invalid> - 2016-05-02 17:48 -0700
          Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-02 21:16 -0500
            Re: How to write a compile documentation Cecil Bayona <cbayona@cbayona.com> - 2016-05-02 21:24 -0500

csiph-web