Müsste es dann nicht c!wd heißen?
Michael
2017-05-07 15:42 GMT+02:00 Matthias Trute :
> Hi Tristan,
>
> I've put your code online, revision 2252 contains the new
> file. There is only one change: I renamed the wd! into !wdc.
> It tells "store to watchdog control" and follows the more
> or less in
Is there a link to a list of those strange behaving? May be of use beyond
amforth.
Michael
Am 04.07.2016 20:26 schrieb "Matthias Trute" :
> Hi,
>
> It's been a long time since the last release but some strange
> effects needed to be handled with the FRAM equipped MSP430 devices.
> They behave much
And it was covered in Forth Magazin "Vierte Dimension"
4d2014-01.pdf
www.forth-ev.de --> Menu: Download --> PDF-Archiv
Michael
2015-12-21 15:24 GMT+01:00 craig and heather :
> In case anyone is interested I also coded up the FM radio project in
> AmForth. It is available on my website here:
>
>
Perhaps we should email?
mik.ka...@gmail.com
Am 04.11.2015 10:42 schrieb "Hannu Vuolasaho" :
>
>
> Michael wrote:
> >
> > ; Were'synced
> > ; calculate output part 1
> > ; wait 2300 cycles
> > ; Read inputs
> > ; Choose output port
> > ; calculate output part 2
> > ; 170 cycles after read write ou
2015-01-31 20:27 GMT+01:00 Andrew Holt :
> : test ," Hello" cr ;
does amforth realy have a ," word? (komma-quote)
Try ." instead (dot-quote)
mk
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sp
.-(
2014-10-29 0:02 GMT+01:00 Enoch :
> Hello Matthias,
>
> (1) I don't know what exactly isn't working but between trunk@1680 to
> trunk@1685 there is something that breaks my system badly. System
> reboots on almost any command line input...
>
> (2) Please explain why you changed the lic
ion state.
>
> Paolo
>
> Inviato da Samsung Mobile
>
> Original message
> Subject: Re: [Amforth] R: Re: R: Re: R: Re: HW flow control
> From: Michael Kalus
> To: Everything around amforth
> CC:
>
> Never forget: xon/xoff is for *single* character e
Never forget: xon/xoff is for *single* character exchange - send one,
get echo, check it, send another one...
Sender must interpret *each* echo character immediately and stop at
xoff at once.
Use xon/xoff to connect two amforth devices via TXD/RXD.
Or on a PC use a sending tool able to do that
Hi.
In 4e4th the PROMPT is a forth word, executed right after INTERPRET .
That way it is easy to modify.
I use character ACK ( $06 EMIT ) as signal for the 4e4th-IDE shell.
You may serve other information with the prompt string, like the
current number base, or what ever you need.
mk
; C PROMP
xon/xoff are characters send.
With USB this is does not work better than CR or any other character.
Target and PC do not communicate character by character any more.
Terminal emulaters do not stop in time, there are buffers inbetween,
overrunning oldfashion xon/off protokolls.
Michael
Am 02.0
Hi.
Never split a winning team :-)
Michael
Am 18.05.2014 um 20:38 schrieb Matthias Trute:
> Hi Enoch,
>
>> I understand the reason for the change in trunk@1584 macros.asm, that
>> is, to put things "behind the curtains". However, you have created
>> another forward reference warning, an unneces
Hi.
Am 08.06.2013 um 02:37 schrieb Enoch:
> "Michael Kalus"
> writes:
>
>> Hi.
>>
>>> ..but not sacrifying compactness
>>
>> Here is what you can do with NO vm kernel word at all:
>> http://mecrisp.sourceforge.net/
>>
Hi.
> ..but not sacrifying compactness
Here is what you can do with NO vm kernel word at all:
http://mecrisp.sourceforge.net/
..standalone native code Forth for MSP430 microcontroller chips...
..It fits tightly into 9kb of Flash and runs with 512 Bytes of Ram...
By the way, its free. Use whate
t --
Am 05.05.2013 um 09:23 schrieb Enoch:
> Hello Michael Kalus,
>
> IIRC Matthias mentioned that you have once written a MARKER version
> that
> backs up the entire EEPROM to the Flash memory.
> IMHO that's the correct
> approach. Can you post this code ag
Hi.
What about mnemonic conventions like
.s .r .line ." xxx"
or
key? ?DO
and such? Don't we already use such "unwritten laws"?
Michael
Am 21.03.2013 um 21:24 schrieb Enoch:
> Matthias Trute writes:
>
>> Hi Wis,
>>
>>> It may be a good practice to prefix any "cvariable" name with
Hi.
Lets take a look at some common Forths, Revision appended.
They do it in the typed order left to right.
Only VFX does it top down linewise, like amforth in its older days.
Though not a "standard", typed order is "Normative Kraft des
Faktischen".
(google: "normative power of the factual")
Bro
TERAL
.dw 3
.db "suf",0
.dw XT_ITYPE
.dw XT_EXIT
Am 03.03.2013 um 13:17 schrieb Erich Waelde:
> Michael,
>
> On 03/03/2013 01:00 AM, Michael Kalus wrote:
>
>> Here is the old form for your collection. It is "Stack UnderFlow"
>>
Hi.
Am 02.03.2013 um 21:27 schrieb Enoch:
> : .s ( -- ) \ stack picture listing order
> depth
> begin dup while dup pick . 1- repeat
> drop
> ;
Maybe you want to have that in assembler. mk
-- next part --
-
Hi.
..
> Should I mention, that I collect good tools and ideas? ;)
>>
Here is the old form for your collection. It is "Stack UnderFlow"
save, telling "SUF" if you do one.
Maybe you have it already. Michael
-- next part --
--
Hi.
Am 20.02.2013 um 10:16 schrieb Enoch:
>> So, do I see this right?
>> WIPE restores a known state. This state needs to be calculated at
>> assembly time.
Yes.
>> It includes the initial state of eeprom, wordlist and
>> other pointers, user area, disabling tasks ... where do you stop?
>> Do
Hi Enoch.
Am 20.02.2013 um 04:35 schrieb Enoch:
..
> Honored to meet you, the "4e4th" guy :-)
To tell the truth, most of 4e4th is Camelforth, so Brad deserves the
honor.
Dirk Brühl is the guy with most of the ideas that brought it onto
MSP430 LaunchPad.
And Ulrich Hoffmann contributed as wel
Hi.
> Comments?
:-)
Michael
Am 19.02.2013 um 22:36 schrieb Enoch:
> G'day to you to you all,
>
> I found something that seems to me useful on http://www.4e4th.eu/
>
> WIPE ( -- ) Back to original status. Stacks unchanged. uarea back to
> original.
>
> Having an asm based word which res
Hi Matthias.
...
> There is currently no
> way to switch between forth and machine code (that would
> be ;CODE btw)
You may go from low to high level and back:
code
(some code)
; -- jump to high level:
ldi XL,low(pfa_forthISR)
ldi XH,high(pfa_forthISR)
jmp DO_NEXT
pfa_forthISR:
Hi Wis.
Since Matthias is bussy, maybe I can help out.
Am 31.01.2013 um 21:37 schrieb Macomson, Wis:
> I'm new to this and I'm trying to understand the amForth inner
> interpreter. There are a couple of clarifications in the "amforth
> Documentation, Release 5.1-wip,January 26, 2013" that wo
Hi Hannu.
Am 27.10.2012 um 21:57 schrieb Hannu Vuolasaho:
..
> Am I right if I say it doesn't know my own assembler words?
You are right.
It knows a lot of amforth words which are ANS forth.
As g4 is written in gforth adding more simple words is quite easy.
Take a look at their syntax in those
Hi,
if you need any help with g4 just ask me.
Michael
Am 27.10.2012 um 20:13 schrieb Erich Waelde:
> Hi,
>
> On 10/27/2012 08:06 PM, Enoch wrote:
>> Is there an automated method to compile frt to asm to skip
>> uploading of
>> debugged words?
>
> Have a look at
> http://www.forth-ev.de/repos
Hi.
gforth:
0 0 10 within . -1 ok
-1 0 10 within . 0 ok
9 0 10 within . -1 ok
10 0 10 within . 0 ok
Michael
Am 12.09.2012 um 14:43 schrieb Hannu Vuolasaho:
>
> Hello!
>
> I had standard :
> Secretariat
>
> Computer and Business Equipment Manufacturers Association
> Approved: March 24, 1994
Hi Jan.
CREATE is not statesmart. Use XT_CREATE inside a definition.
Outside a definition CREATE will work.
You have to use _HEX (with a preceeding underscore) in the source to
switch to hex, otherwise you get a translation of the word "HEX" to
asm. And append BYE at the end of file, forth wi
Hi Jan.
..
> I also not find the win32 forth version any more!
> Please can you take a look!
Its still there and updated:
http://www.forth-ev.de/repos/g4/g4w32f.fs
m
--
Live Security Virtual Conference
Exclusive live ev
29 matches
Mail list logo
