flashforth-devel Mailing List for FlashForth: for PIC and Atmega (Page 26)
Brought to you by:
oh2aun
Menu
▾
▴
flashforth-devel — FlashForth users and developers
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
(22) |
Mar
(3) |
Apr
(4) |
May
(6) |
Jun
(8) |
Jul
|
Aug
(6) |
Sep
|
Oct
(20) |
Nov
(9) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(4) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(14) |
Nov
(1) |
Dec
|
| 2013 |
Jan
(4) |
Feb
(5) |
Mar
(4) |
Apr
(2) |
May
|
Jun
(29) |
Jul
(7) |
Aug
|
Sep
(20) |
Oct
(9) |
Nov
(2) |
Dec
(7) |
| 2014 |
Jan
|
Feb
(23) |
Mar
(113) |
Apr
(25) |
May
(31) |
Jun
(9) |
Jul
(47) |
Aug
(15) |
Sep
(1) |
Oct
(4) |
Nov
(8) |
Dec
(3) |
| 2015 |
Jan
(21) |
Feb
(1) |
Mar
(18) |
Apr
(16) |
May
(100) |
Jun
(33) |
Jul
|
Aug
(10) |
Sep
(8) |
Oct
(7) |
Nov
(5) |
Dec
|
| 2016 |
Jan
(12) |
Feb
(9) |
Mar
|
Apr
(7) |
May
(5) |
Jun
(9) |
Jul
(1) |
Aug
(2) |
Sep
(17) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
(6) |
Feb
(12) |
Mar
(9) |
Apr
(3) |
May
(7) |
Jun
|
Jul
(12) |
Aug
|
Sep
(13) |
Oct
|
Nov
|
Dec
(10) |
| 2018 |
Jan
(1) |
Feb
|
Mar
(7) |
Apr
(4) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(21) |
Oct
(3) |
Nov
|
Dec
|
| 2019 |
Jan
(5) |
Feb
(4) |
Mar
|
Apr
|
May
(3) |
Jun
(11) |
Jul
(4) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
(9) |
Dec
(7) |
| 2020 |
Jan
(2) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(4) |
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(8) |
Apr
(40) |
May
(12) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(4) |
Nov
(10) |
Dec
(4) |
| 2022 |
Jan
(29) |
Feb
(7) |
Mar
(10) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(6) |
| 2023 |
Jan
(8) |
Feb
|
Mar
(5) |
Apr
(9) |
May
(6) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(9) |
Aug
(7) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: GRAHAM B. <gw...@bi...> - 2015-01-23 08:46:13
|
Mikael - I am trying to get started with the assembler. I have compiled
asm.txt and asmtest.txt. testif0,testif1 and testuntil appear to work.
Could you give some more examples - load a register with a constant and
push to stack, pop from stack to a register, pop from stack-2 to a
register would help me get started.
I am not understanding why the square brackets ( enter interpreter
state) is required???
--
Graham Boyd
Managing Director
Geosolutions Pty. Ltd.
16 Centre Way
Belair, 5052
South Australia
Ph. 61 (0)407 563944
61 (0)8 82786752
www.geosol.com.au
|
|
From: Mikael N. <mik...@fl...> - 2015-01-17 11:01:03
|
Timer 1 is used for the CPU load measurement. Timer 2 is free. If you want to use Timer 1 you need to recompile FF without CPU load measurement. When you recompile FF you can in the configuration file select the timer used for MS. It can be timer 0, 1 or 2. /Mike On 17.01.2015 12:56, Claus Kühnel wrote: > Which timers are used internally and which are free for independant use? |
|
From: C. K. <ma...@ck...> - 2015-01-17 10:56:18
|
I try to port some Arduino timer examples into FF and got problems with Timer1. Which timers are used internally and which are free for independant use? Timer0 seems to be used for ms, right? Dr. Claus Kühnel - Talstrasse 39a - CH-8852 Altendorf |
|
From: C. K. <ma...@ck...> - 2015-01-17 00:16:27
|
Programming in Forth means defining new words built on the current vocabulary. It does not necessarily mean that the words have already defined the final properties. Forth offers the possibility to vary the properties of such words afterwards. You can find an prgram sample at https://sourceforge.net/p/flashforthforarduino/wiki/Vectors/ Claus Dr. Claus Kühnel - Talstrasse 39a - CH-8852 Altendorf |
|
From: <fla...@li...> - 2015-01-11 08:12:59
|
You need to configure the UART pins in config file p33_config.inc. .equ RPINR18VAL, 11 ; U1RXPIN RP43 PB11 pin22 microstick2 .equ U1TXPIN, 10 ; PB10 pin21 microstick2 If you use HW flow control you need the separate the CTS RTS pins on the MCP2200 and connect RB12 to the CTS pin13 on the MCP2200. And define the RTS pin in the FF config file. .equ U1RTSPIN, 12 ; Solder to MCP2200 CTS pin13 on microstickplus if HW flow control Attached is the config file I just tried with my dsPIC33FJ128MC802. BR Mike |
|
From: <fla...@li...> - 2015-01-10 21:21:32
|
I recently got my microstick 2 and microstick plus boards in the mail and I'm trying to load flashforth on it. I'm attempting to use the dsPIC33FJ128MC802 that came with the kit. Is there some configuration in the code that I need to do to be able to use the USB serial adapter that is on the microstick plus board? I loaded the code and connected to the microstick plus, but did not see the console. Thanks, -mdg |
|
From: <fla...@li...> - 2015-01-07 23:42:16
|
flashforth.com Dr. Claus Kühnel - Talstrasse 39a - CH-8852 Altendorf -----Original-Nachricht----- Von: fla...@li... An: fla...@li... Datum: 07.01.2015 18:05 Betreff: Re: [Flashforth-devel] FF utilities in Wiki Where is the Wiki? I couldn't find it... Thanks, Don On Tuesday, January 6, 2015 10:09 PM, "fla...@li..." <fla...@li...> wrote: I just uploaded my FF utilities to the FF Wiki. Written for FF 4.8, but should work for 5.0 too. A bunch of useful words, FIG Forth style number conversion, data structures Thanks for setting up the Wiki. I would have sent these long ago, but could not figure out the git system. -- Mike Miller ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Flashforth-devel mailing list Fla...@li... https://lists.sourceforge.net/lists/listinfo/flashforth-devel ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Flashforth-devel mailing list Fla...@li... https://lists.sourceforge.net/lists/listinfo/flashforth-devel |
|
From: <fla...@li...> - 2015-01-07 17:17:58
|
http://sourceforge.net/p/flashforth/wiki/Home/ On Wednesday, January 7, 2015, <fla...@li...> wrote: > Where is the Wiki? I couldn't find it... > > Thanks, > Don > > > On Tuesday, January 6, 2015 10:09 PM, " > fla...@li... > <javascript:_e(%7B%7D,'cvml','fla...@li...');>" > <fla...@li... > <javascript:_e(%7B%7D,'cvml','fla...@li...');>> > wrote: > > > I just uploaded my FF utilities to the FF Wiki. Written for FF 4.8, but > should work for 5.0 too. > > A bunch of useful words, FIG Forth style number conversion, data structures > > > Thanks for setting up the Wiki. I would have sent these long ago, but > could not figure out the git system. > > -- > Mike Miller > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > <javascript:_e(%7B%7D,'cvml','Fla...@li...');> > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > > > |
|
From: <fla...@li...> - 2015-01-07 17:04:47
|
Where is the Wiki? I couldn't find it... Thanks, Don On Tuesday, January 6, 2015 10:09 PM, "fla...@li..." <fla...@li...> wrote: I just uploaded my FF utilities to the FF Wiki. Written for FF 4.8, but should work for 5.0 too. A bunch of useful words, FIG Forth style number conversion, data structures Thanks for setting up the Wiki. I would have sent these long ago, but could not figure out the git system. -- Mike Miller ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Flashforth-devel mailing list Fla...@li... https://lists.sourceforge.net/lists/listinfo/flashforth-devel |
|
From: <fla...@li...> - 2015-01-07 06:09:10
|
I just uploaded my FF utilities to the FF Wiki. Written for FF 4.8, but should work for 5.0 too. A bunch of useful words, FIG Forth style number conversion, data structures Thanks for setting up the Wiki. I would have sent these long ago, but could not figure out the git system. -- Mike Miller |
|
From: <fla...@li...> - 2015-01-06 17:21:21
|
Graham, I have rewritten the Atmega BIT words. The BIO words have been merged into the BIT words so that always the optimal IO register access is used. The BIO words were removed. The new BIT words can be found in git and in the latest ff5.0.zip file. Hope it works now. Tests can be found in bit-test.txt. Mike |
|
From: <fla...@li...> - 2015-01-06 07:05:52
|
Yes, I would really like for people to contribute FF application code. After all FF is a GPL system. You can create a wikipage in the FF wiki where you can paste your code or attach it as a file. Name your pages: CHIP:SUBJECT for example: ATMEGA2560:LCD display using K0066 controller Also put a link to a new page in the wiki front page. I'll take a look at the bit0: problem. Mikael |
|
From: <fla...@li...> - 2015-01-06 06:22:25
|
Mikael - having great success with FF on mega2560. Minor problem with
bit0: I think. Attached code snippet shows the problem.
Do you want code from developers (e.g people like me) uploaded so that
other people can access this. I see someone requesting SPI code and I
have the Adafruit micro SD card working
successfully as well as a number of other "accessories" - LCD display, 4
by 4 keypad, DS3232 clock using i2cbase.txt, GPS using Adafruit
ultimate breakout.
--
Graham Boyd
Managing Director
Geosolutions Pty. Ltd.
16 Centre Way
Belair, 5052
South Australia
Ph. 61 (0)407 563944
61 (0)8 82786752
www.geosol.com.au
|
|
From: <fla...@li...> - 2015-01-05 19:18:37
|
Hi, I do not have any skill in writting AVR code, so I was wondering if someone has done it on ArduinoUno328p and ArduinoMega2560. If yes, then I will be very happy to use some available code. Best regards, Guy |
|
From: <fla...@li...> - 2015-01-05 17:27:09
|
I had a crack at adapting FF to the 18f67k22 but it seems to be harder than I thought. I do not have the chips and the simulator in MPLABX has some bug preventing it to work with the 18F67K22 series chips... Also due to that the 128 byte flash buffer would not fit into access ram, some specific code and a specific linker file would be needed for the 128 Kbyte chips. The 64 Kbyte chip would be easier to adapt to. The only FF specific material there is can be found on the FF website. And there is the code. The way a simple Forth is built up has not changed that much during the decades. The tutorials from Peter are good to have a look at. BR Mike |
|
From: <fla...@li...> - 2015-01-05 13:20:11
|
Response most appreciated . On second question - I was wondering if there was an overview of how the flashforth or any forth system is" put together . I still have my Brodie Book from way back when" but was looking for an explanation of the program flow - : eg On startup the assembler code sets up the pointers to the stack in routine ....... and initializes the serial port in routine ..... . Thereafter the system stays in a loop waiting for character from the serial port and on seeing a space call routine ....... that looks up the word in the dictionary in routine ...... and so on . Many years Hendrix wrote a manual on how the small C compiler worked and I was looking for something similar On Mon, Jan 5, 2015 at 1:24 PM, <fla...@li...> wrote: > This CPU will require a small modification in the flash write routine > of FlashForth to support 128 byte flash sectors. > Sofar only 64-byte flash sectors have been needed by the PIC devices. > > I will try to fix this in the near future. > > Your second question I do not really understand. > Are you asking about debugging or about the FF code generator or > how to write assembly in FF or something else ? > > BR Mike > > On 05.01.2015 11:11, fla...@li... wrote: > > 1. Has anyone got flashforth to work on this processor which has > > 128KB > > flash . Many years ago ( 35 ) we always used Forth to debug new > > hardware designs on Z80's > > and have a new design using the PIC . Words like ON , OFF and TOGGLE > > where you put pin number and in the case of toggle pulse width and > > duty cycle , are great for exercising any I/O pin that you can then > > trace with an oscilloscope. > > > > 2. Where could I find guidance on how the code operates at a higher > > level as single stepping is proving challenging. > > > > Regards > > Hedley > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Flashforth-devel mailing list > Fla...@li... > https://lists.sourceforge.net/lists/listinfo/flashforth-devel > |
|
From: <fla...@li...> - 2015-01-05 12:19:46
|
This CPU will require a small modification in the flash write routine of FlashForth to support 128 byte flash sectors. Sofar only 64-byte flash sectors have been needed by the PIC devices. I will try to fix this in the near future. Your second question I do not really understand. Are you asking about debugging or about the FF code generator or how to write assembly in FF or something else ? BR Mike On 05.01.2015 11:11, fla...@li... wrote: > 1. Has anyone got flashforth to work on this processor which has > 128KB > flash . Many years ago ( 35 ) we always used Forth to debug new > hardware designs on Z80's > and have a new design using the PIC . Words like ON , OFF and TOGGLE > where you put pin number and in the case of toggle pulse width and > duty cycle , are great for exercising any I/O pin that you can then > trace with an oscilloscope. > > 2. Where could I find guidance on how the code operates at a higher > level as single stepping is proving challenging. > > Regards > Hedley |
|
From: <fla...@li...> - 2015-01-05 09:11:23
|
1. Has anyone got flashforth to work on this processor which has 128KB flash . Many years ago ( 35 ) we always used Forth to debug new hardware designs on Z80's and have a new design using the PIC . Words like ON , OFF and TOGGLE where you put pin number and in the case of toggle pulse width and duty cycle , are great for exercising any I/O pin that you can then trace with an oscilloscope. 2. Where could I find guidance on how the code operates at a higher level as single stepping is proving challenging. Regards Hedley |
|
From: <fla...@li...> - 2014-12-24 18:45:15
|
24.12.2014 12:30, fla...@li... пишет: > Merry Christmas ! Thank you very much! & Merry Christmas ! :) -- Bye! Илья |
|
From: <fla...@li...> - 2014-12-24 09:46:18
|
Hi, I have put an example of a microsecond delay in the wiki. http://sourceforge.net/p/flashforth/wiki/Atmega%20microsecond%20delay/ Merry Christmas ! Mike |
|
From: <fla...@li...> - 2014-12-24 01:55:45
|
Tell me, how you can organize a delay in microseconds (mega 2560)? I'm not good at assembler. -- Bye! Илья |
|
From: <mik...@fl...> - 2014-11-10 17:54:27
|
After some investigation the mystery is solved.
The code for redirecting the rx2complete interrupt was missing:-(
This has been fixed in todays FF 5.0 version (10.11.2014).
So now the interrupt numbers in the data sheet can be used.
I also noticed that the Atmega 328 interrupts do not work at all.
Now that is also fixed.
BR Mike
Here is the piece of code that was missing:
.org BOOT_START + 0x64
rcall FF_ISR
.endif
+.if 0x66 < INT_VECTORS_SIZE
+.org BOOT_START + 0x66
+ rcall FF_ISR
+.endif
.if 0x68 < INT_VECTORS_SIZE
.org BOOT_START + 0x68
rcall FF_ISR
|
|
From: <mik...@fl...> - 2014-11-10 17:02:12
|
Thanks Peter. I will include them in the distribution. Mike On 09.11.2014 07:32, Peter Jacobs wrote: > Now that the teaching term is drawing to an end, I've had a chance to > finally build a set of words for I2C master mode on AVR and PIC24. > They're slightly different to Mike's PIC18 i2c-base words, in that > some return flags, so I've built a corresponding new set for PIC18 as > well. They're all in Forth since there doesn't seem to be much need > for speed with an I2C device. The i2c-detect word (adapted from > amforth) runs on top of this base set, with no change for all chip > architectures, as does the small application for reading a TC74 > temperature sensor. > > If these are of use to people, they might be included in the FF > distribution. I've tried to choose names that are similar to, but > will not clash with, the original i2c words for the PIC18. > Cheers, > Peter J. > > |
|
From: Peter J. <pe...@me...> - 2014-11-09 23:25:52
|
On 10/11/14 03:23, mik...@fl... wrote: > Did you try to clear the ODCB.4 and ODCA.4 bits ? > These should be cleared by default, but you never know ? The open-drain bits are zero. blink-ra4-rb4 ok<#,ram> odcb @ u. 0 ok<#,ram> odca @ u. 0 ok<#,ram> > > Strange that the C code did not touch the ANSEL registers. The ANSA and ANSB control only the digital inputs for the pins, as I understand the datasheet. > > The only other thing I can think of is if the pins are used for > something else by FF. That's my guess but I haven't been able to really find such use. I've added my PIC24FV16KM202 configuration to the p24f16ka_config.inc file as this seemed the closest available processor. In that I have FC1_TYPE set to 1 so it shouldn't use the U1RTSPIN which is set to 0xc (RA4, I believe). I've attached my edited version of that file. I also do not have BAUDRATE2 declared so that the U2RTS/ and U2CTS/ should not be active on RB4 and RA4, respectively. Looking at the peripheral module disable, U1MD is enabled (0) while SSPMD, U2MD and ADCMD are disabled (1). That looks appropriate. bin ok<%,ram> $0770 @ u. 11000001 ok<%,ram> > Are those pins defined in the FF confuguration file for load led or > flow control ? The CPU_LOAD_BIT is defined as 8. > > BR Mike > > My version of your source file is from back at the beginning of May 2014. I should port my (small) adjustments for the PIC24FVKM202 to your latest version and try again. Thanks for the hints. Peter J. |
|
From: <mik...@fl...> - 2014-11-09 18:19:37
|
Hello, It seems to work with interrupt number 53 instead of 52. But I really do not understand why ?? The timer 3 example works with the interrupt number in the datasheet, but for rx2 complete there is an offset of one from documented value. Are there several versions of the Atmega 2560 chips with different interrupt vectors ? BR Mike |
17 messages has been excluded from this view by a project administrator.
