Activity for FlashForth: for PIC and Atmega

Mikael Ulfenborg posted a comment on discussion Open Discussion

Mikael Ulfenborg — Sun, 08 Mar 2026 19:29:58 -0000

If anyone is interested: I've tested all digital input/output and the ADC and everything works. The only glitch was that the pins for UART1 were configured for serial communication. Next step was to test TWI/I2C and this does not work. I've compared the 328p and the 1248p and they are the same. Even different AI-chats (they sometimes have a hard time with Forth, but thats ok with me :) ) agree with me, it should work. When I inspect a simple i2c.ping with a logic analyzer the CLK-signal generates...

Mikael Nordman modified a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 17:13:53 -0000

Well, I did just want to run the comparable benchmark. I mean to compare with the original benchmark code. The STM8 benchmark code, seems to be comparable to the first FF code.

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 17:08:49 -0000

Well, I did just want to run the comparable benchmark,

Erol Iscioglu modified a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 16:32:58 -0000

With for..next and u/mod the test runs in 1.7 seconds. Yes the same code above. And with 16 Mhz. There is no mod word in dictionary in FF5. correction : it is not same code. 1.7 secs for the code in that article with u/mod drop.

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 16:27:21 -0000

I see now. But why you try to show FF slower by changing the bench code. If you look to comments in that article, the guy (who promotes his STM8EF or stm8 eforth) says that his eforth for stm8 is faster than FF but not in reality.

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 16:04:04 -0000

: bench ( n -- ) dup for r@ dup for dup r@ gcd drop next drop next drop ; ok this is 1.7 secs the original test in that article

Mikael Nordman modified a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 16:00:28 -0000

I am using a 16 Mhz Arduino Uno. Note that the bench word has been modified to run gcd 40000 times during the test.

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 15:57:22 -0000

Here, you wrote 1.7 secs. which is correct if I remember correctly :)

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 15:49:09 -0000

I am using a 16 Mhz Arduino Uno. Note that the bench word has been modified to run 40000 times during the test.

Mikael Ulfenborg posted a comment on discussion Open Discussion

Mikael Ulfenborg — Sat, 07 Mar 2026 14:16:48 -0000

It looks like the full swing oscillator did the trick. I thought i had tried that but obviously not... Big thanks for the time you've invested in this!

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 13:37:45 -0000

I think here, you used 8 Mhz. Because I see 1.7 secs with 16 Mhz with this code.And mod word is not in dictionary of FF5, there is u/mod. Regards, my blog : erolcum.blogspot.com

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 13:02:07 -0000

With for..next and u/mod the test runs in 1.7 seconds. Yes the same code above. And with 16 Mhz

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 10:36:47 -0000

This code runs in 3898 milliseconds. Replacing u/mod drop with mod runs in 8440 milliseconds. : gcd ( a b -- gcd ) begin dup while swap over u/mod drop repeat drop ; : bench ( n -- ) ticks swap dup for r@ over for dup r@ gcd drop next drop next drop ticks swap - cr . ; 200 bench 3898 ok<#,ram>

Mikael Nordman modified a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 10:27:17 -0000

Sorry for the late answer. I did not notice your message in the moderation queue until now. What code did you run ? With for..next and u/mod the test runs in 1.7 seconds. With for..next and mod the test runs in 3.8 seconds With do..loop and mod the test runs in 8 seconds. Same as Amforth. The word MOD is slow. It is defined using /MOD and SM/REM that then uses UM/MOD that is the basic division routine. In addition the original for..next code on that website only runs half as many iterations as the...

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Sat, 07 Mar 2026 10:09:36 -0000

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Sat, 07 Mar 2026 09:44:16 -0000

Hello Mikael, You make a great job, firstly. You may know the answer possibly for my following question. There is a blog page written 10 years ago, and author says he measured 4 seconds for "200 bench" test (atmega328). But I measured 1.7 seconds with FF5.0. What may be the reason ? It's speed increased twice in 10 years ? https://weblambdazero.blogspot.com/2016/10/go-forth-with-arduino.html Regards, Erol

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Fri, 06 Mar 2026 19:15:02 -0000

You could try with LOW:0xf7 to use the full swing oscillator that has more gain. This could be a solution if the crystal is just marginally working in the low power mode(LOW:0xff).

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Fri, 06 Mar 2026 18:54:31 -0000

You could try with EXT:0x04. That activates the brown-out reset at 4.3 volts. It prevents the chip to run at too low voltages.

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Fri, 06 Mar 2026 18:49:11 -0000

If it sometimes works, I would say you have a hardware problem. Maybe some intermittent connections on the breadboard. Poor decoupling etc, Is the clock reliable ? 16MHz? Check the clock with an oscilloscope. Does the FTDI supply enough current ? Are there voltage dips on the 5 volt. Does USB supply enough current? Are there other devices on the same USB bus? Front side USB connectors can be current limited by the computer internal wiring. I had that problem one time. The USB connectors or the cable...

Mikael Ulfenborg posted a comment on discussion Open Discussion

Mikael Ulfenborg — Fri, 06 Mar 2026 17:54:23 -0000

I've done some more testing and have "reliable" boot after reset with "E FlashForth 5 ATmega1284 05.03.2026" displaying each time. Here's an example of output with a few key press from me: FlashForth 5 ATmega1284p 05.03.2026 � ? ok<#,ram> after that it is non responsive I got it to work TWO TIMES and tried "words" and a few calculations, all working perfectly. Electrically the chip sits on a breadboard with decoupled +5V from the FTDI. As I said before the setup works with a 328p. Fuses are: LOW:...

Mikael Ulfenborg posted a comment on discussion Open Discussion

Mikael Ulfenborg — Fri, 06 Mar 2026 12:51:36 -0000

I use UART0 (pins 14=RXD0, 15=TXD0). I also use the "same" breadboard setup (obviously with shifted pins) for an 328p and it works. I will check all connections (for the umpht time) later today.

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Fri, 06 Mar 2026 12:41:03 -0000

Could it be something simple like the UART line not being connected? In the simulator the UART RX configs and interrupt vectors look right. Are you using UART0 ? I also think the same fuses as the 328P should work.

Mikael Ulfenborg posted a comment on discussion Open Discussion

Mikael Ulfenborg — Thu, 05 Mar 2026 20:41:27 -0000

Hello and thank you for your time! It sort of works, it boots with the message: E FlashForth 5 ATmega1284p 05.03.2026 But then it stops. I've tried several methods of programming the chip (TL866II+ ZIF and ICSP) and avrdude through an usbasp. The latter feels more robust. I've also tried to power it with both external 5V and with the FTDI adapter. The only thing I can think of is the fuses. I've (sort of) read the documentation and concluded it should be the same as the 328p. As this is only an hobby...

Mikael Nordman modified a comment on discussion Open Discussion

Mikael Nordman — Thu, 05 Mar 2026 14:40:45 -0000

Hi, You need to install MPLABX V6.20 and XC8 V3.10. These are the versions I am using. Then create a project with ff-xc8.asm as source file. I will update the code to compile with the Atmega1284 and related CPUs. Obviously I cannot test since I do not have the hardware.

Mikael Nordman modified a comment on discussion Open Discussion

Mikael Nordman — Thu, 05 Mar 2026 14:40:18 -0000

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Thu, 05 Mar 2026 14:28:42 -0000

Wow, you're really fast!

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Thu, 05 Mar 2026 13:30:57 -0000

So now there is support for 1284 and 1284P. Also many others seem to compile and run in the MPLABX símulator. There are also ready made HEX files for 1284 and 1284P. These are not tested on real hardware. Don't hesitate to ask in case of problems.

FlashForth: for PIC and Atmega updated /ff5.0.zip

FlashForth: for PIC and Atmega — Thu, 05 Mar 2026 13:29:03 -0000

Mikael Nordman committed [6f2fd2] on Code

Mikael Nordman — Thu, 05 Mar 2026 13:27:12 -0000

ATMEGA: ATmega 1284P, better support for more processors

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Thu, 05 Mar 2026 12:30:05 -0000

Hi, You need to install MPLABX V6.20 and XC8 V3.10. These are the versions I am using. Then create a project ff-xc8.asm as source file. I will update the code to compile with the Atmega1284 and related CPUs. Obviously I cannot test since I do not have the hardware. Probably it could work since the related Atmega644 is already included.

Erol Iscioglu posted a comment on discussion Open Discussion

Erol Iscioglu — Thu, 05 Mar 2026 11:25:01 -0000

I think you mention about Mikael's github : https://github.com/oh2aun/flashforth/tree/master/avr/FF-ATMEGA.X But every chip has different specs or peripherals, I think it is not an easy step as you think. He can answer your question if he wants

Mikael Ulfenborg posted a comment on discussion Open Discussion

Mikael Ulfenborg — Tue, 03 Mar 2026 19:08:42 -0000

Hello! Is there any documentation for how to compile for the Atmega 1284p? I've found one in my component storage and it would be nice to test this chip. I'm used to electronics and programming but I have no experience with compiling for Atmega processors (and quite rusty when it comes to assembler)

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Tue, 20 Jan 2026 21:28:40 -0000

Added back the stack underflow detection. It got lost when I updated the code from AVRASM2 to XC8 compiler.

FlashForth: for PIC and Atmega updated /ff5.0.zip

FlashForth: for PIC and Atmega — Tue, 20 Jan 2026 21:27:02 -0000

Mikael Nordman committed [db05e0] on Code

Mikael Nordman — Tue, 20 Jan 2026 21:24:41 -0000

ATMEGA: Add stack underflow check

FlashForth: for PIC and Atmega updated /ff5.0.zip

FlashForth: for PIC and Atmega — Mon, 19 Jan 2026 20:53:02 -0000

Mikael Nordman committed [b0f51e] on Code

Mikael Nordman — Mon, 19 Jan 2026 20:50:35 -0000

PIC18: BLOCK EDIT CORE

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Mon, 19 Jan 2026 12:08:29 -0000

Had to revert INTERPRET and re-introduce ABORT for unknown words. It did not work like I was thinking with blocks. Also blocks24.fs was updated to work. There is a new word EXECUTE? to prevent potentially unknown words from aborting the evaluation of a block. execute? -mark marker -mark

FlashForth: for PIC and Atmega updated /ff5.0.zip

FlashForth: for PIC and Atmega — Mon, 19 Jan 2026 12:02:06 -0000

Mikael Nordman committed [4b0cea] on Code

Mikael Nordman — Mon, 19 Jan 2026 11:58:48 -0000

PIC24: Revert to use ABORT in INTERPRET. Fixed BLOCK words

Mikael Nordman committed [98417c] on FlashForth 6

Mikael Nordman — Mon, 19 Jan 2026 10:33:00 -0000

PIC18: put back ABORT for unkown words

Mikael Nordman committed [a637bc] on FlashForth 6

Mikael Nordman — Sun, 18 Jan 2026 21:20:53 -0000

PIC18: BLOCK EDIT

Mikael Nordman committed [13bd03] on FlashForth 6

Mikael Nordman — Sat, 17 Jan 2026 16:06:19 -0000

PIC18: Remove DO LOOP

Mikael Nordman committed [372357] on FlashForth 6

Mikael Nordman — Sat, 17 Jan 2026 15:02:04 -0000

PIC18:Remove P from PAUSE

Mikael Nordman committed [36ee2f] on FlashForth 6

Mikael Nordman — Fri, 16 Jan 2026 21:11:52 -0000

PIC18: move words to root vocabulary

Mikael Nordman committed [3a8ce0] on FlashForth 6

Mikael Nordman — Fri, 16 Jan 2026 15:39:49 -0000

PIC18: Remove flow control and cpuload

Mikael Nordman committed [8bec2a] on FlashForth 6

Mikael Nordman — Fri, 16 Jan 2026 15:35:57 -0000

PIC18: Remove flow control and cpuload

Mikael Nordman committed [e49022] on FlashForth 6

Mikael Nordman — Fri, 16 Jan 2026 11:38:13 -0000

PIC18: FORGET HUH? assembler

Mikael Nordman committed [b17d34] on FlashForth 6

Mikael Nordman — Thu, 15 Jan 2026 21:35:37 -0000

PIC18: MARKER TINIT

Mikael Nordman committed [2ad68f] on FlashForth 6

Mikael Nordman — Thu, 15 Jan 2026 21:10:36 -0000

PIC18: H.N, tasks MARKER

Mikael Nordman committed [77fcb1] on FlashForth 6

Mikael Nordman — Thu, 15 Jan 2026 16:44:52 -0000

PIC18: Dot words, remove P words

Mikael Nordman committed [aa0a3e] on FlashForth 6

Mikael Nordman — Thu, 15 Jan 2026 15:35:09 -0000

PIC18: first 'working' version

Mikael Nordman committed [2182d1] on FlashForth 6

Mikael Nordman — Wed, 14 Jan 2026 19:48:08 -0000

PIC18: Abandon buggy xtended instruction set

Mikael Nordman committed [4f7b6a] on FlashForth 6

Mikael Nordman — Sat, 10 Jan 2026 19:24:31 -0000

PIC24: H.N SPACES

Mikael Nordman committed [6b932d] on FlashForth 6

Mikael Nordman — Fri, 09 Jan 2026 21:51:54 -0000

PIC18: ff-pic18.S

Mikael Nordman committed [46b1cc] on FlashForth 6

Mikael Nordman — Fri, 09 Jan 2026 21:49:06 -0000

PIC18: rename ff-pic18.S

Mikael Nordman committed [33cc1d] on FlashForth 6

Mikael Nordman — Fri, 09 Jan 2026 21:47:07 -0000

PIC18: rename directory

Mikael Nordman committed [6feadd] on FlashForth 6

Mikael Nordman — Fri, 09 Jan 2026 21:41:06 -0000

PIC18: updates

Mikael Nordman committed [09b446] on FlashForth 6

Mikael Nordman — Fri, 09 Jan 2026 21:29:49 -0000

PIC24: forth files

Mikael Nordman committed [7e7a97] on FlashForth 6

Mikael Nordman — Fri, 09 Jan 2026 20:47:17 -0000

PIC24: config files

Mikael Nordman posted a comment on discussion Open Discussion

Mikael Nordman — Thu, 08 Jan 2026 19:52:03 -0000

Did some updates to the PIC24 part. - Less writes to flash on chips that do not have eeprom (almost all chips). A smarter algorithm compares the highest written flash address with the xt to be executed. - DOES> fixed to work also with an empty DOES> part. - Unknown words do not cause INTERPRET to ABORT. This allows that unknown (marker words) words do not abort the loading from blocks or from Pere's file system. This was needed to let MARKER words to be used in those scenarios. - 64 by 64-bit unsigned...

FlashForth: for PIC and Atmega updated /ff5.0.zip

FlashForth: for PIC and Atmega — Thu, 08 Jan 2026 19:33:02 -0000

Mikael Nordman committed [250095] on Code

Mikael Nordman — Thu, 08 Jan 2026 19:29:58 -0000

PIC24:Less flash writes,UQ/,fix DOES>

Mikael Nordman committed [d8028a] on FlashForth 6

Mikael Nordman — Wed, 07 Jan 2026 11:16:37 -0000

PIC24: improved flash write algorithm

Mikael Nordman committed [a749e1] on FlashForth 6

Mikael Nordman — Sat, 03 Jan 2026 19:48:14 -0000

PIC24: PIC24F32KA302

Mikael Nordman committed [49f6c3] on FlashForth 6

Mikael Nordman — Sat, 03 Jan 2026 19:41:07 -0000

PIC24: PIC24F32KA302

Mikael Nordman committed [cb3767] on FlashForth 6

Mikael Nordman — Fri, 02 Jan 2026 13:54:17 -0000