Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #46348 > unrolled thread
| Started by | rickman <gnuarm@gmail.com> |
|---|---|
| First post | 2016-03-30 21:39 -0400 |
| Last post | 2016-03-31 23:23 -0700 |
| Articles | 20 on this page of 119 — 10 participants |
Back to article view | Back to comp.lang.forth
New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-03-30 21:39 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-03-30 18:52 -0700
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-03-30 20:31 -0700
Re: New "Forth" MCU Board, ChipStick JUERGEN <epldfpga@aol.com> - 2016-03-30 23:41 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-03-31 00:37 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-03-31 14:36 -0400
Re: New "Forth" MCU Board, ChipStick JUERGEN <epldfpga@aol.com> - 2016-04-01 00:42 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-01 13:09 -0400
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@spenarnc.xs4all.nl> - 2016-04-01 23:43 +0000
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-04-01 17:28 -0700
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@spenarnc.xs4all.nl> - 2016-04-02 12:10 +0000
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-03-31 17:07 -0500
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@spenarnc.xs4all.nl> - 2016-03-31 23:59 +0000
Re: New "Forth" MCU Board, ChipStick JUERGEN <epldfpga@aol.com> - 2016-04-01 00:52 -0700
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-04-01 12:47 -0500
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-03-31 18:54 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-03-31 22:08 -0400
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-03-31 19:36 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-03-31 23:28 -0400
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-03-31 22:32 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-01 02:39 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-01 04:42 -0700
Re: New "Forth" MCU Board, ChipStick josv@planet.nl - 2016-04-01 04:48 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-01 05:50 -0700
Re: New "Forth" MCU Board, ChipStick anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-04-01 13:35 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-01 13:11 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-02 01:58 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-02 10:15 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-02 08:02 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-02 12:39 -0400
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-02 12:54 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-02 15:14 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-02 22:14 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-02 23:08 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-03 02:11 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-03 22:54 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-04 02:50 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-04 16:37 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-04 23:15 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 02:21 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-05 00:01 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 03:17 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-05 01:15 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 12:50 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-04 23:21 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 02:29 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-05 00:02 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-05 02:07 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 13:12 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-05 00:12 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 03:22 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-05 01:22 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-05 02:12 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 13:15 -0400
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-04-05 17:14 -0500
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-04 03:03 -0700
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-04-04 19:51 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-04 20:18 -0700
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-04-04 20:44 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-04 22:39 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 02:25 -0400
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-04 16:23 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-04 23:18 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 13:22 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-05 13:34 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-04-05 21:28 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-05 22:34 -0700
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-04-01 15:52 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-04-02 01:55 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-04 22:38 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-05-04 23:10 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-05 16:28 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-05 22:35 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-05 21:40 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-05-05 22:13 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-05 22:44 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-06 02:41 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-06 01:26 -0700
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-05-06 02:02 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-06 09:06 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-06 05:09 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-05-06 03:50 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-06 19:23 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-06 16:29 -0700
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-07 11:32 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-07 15:38 -0400
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-08 09:45 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-08 11:04 -0400
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-08 17:36 +0000
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-08 17:39 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-08 14:08 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-08 10:52 -0700
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-05-08 14:57 -0500
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-08 13:23 -0700
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-09 09:26 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-09 10:26 -0400
Re: New "Forth" MCU Board, ChipStick Raimond Dragomir <raimond.dragomir@gmail.com> - 2016-05-09 09:38 -0700
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-09 12:58 -0400
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-09 22:53 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-09 22:41 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-09 11:08 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-09 13:21 -0700
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-09 23:39 +0000
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-09 19:03 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-05-09 21:44 -0700
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-10 08:28 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-10 12:34 -0400
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-10 22:27 +0000
Re: New "Forth" MCU Board, ChipStick Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-09 09:16 +0000
Re: New "Forth" MCU Board, ChipStick rickman <gnuarm@gmail.com> - 2016-05-08 14:01 -0400
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-03-31 23:26 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-03-31 19:09 -0700
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-03-31 21:41 -0500
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-03-31 23:10 -0700
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-04-01 12:37 -0500
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-04-01 15:35 -0700
Re: New "Forth" MCU Board, ChipStick David Schultz <abuse@127.0.0.1> - 2016-04-01 18:11 -0500
Re: New "Forth" MCU Board, ChipStick visualforth@rocketmail.com - 2016-03-31 19:47 -0700
Re: New "Forth" MCU Board, ChipStick Paul Rubin <no.email@nospam.invalid> - 2016-03-31 23:23 -0700
Page 1 of 6 [1] 2 3 4 5 6 Next page →
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2016-03-30 21:39 -0400 |
| Subject | New "Forth" MCU Board, ChipStick |
| Message-ID | <ndhuv2$4tk$1@dont-email.me> |
I know some here are into the small, inexpensive MCU boards available. I don't think I've seen this one mentioned here, ChipStick, by Ken Boak. I see in the comments on the page that Juergen has discovered it. http://sustburbia.blogspot.com/2016/03/chipstick-small-scale-experimental.html I'm not sure what is special about this board other than the size I suppose. It includes a spot for an external serial memory which can be RAM or FRAM. He says this would allow Forth code to be fetched and interpreted from off the MCU chip. Otherwise it seems to be YASMB (Yet Another Small MCU Board). Anyone here seen the OSHChip? It is a similar product that includes an ARM and Bluetooth LE on a 16 pin DIP format using the Nordic Semi MCU. http://oshchip.org/ I looked at this one as well as having looked at the Nordic chips some time ago. The MCU chips seem to be oriented to people who know what they are doing with Bluetooth and might be a bit difficult to get going if you aren't. Still, the OSHChip is pretty interesting. -- Rick
[toc] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2016-03-30 18:52 -0700 |
| Message-ID | <87d1qbtnvq.fsf@nightsong.com> |
| In reply to | #46348 |
rickman <gnuarm@gmail.com> writes: > http://sustburbia.blogspot.com/2016/03/chipstick-small-scale-experimental.html > > I'm not sure what is special about this board other than the size I > suppose. It includes a spot for an external serial memory which can > be RAM or FRAM. 1) cheap, low power, narrow DIP format 2) supports RTC crystal on the board 3) supports external sram/fram, maybe it can also suport SPI flash for more capacity (the comment suggesting that was from me) 4) FRAM in cpu is very cool, and not available in non-MSP430 devices for now. 5) MSP430 architecture might be getting slowly squeezed out by ARM but it's still a good fit for low-resource Forth. > He says this would allow Forth code to be fetched and interpreted from > off the MCU chip. Otherwise it seems to be YASMB (Yet Another Small > MCU Board). Yeah but there are so many YASMB's because they're useful. This one has an interesting new combination of features, always a welcome thing. > Anyone here seen the OSHChip? I've only seen the online pages that you've seen. > The MCU chips seem to be oriented to people who know what they are > doing with Bluetooth and might be a bit difficult to get going if you > aren't. Still, the OSHChip is pretty interesting. Bluetooth seems like a big bureaucratic mess like IRDA was (I was involved with IRDA way back when). I've begun to think wifi is a better choice for many purposes even at low data rates. I don't know how low you can get the power consumption though.
[toc] | [prev] | [next] | [standalone]
| From | visualforth@rocketmail.com |
|---|---|
| Date | 2016-03-30 20:31 -0700 |
| Message-ID | <ec834531-9885-4afe-9428-4db5be781050@googlegroups.com> |
| In reply to | #46348 |
On Wednesday, March 30, 2016 at 9:39:51 PM UTC-4, rickman wrote: > I know some here are into the small, inexpensive MCU boards available. > I don't think I've seen this one mentioned here, ChipStick, by Ken Boak. > I see in the comments on the page that Juergen has discovered it. > > http://sustburbia.blogspot.com/2016/03/chipstick-small-scale-experimental.html > > I'm not sure what is special about this board other than the size I > suppose. It includes a spot for an external serial memory which can be > RAM or FRAM. He says this would allow Forth code to be fetched and > interpreted from off the MCU chip. Otherwise it seems to be YASMB (Yet > Another Small MCU Board). > > Anyone here seen the OSHChip? It is a similar product that includes an > ARM and Bluetooth LE on a 16 pin DIP format using the Nordic Semi MCU. > > http://oshchip.org/ > > I looked at this one as well as having looked at the Nordic chips some > time ago. The MCU chips seem to be oriented to people who know what > they are doing with Bluetooth and might be a bit difficult to get going > if you aren't. Still, the OSHChip is pretty interesting. > > -- > > Rick The FRAM CPU is the ultimate CPU for Forth: with Token threaded Forth on chip - like Jupiter ACE and Canon Cat - it can be used for enhanced interactive developing - editing words without needing reload. That's a boon for education. DB.
[toc] | [prev] | [next] | [standalone]
| From | JUERGEN <epldfpga@aol.com> |
|---|---|
| Date | 2016-03-30 23:41 -0700 |
| Message-ID | <f27d9c9d-7e4e-45d2-b9ba-81eedfc09833@googlegroups.com> |
| In reply to | #46348 |
On Thursday, March 31, 2016 at 2:39:51 AM UTC+1, rickman wrote: > I know some here are into the small, inexpensive MCU boards available. > I don't think I've seen this one mentioned here, ChipStick, by Ken Boak. > I see in the comments on the page that Juergen has discovered it. > > http://sustburbia.blogspot.com/2016/03/chipstick-small-scale-experimental.html > > I'm not sure what is special about this board other than the size I > suppose. It includes a spot for an external serial memory which can be > RAM or FRAM. He says this would allow Forth code to be fetched and > interpreted from off the MCU chip. Otherwise it seems to be YASMB (Yet > Another Small MCU Board). > > Anyone here seen the OSHChip? It is a similar product that includes an > ARM and Bluetooth LE on a 16 pin DIP format using the Nordic Semi MCU. > > http://oshchip.org/ > > I looked at this one as well as having looked at the Nordic chips some > time ago. The MCU chips seem to be oriented to people who know what > they are doing with Bluetooth and might be a bit difficult to get going > if you aren't. Still, the OSHChip is pretty interesting. > > -- > > Rick Rick, there have been many discussions about little boards. But THIS ONE HAS A DIFFERENCE NOT MENTIONED HERE YET. And this is how I found it and started discussions with Ken: www.forth-ev.de. NO Lauchpad needed for Flash programming - done directly via USB. I hope we can move this SW Option over to the good old MSP430G2553 as well. And MicroBox could live without the LP then as well. Bristol http://www.digimakers.co.uk/ We are planning to show all of this at the Bristol Maker Show 11 June. And we might ask for HELP to support us there. Anybody interested or will be there anyway? Just in the final stages of getting it organized. Stick an FRAM on instead of the RAM and you got a "Disk". So is there a small Block Editor around that can be used? I would like to replicate the """editor""" described in Chuck's Problem Oriented Language booklet.
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2016-03-31 00:37 -0700 |
| Message-ID | <87zitfrtcv.fsf@nightsong.com> |
| In reply to | #46354 |
JUERGEN <epldfpga@aol.com> writes: > NO Lauchpad needed for Flash programming - done directly via USB. Hmm, good point, though Arduino-ish boards can also do that, and some of them are cheap and tiny. > I hope we can move this SW Option over to the good old MSP430G2553 as > well. I sure like that FRAM part! I think the value line parts don't have as much stuff on them, so maybe it's harder. Also the ChipStick seems to have an optional breakaway FTDI-like chip on it, so maybe that's required if you want to program it by USB. > Stick an FRAM on instead of the RAM and you got a "Disk". With just 32k that's not much of a disk... an SPI flash chip might be better. > So is there a small Block Editor around that can be used? Could some of the old ones like F83's be usable or adaptable? There's also one in 4th that I didn't quite figure out how to use. And after asking some of the old-timers here about block editing, it sounds painful with little benefit. But if you want to go that route, maybe it's better to use the bigger FRAM Launchpad board. I remember someone (trying to remember who) did a "modern" blocks system where the block size was 4k, giving a 25x80 code screen and accompanying shadow screen in each block, with a few bytes left over for metadata. Maybe that's more palatable than the old 16x64 screens with no explicit line breaks.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2016-03-31 14:36 -0400 |
| Message-ID | <ndjqgb$p40$1@dont-email.me> |
| In reply to | #46356 |
On 3/31/2016 3:37 AM, Paul Rubin wrote: > JUERGEN <epldfpga@aol.com> writes: >> NO Lauchpad needed for Flash programming - done directly via USB. > > Hmm, good point, though Arduino-ish boards can also do that, and some of > them are cheap and tiny. I'm not sure what Juergen means by "no launchpad needed". A Launchpad is an MCU board that incorporates a USB to serial and programmer chip (FET). This board uses a CH340G USB to serial chip which is *not* the same as the part used on the Launchpads to provide the FET capability. In fact, Ken's notes describe using the FET of a Launchpad along with Code Composer to debug and program the board. I suppose Juergen is talking about programming in Forth to the FRAM which will not need the FET. >> I hope we can move this SW Option over to the good old MSP430G2553 as >> well. > > I sure like that FRAM part! I think the value line parts don't have as > much stuff on them, so maybe it's harder. Also the ChipStick seems to > have an optional breakaway FTDI-like chip on it, so maybe that's > required if you want to program it by USB. The CH430G is just a serial port, no JTAG capability unless you write a driver to bit bang the control lines. >> Stick an FRAM on instead of the RAM and you got a "Disk". > > With just 32k that's not much of a disk... an SPI flash chip might be > better. > >> So is there a small Block Editor around that can be used? > > Could some of the old ones like F83's be usable or adaptable? There's > also one in 4th that I didn't quite figure out how to use. And after > asking some of the old-timers here about block editing, it sounds > painful with little benefit. But if you want to go that route, maybe > it's better to use the bigger FRAM Launchpad board. > > I remember someone (trying to remember who) did a "modern" blocks system > where the block size was 4k, giving a 25x80 code screen and accompanying > shadow screen in each block, with a few bytes left over for metadata. > Maybe that's more palatable than the old 16x64 screens with no explicit > line breaks. > -- Rick
[toc] | [prev] | [next] | [standalone]
| From | JUERGEN <epldfpga@aol.com> |
|---|---|
| Date | 2016-04-01 00:42 -0700 |
| Message-ID | <081ca73b-b353-48ec-8544-b3bdc4351807@googlegroups.com> |
| In reply to | #46363 |
On Thursday, March 31, 2016 at 7:35:59 PM UTC+1, rickman wrote: > On 3/31/2016 3:37 AM, Paul Rubin wrote: > > JUERGEN <epldfpga@aol.com> writes: > >> NO Lauchpad needed for Flash programming - done directly via USB. > > > > Hmm, good point, though Arduino-ish boards can also do that, and some of > > them are cheap and tiny. > > I'm not sure what Juergen means by "no launchpad needed". A Launchpad > is an MCU board that incorporates a USB to serial and programmer chip > (FET). This board uses a CH340G USB to serial chip which is *not* the > same as the part used on the Launchpads to provide the FET capability. > In fact, Ken's notes describe using the FET of a Launchpad along with > Code Composer to debug and program the board. I suppose Juergen is > talking about programming in Forth to the FRAM which will not need the FET. > > > >> I hope we can move this SW Option over to the good old MSP430G2553 as > >> well. > > > > I sure like that FRAM part! I think the value line parts don't have as > > much stuff on them, so maybe it's harder. Also the ChipStick seems to > > have an optional breakaway FTDI-like chip on it, so maybe that's > > required if you want to program it by USB. > > The CH430G is just a serial port, no JTAG capability unless you write a > driver to bit bang the control lines. > > > >> Stick an FRAM on instead of the RAM and you got a "Disk". > > > > With just 32k that's not much of a disk... an SPI flash chip might be > > better. > > > >> So is there a small Block Editor around that can be used? > > > > Could some of the old ones like F83's be usable or adaptable? There's > > also one in 4th that I didn't quite figure out how to use. And after > > asking some of the old-timers here about block editing, it sounds > > painful with little benefit. But if you want to go that route, maybe > > it's better to use the bigger FRAM Launchpad board. > > > > I remember someone (trying to remember who) did a "modern" blocks system > > where the block size was 4k, giving a 25x80 code screen and accompanying > > shadow screen in each block, with a few bytes left over for metadata. > > Maybe that's more palatable than the old 16x64 screens with no explicit > > line breaks. > > > > > -- > > Rick You would normally need to buy/own a TI Launchpad to flash the 2553 - Ken has found a way around this - no LP needed anymore, just this board. Programming in Forth is seperate and comes after you flashed the Forth.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2016-04-01 13:09 -0400 |
| Message-ID | <ndm9pf$m6l$1@dont-email.me> |
| In reply to | #46384 |
On 4/1/2016 3:42 AM, JUERGEN wrote: > On Thursday, March 31, 2016 at 7:35:59 PM UTC+1, rickman wrote: >> On 3/31/2016 3:37 AM, Paul Rubin wrote: >>> JUERGEN <epldfpga@aol.com> writes: >>>> NO Lauchpad needed for Flash programming - done directly via USB. >>> >>> Hmm, good point, though Arduino-ish boards can also do that, and some of >>> them are cheap and tiny. >> >> I'm not sure what Juergen means by "no launchpad needed". A Launchpad >> is an MCU board that incorporates a USB to serial and programmer chip >> (FET). This board uses a CH340G USB to serial chip which is *not* the >> same as the part used on the Launchpads to provide the FET capability. >> In fact, Ken's notes describe using the FET of a Launchpad along with >> Code Composer to debug and program the board. I suppose Juergen is >> talking about programming in Forth to the FRAM which will not need the FET. >> >> >>>> I hope we can move this SW Option over to the good old MSP430G2553 as >>>> well. >>> >>> I sure like that FRAM part! I think the value line parts don't have as >>> much stuff on them, so maybe it's harder. Also the ChipStick seems to >>> have an optional breakaway FTDI-like chip on it, so maybe that's >>> required if you want to program it by USB. >> >> The CH430G is just a serial port, no JTAG capability unless you write a >> driver to bit bang the control lines. > > You would normally need to buy/own a TI Launchpad to flash the 2553 > - Ken has found a way around this > - no LP needed anymore, just this board. > Programming in Forth is seperate and comes after you flashed the Forth. Funny, he doesn't mention that in the post I saw. He specifically indicates he needed a Launchpad to use the FET portion. I dug around a bit and it looks like the bootloader docs are a mess. I'm guessing that slau319k.pdf is complete but not at all trivial to read. There are many variations on the bootloader and ways to invoke it. I'll dig into this more later, but I'm really more interested in ARM devices these days. I'm also looking to work with BlueTooth. -- Rick
[toc] | [prev] | [next] | [standalone]
| From | Albert van der Horst <albert@spenarnc.xs4all.nl> |
|---|---|
| Date | 2016-04-01 23:43 +0000 |
| Message-ID | <56ff0799$0$5911$e4fe514c@news.xs4all.nl> |
| In reply to | #46393 |
rickman <gnuarm@gmail.com> writes: >On 4/1/2016 3:42 AM, JUERGEN wrote: >> On Thursday, March 31, 2016 at 7:35:59 PM UTC+1, rickman wrote: >>> On 3/31/2016 3:37 AM, Paul Rubin wrote: >>>> JUERGEN <epldfpga@aol.com> writes: >>>>> NO Lauchpad needed for Flash programming - done directly via USB. >>>> >>>> Hmm, good point, though Arduino-ish boards can also do that, and some of >>>> them are cheap and tiny. >>> >>> I'm not sure what Juergen means by "no launchpad needed". A Launchpad >>> is an MCU board that incorporates a USB to serial and programmer chip >>> (FET). This board uses a CH340G USB to serial chip which is *not* the >>> same as the part used on the Launchpads to provide the FET capability. >>> In fact, Ken's notes describe using the FET of a Launchpad along with >>> Code Composer to debug and program the board. I suppose Juergen is >>> talking about programming in Forth to the FRAM which will not need the FET. >>> >>> >>>>> I hope we can move this SW Option over to the good old MSP430G2553 as >>>>> well. >>>> >>>> I sure like that FRAM part! I think the value line parts don't have as >>>> much stuff on them, so maybe it's harder. Also the ChipStick seems to >>>> have an optional breakaway FTDI-like chip on it, so maybe that's >>>> required if you want to program it by USB. >>> >>> The CH430G is just a serial port, no JTAG capability unless you write a >>> driver to bit bang the control lines. >> >> You would normally need to buy/own a TI Launchpad to flash the 2553 >> - Ken has found a way around this >> - no LP needed anymore, just this board. >> Programming in Forth is seperate and comes after you flashed the Forth. >Funny, he doesn't mention that in the post I saw. He specifically >indicates he needed a Launchpad to use the FET portion. I dug around a >bit and it looks like the bootloader docs are a mess. I'm guessing that >slau319k.pdf is complete but not at all trivial to read. There are many >variations on the bootloader and ways to invoke it. I'll dig into this >more later, but I'm really more interested in ARM devices these days. >I'm also looking to work with BlueTooth. The Dutch Forth User group has developped their own board (Egel, still somewhat experimental and in kit form). You must be able to solder SMD to get it running. The chip is in a socket and the easiest way to program noforth on it is to put the 430 in a Launchpad, then put it on the Egel board. >-- >Rick -- 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]
| From | visualforth@rocketmail.com |
|---|---|
| Date | 2016-04-01 17:28 -0700 |
| Message-ID | <a48b27fd-6f89-4492-b22c-4d55066d1930@googlegroups.com> |
| In reply to | #46405 |
On Friday, April 1, 2016 at 7:43:23 PM UTC-4, Albert van der Horst wrote: > rickman <gnuarm.com> writes: > > >On 4/1/2016 3:42 AM, JUERGEN wrote: > >> On Thursday, March 31, 2016 at 7:35:59 PM UTC+1, rickman wrote: > >>> On 3/31/2016 3:37 AM, Paul Rubin wrote: > >>>> JUERGEN <.com> writes: > >>>>> NO Lauchpad needed for Flash programming - done directly via USB. > >>>> > >>>> Hmm, good point, though Arduino-ish boards can also do that, and some of > >>>> them are cheap and tiny. > >>> > >>> I'm not sure what Juergen means by "no launchpad needed". A Launchpad > >>> is an MCU board that incorporates a USB to serial and programmer chip > >>> (FET). This board uses a CH340G USB to serial chip which is *not* the > >>> same as the part used on the Launchpads to provide the FET capability. > >>> In fact, Ken's notes describe using the FET of a Launchpad along with > >>> Code Composer to debug and program the board. I suppose Juergen is > >>> talking about programming in Forth to the FRAM which will not need the FET. > >>> > >>> > >>>>> I hope we can move this SW Option over to the good old MSP430G2553 as > >>>>> well. > >>>> > >>>> I sure like that FRAM part! I think the value line parts don't have as > >>>> much stuff on them, so maybe it's harder. Also the ChipStick seems to > >>>> have an optional breakaway FTDI-like chip on it, so maybe that's > >>>> required if you want to program it by USB. > >>> > >>> The CH430G is just a serial port, no JTAG capability unless you write a > >>> driver to bit bang the control lines. > >> > >> You would normally need to buy/own a TI Launchpad to flash the 2553 > >> - Ken has found a way around this > >> - no LP needed anymore, just this board. > >> Programming in Forth is seperate and comes after you flashed the Forth. > > >Funny, he doesn't mention that in the post I saw. He specifically > >indicates he needed a Launchpad to use the FET portion. I dug around a > >bit and it looks like the bootloader docs are a mess. I'm guessing that > >slau319k.pdf is complete but not at all trivial to read. There are many > >variations on the bootloader and ways to invoke it. I'll dig into this > >more later, but I'm really more interested in ARM devices these days. > >I'm also looking to work with BlueTooth. > > The Dutch Forth User group has developped their own board (Egel, still > somewhat experimental and in kit form). > You must be able to solder SMD to get it running. The chip is > in a socket and the easiest way to program noforth on it is to put the > 430 in a Launchpad, then put it on the Egel board. > > >-- > > >Rick > -- > 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 Which 430 does your Egel board use? Are there technical data available? Is this board available somewhere? I looked into the Egel werkboek, 430 mentioned only once: 430µs on page 61.
[toc] | [prev] | [next] | [standalone]
| From | Albert van der Horst <albert@spenarnc.xs4all.nl> |
|---|---|
| Date | 2016-04-02 12:10 +0000 |
| Message-ID | <56ffb6ad$0$5851$e4fe514c@news.xs4all.nl> |
| In reply to | #46406 |
visualforth@rocketmail.com writes: >On Friday, April 1, 2016 at 7:43:23 PM UTC-4, Albert van der Horst wrote: >> rickman <gnuarm.com> writes: >>=20 >> >On 4/1/2016 3:42 AM, JUERGEN wrote: >> >> On Thursday, March 31, 2016 at 7:35:59 PM UTC+1, rickman wrote: >> >>> On 3/31/2016 3:37 AM, Paul Rubin wrote: >> >>>> JUERGEN <.com> writes: >> >>>>> NO Lauchpad needed for Flash programming - done directly via USB. >> >>>> >> >>>> Hmm, good point, though Arduino-ish boards can also do that, and som= >e of >> >>>> them are cheap and tiny. >> >>> >> >>> I'm not sure what Juergen means by "no launchpad needed". A Launchpa= >d >> >>> is an MCU board that incorporates a USB to serial and programmer chip >> >>> (FET). This board uses a CH340G USB to serial chip which is *not* th= >e >> >>> same as the part used on the Launchpads to provide the FET capability= >. >> >>> In fact, Ken's notes describe using the FET of a Launchpad along with >> >>> Code Composer to debug and program the board. I suppose Juergen is >> >>> talking about programming in Forth to the FRAM which will not need th= >e FET. >> >>> >> >>> >> >>>>> I hope we can move this SW Option over to the good old MSP430G2553 = >as >> >>>>> well. >> >>>> >> >>>> I sure like that FRAM part! I think the value line parts don't have= > as >> >>>> much stuff on them, so maybe it's harder. Also the ChipStick seems = >to >> >>>> have an optional breakaway FTDI-like chip on it, so maybe that's >> >>>> required if you want to program it by USB. >> >>> >> >>> The CH430G is just a serial port, no JTAG capability unless you write= > a >> >>> driver to bit bang the control lines. >> >> >> >> You would normally need to buy/own a TI Launchpad to flash the 2553 >> >> - Ken has found a way around this >> >> - no LP needed anymore, just this board. >> >> Programming in Forth is seperate and comes after you flashed the Forth= >. >>=20 >> >Funny, he doesn't mention that in the post I saw. He specifically >> >indicates he needed a Launchpad to use the FET portion. I dug around a >> >bit and it looks like the bootloader docs are a mess. I'm guessing that >> >slau319k.pdf is complete but not at all trivial to read. There are many >> >variations on the bootloader and ways to invoke it. I'll dig into this >> >more later, but I'm really more interested in ARM devices these days. >> >I'm also looking to work with BlueTooth. >>=20 >> The Dutch Forth User group has developped their own board (Egel, still >> somewhat experimental and in kit form). >> You must be able to solder SMD to get it running. The chip is >> in a socket and the easiest way to program noforth on it is to put the >> 430 in a Launchpad, then put it on the Egel board. >>=20 >> >-- >>=20 >> >Rick >> --=20 >> Albert van der Horst, UTRECHT,THE NETHERLANDS >> Economic growth -- being exponential -- ultimately falters. >> albert@spe&ar&c.xs4all.nl &=3Dn http://home.hccnet.nl/a.w.m.van.der.horst >Which 430 does your Egel board use? >Are there technical data available? Look at http://home.hccnet.nl/anij/nof/noforth.html >Is this board available somewhere? In due time. We also want to make the design of the board available. >I looked into the Egel werkboek, 430 mentioned only once: 430=B5s on page 6= >1. That'll probably the old Egel for o.a. 8051. This is a collection of small idea's and projects that you can use to paste together a larger project. The idea is to make all that and more available for the 430 too. The Egel predates and rivals the Arduino project. 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]
| From | David Schultz <abuse@127.0.0.1> |
|---|---|
| Date | 2016-03-31 17:07 -0500 |
| Message-ID | <ZPCdnanXhcYlAmDLnZ2dnUU7-IHNnZ2d@earthlink.com> |
| In reply to | #46356 |
On 03/31/2016 02:37 AM, Paul Rubin wrote: >> So is there a small Block Editor around that can be used? > > Could some of the old ones like F83's be usable or adaptable? There's > also one in 4th that I didn't quite figure out how to use. And after > asking some of the old-timers here about block editing, it sounds > painful with little benefit. But if you want to go that route, maybe > it's better to use the bigger FRAM Launchpad board. I am working on a project that I decided to use Forth on and as a result I have two block editors working. The smallest is the old figForth block editor. That works but is less fun than vi. I also have the Laxen screen editor running. I am using these on an MSP430FR5969 Launchpad running eForth and connected to a micro-SD card. -- David W. Schultz http://home.earthlink.net/~david.schultz Returned for Regrooving
[toc] | [prev] | [next] | [standalone]
| From | Albert van der Horst <albert@spenarnc.xs4all.nl> |
|---|---|
| Date | 2016-03-31 23:59 +0000 |
| Message-ID | <56fdb9c9$0$5887$e4fe514c@news.xs4all.nl> |
| In reply to | #46369 |
David Schultz <abuse@127.0.0.1> writes: >On 03/31/2016 02:37 AM, Paul Rubin wrote: >>> So is there a small Block Editor around that can be used? >> >> Could some of the old ones like F83's be usable or adaptable? There's >> also one in 4th that I didn't quite figure out how to use. And after >> asking some of the old-timers here about block editing, it sounds >> painful with little benefit. But if you want to go that route, maybe >> it's better to use the bigger FRAM Launchpad board. >I am working on a project that I decided to use Forth on and as a result >I have two block editors working. The smallest is the old figForth block >editor. That works but is less fun than vi. I also have the Laxen screen >editor running. >I am using these on an MSP430FR5969 Launchpad running eForth and >connected to a micro-SD card. You mean you've interfaced a Launchpad to micro SD card and use it as a block device? That's cool! >-- >David W. Schultz 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]
| From | JUERGEN <epldfpga@aol.com> |
|---|---|
| Date | 2016-04-01 00:52 -0700 |
| Message-ID | <0efcff25-0fa4-48af-b2ad-d866e1d23445@googlegroups.com> |
| In reply to | #46369 |
On Thursday, March 31, 2016 at 11:07:53 PM UTC+1, David Schultz wrote: > On 03/31/2016 02:37 AM, Paul Rubin wrote: > >> So is there a small Block Editor around that can be used? > > > > Could some of the old ones like F83's be usable or adaptable? There's > > also one in 4th that I didn't quite figure out how to use. And after > > asking some of the old-timers here about block editing, it sounds > > painful with little benefit. But if you want to go that route, maybe > > it's better to use the bigger FRAM Launchpad board. > > I am working on a project that I decided to use Forth on and as a result > I have two block editors working. The smallest is the old figForth block > editor. That works but is less fun than vi. I also have the Laxen screen > editor running. > > I am using these on an MSP430FR5969 Launchpad running eForth and > connected to a micro-SD card. > > -- > David W. Schultz > http://home.earthlink.net/~david.schultz > Returned for Regrooving David, would it be difficult to have the eForth ported to this Stick - which is probably not different to just having it adapted to the chip? With an image available for download, eForth should be running soon.
[toc] | [prev] | [next] | [standalone]
| From | David Schultz <abuse@127.0.0.1> |
|---|---|
| Date | 2016-04-01 12:47 -0500 |
| Message-ID | <tdednRxGt9_YKWPLnZ2dnUU7-dvNnZ2d@earthlink.com> |
| In reply to | #46385 |
On 04/01/2016 02:52 AM, JUERGEN wrote: > David, would it be difficult to have the eForth ported to this Stick > - which is probably not different to just having it adapted to the chip? > With an image available for download, eForth should be running soon. > I have no idea how easy the port would be. I put an early version here: http://home.earthlink.net/~schultdw/msp430/eforth/index.html That does not have any of the SD card routines. I have a much tweaked version of the basic eForth that I am using for that work -- David W. Schultz http://home.earthlink.net/~david.schultz Returned for Regrooving
[toc] | [prev] | [next] | [standalone]
| From | visualforth@rocketmail.com |
|---|---|
| Date | 2016-03-31 18:54 -0700 |
| Message-ID | <5ffa7735-547a-4352-b5d7-935656f3471a@googlegroups.com> |
| In reply to | #46354 |
On Thursday, March 31, 2016 at 2:41:04 AM UTC-4, JUERGEN wrote: > > Stick an FRAM on instead of the RAM and you got a "Disk". > > So is there a small Block Editor around that can be used? With FRAM and a token threaded Forth (like Jupiter ACE's Forth) no Block Editor is needed: programming as you go and editing/debugging the source code directly on chip if needed. The greatest discovery Ken made is demystifying the BSL story! Enables transferring Forth to the MSP430 with no additional hardware. Then Forth makes programming possible directly with the MSP430 alone. Even cloning will be possible this way. Cheers, Dirk.
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2016-03-31 22:08 -0400 |
| Message-ID | <ndkl13$k5c$1@dont-email.me> |
| In reply to | #46372 |
On 3/31/2016 9:54 PM, visualforth@rocketmail.com wrote: > On Thursday, March 31, 2016 at 2:41:04 AM UTC-4, JUERGEN wrote: >> >> Stick an FRAM on instead of the RAM and you got a "Disk". >> >> So is there a small Block Editor around that can be used? > > With FRAM and a token threaded Forth (like Jupiter ACE's Forth) no Block Editor is needed: programming as you go and editing/debugging the source code directly on chip if needed. > > The greatest discovery Ken made is demystifying the BSL story! > Enables transferring Forth to the MSP430 with no additional hardware. > Then Forth makes programming possible directly with the MSP430 alone. > Even cloning will be possible this way. BSL? Boot Strap Loader? -- Rick
[toc] | [prev] | [next] | [standalone]
| From | visualforth@rocketmail.com |
|---|---|
| Date | 2016-03-31 19:36 -0700 |
| Message-ID | <c02db534-aa8d-4f6f-a290-4c8ef39b91cb@googlegroups.com> |
| In reply to | #46373 |
On Thursday, March 31, 2016 at 10:08:39 PM UTC-4, rickman wrote: > On 3/31/2016 9:54 PM, visualforth.com wrote: > > On Thursday, March 31, 2016 at 2:41:04 AM UTC-4, JUERGEN wrote: > >> > >> Stick an FRAM on instead of the RAM and you got a "Disk". > >> > >> So is there a small Block Editor around that can be used? > > > > With FRAM and a token threaded Forth (like Jupiter ACE's Forth) no Block Editor is needed: programming as you go and editing/debugging the source code directly on chip if needed. > > > > The greatest discovery Ken made is demystifying the BSL story! > > Enables transferring Forth to the MSP430 with no additional hardware. > > Then Forth makes programming possible directly with the MSP430 alone. > > Even cloning will be possible this way. > > BSL? Boot Strap Loader? > > -- > > Rick Yes!
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2016-03-31 23:28 -0400 |
| Message-ID | <ndkpnd$v2j$3@dont-email.me> |
| In reply to | #46375 |
On 3/31/2016 10:36 PM, visualforth@rocketmail.com wrote: > On Thursday, March 31, 2016 at 10:08:39 PM UTC-4, rickman wrote: >> On 3/31/2016 9:54 PM, visualforth.com wrote: >>> On Thursday, March 31, 2016 at 2:41:04 AM UTC-4, JUERGEN wrote: >>>> >>>> Stick an FRAM on instead of the RAM and you got a "Disk". >>>> >>>> So is there a small Block Editor around that can be used? >>> >>> With FRAM and a token threaded Forth (like Jupiter ACE's Forth) no Block Editor is needed: programming as you go and editing/debugging the source code directly on chip if needed. >>> >>> The greatest discovery Ken made is demystifying the BSL story! >>> Enables transferring Forth to the MSP430 with no additional hardware. >>> Then Forth makes programming possible directly with the MSP430 alone. >>> Even cloning will be possible this way. >> >> BSL? Boot Strap Loader? >> >> -- >> >> Rick > > Yes! Personally I feel they are a bit overrated. They have to be installed using a JTAG or similar programmer. Then if they are clobbered, back to the programmer. So why not just use one all the time to begin with. Or do I misunderstand what this bootloader is doing? Is it pre-installed by TI? -- Rick
[toc] | [prev] | [next] | [standalone]
| From | visualforth@rocketmail.com |
|---|---|
| Date | 2016-03-31 22:32 -0700 |
| Message-ID | <bcb78e3b-795d-4106-82d5-706f3934e0c5@googlegroups.com> |
| In reply to | #46378 |
On Thursday, March 31, 2016 at 11:28:50 PM UTC-4, rickman wrote: > On 3/31/2016 10:36 PM, visualforth.com wrote: > > On Thursday, March 31, 2016 at 10:08:39 PM UTC-4, rickman wrote: > >> On 3/31/2016 9:54 PM, visualforth.com wrote: > >>> On Thursday, March 31, 2016 at 2:41:04 AM UTC-4, JUERGEN wrote: > >>>> > >>>> Stick an FRAM on instead of the RAM and you got a "Disk". > >>>> > >>>> So is there a small Block Editor around that can be used? > >>> > >>> With FRAM and a token threaded Forth (like Jupiter ACE's Forth) no Block Editor is needed: programming as you go and editing/debugging the source code directly on chip if needed. > >>> > >>> The greatest discovery Ken made is demystifying the BSL story! > >>> Enables transferring Forth to the MSP430 with no additional hardware. > >>> Then Forth makes programming possible directly with the MSP430 alone. > >>> Even cloning will be possible this way. > >> > >> BSL? Boot Strap Loader? > >> > >> -- > >> > >> Rick > > > > Yes! > > Personally I feel they are a bit overrated. They have to be installed > using a JTAG or similar programmer. Then if they are clobbered, back to > the programmer. So why not just use one all the time to begin with. Or > do I misunderstand what this bootloader is doing? Is it pre-installed > by TI? > > -- > > Rick The BSL is part of the MSP430FR2433 ROM.
[toc] | [prev] | [next] | [standalone]
Page 1 of 6 [1] 2 3 4 5 6 Next page →
Back to top | Article view | comp.lang.forth
csiph-web