amforth-devel — Development discussion and user support

[Amforth] Soft Serial Port

[Jan K. <jan...@ic...>]

Hello,

Is soft-serial implemented in amForth.
I wont to connect a serial device to the arduino.

Cheers,

Jan

Re: [Amforth] Butterfly

[Jan K. <jan...@ic...>]

Hi Martin,

Thanks for the link, found the hex files.
Do you know where the find the the fuse settings?
Can I use the “amforth-shell.py” for programming the Butterfly? 

Mit freundlichem Gruß
Jan


> Op 20 jan. 2019, om 08:40 heeft Martin Bitter <mar...@t-...> het volgende geschreven:
> 
> Hi Jan,
> 
> in amforth 6.3 there is a folder .../appl/avr-butterfly/
> 
> Regards
> 
> Martin
> 
> 
> 
> Am Samstag, 19. Januar 2019, 19:00:25 CET schrieb Jan Kromhout:
>> Hello,
>> 
>> Is there an amForth hex file for the Butterfly available?
>> 
>> Cheers,
>> 
>> Jan
>> 
>> 
>> 
>> _______________________________________________
>> Amforth-devel mailing list for http://amforth.sf.net/
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
> 
> 
> -- 
> Getippt im 9-Fingersystem von mir selbst.
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] Butterfly

[Martin B. <mar...@t-...>]

Hi Jan,

in amforth 6.3 there is a folder .../appl/avr-butterfly/

Regards

Martin



Am Samstag, 19. Januar 2019, 19:00:25 CET schrieb Jan Kromhout:
> Hello,
> 
> Is there an amForth hex file for the Butterfly available?
> 
> Cheers,
> 
> Jan
> 
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel


-- 
Getippt im 9-Fingersystem von mir selbst.

Re: [Amforth] Butterfly

[Martin B. <mar...@t-...>]

Hi Jan

don't know if this is up to date.

https://wiki.forth-ev.de/doku.php/projects:avr:hilfsmittel

May the forth be with you!

Martin



Am Samstag, 19. Januar 2019, 19:00:25 CET schrieb Jan Kromhout:
> Hello,
> 
> Is there an amForth hex file for the Butterfly available?
> 
> Cheers,
> 
> Jan
> 
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel


-- 
Getippt im 9-Fingersystem von mir selbst.

[Amforth] Butterfly

[Jan K. <kro...@ho...>]

Hello,

Is there an amForth hex file for the Butterfly available?

Cheers,

Jan

Re: [Amforth] Error

[Erich W. <ew....@na...>]

Hello Jan,

> Where can I find some description of the used error numbers?
>
> I have now -4

read the fine document at
http://amforth.sourceforge.net/TG/Architecture.html#exceptions

:-)
Erich

-- 
May the Forth be with you ...

Re: [Amforth] Error

[Matthias T. <mt...@we...>]

Hi,

> Where can I find some description of the used error numbers?
> 
> I have now -4

This is an exception, as explained in
http://amforth.sourceforge.net/TG/recipes/Exceptions.html

it has a link to the complete table at
http://amforth.sourceforge.net/TG/Architecture.html#exceptiontable


HTH
Matthias

[Amforth] Error

[Jan K. <kro...@ho...>]

Hello,

Where can I find some description of the used error numbers?

I have now -4

Cheers,

Jan

Re: [Amforth] String

[Jan K. <kro...@ho...>]

Thanks, it is working now. Next time I will read more careful!

Cheers,

Jan



> Op 18 jan. 2019, om 16:01 heeft Richard Burden <ric...@gm...> het volgende geschreven:
> 
> Jan
> 
> The hint on the suggested page is ITYPE.
> 
> Regards
> Richard
> 
> 
> On Fri., 18 Jan. 2019, 10:53 pm Jan Kromhout via Amforth-devel <
> amf...@li... wrote:
> 
>> Hi Matthias,
>> 
>> I have read that but it is not working.
>> 
>> : test s" test " type ;  => no output
>> : test s" test “         ;  => no output
>> 
>> I don’t know what is wrong!
>> 
>> Jan
>> 
>> 
>>> Op 18 jan. 2019, om 15:50 heeft Matthias Trute <mt...@we...> het
>> volgende geschreven:
>>> 
>>> Hi Jan,
>>> 
>>>> I try this and notting is happens. How do I use this to print a
>>>> string when I run a compiled word?
>>> 
>>> please have a look at
>>> 
>>> http://amforth.sourceforge.net/TG/recipes/Simple-Strings.html
>>> 
>>> it should answer your question(s)
>>> 
>>> Matthias
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Amforth-devel mailing list for http://amforth.sf.net/
>>> Amf...@li...
>>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>> 
>> 
>> 
>> _______________________________________________
>> Amforth-devel mailing list for http://amforth.sf.net/
>> Amf...@li...
>> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] String

[Richard B. <ric...@gm...>]

Jan

The hint on the suggested page is ITYPE.

Regards
Richard


On Fri., 18 Jan. 2019, 10:53 pm Jan Kromhout via Amforth-devel <
amf...@li... wrote:

> Hi Matthias,
>
> I have read that but it is not working.
>
>  : test s" test " type ;  => no output
>  : test s" test “         ;  => no output
>
> I don’t know what is wrong!
>
> Jan
>
>
> > Op 18 jan. 2019, om 15:50 heeft Matthias Trute <mt...@we...> het
> volgende geschreven:
> >
> > Hi Jan,
> >
> >> I try this and notting is happens. How do I use this to print a
> >> string when I run a compiled word?
> >
> > please have a look at
> >
> > http://amforth.sourceforge.net/TG/recipes/Simple-Strings.html
> >
> > it should answer your question(s)
> >
> > Matthias
> >
> >
> >
> >
> > _______________________________________________
> > Amforth-devel mailing list for http://amforth.sf.net/
> > Amf...@li...
> > https://lists.sourceforge.net/lists/listinfo/amforth-devel
>
>
>
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel
>

Re: [Amforth] String

[Jan K. <jan...@ic...>]

Hi Matthias,

I have read that but it is not working.

 : test s" test " type ;  => no output
 : test s" test “         ;  => no output 

I don’t know what is wrong!

Jan


> Op 18 jan. 2019, om 15:50 heeft Matthias Trute <mt...@we...> het volgende geschreven:
> 
> Hi Jan,
> 
>> I try this and notting is happens. How do I use this to print a
>> string when I run a compiled word?
> 
> please have a look at
> 
> http://amforth.sourceforge.net/TG/recipes/Simple-Strings.html
> 
> it should answer your question(s)
> 
> Matthias
> 
> 
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] String

[Matthias T. <mt...@we...>]

Hi Jan,

> I try this and notting is happens. How do I use this to print a
> string when I run a compiled word?

please have a look at

http://amforth.sourceforge.net/TG/recipes/Simple-Strings.html

it should answer your question(s)

Matthias

[Amforth] String

[Jan K. <jan...@ic...>]

Hello,


I try this and notting is happens. How do I use this to print a string when I run a compiled word?


  : test s" test " type ; 


Cheers,

Jan
 

[Amforth] New release 6.8

[Matthias T. <mt...@we...>]

Hi,

It's been a long time since the last release so
I felt it's time for a new one.

The release 6.8 is an adventure release. It is
for the brave ones. It contains experimental 
stuff that is not yet stabilized. It's more a 
snapshot release of a work in progress. I welcome
feedback, patches etc.

The RISC-V can now compile to RAM. The amforth-shell 
utility can be used to upload code, some examples that 
are close to the CPU are included. Note that the dictionary
search is still awfully slow.

A by-product of the work on the RISC-V is another 
platform that found it's way to amforth: ARM. First 
with an old Launchpad Stellaris board, nobody but me 
probably still owns, and later on Linux too. To be 
more precious it runs inside a qemu on a PC and nativly on 
a Raspberry Pi. The Raspberry Pi can build amforth with 
the standard binutils too. This opens a door to the 
fascinating world of the Linux platform from the lowest 
level up. Since it's not running bare metal, all features of 
Linux are available, as long as ... code gets written. There 
is no interface to C libs, hard core syscall swi#0 is the 
way to go, examples included :)

Both 32-bit platforms share a great amount of code, and the
build toolchain too. All that would not be possible without
the work of Matthias Koch, the author of another great
Forth system called mecrisp. His system is much more 
complex however, I like the simple ones better ;)

All information about the new platforms is at the
website http://amforth.sf.net/.

What about the platforms AVR and MSP430? They got 
some small fixes, but nothing really breathtaking.
Update is recommended, but not strictly necessary.

Thanks to all, who contributed and kept the mailing 
list active. Your work is very appreciated!

Have fun
Matthias

Re: [Amforth] Reading from a TM1638

[Matthias T. <mt...@we...>]

Am Donnerstag, den 03.01.2019, 15:49 +0000 schrieb Jan Kromhout:
> hello,
> 
> The best wishes for 2019.

>From my side too :=)

> 
> I’m try to get info from a TM1638 ( reading button status).
> This is my simple routine, I read the lower byte first!
> The code is simple and is straight forward
> Is the code correct?

Does it work as expected? I'd add a delay between the
clock-pin high and the data-pin high? to let things
stabilize. -> check the datasheet/code examples for 
the chip.

Matthias

Re: [Amforth] microsecond delay

[Matthias T. <mt...@we...>]

Am Freitag, den 04.01.2019, 18:46 +0000 schrieb Tristan Williams:
> 
> On 03Jan19 16:07, Jan Kromhout wrote:
> > Hello,
> > 
> > Is in AmForth a microsecond delay available?
> > 
> > Cheers,
> > 
> > Jan
> > 
> 
> Jan,
> 
> As far as I know, whilst AmForth does have a millisecond word 1ms, it
> does not have an equivelent microsecond word, say 1us. I think it
> would be possible to make one, using 1ms.asm as a template.

A full cycle through the (AVR) inner interpreter takes around 45 
CPU cycles. At 1MHz that translates to 45us *at least*.
Probably the NOOP word is the closest approximation to the
1us, the actual time spent there depends on the cpu frequency.
at 16MHz it comes down to 3us (45/16)


> I have, however, made specific assembler words for specific project
> delays (eg. 250us), for when the existing 1ms was too long.

You may use the macro DELAY that optimizes the cpu cycles to
spent for given fixed delay. It is used in the 1-wire code, but it
cannot be exposed to Forth level due to the very specific operations
it has to do *at compile time*.

Matthias

Re: [Amforth] microsecond delay

[Tristan W. <ho...@tj...>]

On 03Jan19 16:07, Jan Kromhout wrote:
> Hello,
> 
> Is in AmForth a microsecond delay available?
> 
> Cheers,
> 
> Jan
> 

Jan,

As far as I know, whilst AmForth does have a millisecond word 1ms, it
does not have an equivelent microsecond word, say 1us. I think it
would be possible to make one, using 1ms.asm as a template. However,

: 10us ( -- ) 1us 1us 1us 1us 1us 1us 1us 1us 1us 1us ;

would not give the 10 microsecond delay one might hope for because of
the time taken by the inner interpreter between forth words, which I
think, on a 16MHz UNO, is the same order of magnitude as a microsecond[1]. 

I have, however, made specific assembler words for specific project
delays (eg. 250us), for when the existing 1ms was too long.

Tristan

[1] In the absence of an interrupt

[Amforth] microsecond delay

[Jan K. <kro...@ho...>]

Hello,

Is in AmForth a microsecond delay available?

Cheers,

Jan

[Amforth] Reading from a TM1638

[Jan K. <kro...@ho...>]

hello,

The best wishes for 2019.

I’m try to get info from a TM1638 ( reading button status).
This is my simple routine, I read the lower byte first!
The code is simple and is straight forward
Is the code correct?

Does anyone have experience whit  this?


variable received_byte
: receiveByte ( --- byte )
  0 received_byte !
  8 0 do
    clockPin high
    dataPin pin_high?
    if
      received_byte @ 1 i << or received_byte !
    else
      received_byte @ 0 i << or received_byte !
    then
    clockPin low
  loop
  received_byte @  \ byte
;


May the Forth be with you in the new year 2019

Cheers

Jan

[Amforth] Doc: Clockworks Model 4

[Erich W. <ew....@na...>]

Hello,

<shameless advertisement>

for those who like to read other peoples Forth code, I have added
another clock to the commented projects/clockworks. It features a DCF77
radio receiver and reads the time information from there. However, this
code is lengthy.

http://amforth.sourceforge.net/Projects/ClockWorks/index.html#ingredients-and-clocks
Model 4

Errors, corrections and suggestions are welcome!
Thanks to Matthias for hosting these documents.

Cheers,
Erich

</shameless advertisement>



-- 
May the Forth be with you ...

[Amforth] Assembler routines

[Jan K. <kro...@ho...>]

Dear all

When I look to this part of the code of the double add, is it correct that

temp4 to temp 7 is the second part of d+, but how to get the first part?

Thanks again for any help.

Cheers,

Jan


    ld temp2, Y+
    ld temp3, Y+

    ld temp4, Y+  == second item from the stack ==
    ld temp5, Y+
    ld temp6, Y+
    ld temp7, Y+

    add temp2, temp6
    adc temp3, temp7
    adc tosl, temp4
    adc tosh, temp5

Re: [Amforth] Need some help to construct an .asm file

[Jan K. <jan...@ic...>]

Thanks for the rsponse.

Merry Christmad,

Jan

Verstuurd vanaf mijn iPad

> Op 25 dec. 2018 om 10:36 heeft Matthias Trute <mt...@we...> het volgende geschreven:
> 
> Am Montag, den 24.12.2018, 17:51 +0000 schrieb Jan Kromhout:
>> Hello,
>> 
>> I wont to write my own routine in assembler as a learning goal.
>> Have looked into a lot of asm routines, but can’t figure out how to
>> add two doubles into R16 to R23
>> and after the calculation put R16 to R19 back to the stack.
>> 
>> Can I use R16 to R19 freely for my own use, or should I take another
>> set.
>> 
>> The calculation between is no problem.
>> 
>> Please can someone help me out with this,
>> and any help is appriciated!
> 
> The registers that are free to use in own assembly words
> are documented here:
> http://amforth.sourceforge.net/TG/AVR8.html#register-mapping
> 
> The mapping between the temp-Names and the actual registers
> can be found at avr8/macros.asm.
> 
> If you want to go deep into the assembler programming, esp.
> within amforth, I'd strongly recommend, that you study the
> code very carefully. It contains optimizations and macros
> that are not trivially to understand. Adding two double 
> numbers (that is 2x4 avr registers) is more on the
> trivial side however. look at words/d-plus.asm.
> 
> Matthias
> 
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel

Re: [Amforth] Need some help to construct an .asm file

[Matthias T. <mt...@we...>]

Am Montag, den 24.12.2018, 17:51 +0000 schrieb Jan Kromhout:
> Hello,
> 
> I wont to write my own routine in assembler as a learning goal.
> Have looked into a lot of asm routines, but can’t figure out how to
> add two doubles into R16 to R23
> and after the calculation put R16 to R19 back to the stack.
> 
> Can I use R16 to R19 freely for my own use, or should I take another
> set.
> 
> The calculation between is no problem.
> 
> Please can someone help me out with this,
> and any help is appriciated!

The registers that are free to use in own assembly words
are documented here:
http://amforth.sourceforge.net/TG/AVR8.html#register-mapping

The mapping between the temp-Names and the actual registers
can be found at avr8/macros.asm.

If you want to go deep into the assembler programming, esp.
within amforth, I'd strongly recommend, that you study the
code very carefully. It contains optimizations and macros
that are not trivially to understand. Adding two double 
numbers (that is 2x4 avr registers) is more on the
trivial side however. look at words/d-plus.asm.

Matthias

[Amforth] Need some help to construct an .asm file

[Jan K. <kro...@ho...>]

Hello,

I wont to write my own routine in assembler as a learning goal.
Have looked into a lot of asm routines, but can’t figure out how to add two doubles into R16 to R23
and after the calculation put R16 to R19 back to the stack.

Can I use R16 to R19 freely for my own use, or should I take another set.

The calculation between is no problem.

Please can someone help me out with this,
and any help is appriciated!

Cheers,

Jan


Mij template:

; ( d1 d2 -- d1  )
; Math
; Multiplies two doubles (32 bits * 32 bits => 32 bits)
; This is a unsigned 32x32 multiplication


VE_DMUL:
    .dw $ff02
    .db "d*"
    .dw VE_HEAD
    .set VE_HEAD = VE_DMUL
XT_DMUL:
    .dw DO_COLON
PFA_DMUL:

;
; place the top two doubles into R16,R17,R18,R19,R20,R21,R22,R23
; and remove the two doubles of TOS
;

;
; do the calculation
;

;
; place R16,R17,R18,R19 on the top of the stack, so the result is a double.
; do next word
;

    .dw XT_EXIT

Re: [Amforth] Assembler listing of some words

[Jan K. <jan...@ic...>]

Hello Erich,

This was helpfull

Cheers,

Jan





> Op 21 dec. 2018, om 17:15 heeft Erich Wälde <ew....@na...> het volgende geschreven:
> 
> Hello Jan,
> 
> Jan Kromhout via Amforth-devel writes:
> 
>> Hello,
>> 
>> I was looking into some words (.asm).
>> Can someone explain me why the content of the first data word is different.
>> PLUSSTORE => .dw $ff02
>> RSHIFT => .dw $ff06
>> PLUS => .dw $ff01
> 
> I'm sure this is explained somewhere, maybe in the technical guide. But
> I did not find it in 20 seconds, so here we go:
> 
> 
>> $ cat ./avr8/words/plusstore.asm
>> VE_PLUSSTORE:
>>    .dw $ff02
>>    .db "+!"
>>    .dw VE_HEAD
>> ...
> 
> The first .dw entry is "some number", where the low part "02" is the length
> of the string to come. That string is "+!", 2 bytes.
> 
> The high part "ff" is a flags thing. "immediate" words are different:
> 
>> $ cat ./common/words/then.asm
>> ...
>> VE_THEN:
>>    .dw $0004
>>    .db "then"
>> ...
> 
> There might be other values, but I'm not sure.
> 
> This stuff is implementation dependant and may be all different in other
> Forth implementations.
> 
> 
> 
> Cheers,
> Erich
> 
> --
> May the Forth be with you ...
> 
> 
> _______________________________________________
> Amforth-devel mailing list for http://amforth.sf.net/
> Amf...@li...
> https://lists.sourceforge.net/lists/listinfo/amforth-devel