flashforth-devel — FlashForth users and developers

[Flashforth-devel] Flashforth compiling help

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

I am new to Forth and PIC's, but am very interested in getting
Flashforth working on a PIC18LF4553. My PIC experience thus far has been
with PICBASICPRO and the 16F876, with no experience at all with the
MPLAB IDE environment.

Are there step-by-step instructions for getting through the compile
process using MPLAB? Once I have a hex file, I can use my PicKit2
programmer to put it into the 4553.

Thank you!

Re: [Flashforth-devel] P18F Accessing FLASH above 0xebff

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

Thanks Mikael,

That is great information for me to start with.   The concepts in 
FLASH_TO_RAM and RAM_TO_FLASH would work just fine to use the  processor 
with more flash memory.

Pete

Re: [Flashforth-devel] P18F Accessing FLASH above 0xebff

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

On 28.10.2011 20:32, Mikael Nordman wrote:
> On 28.10.2011 19:03, Pete Zawasky wrote:
>> HI Mikael,
>>
>> As you know I currently use the PIC18F6527 quite often.  As for using
>> the PIC18F6722, any thoughts/recommendations for accessing the FLASH
>> memory above 0xebff?   Perhaps not so much for program space as the
>> storage of somewhat permanent data for LCD screens, etc.
>>
> It could work by setting TBLPTRU to 1 and then moving data with memory
> operators.
> The catch is, you cannot use the interpreter in between
> so you have to first compile a word that does the actual moving of data.
> For example like this:
>
> : flash_to_ram ( flashaddr ramaddr count 64Kbyte_flash_page --- )
>     iflush
>     tblptru c!
>     cmove
>     0 tblptru c!
> ;
>
> : ram_to flash ( ramaddr flashaddr count 64Kbyte_flash_page --- )
>     iflush
>     tblptru c!
>     cmove
>     0 tblptru c!
> ;
>
> To be able to set the tblptru interactively, then
> LIT: DOCREATE: DODOES: DOUSER:
> would need to push tblptru, clear tblptru, do their stuff and pop tblptru.
>
> If using forth interrupt words, then i] and [i needs to push and pop
> also tblptru.
>
> Heres your chance to hack FlashForth :-)
>
> Best Regards
> Mike

To access the flash between ec00 - ffff one would need to expose i@ ic@ 
i! ic! as words in the wordlist.

BR Mike

Re: [Flashforth-devel] P18F Accessing FLASH above 0xebff

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

On 28.10.2011 19:03, Pete Zawasky wrote:
> HI Mikael,
>
> As you know I currently use the PIC18F6527 quite often.  As for using
> the PIC18F6722, any thoughts/recommendations for accessing the FLASH
> memory above 0xebff?   Perhaps not so much for program space as the
> storage of somewhat permanent data for LCD screens, etc.
>
It could work by setting TBLPTRU to 1 and then moving data with memory 
operators.
The catch is, you cannot use the interpreter in between
so you have to first compile a word that does the actual moving of data.
For example like this:

: flash_to_ram ( flashaddr ramaddr count 64Kbyte_flash_page --- )
   iflush
   tblptru c!
   cmove
   0 tblptru c!
;

: ram_to flash ( ramaddr flashaddr count 64Kbyte_flash_page --- )
   iflush
   tblptru c!
   cmove
   0 tblptru c!
;

To be able to set the tblptru interactively, then
LIT: DOCREATE: DODOES: DOUSER:
would need to push tblptru, clear tblptru, do their stuff and pop tblptru.

If using forth interrupt words, then i] and [i needs to push and pop 
also tblptru.

Heres your chance to hack FlashForth :-)

Best Regards
Mike

[Flashforth-devel] P18F Accessing FLASH above 0xebff

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

HI Mikael,

As you know I currently use the PIC18F6527 quite often.  As for using 
the PIC18F6722, any thoughts/recommendations for accessing the FLASH 
memory above 0xebff?   Perhaps not so much for program space as the 
storage of somewhat permanent data for LCD screens, etc.

Pete

Re: [Flashforth-devel] FF 4.8 - backspace issue

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

Thats how it should work.
Characters are deleted from the Terminal Input Buffer, but not from the 
screen.
Simplest possible solution.

Mike

Re: [Flashforth-devel] FF 4.8 - backspace issue

[om1zz <om...@vo...>]

I've tackled that as well:
a) when BCKSP or DEL is selected (or both) it does not work,
b) when both deselected, then it moves the cursor back without
deleting the chars from the screen. Basically ok, but it did
actually remove the chars from buffer, so when you do following:
1234 1234 + .
with the backspace going back and retype to 8
1238 1234 + . 
and press enter without retyping " 1234 + ." then you get 1238 on
stack only (as it deleted the " 1234 + ." actualy, but not from the
screen)..
:) TT 4.69
i.

----- PŮVODNÍ ZPRÁVA -----
Od: "Mikael Nordman" <mik...@pp...>
Komu: fla...@li...
Předmět: Re: [Flashforth-devel] FF 4.8 - backspace issue
Datum: 26.10.2011 - 18:03:53

> It works.
> Check your teraterm settings.
> 
> Setup->keyboard->Transmit DEL by...
> 
> Mike
> 
> On 26.10.2011 12:36, om1zz wrote:
> > Hi, running FF 4.8 with Teraterm, it seems the
> > backspace does not
> > > work when editing the input line. I think it
> > worked in past.
> > > I.
> >
> >
> > ------------------------------------------------------------------------------
> > > > > The demand for IT networking professionals
> > continues to grow, and the
> > > demand for specialized networking skills is
> > growing even more rapidly.
> > > Take a complimentary Learning@Cisco
> > Self-Assessment and learn
> > > about Cisco certifications, training, and career
> > opportunities.
> > > http://p.sf.net/sfu/cisco-dev2dev
> > _______________________________________________
> > Flashforth-devel mailing list
> > Fla...@li...
> > https://lists.sourceforge.net/lists/listinfo/flashforth-devel
> > >
> 
> ------------------------------------------------------------------------------
> > The demand for IT networking professionals
> continues to grow, and the
> demand for specialized networking skills is
> growing even more rapidly.
> Take a complimentary Learning@Cisco
> Self-Assessment and learn 
> about Cisco certifications, training, and career
> opportunities. 
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
> 


-- 
Jak se vyhnout nachlazení a dalším zdravotním potížím v nepříjemném
podzimním období? Čtěte speciál Zdraví na podzim na
http://web.volny.cz/data/click.php?id=1290

Re: [Flashforth-devel] PIC32 in DIL28

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

I looked shortly at the MIPS CPU last year.
It seems to me that making a subroutine call and returning
is cumbersome in MIPS.
You had to write to a linkregister to be able to return from
a subroutine call. Also It was not clear to me if the
retrun stack is managed in HW.
Also you had to fill some delay slots with nops after the subroutine call.
MIPS is perhaps better suited for a threaded Forth instead.

Mike

On 24.10.2011 23:05, om1zz wrote:
> Hi Mike,
> there should be a new series PIC32MX1XX/2XX avialable (also in
> dip28) 32-bit Microcontrollers (up to 128 KB Flash and 32 KB SRAM)
> with Audio and Graphics Interfaces, USB, and Advanced Analog..
> Maybe a new talented chip for FF :)
> Igor
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

Re: [Flashforth-devel] FF 4.8 - backspace issue

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

It works.
Check your teraterm settings.

Setup->keyboard->Transmit DEL by...

Mike

On 26.10.2011 12:36, om1zz wrote:
> Hi, running FF 4.8 with Teraterm, it seems the backspace does not
> work when editing the input line. I think it worked in past.
> I.
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

[Flashforth-devel] FF 4.8 - backspace issue

[om1zz <om...@vo...>]

Hi, running FF 4.8 with Teraterm, it seems the backspace does not
work when editing the input line. I think it worked in past.
I.

[Flashforth-devel] Do-loop

[om1zz <om...@vo...>]

Hi Mike,
even you have indicated the do-loop (and its friends) are not a
priority for FF, let me suggest to consider it at least as an
option, when the "do-loop" performance is not critical.. It will
help us to run existing words..
I.

[Flashforth-devel] PIC32 in DIL28

[om1zz <om...@vo...>]

Hi Mike,
there should be a new series PIC32MX1XX/2XX avialable (also in
dip28) 32-bit Microcontrollers (up to 128 KB Flash and 32 KB SRAM)
with Audio and Graphics Interfaces, USB, and Advanced Analog..
Maybe a new talented chip for FF :)
Igor

[Flashforth-devel] Microchip and FlashForth

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

I just got a survey to answer from Microchip.   They asked what 
Microchip could do to help me on projects.
Obviously I answered that they should actively support FlashForth.

I hope others can answer the same.

Pete

Re: [Flashforth-devel] flashforth on p18f4550 - No usb?

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

Hi Scott.
Great that it works !

So if you want you can make the CPU run slower with the CPUDIV.
PLLDIV must be set according to what kind of XTAL you have.
USBDIV should always be 2
The clock constant tells how fast the CPU is running.
It is needed for setting up the 1 ms timer and for configuring
the UART baud rate.

Did you have any special project in mid for FlashForth.

For the 4550 and cousins, here are a few examples
for full speed USB.

config PLLDIV = 1           ; 4 MHz XT xtal
config PLLDIV = 2           ; 8 MHz XT xtal
config PLLDIV = 3           ; 12 MHz XT xtal
config PLLDIV = 4           ; 16 MHz XT xtal
config PLLDIV = 5           ; 20 MHz XT xtal

config CPUDIV = OSC1_PLL2   ; 48 MHz cpu clock
constant clock=d'48000000'

config CPUDIV = OSC2_PLL3   ; 24 MHz cpu clock
constant clock=d'24000000'

config CPUDIV = OSC3_PLL4   ; 16 MHz cpu clock
constant clock=d'16000000'

config CPUDIV = OSC4_PLL6   ; 8 MHz cpu clock
constant clock=d'8000000'

config USBDIV = 2           ; USB clock from 96 MHZ PLL divided by 2


Cheers
Mike

Re: [Flashforth-devel] flashforth on p18f4550 - No usb?

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

Hi Scott,

That is great news...Good luck with FF on the 4550.  I use the PICDEM 
FSUSB Demo board here for the USB testing.

I generally go to the PIC Data Sheet  for the particular processor and 
study the Oscillator Configuration section carefully.
One way or another, you will need  20MHz  for the USB.   Other internal 
frequencies will be your decision.

As another example, for the 18F6527 FF3.8 with UART at 38.4K baud, I 
change the following:

ff18_usb.asm

FROM:
#ifdef OSCCON
         movlw   0x70            ; Use full internal OSC frequency
         movwf   OSCCON, A
#endif

TO:
; ppz osc
; ------------------------------------------------------------
#ifdef __18F6527
; Internal Oscillator
         movf    OSCCON, W, A
         iorlw   b'01110000'            ; 8MHz
         movwf   OSCCON, A
         nop
; Enable Oscillator PLL
         movf    OSCTUNE, W, A
         iorlw   b'01000000'            ; Enable PLL for 4x8MHz
         movwf   OSCTUNE, A
         nop
         nop
#else
#ifdef OSCCON
         movlw   0x70            ; Use full internal OSC frequency
         movwf   OSCCON, A
#endif

#endif
; ------------------------------------------------------------

p18f-main.cfg

;;;;  PIC18F6527 Internal Oscillator with PLL
         constant clock = d'32000000'

p18fxxxx.cfg

         ifdef __18F6527
             #include p18f6527.inc
;;;            #include p18f6722-family.cfg
             #include p18f6527.cfg
             #define  PICTYPE "PIC18F6527 "
             #define FLASH_HI  0xbfff
             #define EEPROM_HI 0xefff
             #define RAM_HI    0xff60
         endif

And add the following file:

;**********************************************************************
;                                                                     *
;    Filename:      p18f6527.cfg                                      *
;    Date:          4:23 PM 10/4/2011                                 *
;    FF Version:    3.8                                               *
;    Copyright:     Pete Zawasky                                      *
;    Author:        Pete Zawasky                                      *
;                                                                     *
;**********************************************************************
;    Based on p18f6722-family.cfg by Mikael Nordman                   *
;**********************************************************************
;    FlashForth is licensed acording to the GNU General Public License*
;**********************************************************************
;;; FlashForth processor specific configuration

; The config directive is used control the processor configuration bits
; See processor specific include file for details.


#if CONFIG_RESET == 0x0000
         config OSC = INTIO67
         config FCMEN = OFF
         config IESO = OFF
         config PWRT = OFF
         config BOREN = SBORDIS
         config BORV = 3
         config WDT = OFF
         config WDTPS = 32768
         config MCLRE = ON
         config LPT1OSC = ON
         config CCP2MX = PORTC
         config STVREN = ON
         config LVP = OFF
         config BBSIZ = BB8K
         config XINST = OFF
         config DEBUG = OFF
         config CP0 = OFF
         config CP1 = OFF
         config CP2 = OFF
         config CPB = OFF
         config CPD = OFF
         config WRT0 = OFF
         config WRT1 = OFF
         config WRT2 = OFF
         config WRTB = ON
         config WRTC = ON
         config WRTD = OFF
         config EBTR0 = OFF
         config EBTR1 = OFF
         config EBTR2 = OFF
         config EBTRB = OFF

#endif

;;; Some constants controlling how writes to program flash is made.
         constant flash_write_outer_loop = d'1'
         constant flash_write_inner_loop = d'64'
;**********************************************************************

As you can see, one has to really focus on the particular processor for 
the OSC, PLL, and CONFIGURATION bits.
Then I really pound away on Mikael's FF code to see if it really works 
like he says it should....

A software test suite (validation suite) for FF like we had in eFORTH 
would really be great.
In the mean time,  try all the different applications you can with lots 
of different words and learn FF.

Pete

Re: [Flashforth-devel] flashforth on p18f4550 - No usb?

[Scott B. <sba...@al...>]

On 11-10-13 08:24 PM, Pete Zawasky wrote:
> Scott,
>
> Here are some changes I have made for a    4550 USB  board that has a 20
> MHz XTAL.
>    p18f-main.cfg
>       disable IDLE_MODE and CPU_LOAD
>       ;;;;  PIC18F4550
>           constant clock = d'48000000'  ; Hz
>
>
> p18f2455-2550-4455-4550.cfg
>       config PLLDIV = 5           ; 20 MHz XT xtal
>
>
> Pete

OK, let's try!

<recompile, reprogram, plug in>

Oooo!  Looks good!

Output from dmesg:

[  165.030295] usb 5-1: new full speed USB device using ohci_hcd and 
address 5
[  165.249659] cdc_acm 5-1:1.0: This device cannot do calls on its own. 
It is not a modem.
[  165.249703] cdc_acm 5-1:1.0: ttyACM0: USB ACM device
[  165.253145] usbcore: registered new interface driver cdc_acm
[  165.253152] cdc_acm: v0.26:USB Abstract Control Model driver for USB 
modems and ISDN adapters

lsusb:

Bus 005 Device 005: ID faf0:faf0

That's what we're looking for.

ls -la /dev/ttyACM0

crw-rw---- 1 root dialout 166, 0 2011-10-13 21:18 /dev/ttyACM0

OK, proof's in the pudding:

Welcome to minicom 2.5

OPTIONS: I18n
Compiled on Feb  5 2011, 06:31:42.
Port /dev/ttyACM0

Press CTRL-A Z for help on special keys

   ok<$,ram>
1 2 + . 3  ok<$,ram>


WOW!  $5 chip running a high level language.  Now THIS is cool!

Thanks to Mikael for FF, and to you, Pete, for the magic!

I'm new to the PIC world, so how does one calculate the PLL, etc, values?

Cheers,
Scott

>
>
>
>
> On 10/13/2011 8:09 PM, Scott Balneaves wrote:
>> On 11-10-12 02:38 PM, Mikael Nordman wrote:
>>> The first thing to try is to skip the IDLE_MODE in the config file.
>>> The IDLE_MODE causes the PIC to poll the USB tranceiver
>>> too seldom.
>> Gak!  I realized now that my first response was to Mikael, and not to the
>> list.  My apologies.
>>
>> I've disabled IDLE_MODE in p18f-main.cfg.
>>
>>> Newer and faster PCs seems to have a problem with that !
>>>
>>> Are xtal and pll setting correct ?
>> I've set:
>>
>> constant clock=d'20000000'
>>
>> in p18f-main.cfg, recompiled, and re-flashed.  Same thing's happening on the
>> USB bus.
>>
>> Looking in p18f2455-2550-4455-4550.cfg, I'm seeing:
>>
>>            config PLLDIV = 3           ; 12 MHz XT xtal
>>            config CPUDIV = OSC1_PLL2   ; 48 MHz cpu clock
>>            config USBDIV = 2           ; USB clock from 96 MHZ PLL divided by 2
>>
>> I'd imagine these aren't correct, but I've no clue how they should be set.
>>
>> Mike, thanks for the help so far.  This looks SO cool if I can get it running!
>>
>> Cheers,
>> Scott
>>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel

Re: [Flashforth-devel] flashforth on p18f4550 - No usb?

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

Scott,

Here are some changes I have made for a    4550 USB  board that has a 20 
MHz XTAL.
  p18f-main.cfg
     disable IDLE_MODE and CPU_LOAD
     ;;;;  PIC18F4550
         constant clock = d'48000000'  ; Hz


p18f2455-2550-4455-4550.cfg
     config PLLDIV = 5           ; 20 MHz XT xtal


Pete




On 10/13/2011 8:09 PM, Scott Balneaves wrote:
> On 11-10-12 02:38 PM, Mikael Nordman wrote:
>> The first thing to try is to skip the IDLE_MODE in the config file.
>> The IDLE_MODE causes the PIC to poll the USB tranceiver
>> too seldom.
> Gak!  I realized now that my first response was to Mikael, and not to the
> list.  My apologies.
>
> I've disabled IDLE_MODE in p18f-main.cfg.
>
>> Newer and faster PCs seems to have a problem with that !
>>
>> Are xtal and pll setting correct ?
> I've set:
>
> constant clock=d'20000000'
>
> in p18f-main.cfg, recompiled, and re-flashed.  Same thing's happening on the
> USB bus.
>
> Looking in p18f2455-2550-4455-4550.cfg, I'm seeing:
>
>           config PLLDIV = 3           ; 12 MHz XT xtal
>           config CPUDIV = OSC1_PLL2   ; 48 MHz cpu clock
>           config USBDIV = 2           ; USB clock from 96 MHZ PLL divided by 2
>
> I'd imagine these aren't correct, but I've no clue how they should be set.
>
> Mike, thanks for the help so far.  This looks SO cool if I can get it running!
>
> Cheers,
> Scott
>

Re: [Flashforth-devel] flashforth on p18f4550 - No usb?

[Scott B. <sba...@al...>]

On 11-10-12 02:38 PM, Mikael Nordman wrote:
> The first thing to try is to skip the IDLE_MODE in the config file.
> The IDLE_MODE causes the PIC to poll the USB tranceiver
> too seldom.

Gak!  I realized now that my first response was to Mikael, and not to the
list.  My apologies.

I've disabled IDLE_MODE in p18f-main.cfg.

> Newer and faster PCs seems to have a problem with that !
>
> Are xtal and pll setting correct ?

I've set:

constant clock=d'20000000'

in p18f-main.cfg, recompiled, and re-flashed.  Same thing's happening on the
USB bus.

Looking in p18f2455-2550-4455-4550.cfg, I'm seeing:

         config PLLDIV = 3           ; 12 MHz XT xtal
         config CPUDIV = OSC1_PLL2   ; 48 MHz cpu clock
         config USBDIV = 2           ; USB clock from 96 MHZ PLL divided by 2

I'd imagine these aren't correct, but I've no clue how they should be set.

Mike, thanks for the help so far.  This looks SO cool if I can get it running!

Cheers,
Scott

>
> Mike
>
> On 13.10.2011 20:46, Scott Balneaves wrote:
>> Hello!
>>
>> I'm trying to get flashforth going on a p18f4550.  I've bought an experimenter
>> board from Olimex:
>>
>> http://www.olimex.com/dev/pic-usb-4550.html
>>
>> I've git-cloned the latest flashforth, and installed the MPLAB tools
>> that came with my PICKIT2 burner.
>>
>> I create a new project, add ff18_usb.asm, PF18_USB_REG.asm, and add the
>> FF_USB_18F4550.lib file.  Build appears to be successful: ends with build
>> succeeded.  I program the device and verify it, and it tells me the device
>> is programmed successfully and verifies successfully.
>>
>> I plug the board into my Linux box (64 bit Ubuntu 11.04), and here's what
>> I'm seeing in dmesg:
>>
>> [13843.230116] usb 6-3: new full speed USB device using ohci_hcd and address 17
>> [13843.370133] usb 6-3: device descriptor read/64, error -62
>> [13843.630123] usb 6-3: device descriptor read/64, error -62
>> [13843.890117] usb 6-3: new full speed USB device using ohci_hcd and address 18
>> [13844.040144] usb 6-3: device descriptor read/64, error -62
>> [13844.300133] usb 6-3: device descriptor read/64, error -62
>> [13844.560128] usb 6-3: new full speed USB device using ohci_hcd and address 19
>> [13844.980126] usb 6-3: device not accepting address 19, error -62
>> [13845.130133] usb 6-3: new full speed USB device using ohci_hcd and address 20
>> [13845.550143] usb 6-3: device not accepting address 20, error -62
>> [13845.550197] hub 6-0:1.0: unable to enumerate USB device on port 3
>>
>> I'm assuming it's supposed to look like a USB serial device that I can
>> connect minicom to port /dev/ttyUSB0 or the like.
>>
>> Any ideas on what I'm doing wrong?
>>
>> Cheers,
>> Scott
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2d-oct
>> _______________________________________________
>> Flashforth-devel mailing list
>> Fla...@li...
>> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel


-- 
Scott L. Balneaves | Eating words has never given me indigestion.
Systems Department |   -- Winston Churchill
Legal Aid Manitoba |

Re: [Flashforth-devel] flashforth on p18f4550 - No usb?

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

The first thing to try is to skip the IDLE_MODE in the config file.
The IDLE_MODE causes the PIC to poll the USB tranceiver
too seldom.
Newer and faster PCs seems to have a problem with that !

Are xtal and pll setting correct ?

Mike

On 13.10.2011 20:46, Scott Balneaves wrote:
> Hello!
>
> I'm trying to get flashforth going on a p18f4550.  I've bought an experimenter
> board from Olimex:
>
> http://www.olimex.com/dev/pic-usb-4550.html
>
> I've git-cloned the latest flashforth, and installed the MPLAB tools
> that came with my PICKIT2 burner.
>
> I create a new project, add ff18_usb.asm, PF18_USB_REG.asm, and add the
> FF_USB_18F4550.lib file.  Build appears to be successful: ends with build
> succeeded.  I program the device and verify it, and it tells me the device
> is programmed successfully and verifies successfully.
>
> I plug the board into my Linux box (64 bit Ubuntu 11.04), and here's what
> I'm seeing in dmesg:
>
> [13843.230116] usb 6-3: new full speed USB device using ohci_hcd and address 17
> [13843.370133] usb 6-3: device descriptor read/64, error -62
> [13843.630123] usb 6-3: device descriptor read/64, error -62
> [13843.890117] usb 6-3: new full speed USB device using ohci_hcd and address 18
> [13844.040144] usb 6-3: device descriptor read/64, error -62
> [13844.300133] usb 6-3: device descriptor read/64, error -62
> [13844.560128] usb 6-3: new full speed USB device using ohci_hcd and address 19
> [13844.980126] usb 6-3: device not accepting address 19, error -62
> [13845.130133] usb 6-3: new full speed USB device using ohci_hcd and address 20
> [13845.550143] usb 6-3: device not accepting address 20, error -62
> [13845.550197] hub 6-0:1.0: unable to enumerate USB device on port 3
>
> I'm assuming it's supposed to look like a USB serial device that I can
> connect minicom to port /dev/ttyUSB0 or the like.
>
> Any ideas on what I'm doing wrong?
>
> Cheers,
> Scott
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

[Flashforth-devel] flashforth on p18f4550 - No usb?

[Scott B. <sba...@al...>]

Hello!

I'm trying to get flashforth going on a p18f4550.  I've bought an experimenter
board from Olimex:

http://www.olimex.com/dev/pic-usb-4550.html

I've git-cloned the latest flashforth, and installed the MPLAB tools
that came with my PICKIT2 burner.

I create a new project, add ff18_usb.asm, PF18_USB_REG.asm, and add the
FF_USB_18F4550.lib file.  Build appears to be successful: ends with build
succeeded.  I program the device and verify it, and it tells me the device
is programmed successfully and verifies successfully.

I plug the board into my Linux box (64 bit Ubuntu 11.04), and here's what
I'm seeing in dmesg:

[13843.230116] usb 6-3: new full speed USB device using ohci_hcd and address 17
[13843.370133] usb 6-3: device descriptor read/64, error -62
[13843.630123] usb 6-3: device descriptor read/64, error -62
[13843.890117] usb 6-3: new full speed USB device using ohci_hcd and address 18
[13844.040144] usb 6-3: device descriptor read/64, error -62
[13844.300133] usb 6-3: device descriptor read/64, error -62
[13844.560128] usb 6-3: new full speed USB device using ohci_hcd and address 19
[13844.980126] usb 6-3: device not accepting address 19, error -62
[13845.130133] usb 6-3: new full speed USB device using ohci_hcd and address 20
[13845.550143] usb 6-3: device not accepting address 20, error -62
[13845.550197] hub 6-0:1.0: unable to enumerate USB device on port 3

I'm assuming it's supposed to look like a USB serial device that I can
connect minicom to port /dev/ttyUSB0 or the like.

Any ideas on what I'm doing wrong?

Cheers,
Scott

[Flashforth-devel] FF3.8 USB mode with USB disconnected

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

Attila Herman asked for it and now
the FF 3.8 in USB mode now also works with 
the USB cord disconnected.

It should make it more useful for self-powered 
gadgets.

F3.8 is sofar only available in the git repository.

Mike

Re: [Flashforth-devel] Thanks, and a question

[Mikael N. <oh...@gm...>]

> It was a bug in FF. Introduced together with the double number parsing.
> I have pushed a solution to git.
Thanks. I downloaded, compiled, and installed last night and it works fine.

>How are you reading the keypad ?
>Scanning in a BG task ?

I have just started the keypad work. It is going to be part of the LCD
task since it is sharing 4 port lines with the LCD module. I have not
quite decided yet how the interface to the other tasks will work but I
think like key? and key so 'key and 'key? can be vectored to the keypad.

One of my projects is to replace the pic in the Fox Delta PM3a power meter
( http://www.foxdelta.com/products/pm3.htm ) with a processor running FF
so I can control the averaging. The source code for the firmware in the
kit is not available and the least significant digit on the display is
changing so rapidly that it is unuseable. It needs more averaging for me.
So, the power meter is really just a sub part of the antenna tuner
projects.

73
Lowell

Re: [Flashforth-devel] FF4.7

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

Actually there is a small assembler in FF4.7.
Making a complete assembler would require some effort.
I also think it would be quite large, using quite much program memory.
/Mike

ASSEMBLER words
---------------

The following definitions are in the core dictionary.

as,        ( lower upper -- )
            Append a 24-bit code

as0        ( bit ram-addr -- u )
            Help word for bit manipulation opcodes

rcall,     ( rel-addr -- )
bra,       ( cc rel-addr -- )
return,    ( -- )
retfie,    ( -- )
bclr,      ( bit ram-addr -- )
bset,      ( bit ram-addr -- )
btst,      ( bit ram-addr -- )
btsc,      ( bit ram-addr -- )
btss,      ( bit ram-addr -- )
z,         ( -- cc )
nz,        ( -- cc )
not,       ( cc -- not-cc )
if,        ( cc -- here )
else,      ( back-addr -- here )
then,      ( back-addr -- )
begin,     ( -- here )
again,     ( back-addr -- )
until,     ( back-addr cc -- )



On 20.8.2011 17:59, mik...@pp... wrote:
> I did no make any assembler for the dsPIC.
> You can write the assembly coded words into the FF source code in MPLAB.
> Or you can use AS, to store assembly hex codes into program memory.
>
> Cheers Mikael
>
>> ----Alkuperäinen viesti----
>> Lähettäjä: nic...@ve...
>> Päivämäärä: 19.8.2011 21:58
>> Vastaanottaja:<fla...@li...>
>> Aihe: [Flashforth-devel] FF4.7
>>
>> Hi
>>
>> I have Flash Forth 4.7 running on a dsPIC33FJ128GP802 board.  I would like
> to make use of the assembler words.
>
>> I note there is no asm package available as there is in FF3.7.  What is the
> status of the assembler addition to FF4.7?
>
>>
>
>> Nick
> Lordi------------------------------------------------------------------------------
>
>> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
>
>> user administration capabilities and model configuration. Take
>
>> the hassle out of deploying and managing Subversion and the
>
>> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2_______________________________________________
>
>
>> Flashforth-devel mailing list
>> Fla...@li...
>> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>
>>
>
>
>
> ------------------------------------------------------------------------------
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
> user administration capabilities and model configuration. Take
> the hassle out of deploying and managing Subversion and the
> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
>

Re: [Flashforth-devel] FF4.7

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

I did no make any assembler for the dsPIC.
You can write the assembly coded words into the FF source code in MPLAB.
Or you can use AS, to store assembly hex codes into program memory.

Cheers Mikael

>----Alkuperäinen viesti----
>Lähettäjä: nic...@ve...
>Päivämäärä: 19.8.2011 21:58
>Vastaanottaja: <fla...@li...>
>Aihe: [Flashforth-devel] FF4.7
>
>Hi
>
>I have Flash Forth 4.7 running on a dsPIC33FJ128GP802 board.  I would like 
to make use of the assembler words. 

>I note there is no asm package available as there is in FF3.7.  What is the 
status of the assembler addition to FF4.7?

>

>Nick 
Lordi------------------------------------------------------------------------------

>Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 

>user administration capabilities and model configuration. Take 

>the hassle out of deploying and managing Subversion and the 

>tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2_______________________________________________


>Flashforth-devel mailing list
>Fla...@li...
>https://lists.sourceforge.net/lists/listinfo/flashforth-devel

>

[Flashforth-devel] FF4.7

[Nicholas L. <nic...@ve...>]

Hi

I have Flash Forth 4.7 running on a dsPIC33FJ128GP802 board.  I would like to make use of the assembler words. 
I note there is no asm package available as there is in FF3.7.  What is the status of the assembler addition to FF4.7?

Nick Lordi