[Amforth] User exceptions allocation

Hi I have used the following definitions to aid allocating user defined exceptions. In my forth implementation, EXCP# variable is always reset to -4096 at boot time. Greetings Rafael \ EXCEPTION Number handling VARIABLE EXCP# \ initialized to -4096 EXCP# ! at boot time : EXCP-RANGE: ( n1

[Amforth] Bug in ?throw

Hi Matthias Reviewing the file lib/ans94/core-ext/exceptions.frt : ?throw ( f exc -- ) if throw then ; : ?comp ( -- ) state @ 0= -&14 ?throw ; : ?pairs ( n1 n2 -- ) - -&22 ?throw ; I think that the definition of ?throw - as intended in ?comp and ?pairs - is not correct, as

Re: [Amforth] Quiestion about SPI core word spirw.asm

ok, understood. Thank you ! So the optimized routine would be do_spirw: out_ SPDR, tosl do_spirw1: in_ temp0, SPSR sbrs temp0, 7 rjmp do_spirw1 ; wait until complete in_ tosl, SPDR ret Greetings Rafael El Viernes 29 de agosto de 2014 19:37, Matthias Trute escribió:

[Amforth] Quiestion about SPI core word spirw.asm

Hi Amforthers, I was learning a bit about the internals of the SPI driver and finally found the "core" word c!@spi I'm comparing side by side the assembler source with the 328P datasheet (=Arduino) and I can't understand completely the purpose of some of this code, which I list here for conven

Re: [Amforth] Making menus to LCD

You could use a Finite State Machine module. AFAIK, there is one included in the latests amforth release br Rafael De: Hannu Vuolasaho Para: "amforth-devel@lists.sourceforge.net" Enviado: Sábado 24 de agosto de 2013 15:55 Asunto: [Amforth] Making menus to LC

Re: [Amforth] Waking up a dormant forum :-)

One of the criteria that you should use is that the pure assembly implementation should not exceed  in size to the VM assembly implementation +10% (let's give a margin, ok?) Speed, yes but not sacrifying compactness Rafael De: Enoch Para: amforth-devel@lists.so

Re: [Amforth] amforth-shell.py bugfix

Other  interesting papers by the same author http://www.holonforth.com/holon/papers/ef89.htm http://www.holonforth.com/holon/papers/ef94.htm http://www.holonforth.com/holon/papers/ef95.htm De: Rafael Gonzalez Para: Everything around amforth Enviado: Martes

Re: [Amforth] amforth-shell.py bugfix

I think the python script is becoming more and more complex. Maybe it is the time to switch to an umbilical-like system. For that, a new tool is needed and HolonU may be what your are looking for. http://www.holonforth.com/new/holon.html Probably you can attach a communication backend to the ta

Re: [Amforth] imove

mmm ... I think the 200x proposal misses EEPROM as Data space  De: Matthias Trute Para: Everything around amforth Enviado: Miércoles 10 de abril de 2013 20:58 Asunto: Re: [Amforth] imove Hi, > May I suggest renaming the new implementation of imove > ( i-ad

Re: [Amforth] Quite trivial

Sorry, I was referring to Flash addresses.  :-) De: Matthias Trute Para: Everything around amforth Enviado: Martes 2 de abril de 2013 20:08 Asunto: Re: [Amforth] Quite trivial Hi, > Maybe it is a trivial observation, but I see that 2/ is a bad idea for > ad

Re: [Amforth] Quite trivial

Maybe it is a trivial observation, but I see that 2/ is a bad idea for addresses > 32KWhatever (bytes or words) since sign propagation will produce an incorrect address. I defined u2/ myself for that purpose. cheers Rafael   De: Enoch Para: amforth-devel@list

Re: [Amforth] Code snippet

: Enoch Para: amforth-devel@lists.sourceforge.net Enviado: Sábado 16 de febrero de 2013 19:55 Asunto: Re: [Amforth] Code snippet Rafael Gonzalez writes: > Hi, If you want to do a variable jump vector table, that is fine > > If you jump vector table has a known size, you' may also

Re: [Amforth] Code snippet

Hi, If you want to do a variable jump vector table, that is fine If you jump vector table has a known size, you' may also use forth200x structures for field names. That is the approach of forths like VFX Forth for its I/O vectors (GENIO drivers) For something more sophisticated as Finite State

Re: [Amforth] no-wdt

t.asm file is missing. Greetings Rafael De: Enoch Para: amforth-devel@lists.sourceforge.net Enviado: Sábado 16 de febrero de 2013 18:32 Asunto: Re: [Amforth] no-wdt Rafael Gonzalez writes: > Hello list > > Trying to include dict_mcu.inc, I c

[Amforth] no-wdt

Hello list Trying to include dict_mcu.inc, I can't find file  words/no-wdt.asm It seems this file is missing from the distribution (amforth-5.0 or amforth-code trunk) Greetings Rafael -- The Go Parallel Website, sponsore

Re: [Amforth] Assembing Ardunio files

OK, I found this is a known issue in the build.xml file I'm resending my Makefile.  I forgot to include source files dependencies. Cheers Rafael - Mensaje original - De: Rafael Gonzalez Para: "amforth-devel@lists.sourceforge.net" CC: Enviado: Sábado 9 de febrer