Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #29447
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M |
| Date | 2014-04-08 08:55 -0700 |
| Organization | Nightsong/Fort GNOX |
| Message-ID | <7xd2grddeu.fsf@ruckus.brouhaha.com> (permalink) |
| References | (2 earlier) <lho2c6$9jp$1@dont-email.me> <7xa9c0mhwl.fsf@ruckus.brouhaha.com> <f5b0c696-6c9c-4cfa-8777-9b83cd8fc69e@googlegroups.com> <7xbnwcner9.fsf@ruckus.brouhaha.com> <li13ad$6rc$1@newsserver.rrzn.uni-hannover.de> |
Matthias Koch <matthias.koch@hot.uni-hannover.de> writes: > FRAM is a nice technology, but it appears to me as read cycles are > limited because of a write-on-read operation like old days core > memory. Oh that's interesting, I knew there was a small amount of write wear (they mention 1e15 cycles) but I didn't realize every read also did a write. Still, at 10 mhz (1e7 hz), that's still several years of continuously hitting a single cell. By putting the innermost loops in SRAM, I think things should be fine. > One note: TIs FRAM devices contain a 16/20 bit mixed address length > CPU core called "CPUX" which is currently not supported by Mecrisp. As > the extended instruction set is downstream binary compatible to the > classic MSP430 CPU, you may have luck, but you won't have a change to > use the upper address range. Aha, I knew there were some big 430's that have extended range. The early FRAM parts had 16k of FRAM and 1k or so of SRAM, so 16 bit addressing would seem like enough. The one on the Launchpad has 64k of FRAM and 2k of SRAM. If that means a tiny bit of the FRAM is unreachable (or needs some CODE words to reach) then that's fine. If it means the SRAM is unreachable I guess that's more of a problem. In this day and age anything needing more than 64k of address space should probably use a 32 bit cpu. I hope they make some ARM devices with FRAM at some point.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-03-04 12:04 +0100
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-03-26 15:57 +0100
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-05 00:55 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-04 23:04 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-05 04:16 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-05 12:52 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-05 19:39 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-05 18:27 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-05 22:28 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-05 20:25 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-06 00:37 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-05 22:59 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-06 03:08 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-07 19:26 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-08 00:13 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-07 21:41 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Mark Wills <markwills1970@gmail.com> - 2014-04-08 02:20 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-08 05:59 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-09 00:41 -0400
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Mark Wills <markwills1970@gmail.com> - 2014-04-08 02:24 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-08 06:15 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Mark Wills <markwills1970@gmail.com> - 2014-04-08 06:46 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-04-08 17:00 +0200
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Paul Rubin <no.email@nospam.invalid> - 2014-04-08 08:55 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Mark Wills <markwills1970@gmail.com> - 2014-04-09 00:50 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M visualforth@rocketmail.com - 2014-04-05 10:37 -0700
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M Matthias Koch <matthias.koch@hot.uni-hannover.de> - 2014-04-08 13:09 +0200
Re: Announcing the first stable release of Mecrisp-Stellaris for ARM Cortex M rickman <gnuarm@gmail.com> - 2014-04-09 00:50 -0400
csiph-web