flashforth-devel — FlashForth users and developers

[Flashforth-devel] FlashForth for Atmega 2560/2561

[Mikael N. <mik...@pp...>]

There is now a version in the git repository  that supports the Atmega 
2560/2561.

It is only partially tested in the avr studio 4 simulator.

I would appreciate it if someone with a real chip could test it and 
report how it works.

You can clone  the repository with
git clone git://git.code.sf.net/p/flashforth/code flashforth-code

Thanks
/Mike

[Flashforth-devel] atMega 2560 -- easiest method?

[Michael P. <mp...@ca...>]

Can someone point me to a working method that will yield a hex file I 
can use to put FF into
an atMega 2560, or is there someone that's already accomplished this 
that wouldn't mind
sharing their hex file?

Thanks,

Michael
K6MLE

Re: [Flashforth-devel] fl+ in FF4.8

[Pete Z. <pza...@pz...>]

Hi Mike,

Thanks for the info.   The config bits and the programmable pin 
assignments are "challenging".
I thought I was the only one confused.....

Are you using the uart or usb function on the  PIC24FJ256G110 ?

Pete

Re: [Flashforth-devel] fl+ in FF4.8

[Mike M. <mi...@mo...>]

Pete,

We brought FF4.8 up first on the PIC24FJ128GA110 with the Microchip 
Explorer16 board.  All that was needed was to get the clock and PFLASH 
settings right, and switching serial ports.

Switching later to the PIC24FJ256GB110 was a bit more trouble, only 
because Microchip's documentation is so confusing.  We had trouble 
getting the config bits right, and the programmable pin assignments are 
Byzantine.

The PIC24FJ256GB110has flash, but not eeprom.  The flash can be used as 
eeprom, as long as you don't exceed 10000 writes. We are using a battery 
to support the RAM, which works as long as you put it in sleep while 
power is down.  When asleep, it draws a microamp or two.  They do have 
lower power chips, too.

Mike Miller
Moon Valley Circuits
mike@moonvalleycircuits (dot)com
http://www.moonvalleycircuits.com/
(707) 996-4157
12350 Maple Glen Rd.
Glen Ellen, CA 95442

On 9/7/13 7:38 AM, Pete Zawasky wrote:
> Hi Mike,
>
> Also very interested in your results with FF4.8 on the PIC24FJ256GB110.
> Just received the PIC24F Starter Kit DM240011 with the PIC24FJ256GB106.
> Still looking for a good solution for our needs of a 16-bit PIC with USB
> to run FF on (EEPROM or not).
>
> Any hints would be appreciated.
>
> Thanks,
> Pete
>
>
>
>
> ------------------------------------------------------------------------------
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Discover the easy way to master current and previous Microsoft technologies
> and advance your career. Get an incredible 1,500+ hours of step-by-step
> tutorial videos with LearnDevNow. Subscribe today and save!
> http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
>

Re: [Flashforth-devel] fl+ in FF4.8

[Pete Z. <pza...@pz...>]

Hi Mike,

Also very interested in your results with FF4.8 on the PIC24FJ256GB110.
Just received the PIC24F Starter Kit DM240011 with the PIC24FJ256GB106.
Still looking for a good solution for our needs of a 16-bit PIC with USB 
to run FF on (EEPROM or not).

Any hints would be appreciated.

Thanks,
Pete

Re: [Flashforth-devel] fl+ in FF4.8

[Mikael N. <mik...@pp...>]

Hi Mike,
Great to hear that FlashForth is working out for you.

The fl+ and fl- are correct in words.txt but reversed in the code.
Just correct the code and it will work the same way as in other FlashForths.
I will fix that in git.

The flash write should succeed like this:

fl+ 1234 flashVar ! iflush fl-

IFLUSH triggers the write to flash.

Waiting for the C-interface !

BR Mike

On 09/03/2013 10:35 PM, Mike Miller wrote:
> We are nearing completion of our project, using FF4.8 on the
> PIC24FJ256GB110.
> FF has proven to be a robust platform.
> We have found and fixed some minor bugs, which we will later post.
> Tovar has worked out a good interface to C that has C and FF cooperating.
> When it is ready we will post it.
>
> I am currently stuck trying to use fl+ to protect flash.
> BTW: The words.txt file has the definitions of fl- and fl+ reversed.
> I have a few variables that need to be in flash.  I would like to call
> fl+ at startup, locking flash.
> Then, when the code needs to write to a flash variable, it would call
> fl-, write, and then call fl+.
>
> The problem is that I cannot call fl+ from the word that writes to
> flash, or even from the same line at the console.  When I try, the
> routine LOCKED: calls an address error, apparently because it is not
> done writing?
> Adding a long delay before fl+ does not work.
> I can call fl+ from a new line at the console after the write without error.
>
> Is there a bit or flag that I can test to tell when the flash write is
> done, before calling fl+ ?
>
> 73
>

[Flashforth-devel] fl+ in FF4.8

[Mike M. <mi...@mo...>]

We are nearing completion of our project, using FF4.8 on the 
PIC24FJ256GB110.
FF has proven to be a robust platform.
We have found and fixed some minor bugs, which we will later post.
Tovar has worked out a good interface to C that has C and FF cooperating.
When it is ready we will post it.

I am currently stuck trying to use fl+ to protect flash.
BTW: The words.txt file has the definitions of fl- and fl+ reversed.
I have a few variables that need to be in flash.  I would like to call 
fl+ at startup, locking flash.
Then, when the code needs to write to a flash variable, it would call 
fl-, write, and then call fl+.

The problem is that I cannot call fl+ from the word that writes to 
flash, or even from the same line at the console.  When I try, the 
routine LOCKED: calls an address error, apparently because it is not 
done writing?
Adding a long delay before fl+ does not work.
I can call fl+ from a new line at the console after the write without error.

Is there a bit or flag that I can test to tell when the flash write is 
done, before calling fl+ ?

73

-- 
Mike Miller WB6TMH
Moon Valley Circuits
mike@moonvalleycircuits (dot) com
http://www.moonvalleycircuits.com/
(707) 996-4157
12350 Maple Glen Rd.
Glen Ellen, CA 95442

Re: [Flashforth-devel] PIC18F87J50

[Mikael N. <mik...@pp...>]

Hi,

On 07/25/2013 08:28 PM, Pete Zawasky wrote:
> Hi Mikael,
>
> Upon further review and research through the data sheets, I think the J
> chips (especially the PICF87J50) are not a good match for us and FF.
> The limited FLASH writes are a show stopper.
You are right about that. I had forgotten that the J series has a quite 
small
flash write endurance.
>
> The last board I did contained the PIC18F4550 for USB reasons.  I think
> I will just revisit that design but try to use the newer PIC18F45K50.
Check to which adresses the USB dual port memory is mapped.
Is it the same is in the PIC18F14K series or the 18F2455 series ?

Mike

Re: [Flashforth-devel] PIC18F87J50

[Pete Z. <pza...@pz...>]

Hi Mikael,

Upon further review and research through the data sheets, I think the J 
chips (especially the PICF87J50) are not a good match for us and FF.  
The limited FLASH writes are a show stopper.

The last board I did contained the PIC18F4550 for USB reasons.  I think 
I will just revisit that design but try to use the newer PIC18F45K50.

Pete

Re: [Flashforth-devel] PIC18F87J50

[Pete Z. <pza...@pz...>]

Yes, I thought we covered this (without the USB) almost 2 years ago 
regarding the PIC18F87J11 but I can't find any info here.
I only see  the p18f87j11.cfg file in FF3.8 .
I never tried it as I don't have any PIC18F87J11 chips here, only the 
PIC18F87J50.

Maybe I'm thinking of the PIC33FJ128 in FF4.8 .

Let know if you find anything on the FF that would work on chips with no 
eeprom.


Pete


*****************************************************************************************

Hi Pete,
As you know the J series does not have any eeprom so it does not work
with FF 3.8.

I have a FF3.x  proto for the J series somewhere that could be
integrated into FF 3.8 and the USB lib
recompiled for the 87J50.

BR Mike

Re: [Flashforth-devel] PIC18F87J50

[Mikael N. <mik...@pp...>]

On 07/23/2013 12:15 AM, Pete Zawasky wrote:
> Hi Michael,
>
> Any thoughts/hints on setting up FF3.8 on the PIC18F87J50 ?
> Similar to the PIC18F87J11 but with USB.
> FF_USB_18F87J50.LIB ?
>
> Pete
Hi Pete,
As you know the J series does not have any eeprom so it does not work 
with FF 3.8.

I have a FF3.x  proto for the J series somewhere that could be 
integrated into FF 3.8 and the USB lib
recompiled for the 87J50.

BR Mike

[Flashforth-devel] PIC18F87J50

[Pete Z. <pza...@pz...>]

Hi Michael,

Any thoughts/hints on setting up FF3.8 on the PIC18F87J50 ?
Similar to the PIC18F87J11 but with USB.
FF_USB_18F87J50.LIB ?

Pete

Re: [Flashforth-devel] Servo PIC 18F4620

[Mikael N. <mik...@pp...>]

Hi,
There is no need to recalculate  anything.
Fcy has the value Fosc/4.

BR Mike


On 07/14/2013 02:58 AM, hi...@ao... wrote:
> I am working with the servo example at 
> http://flashforth.sourceforge.net/servo.txt
> and using a PIC 18F4620 running at ~18 Mhz, 9600 BAUD.
> Does the example assume a given clock rate? If so how can I calculate 
> these for my crystal?
> Is the part of the code I should be adjusting?
> Fcy #1000 /          con clk/us
> 0 #1500 clk/us *  -  con midhi
> 0 #500 clk/us * -    con midlo
> 0 #12000 clk/us * -  con endlo
> 0 #2000 clk/us * -   con stime
>
> Many thanks for any direction..
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel

[Flashforth-devel] Servo PIC 18F4620

[<hi...@ao...>]

I am working with the servo example at http://flashforth.sourceforge.net/servo.txt
and using a PIC 18F4620 running at ~18 Mhz, 9600 BAUD. 

Does the example assume a given clock rate? If so how can I calculate these for my crystal? 

Is the part of the code I should be adjusting? 
Fcy #1000 /          con clk/us
0 #1500 clk/us *  -  con midhi
0 #500 clk/us * -    con midlo
0 #12000 clk/us * -  con endlo
0 #2000 clk/us * -   con stime

Many thanks for any direction.. 

Re: [Flashforth-devel] Bug report: Can't write beyond $a300

[Mikael N. <mik...@pp...>]

Thanks Pablo for spotting that.

I hope unsigned compare is used in all other places that does the memory 
mapping.

I will include this fix.

BR Mikael

On 06/17/2013 08:52 PM, Pablo M. Muñoz wrote:
> I think I have found a (small) bug.
>
> In FF 3.8 (original) compiled for a 18F2620, trying to write beyond 
> $a300 gives an "AD?" error.
>
> I have found the problem here:
>
> ISTORECHK:
>         movlw    HIGH dpcode ;(dp_user_dictionary>>8) ;
>         subwf    Srw, W, A
>         btfsc   STATUS, N, A
>         bra     ISTORERR
>         return
>
> The instruction subwf gives a signed result, and sets N if (Srw) - W > $7f
>
> This can be solved with an unsigned compare:
>
> ISTORECHK:
>         movlw    HIGH dpcode ;(dp_user_dictionary>>8) ;
>         cpfslt  Srw, A
>         return
>         bra     ISTORERR
>
> With this change, writes work OK from $2300 to $ebff.
>
> I made this change in order to put the help system at the end of the 
> flash space.
>
>

[Flashforth-devel] Bug report: Can't write beyond $a300

[Pablo M. M. <ea...@ho...>]

I think I have found a (small) bug.

In FF 3.8 (original) compiled for a 18F2620, trying to write beyond $a300 gives an "AD?" error. 

I have found the problem here:

ISTORECHK:
        movlw    HIGH dpcode ;(dp_user_dictionary>>8) ;
        subwf    Srw, W, A
        btfsc   STATUS, N, A
        bra     ISTORERR
        return

The instruction subwf gives a signed result, and sets N if (Srw) - W > $7f

This can be solved with an unsigned compare:

ISTORECHK:
        movlw    HIGH dpcode ;(dp_user_dictionary>>8) ;
        cpfslt  Srw, A
        return
        bra     ISTORERR

With this change, writes work OK from $2300 to $ebff.

I made this change in order to put the help system at the end of the flash space.


Regards, 

    Pablo.
 		 	   		  

Re: [Flashforth-devel] WG: Re: flashforth arduino duemilanove

[Mikael N. <mik...@pp...>]

Right now I have no plans for developing an assembler for the AVR.

If you, or someone is interested to do that, a contribution to 
FlashForth would be welcome.

/Mike

On 06/13/2013 03:07 PM, Sven wrote:
>   Hi Mikael,
>   exactly that was exact my fault. I tried it again, uploaded
>   the flash data first and then the eeprom data with the same
>   result as bevore. Then I tried it viceversa uploaded the
>   eeprom data first and then the flash and that led to
>   success.
>   I then tried the classical LED blink program:
>   
>   marker -blink
>   $24 constant DDRB
>   $25 constant PORTB
>   : led-init $20 DDRB c! ;
>   : led-on $20 PORTB c! ;
>   : led-off $0 PORTB c! ;
>   : led-blink for led-on 100 ms led-off 100 ms next ;
>   
>   That works fine so far but not at the first try. I first
>   used DDRB=0x04 and PORTB=0x05 like it was defined in
>   m328Pdef.inc. After some investigation I found that for most
>   AVR devices, the IO register space is mapped into the data
>   memory address space with an offset of 0x20 since the bottom
>   of this space is reserved for direct access to the MCU
>   registers.
>   
>   Do you have plans to add an assembler, like in the PIC
>   implementation, for the avr flashforth ?
>   
>   thanks for helping
>

[Flashforth-devel] WG: Re: flashforth arduino duemilanove

[Sven <sve...@ya...>]

 Hi Mikael,
 exactly that was exact my fault. I tried it again, uploaded
 the flash data first and then the eeprom data with the same
 result as bevore. Then I tried it viceversa uploaded the
 eeprom data first and then the flash and that led to
 success.
 I then tried the classical LED blink program:
 
 marker -blink
 $24 constant DDRB
 $25 constant PORTB
 : led-init $20 DDRB c! ;
 : led-on $20 PORTB c! ;
 : led-off $0 PORTB c! ;
 : led-blink for led-on 100 ms led-off 100 ms next ;
 
 That works fine so far but not at the first try. I first
 used DDRB=0x04 and PORTB=0x05 like it was defined in
 m328Pdef.inc. After some investigation I found that for most
 AVR devices, the IO register space is mapped into the data
 memory address space with an offset of 0x20 since the bottom
 of this space is reserved for direct access to the MCU
 registers.
 
 Do you have plans to add an assembler, like in the PIC
 implementation, for the avr flashforth ?
 
 thanks for helping
 Sven
 
 

> --- Mikael Nordman <mik...@pp...>
> schrieb am Mi, 12.6.2013:
> 
> > Von: Mikael Nordman <mik...@pp...>
> > Betreff: Re: [Flashforth-devel] flashforth arduino
> duemilanove
> > An: fla...@li...
> > Datum: Mittwoch, 12. Juni, 2013 16:23 Uhr
> > Hi Sven,
> > My guess is that you forgot to program the eeprom.
> > 
> > BR Mikael
> 
> 

Re: [Flashforth-devel] Elements of FlashForth tutorial

[Peter J. <p.j...@uq...>]

Thanks Pete.  The latest version (June-13) includes Mike's suggestions.  

Mike,
I've also tried the latex2html button in Kile and the resultant HTML files are in the directory eoff/  I don't much like the result but I guess it could be cleaned up.  For web-delivered documentation, I usually use Sphinx but it's very Python-oriented.  Anyway, these days, I like using the PDF viewer built into Firefox.

http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/

Cheers,
Peter J.

________________________________________
From: Pete Zawasky [pza...@pz...]
Sent: Thursday, June 13, 2013 4:02 AM
To: FF mailing list
Subject: Re: [Flashforth-devel] Elements of FlashForth tutorial

Peter,
I think you have put together an excellent tutorial for the students to
get started with FlashForth.
Mikael's comments are ,as usual, 'spot  on'.

Hopefully, with a set of well defined labs, they will be able to use the
tools of FlashForth and PICs to learn the basics of Mechatronics quickly
and clearly.

Please let me know if you get this as my SourceForce Mailing List is
still not updating properly.

Pete

On 6/12/2013 10:56 AM, Peter Jacobs wrote:
> Pete, Mike,
>     I've put up a (slightly) more polished version.  Fixed up some typographical errors and improved (hopefully) the discussion of defining words.  I'm happy with it at this point.
>
> http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/eoff-2013-jun-12.pdf
>
> Cheers,
> Peter J.
>
> _


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Flashforth-devel mailing list
Fla...@li...
https://lists.sourceforge.net/lists/listinfo/flashforth-devel

Re: [Flashforth-devel] Elements of FlashForth tutorial

[Pete Z. <pza...@pz...>]

Peter,
I think you have put together an excellent tutorial for the students to 
get started with FlashForth.
Mikael's comments are ,as usual, 'spot  on'.

Hopefully, with a set of well defined labs, they will be able to use the 
tools of FlashForth and PICs to learn the basics of Mechatronics quickly 
and clearly.

Please let me know if you get this as my SourceForce Mailing List is 
still not updating properly.

Pete

On 6/12/2013 10:56 AM, Peter Jacobs wrote:
> Pete, Mike,
>     I've put up a (slightly) more polished version.  Fixed up some typographical errors and improved (hopefully) the discussion of defining words.  I'm happy with it at this point.
>
> http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/eoff-2013-jun-12.pdf
>
> Cheers,
> Peter J.
>
> _

Re: [Flashforth-devel] Elements of FlashForth tutorial

[Mikael N. <mik...@pp...>]

Some minor comments.

Chapter 8
The word (  a left parenthesis followed by a space  says disregard all 
following text until
the next right parenthesis OR END OF LINE in the input stream"

Table2
leave sets the loop counter to zero, not r@

Chapter12
The compiler word create makes a new dictionary entry using the next 
name in the input
stream and compiles the pointer value of the first free data space 
location of the current data space context.
When executed, the new dictionary entry returns the pointer value.

Is that clear or can it be said simpler ? /Mike

Chapter 12.3
The word 'of' is missing.

Thanks Peter for a really good basic tutorial.

I wonder if it could be converted to html and make it readable directly 
on the web.

BR Mike

On 06/12/2013 05:56 PM, Peter Jacobs wrote:
> Pete, Mike,
>     I've put up a (slightly) more polished version.  Fixed up some typographical errors and improved (hopefully) the discussion of defining words.  I'm happy with it at this point.
>
> http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/eoff-2013-jun-12.pdf
>
> Cheers,
> Peter J.
>
> ________________________________________
> From: Peter Jacobs [p.j...@uq...]
> Sent: Tuesday, June 11, 2013 9:16 PM
> To: Pete Zawasky; FF mailing list
> Subject: Re: [Flashforth-devel] Elements of FlashForth tutorial
>
> A fresh version is up, using some of your suggestions.
>
> http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/eoff-2013-jun-11.pdf
>
> I have to admit to not getting around to fixing the typos, yet.
> PJ
>
> ________________________________________
> From: Pete Zawasky [pza...@pz...]
> Sent: Sunday, June 09, 2013 2:11 AM
> To: FF mailing list
> Subject: [Flashforth-devel] Elements of FlashForth tutorial
>
> Hi Peter,
>
> Not sure I am able to see your new version yet.
> Only found a few spelling typos in the original.
>
> Here are 2 words I find very helpful exploring the usefulness of
> FlashForth and PIC18 microcontrollers:
>
>    : .mem  ( -- )          \ print current memory locations
>       base @  hex
>       cr ." flash  "  flash  here #4 u.r
>       cr ." eeprom "  eeprom here #4 u.r
>       cr ." ram    "  ram    here #4 u.r
>       base !  ;
>
>    : c?%  ( addr -- )                 \ print byte contents at addr in binary
>       2 spaces base @ swap
>       c@ 8 bin u.r
>       base !  ;
>
> c?% is useful to look at SFRs.
>
> .mem is useful to examine further what Mikael was saying about FORGET vs
> EMPTY .
>
>            Side note:  I still prefer the original FORTH word COLD to
> Mikael's EMPTY.
>
> Don't leave out DUMP, especially when learning to create arrays and jump
> tables.
>
> Pete
>
> Pete Zawasky
> PZEF Co.
> 361 Mills RD
> Oriental, NC 28571
> www.pzef.net
> pza...@pz...
> 1-252-249-3393 (voice and fax)
> 1-252-670-6940 (cell)
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

Re: [Flashforth-devel] flashforth arduino duemilanove

[Mikael N. <mik...@pp...>]

I just remembered.
The easiest way to recover from faulty eeprom data
is to just give the command

empty

from the command line. It will reinitialize the eeprom to
default values.

BR Mike

On 06/12/2013 05:23 PM, Mikael Nordman wrote:
> Hi Sven,
> My guess is that you forgot to program the eeprom.
>
> BR Mikael
>
> On 06/12/2013 02:20 PM, Sven wrote:
>> Hi,
>> I've downloaded flashforth V3.8 for the Atmega and because I only have Linux on my PC, I assembeled it with AVR Studio V4.17.666 ( That's the only version I got to run with wine ). I got no errors and after checking and changing the fuses, like the recommendation, to: lfuse: 0xFF, hfuse:0xDA, efuse:0xFD
>> I downloaded the hex file via ISP to the arduino board. After I started minicom (38400 8N1, Software handshake) and pressing the reset button I got: FlashForth Atmega 18.11.2012
>> Then I typed in 1 [cr] 1 [cr] 1 [cr] .s [cr] and got: 0 0 0 0 0  ok
>> If I tried the same with "2", there is no input possible anymore after pressing CR. I could revive the flashforth with CTRL-o or by pressing the reset button.
>> If I type in "words" the only output I got is: ...............
>>    
>> I think there's something wrong with my flashforth system any idea what could be wrong ?
>> Is it perhaps the old AVR studio, which I used for assembling and is it possible to use another AVR assembler to build flashforth?
>>
>> Sven
>>
>>        
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Flashforth-devel mailing list
>> Fla...@li...
>> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

Re: [Flashforth-devel] Elements of FlashForth tutorial

[Peter J. <p.j...@uq...>]

Pete, Mike,
   I've put up a (slightly) more polished version.  Fixed up some typographical errors and improved (hopefully) the discussion of defining words.  I'm happy with it at this point.

http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/eoff-2013-jun-12.pdf

Cheers,
Peter J.

________________________________________
From: Peter Jacobs [p.j...@uq...]
Sent: Tuesday, June 11, 2013 9:16 PM
To: Pete Zawasky; FF mailing list
Subject: Re: [Flashforth-devel] Elements of FlashForth tutorial

A fresh version is up, using some of your suggestions.

http://dropbox.eait.uq.edu.au/e4pjacob/flash-forth/eoff-2013-jun-11.pdf

I have to admit to not getting around to fixing the typos, yet.
PJ

________________________________________
From: Pete Zawasky [pza...@pz...]
Sent: Sunday, June 09, 2013 2:11 AM
To: FF mailing list
Subject: [Flashforth-devel] Elements of FlashForth tutorial

Hi Peter,

Not sure I am able to see your new version yet.
Only found a few spelling typos in the original.

Here are 2 words I find very helpful exploring the usefulness of
FlashForth and PIC18 microcontrollers:

  : .mem  ( -- )          \ print current memory locations
     base @  hex
     cr ." flash  "  flash  here #4 u.r
     cr ." eeprom "  eeprom here #4 u.r
     cr ." ram    "  ram    here #4 u.r
     base !  ;

  : c?%  ( addr -- )                 \ print byte contents at addr in binary
     2 spaces base @ swap
     c@ 8 bin u.r
     base !  ;

c?% is useful to look at SFRs.

.mem is useful to examine further what Mikael was saying about FORGET vs
EMPTY .

          Side note:  I still prefer the original FORTH word COLD to
Mikael's EMPTY.

Don't leave out DUMP, especially when learning to create arrays and jump
tables.

Pete

Pete Zawasky
PZEF Co.
361 Mills RD
Oriental, NC 28571
www.pzef.net
pza...@pz...
1-252-249-3393 (voice and fax)
1-252-670-6940 (cell)

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Flashforth-devel mailing list
Fla...@li...
https://lists.sourceforge.net/lists/listinfo/flashforth-devel

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Flashforth-devel mailing list
Fla...@li...
https://lists.sourceforge.net/lists/listinfo/flashforth-devel

Re: [Flashforth-devel] flashforth arduino duemilanove

[Mikael N. <mik...@pp...>]

Hi Sven,
My guess is that you forgot to program the eeprom.

BR Mikael

On 06/12/2013 02:20 PM, Sven wrote:
> Hi,
> I've downloaded flashforth V3.8 for the Atmega and because I only have Linux on my PC, I assembeled it with AVR Studio V4.17.666 ( That's the only version I got to run with wine ). I got no errors and after checking and changing the fuses, like the recommendation, to: lfuse: 0xFF, hfuse:0xDA, efuse:0xFD
> I downloaded the hex file via ISP to the arduino board. After I started minicom (38400 8N1, Software handshake) and pressing the reset button I got: FlashForth Atmega 18.11.2012
> Then I typed in 1 [cr] 1 [cr] 1 [cr] .s [cr] and got: 0 0 0 0 0  ok
> If I tried the same with "2", there is no input possible anymore after pressing CR. I could revive the flashforth with CTRL-o or by pressing the reset button.
> If I type in "words" the only output I got is: ...............
>   
> I think there's something wrong with my flashforth system any idea what could be wrong ?
> Is it perhaps the old AVR studio, which I used for assembling and is it possible to use another AVR assembler to build flashforth?
>
> Sven
>
>       
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

[Flashforth-devel] flashforth arduino duemilanove

[Sven <sve...@ya...>]

Hi,
I've downloaded flashforth V3.8 for the Atmega and because I only have Linux on my PC, I assembeled it with AVR Studio V4.17.666 ( That's the only version I got to run with wine ). I got no errors and after checking and changing the fuses, like the recommendation, to: lfuse: 0xFF, hfuse:0xDA, efuse:0xFD
I downloaded the hex file via ISP to the arduino board. After I started minicom (38400 8N1, Software handshake) and pressing the reset button I got: FlashForth Atmega 18.11.2012
Then I typed in 1 [cr] 1 [cr] 1 [cr] .s [cr] and got: 0 0 0 0 0  ok
If I tried the same with "2", there is no input possible anymore after pressing CR. I could revive the flashforth with CTRL-o or by pressing the reset button.
If I type in "words" the only output I got is: ...............
 
I think there's something wrong with my flashforth system any idea what could be wrong ?
Is it perhaps the old AVR studio, which I used for assembling and is it possible to use another AVR assembler to build flashforth?

Sven