FlashForth 4.7 for 24,30 and 33 series

Brought to you by: oh2aun

FlashForth 4.7 for 24,30 and 33 series

Forum: Open Discussion

Creator: Mikael Nordman

Created: 2010-10-11

Updated: 2012-11-19

Mikael Nordman - 2010-10-11

I pushed an alpha release of FF4.7 to the git repository.
Please pull it and test it.
It supports now all 16-bit devices with enough memory.
I have run it in the simulator with some different PIC types.
There it starts and goes into ACCEPT.

On dsPIC30F it has been run on target on a 30F4012.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mikael Nordman - 2010-10-22

FF4.7 can now run on dsPIC33FJ128.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

zr123 - 2010-10-23

Can it run on F33 devices with 64K flash?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mikael Nordman - 2010-10-23

In practice FF 4.7 can run on 24 and 33 devices with at least 32 Kbytes of flash and 4 Kb of ram.
On the 30 series it can run with smaller devices with at least 16 Kb of flash and 1 Kb of memory

On the 33 and 24 series FF uses for the kernel 2 Kbytes of ram
and 12 Kb of Flash, In addition 6 Kb of flash is used for
eeprom emulation.
So any device with more memory than that,
can ran FlashForth.
The eeprom emulation falsh usage could be reduced to 1.5 Kbytes in the future.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pete Zawasky - 2010-10-24

Hi FF_4.7 users,

Here is the set up I am using to test and learn the FF_4.7 Preliminary release from Mikael…

FlashForth V4.7p from the SourceForge git repository
MPLAB IDE v8.56
PICkit 2 for programming
Microchip DM300027 16-Bit 28-Pin Starter Development Board
PIC30F4012 for the mcu on the DM300027
USB for communications and power to the DM300027
RealTerm for the terminal s/w on the WIN XP PC

Be sure to set the CHAR DLY and LINE DLY a bit longer than you would first expect in RealTerm in order to send files to the MCU. Otherwise, all is up and running as a development board.

Please share any testing results with Mikael and the rest of us here on this Forum.

Pete

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mikael Nordman - 2010-10-25

Pete,
Increasing the write delay could in the config file could
remove for need delays in realterm.

.equ write_delay, 20

Mikael

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pete Zawasky - 2010-10-25

Yes, that could help. But I think the real problem is RealTerm. It is OK but not a completely finished terminal program, especially when connected via USB. I am getting display problems sometimes on lines which are comments only and do not require flashing in the mcu. Life with FlashForth has always been better here with a pc with a true rs232 serial port……

Pete

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.