hi, forther
I've developped "tinyForth(tF) development" for msp430g2553. It contains
assembler+disassembler+decompiler+xcompiler. Here are the Forth systems that can
be choosed to run in 2553.
The execution file of 4e4th can be found in:
tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx and 99.lst
rename 99.xxx to 99.exe to execute.
now just type 99.exe
words'' <-- saving it into a file to read.
flash M
9.6k
The biggest advantage of tF system is that you can design assembly language
program in the same enviroment.
******** choose one ********
0 ( 0.exe) tinyForth(stc) only (
9800~9fff ) for 32k up flash , T in Ra
1 ( 1.exe) 8051 tF only
T in Ra
2 ( 2.exe) tinyForth(stc) only (
f800~ffff ) for 2k up flash , T in Ra
3 ( 3.exe) P.B.'s msp430f1611eForth(dtc)+tinyForth(dtc) (
a000~dfff ) for 32k up flash
4 ( 4.exe) msp430f1611camelForth(itc)+tinyForth(itc) (
e000~fa13 ) for 8k up flash , T in R7
5 ( 5.exe) Dr. C. H. Ting's 430eForth(stc)+tinyForth(stc) (
c000~d74b ) for 16k up flash , T in R4
6 ( 6.exe) msp430g2553mecrispForth(stc)+tinyForth(stc)ledcomm (
d800~ffff ) for 16k up flash
7 ( 7.exe) Dr. L. C. Wang's 430eForth(stc)+tinyForth(stc) (
c000~d74b ) for 16k up flash , T in R4
8 ( 8.exe) tinyForth(stc) only (
c800~cfff ) for 16k up flash , T in Ra
9 ( 9.exe) tinyForth(stc) only (
d000~d7ff ) for 16k up flash , T in Ra
! (11.exe) Dr. C. H. Ting's 430uForth(stc)+tinyForth(stc) (
c000~c800 ) for 2k up flash , T in R4
@ (12.exe) msp430g2553mecrispForth(stc)+tinyForth(stc) (
dc00~ffff ) for 16k up flash
# (13.exe) new msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
c000~ffff ) for 16k up flash , T in R7
$ (14.exe)
other key (99.exe) msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
c000~ffff ) for 16k up flash , T in R7
Re: USB MSP430 LaunchPad from/to PC communication?
Started by ●September 1, 2012
Reply by ●September 1, 20122012-09-01
I am both very interested and completely baffled by this post.
I am familiar w/ forth, but haven't used it in many years (Vic20 & C64 ROMs). So I have no grasp of the various dialects mentioned. I also don't use Windows, so .exe has no significance in my environment (other than to suggest it won't work).
A more complete description of the items in this list would be very helpful. "T in R4" is incomprehensible w/o more information. I am also unable to make sense of the "fooForth + barForth". I would guess that this is meant to indicate the dictionary contains the combined vocabulary from the two dialects, but that's just a guess.
I am using mspdebug to load images to the msp430 Launchpad which have been compiled w/ mspgcc on Solaris and/or Linux.
I would like to suggest that the best place to document this would be on the msp430 wiki as interested parties are more likely to find it there than in a yahoo group file area for the ARM.
Things I would need to be able to use this:
C, forth & assembly source files
description of development system (IAR, CCS, mspgcc or whatever)
summary of relevant features (memory map, peripherals supported, etc)
a few short sentences describing things about each variant not covered by the above
The prospect of being able to develop simple controllers on a bare '2553 using a TTY is very appealing. However, it's not clear yet that that is actually possible.
Have Fun!
Reg
--- On Sat, 9/1/12, h...@yahoo.com.tw wrote:
> From: h...@yahoo.com.tw
> Subject: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
> To: m...
> Date: Saturday, September 1, 2012, 12:53 AM
> hi, forther
> I've developped "tinyForth(tF)
> development" for msp430g2553. It contains
> assembler+disassembler+decompiler+xcompiler. Here are the
> Forth systems that can be choosed to run in 2553.
> The execution file of 4e4th can be found in:
> tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx
> and 99.lst
> rename 99.xxx to 99.exe to execute.
> now just type 99.exe
> words'' <-- saving it into a file to read.
> flash M
> 9.6k
>
> The biggest advantage of tF system is that you can design
> assembly language program in the same enviroment.
>
>
>
> ******** choose one ********
> 0 ( 0.exe)
>
> tinyForth(stc)
> only( 9800~9fff ) for 32k up flash , T in
> Ra
> 1 ( 1.exe)
>
> 8051
> tF only
>
> T in Ra
> 2 ( 2.exe)
>
> tinyForth(stc)
> only( f800~ffff ) for 2k up flash ,
> T in Ra
> 3 ( 3.exe)
> P.B.'smsp430f1611eForth(dtc)+tinyForth(dtc)
> ( a000~dfff ) for 32k up flash
> 4 ( 4.exe)
> msp430f1611camelForth(itc)+tinyForth(itc)
> ( e000~fa13 ) for 8k up flash , T
> in R7
> 5 ( 5.exe) Dr. C. H. Ting's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 6 ( 6.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)ledcomm
> ( d800~ffff ) for 16k up flash
> 7 ( 7.exe) Dr. L. C. Wang's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 8 ( 8.exe)
>
> tinyForth(stc)
> only( c800~cfff ) for 16k up flash , T in
> Ra
> 9 ( 9.exe)
>
> tinyForth(stc)
> only( d000~d7ff ) for 16k up flash , T in
> Ra
> ! (11.exe) Dr. C. H. Ting's
> 430uForth(stc)+tinyForth(stc) (
> c000~c800 ) for 2k up flash , T in R4
> @ (12.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)
> ( dc00~ffff ) for 16k up flash
> # (13.exe) new
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
> $ (14.exe)
> other key (99.exe)
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
>
>
>
>
>
>
>
I am familiar w/ forth, but haven't used it in many years (Vic20 & C64 ROMs). So I have no grasp of the various dialects mentioned. I also don't use Windows, so .exe has no significance in my environment (other than to suggest it won't work).
A more complete description of the items in this list would be very helpful. "T in R4" is incomprehensible w/o more information. I am also unable to make sense of the "fooForth + barForth". I would guess that this is meant to indicate the dictionary contains the combined vocabulary from the two dialects, but that's just a guess.
I am using mspdebug to load images to the msp430 Launchpad which have been compiled w/ mspgcc on Solaris and/or Linux.
I would like to suggest that the best place to document this would be on the msp430 wiki as interested parties are more likely to find it there than in a yahoo group file area for the ARM.
Things I would need to be able to use this:
C, forth & assembly source files
description of development system (IAR, CCS, mspgcc or whatever)
summary of relevant features (memory map, peripherals supported, etc)
a few short sentences describing things about each variant not covered by the above
The prospect of being able to develop simple controllers on a bare '2553 using a TTY is very appealing. However, it's not clear yet that that is actually possible.
Have Fun!
Reg
--- On Sat, 9/1/12, h...@yahoo.com.tw wrote:
> From: h...@yahoo.com.tw
> Subject: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
> To: m...
> Date: Saturday, September 1, 2012, 12:53 AM
> hi, forther
> I've developped "tinyForth(tF)
> development" for msp430g2553. It contains
> assembler+disassembler+decompiler+xcompiler. Here are the
> Forth systems that can be choosed to run in 2553.
> The execution file of 4e4th can be found in:
> tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx
> and 99.lst
> rename 99.xxx to 99.exe to execute.
> now just type 99.exe
> words'' <-- saving it into a file to read.
> flash M
> 9.6k
>
> The biggest advantage of tF system is that you can design
> assembly language program in the same enviroment.
>
>
>
> ******** choose one ********
> 0 ( 0.exe)
>
> tinyForth(stc)
> only( 9800~9fff ) for 32k up flash , T in
> Ra
> 1 ( 1.exe)
>
> 8051
> tF only
>
> T in Ra
> 2 ( 2.exe)
>
> tinyForth(stc)
> only( f800~ffff ) for 2k up flash ,
> T in Ra
> 3 ( 3.exe)
> P.B.'smsp430f1611eForth(dtc)+tinyForth(dtc)
> ( a000~dfff ) for 32k up flash
> 4 ( 4.exe)
> msp430f1611camelForth(itc)+tinyForth(itc)
> ( e000~fa13 ) for 8k up flash , T
> in R7
> 5 ( 5.exe) Dr. C. H. Ting's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 6 ( 6.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)ledcomm
> ( d800~ffff ) for 16k up flash
> 7 ( 7.exe) Dr. L. C. Wang's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 8 ( 8.exe)
>
> tinyForth(stc)
> only( c800~cfff ) for 16k up flash , T in
> Ra
> 9 ( 9.exe)
>
> tinyForth(stc)
> only( d000~d7ff ) for 16k up flash , T in
> Ra
> ! (11.exe) Dr. C. H. Ting's
> 430uForth(stc)+tinyForth(stc) (
> c000~c800 ) for 2k up flash , T in R4
> @ (12.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)
> ( dc00~ffff ) for 16k up flash
> # (13.exe) new
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
> $ (14.exe)
> other key (99.exe)
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
>
>
>
>
>
>
>
Reply by ●September 2, 20122012-09-02
> I am both very interested and completely baffled by
this post.
Ans: I'm very grateful for your attention. As for baffled that's in my predition. since this the first design style you've never seen before. If one is patient with this he/she will find this is an excellent job to do.
> I am familiar w/ forth, but haven't used it in many years (Vic20 & C64 ROMs). So I have no grasp of the
> various dialects mentioned. I also don't use Windows, so .exe has no significance in my environment
> ( other than to suggest it won't work).
> A more complete description of the items in this list would be very helpful.
Ans: A complete souce code can be found in the original souce code. The decompiled/disassembled listing is just for reference only.
> "T in R4" is incomprehensible w/o more information.
Ans: In forth VM ( Virture Machine ), T stands for Top of data stack.. S means Second item of the data stack.
sp == stack pointer, rp == return stack pointer and so forth.
> I am also unable to make sense of the "fooForth + barForth".
Ans: tF == tinyForth == a very small workable Forth. everything can start from the smallest one.
I'd suggest that experence forther can try this in his interest. Under the executing of fooForth you can type tF to enter it. now type C to see the data stack Content, D to enter Data. B to Branch to the code field address ( cfa ) of the code. It very interesting and useful. Practice it now.
After doing that type to return to pc side. You can type IC ( Interactive Communication ) to talk with tF.
With this it's just like a umbilical Forth.
> I am using mspdebug to load images to the msp430 Launchpad which have been compiled w/ mspgcc on
> Solaris and/or Linux.
Ans: My system is win32for 4.2.671. The newer version can not work.
> I would like to suggest that the best place to document this would be on the msp430 wiki as interested parties > are more likely to find it there than in a yahoo group file area for the ARM.
Ans: You're right.
> Things I would need to be able to use this:
> C, forth & assembly source files
> description of development system (IAR, CCS, mspgcc or whatever)
> summary of relevant features (memory map, peripherals supported, etc)
Ans: Forth can be developped under forth is the best pollice.
a few short sentences describing things about each variant not covered by the above
>The prospect of being able to develop simple controllers on a bare '2553 using a TTY is very appealing. >However, it's not clear yet that that is actually possible.
Ans: Definitly yes.
Just execute 99.exe and then
flash M
you can start your debug session interactively.
Or just add a new instruction, for instance,
: T1 1111 . ;
flash M
Your new instruction has been added to the flash memory.
You don't have to read a lot of manual to know how to use it. Congratulations.
I need to know someone who already understand how to play with this to respond to the public.
This can testify that how easy it is to use with this system.
more on this:
see'' drop <-- more things to see.see' green' <-- redesigning GREEN as assembly language program.see' pwm%' <-- redesigning RED assembly language program.
see' cold
h1 words''
h2 words''
...
h15 words''
Notice that the decompiled code can be used as the source code.
Still new to come.
________________________________
寄件者： Reginald Beardsley
收件者： m...
寄件日期： 2012/9/1 (週六) 8:58 PM
主旨： Re: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
I am both very interested and completely baffled by this post.
I am familiar w/ forth, but haven't used it in many years (Vic20 & C64 ROMs). So I have no grasp of the various dialects mentioned. I also don't use Windows, so .exe has no significance in my environment (other than to suggest it won't work).
A more complete description of the items in this list would be very helpful. "T in R4" is incomprehensible w/o more information. I am also unable to make sense of the "fooForth + barForth". I would guess that this is meant to indicate the dictionary contains the combined vocabulary from the two dialects, but that's just a guess.
I am using mspdebug to load images to the msp430 Launchpad which have been compiled w/ mspgcc on Solaris and/or Linux.
I would like to suggest that the best place to document this would be on the msp430 wiki as interested parties are more likely to find it there than in a yahoo group file area for the ARM.
Things I would need to be able to use this:
C, forth & assembly source files
description of development system (IAR, CCS, mspgcc or whatever)
summary of relevant features (memory map, peripherals supported, etc)
a few short sentences describing things about each variant not covered by the above
The prospect of being able to develop simple controllers on a bare '2553 using a TTY is very appealing. However, it's not clear yet that that is actually possible.
Have Fun!
Reg
--- On Sat, 9/1/12, mailto:holinepu%40yahoo.com.tw wrote:
> From: mailto:holinepu%40yahoo.com.tw
> Subject: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
> To: mailto:msp430%40yahoogroups.com
> Date: Saturday, September 1, 2012, 12:53 AM
> hi, forther
> I've developped "tinyForth(tF)
> development" for msp430g2553. It contains
> assembler+disassembler+decompiler+xcompiler. Here are the
> Forth systems that can be choosed to run in 2553.
> The execution file of 4e4th can be found in:
> tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx
> and 99.lst
> rename 99.xxx to 99.exe to execute.
> now just type 99.exe
> words'' <-- saving it into a file to read.
> flash M
> 9.6k
>
> The biggest advantage of tF system is that you can design
> assembly language program in the same enviroment.
>
>
>
> ******** choose one ********
> 0 ( 0.exe)
>
> tinyForth(stc)
> only ( 9800~9fff ) for 32k up flash , T in
> Ra
> 1 ( 1.exe)
>
> 8051
> tF only
>
> T in Ra
> 2 ( 2.exe)
>
> tinyForth(stc)
> only ( f800~ffff ) for 2k up flash ,
> T in Ra
> 3 ( 3.exe)
> P.B.'s msp430f1611eForth(dtc)+tinyForth(dtc)
> ( a000~dfff ) for 32k up flash
> 4 ( 4.exe)
> msp430f1611camelForth(itc)+tinyForth(itc)
> ( e000~fa13 ) for 8k up flash , T
> in R7
> 5 ( 5.exe) Dr. C. H. Ting's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 6 ( 6.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)ledcomm
> ( d800~ffff ) for 16k up flash
> 7 ( 7.exe) Dr. L. C. Wang's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 8 ( 8.exe)
>
> tinyForth(stc)
> only ( c800~cfff ) for 16k up flash , T in
> Ra
> 9 ( 9.exe)
>
> tinyForth(stc)
> only ( d000~d7ff ) for 16k up flash , T in
> Ra
> ! (11.exe) Dr. C. H. Ting's
> 430uForth(stc)+tinyForth(stc) (
> c000~c800 ) for 2k up flash , T in R4
> @ (12.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)
> ( dc00~ffff ) for 16k up flash
> # (13.exe) new
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
> $ (14.exe)
> other key (99.exe)
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
>
>
>
>
>
>
>
Ans: I'm very grateful for your attention. As for baffled that's in my predition. since this the first design style you've never seen before. If one is patient with this he/she will find this is an excellent job to do.
> I am familiar w/ forth, but haven't used it in many years (Vic20 & C64 ROMs). So I have no grasp of the
> various dialects mentioned. I also don't use Windows, so .exe has no significance in my environment
> ( other than to suggest it won't work).
> A more complete description of the items in this list would be very helpful.
Ans: A complete souce code can be found in the original souce code. The decompiled/disassembled listing is just for reference only.
> "T in R4" is incomprehensible w/o more information.
Ans: In forth VM ( Virture Machine ), T stands for Top of data stack.. S means Second item of the data stack.
sp == stack pointer, rp == return stack pointer and so forth.
> I am also unable to make sense of the "fooForth + barForth".
Ans: tF == tinyForth == a very small workable Forth. everything can start from the smallest one.
I'd suggest that experence forther can try this in his interest. Under the executing of fooForth you can type tF to enter it. now type C to see the data stack Content, D to enter Data. B to Branch to the code field address ( cfa ) of the code. It very interesting and useful. Practice it now.
After doing that type to return to pc side. You can type IC ( Interactive Communication ) to talk with tF.
With this it's just like a umbilical Forth.
> I am using mspdebug to load images to the msp430 Launchpad which have been compiled w/ mspgcc on
> Solaris and/or Linux.
Ans: My system is win32for 4.2.671. The newer version can not work.
> I would like to suggest that the best place to document this would be on the msp430 wiki as interested parties > are more likely to find it there than in a yahoo group file area for the ARM.
Ans: You're right.
> Things I would need to be able to use this:
> C, forth & assembly source files
> description of development system (IAR, CCS, mspgcc or whatever)
> summary of relevant features (memory map, peripherals supported, etc)
Ans: Forth can be developped under forth is the best pollice.
a few short sentences describing things about each variant not covered by the above
>The prospect of being able to develop simple controllers on a bare '2553 using a TTY is very appealing. >However, it's not clear yet that that is actually possible.
Ans: Definitly yes.
Just execute 99.exe and then
flash M
you can start your debug session interactively.
Or just add a new instruction, for instance,
: T1 1111 . ;
flash M
Your new instruction has been added to the flash memory.
You don't have to read a lot of manual to know how to use it. Congratulations.
I need to know someone who already understand how to play with this to respond to the public.
This can testify that how easy it is to use with this system.
see'' drop <-- more things to see.see' green' <-- redesigning GREEN as assembly language program.see' pwm%' <-- redesigning RED assembly language program.
see' cold
h1 words''
h2 words''
...
h15 words''
Notice that the decompiled code can be used as the source code.
Still new to come.
________________________________
寄件者： Reginald Beardsley
收件者： m...
寄件日期： 2012/9/1 (週六) 8:58 PM
主旨： Re: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
I am both very interested and completely baffled by this post.
I am familiar w/ forth, but haven't used it in many years (Vic20 & C64 ROMs). So I have no grasp of the various dialects mentioned. I also don't use Windows, so .exe has no significance in my environment (other than to suggest it won't work).
A more complete description of the items in this list would be very helpful. "T in R4" is incomprehensible w/o more information. I am also unable to make sense of the "fooForth + barForth". I would guess that this is meant to indicate the dictionary contains the combined vocabulary from the two dialects, but that's just a guess.
I am using mspdebug to load images to the msp430 Launchpad which have been compiled w/ mspgcc on Solaris and/or Linux.
I would like to suggest that the best place to document this would be on the msp430 wiki as interested parties are more likely to find it there than in a yahoo group file area for the ARM.
Things I would need to be able to use this:
C, forth & assembly source files
description of development system (IAR, CCS, mspgcc or whatever)
summary of relevant features (memory map, peripherals supported, etc)
a few short sentences describing things about each variant not covered by the above
The prospect of being able to develop simple controllers on a bare '2553 using a TTY is very appealing. However, it's not clear yet that that is actually possible.
Have Fun!
Reg
--- On Sat, 9/1/12, mailto:holinepu%40yahoo.com.tw wrote:
> From: mailto:holinepu%40yahoo.com.tw
> Subject: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
> To: mailto:msp430%40yahoogroups.com
> Date: Saturday, September 1, 2012, 12:53 AM
> hi, forther
> I've developped "tinyForth(tF)
> development" for msp430g2553. It contains
> assembler+disassembler+decompiler+xcompiler. Here are the
> Forth systems that can be choosed to run in 2553.
> The execution file of 4e4th can be found in:
> tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx
> and 99.lst
> rename 99.xxx to 99.exe to execute.
> now just type 99.exe
> words'' <-- saving it into a file to read.
> flash M
> 9.6k
>
> The biggest advantage of tF system is that you can design
> assembly language program in the same enviroment.
>
>
>
> ******** choose one ********
> 0 ( 0.exe)
>
> tinyForth(stc)
> only ( 9800~9fff ) for 32k up flash , T in
> Ra
> 1 ( 1.exe)
>
> 8051
> tF only
>
> T in Ra
> 2 ( 2.exe)
>
> tinyForth(stc)
> only ( f800~ffff ) for 2k up flash ,
> T in Ra
> 3 ( 3.exe)
> P.B.'s msp430f1611eForth(dtc)+tinyForth(dtc)
> ( a000~dfff ) for 32k up flash
> 4 ( 4.exe)
> msp430f1611camelForth(itc)+tinyForth(itc)
> ( e000~fa13 ) for 8k up flash , T
> in R7
> 5 ( 5.exe) Dr. C. H. Ting's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 6 ( 6.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)ledcomm
> ( d800~ffff ) for 16k up flash
> 7 ( 7.exe) Dr. L. C. Wang's
> 430eForth(stc)+tinyForth(stc) (
> c000~d74b ) for 16k up flash , T in R4
> 8 ( 8.exe)
>
> tinyForth(stc)
> only ( c800~cfff ) for 16k up flash , T in
> Ra
> 9 ( 9.exe)
>
> tinyForth(stc)
> only ( d000~d7ff ) for 16k up flash , T in
> Ra
> ! (11.exe) Dr. C. H. Ting's
> 430uForth(stc)+tinyForth(stc) (
> c000~c800 ) for 2k up flash , T in R4
> @ (12.exe)
> msp430g2553mecrispForth(stc)+tinyForth(stc)
> ( dc00~ffff ) for 16k up flash
> # (13.exe) new
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
> $ (14.exe)
> other key (99.exe)
> msp430g2553camelForth(itc)+tinyForth(itc) 4E4TH (
> c000~ffff ) for 16k up flash , T in R7
>
>
>
>
>
>
>
Reply by ●September 2, 20122012-09-02
Reg,
I am ... baffled by this post... in a yahoo group file area for the ARM.
Actually this is the yahoo MSP430 (not ARM) group.
... Things I would need to be able to use this:
C, forth & assembly source files
description of development system (IAR, CCS, mspgcc or whatever)
summary of relevant features (memory map, peripherals supported, etc)
a few short sentences describing things about each variant not covered by the above ...
Dirk (bluebee2012) suggested 4E4th earlier (msg#50638).
http://www.4e4th.eu/ (a click on the British flag switches to English text).
I am ... baffled by this post... in a yahoo group file area for the ARM.
Actually this is the yahoo MSP430 (not ARM) group.
... Things I would need to be able to use this:
C, forth & assembly source files
description of development system (IAR, CCS, mspgcc or whatever)
summary of relevant features (memory map, peripherals supported, etc)
a few short sentences describing things about each variant not covered by the above ...
Dirk (bluebee2012) suggested 4E4th earlier (msg#50638).
http://www.4e4th.eu/ (a click on the British flag switches to English text).
Reply by ●September 2, 20122012-09-02
I'm *quite* aware that the posts are to the msp430 group. However,
that's not where Luke (holinepu) placed the files referenced in his post.
Those are being placed in the files area of armForth.
From the post to which I was responding:
"The execution file of 4e4th can be found in:
tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx and 99.lst"
I'll let his response speak to the rest.
BTW how do you find the message #s you quoted? I can't find how to view them.
Have Fun!
Reg
--- In m..., "old_cow_yellow" wrote:
>
> Reg,
>
> I am ... baffled by this post... in a yahoo group file area for the ARM.
>
> Actually this is the yahoo MSP430 (not ARM) group.
>
> ... Things I would need to be able to use this:
> C, forth & assembly source files
> description of development system (IAR, CCS, mspgcc or whatever)
> summary of relevant features (memory map, peripherals supported, etc)
> a few short sentences describing things about each variant not covered by the above ...
>
> Dirk (bluebee2012) suggested 4E4th earlier (msg#50638).
> http://www.4e4th.eu/ (a click on the British flag switches to English text).
>
From the post to which I was responding:
"The execution file of 4e4th can be found in:
tech.groups.yahoo.com/group/armForth/files/msp430/99.xxx and 99.lst"
I'll let his response speak to the rest.
BTW how do you find the message #s you quoted? I can't find how to view them.
Have Fun!
Reg
--- In m..., "old_cow_yellow" wrote:
>
> Reg,
>
> I am ... baffled by this post... in a yahoo group file area for the ARM.
>
> Actually this is the yahoo MSP430 (not ARM) group.
>
> ... Things I would need to be able to use this:
> C, forth & assembly source files
> description of development system (IAR, CCS, mspgcc or whatever)
> summary of relevant features (memory map, peripherals supported, etc)
> a few short sentences describing things about each variant not covered by the above ...
>
> Dirk (bluebee2012) suggested 4E4th earlier (msg#50638).
> http://www.4e4th.eu/ (a click on the British flag switches to English text).
>
Reply by ●September 2, 20122012-09-02
--- On Sun, 9/2/12, old_cow_yellow wrote:
[snip]
>
> Dirk (bluebee2012) suggested 4E4th earlier
> (msg#50638).
> http://www.4e4th.eu/ (a click on the British flag
> switches to English text).
MANY thanks!!! I don't know how I missed this, but it's exactly what I want. It's arguably much more capable than the Vic20 I learned forth on and much smaller and cheaper.
I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
Have Fun!
Reg
[snip]
>
> Dirk (bluebee2012) suggested 4E4th earlier
> (msg#50638).
> http://www.4e4th.eu/ (a click on the British flag
> switches to English text).
MANY thanks!!! I don't know how I missed this, but it's exactly what I want. It's arguably much more capable than the Vic20 I learned forth on and much smaller and cheaper.
I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
Have Fun!
Reg
Reply by ●September 2, 20122012-09-02
On Sun, Sep 2, 2012 at 4:16 PM, Reginald Beardsley wrote:
> I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
NXP recently released the LPC1114 in 28 pin DIP format, and they can
be has as cheaply as $1.26 in single-unit quantities. I'd be willing
to bet that clocked at 50 MHz and running 6502 emulation software it
could run faster than a native 6502 at 1 MHz, and it could probably do
VGA generation at the same time.
I ported Adam Dunkels uBasic to the MSP430, using the serial port for
I/O and saving the BASIC code to FLASH on-the-fly. Yes, dealing flash
memory management was a bit of a PITA as you might expect.
Unfortunately it was a *very* tight fit on the 2553, but it should run
very nicely on the ARM, once I learn ARM development, that is.
-p.
> I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
NXP recently released the LPC1114 in 28 pin DIP format, and they can
be has as cheaply as $1.26 in single-unit quantities. I'd be willing
to bet that clocked at 50 MHz and running 6502 emulation software it
could run faster than a native 6502 at 1 MHz, and it could probably do
VGA generation at the same time.
I ported Adam Dunkels uBasic to the MSP430, using the serial port for
I/O and saving the BASIC code to FLASH on-the-fly. Yes, dealing flash
memory management was a bit of a PITA as you might expect.
Unfortunately it was a *very* tight fit on the 2553, but it should run
very nicely on the ARM, once I learn ARM development, that is.
-p.
Reply by ●September 2, 20122012-09-02
Reg,
I bought a 6502 from Chuck Peddle in San Francisco for $30 and it had 40 pins!
Back to 4E4th, did you try it without using any assembler?
Get http://www.forth-ev.de/repos/4e4th/Release0.34/Exe/4e4th.a43
Use mspdebug to load to a G2553 on a LaunchPad (check jumpers for download)
Power down, check jumpers for RXD & TXD
Power up and connect to your terminal emulator at 9600 b/s, press Reset of LaunchPad
--OCY
--- In m..., Reginald Beardsley wrote:
>
> --- On Sun, 9/2/12, old_cow_yellow wrote:
>
> [snip]
>
> >
> > Dirk (bluebee2012) suggested 4E4th earlier
> > (msg#50638).
> > http://www.4e4th.eu/ (a click on the British flag
> > switches to English text).
> >
> > MANY thanks!!! I don't know how I missed this, but it's exactly what I want. It's arguably much more capable than the Vic20 I learned forth on and much smaller and cheaper.
>
> I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
>
> Have Fun!
> Reg
>
I bought a 6502 from Chuck Peddle in San Francisco for $30 and it had 40 pins!
Back to 4E4th, did you try it without using any assembler?
Get http://www.forth-ev.de/repos/4e4th/Release0.34/Exe/4e4th.a43
Use mspdebug to load to a G2553 on a LaunchPad (check jumpers for download)
Power down, check jumpers for RXD & TXD
Power up and connect to your terminal emulator at 9600 b/s, press Reset of LaunchPad
--OCY
--- In m..., Reginald Beardsley wrote:
>
> --- On Sun, 9/2/12, old_cow_yellow wrote:
>
> [snip]
>
> >
> > Dirk (bluebee2012) suggested 4E4th earlier
> > (msg#50638).
> > http://www.4e4th.eu/ (a click on the British flag
> > switches to English text).
> >
> > MANY thanks!!! I don't know how I missed this, but it's exactly what I want. It's arguably much more capable than the Vic20 I learned forth on and much smaller and cheaper.
>
> I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
>
> Have Fun!
> Reg
>
Reply by ●September 2, 20122012-09-02
OCY,
I made a 40 pin free run harness to troubleshoot my Vic20 after I shorted the cartridge connector by accident. Turned out I blew some address lines on the PROM. It cost so much for a replacement PROM I bought a C64 instead. Taught me to troubleshoot a computer w/ a schematic and a scope though. Sort of sad sometimes that you can't access the address & data lines anymore on so many things and if you can, they run too fast.
So did you get one from the top of the bowl? ;-)
I've got 4e4th loaded and running. Even turned the LEDs on and off. Good bit of fuss because I'd never setup a USB terminal port on Solaris and had also left off a wire when I built (but did not test) a 3V-5V level shifter to use w/ the USB<->RS-232 adaptor. So I had to fix that first. I haven't been able to get the LaunchPad USB<->Serial connection to work yet because of the weirdness that is Solaris serial port configuration. SunOS 4.1 was so much easier. I'm sure it can be done though as I had no problem loading the image w/ mspdebug using the LaunchPad USB connection.
Now I'm settling down to read the glossary and try to remember how to program in forth after 20+ years of C, FORTRAN and other in fix stuff.
I'm sorely tempted to install a 'G2553 w/ battery in a DB25 so I have a computer in a loopback connector :-)
It would doubtless be far more powerful than what Chuck Moore used when he wrote his first forth.
I've got an old TTY in storage that would be great w/ it. Of course, no one around here would get the joke at all.
Again, many thanks for calling this to my attention. For the sort of things I'll do w/ an MSP430, forth is much more aligned w/ my thinking than C or assembler. Especially considering the problems w/ using gdb. And I just hate doing Windows.
I can't begin to describe how happy I am. Made my day! 4e4th is cool.
Have Fun!
Reg
I made a 40 pin free run harness to troubleshoot my Vic20 after I shorted the cartridge connector by accident. Turned out I blew some address lines on the PROM. It cost so much for a replacement PROM I bought a C64 instead. Taught me to troubleshoot a computer w/ a schematic and a scope though. Sort of sad sometimes that you can't access the address & data lines anymore on so many things and if you can, they run too fast.
So did you get one from the top of the bowl? ;-)
I've got 4e4th loaded and running. Even turned the LEDs on and off. Good bit of fuss because I'd never setup a USB terminal port on Solaris and had also left off a wire when I built (but did not test) a 3V-5V level shifter to use w/ the USB<->RS-232 adaptor. So I had to fix that first. I haven't been able to get the LaunchPad USB<->Serial connection to work yet because of the weirdness that is Solaris serial port configuration. SunOS 4.1 was so much easier. I'm sure it can be done though as I had no problem loading the image w/ mspdebug using the LaunchPad USB connection.
Now I'm settling down to read the glossary and try to remember how to program in forth after 20+ years of C, FORTRAN and other in fix stuff.
I'm sorely tempted to install a 'G2553 w/ battery in a DB25 so I have a computer in a loopback connector :-)
It would doubtless be far more powerful than what Chuck Moore used when he wrote his first forth.
I've got an old TTY in storage that would be great w/ it. Of course, no one around here would get the joke at all.
Again, many thanks for calling this to my attention. For the sort of things I'll do w/ an MSP430, forth is much more aligned w/ my thinking than C or assembler. Especially considering the problems w/ using gdb. And I just hate doing Windows.
I can't begin to describe how happy I am. Made my day! 4e4th is cool.
Have Fun!
Reg
Reply by ●September 2, 20122012-09-02
But it wouldn't be a 6502/6520 chip, which at 50 MHz would be pretty
potent.
I'm hoping that 4e4th will make it to the Piccolo and Stellaris LaunchPads. A common, self hosting development environment would be very useful for one off projects.
--- On Sun, 9/2/12, Peter Johansson wrote:
From: Peter Johansson
Subject: Re: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
To: m...
Date: Sunday, September 2, 2012, 3:52 PM
On Sun, Sep 2, 2012 at 4:16 PM, Reginald Beardsley wrote:
> I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
NXP recently released the LPC1114 in 28 pin DIP format, and they can
be has as cheaply as $1.26 in single-unit quantities. I'd be willing
to bet that clocked at 50 MHz and running 6502 emulation software it
could run faster than a native 6502 at 1 MHz, and it could probably do
VGA generation at the same time.
I ported Adam Dunkels uBasic to the MSP430, using the serial port for
I/O and saving the BASIC code to FLASH on-the-fly. Yes, dealing flash
memory management was a bit of a PITA as you might expect.
Unfortunately it was a *very* tight fit on the 2553, but it should run
very nicely on the ARM, once I learn ARM development, that is.
-p.
I'm hoping that 4e4th will make it to the Piccolo and Stellaris LaunchPads. A common, self hosting development environment would be very useful for one off projects.
--- On Sun, 9/2/12, Peter Johansson wrote:
From: Peter Johansson
Subject: Re: [msp430] Re: USB MSP430 LaunchPad from/to PC communication?
To: m...
Date: Sunday, September 2, 2012, 3:52 PM
On Sun, Sep 2, 2012 at 4:16 PM, Reginald Beardsley wrote:
> I still wouldn't turn my nose up at a Vic20 in a $2 20 pin DIP though ;-) I've always liked the 6502 instruction set.
NXP recently released the LPC1114 in 28 pin DIP format, and they can
be has as cheaply as $1.26 in single-unit quantities. I'd be willing
to bet that clocked at 50 MHz and running 6502 emulation software it
could run faster than a native 6502 at 1 MHz, and it could probably do
VGA generation at the same time.
I ported Adam Dunkels uBasic to the MSP430, using the serial port for
I/O and saving the BASIC code to FLASH on-the-fly. Yes, dealing flash
memory management was a bit of a PITA as you might expect.
Unfortunately it was a *very* tight fit on the 2553, but it should run
very nicely on the ARM, once I learn ARM development, that is.
-p.
