-
I was checking the PIC24F16KA101 (102) datasheet.
It turns out to be an excellent platform for FlashForth.
It has EEPROM and a 96 byte flash erase block size.
FF for the dsPIC30 should be easy to port to this new
Microchip processor family.
2009-09-12 20:15:20 UTC by oh2aun
-
The CPU part of the PIC24 and 33 are pretty similar so I quess the same code
should work , as long as the memory map and configuration bits are taken care of.
Is the UART the same for PIC30 and 24/33 ? If not, maybe some work is needed there also.
Mikael.
2009-09-09 18:33:31 UTC by oh2aun
-
dsPIC33FJ128MC804 same as 24FJ16GA002 - so I think after changeing the memory allocation and Flashroutine it will work.
2009-09-08 21:26:06 UTC by mm-dv
-
ah - it is an addresserror.
2009-09-08 21:11:27 UTC by mm-dv
-
24FJ16GA002 - the configuration FOSC FWDT FBORPOR FGS in ff30.inc is commented out - also for test - the address NVMADR in the sourcefile.
2009-09-08 21:08:54 UTC by mm-dv
-
Which processor are you simulating ?
I can run the 4013 in the simulator and it does not go to the interrupt vectors.
About the special symbols...
__AddressError:
__StackError:
__MathError:
These are defined in the linker file (.gld) and used as target adresses in the interrupt vector tables (IVT / AIVT) .
To do this project you need to read the datasheet and the programmers...
2009-09-08 19:47:09 UTC by oh2aun
-
Hi Mikael,
at the moment I'm waiting for the delivery of a 30F4013 to start with your flashforth. The goal is to run it on a PIC24F16KA101 (102) (one of the new XLPs). So can you support me with infos about the memory map. The Mplab simulator stops at line 204:
__AddressError:
__StackError:
__MathError:
and I don't know where the error occurs (I have not much experience with the...
2009-09-08 19:28:18 UTC by mm-dv
-
No,
I do not have the time at the moment.
If someone wants to give it a try, I can give some support.
Basically what needs to be done is to enlarge the flash write buffer.
The alternate interrupt vectors should be moved to ram because of the large
flash block size.
The flash write strategy should be slightly changed so that flash writes only occur
when really needed. That should...
2009-09-08 16:51:10 UTC by oh2aun
-
Mikael,
did you already port your flashforth to the PIC24 or dsPIC33 family?
Michael.
2009-09-07 20:31:18 UTC by mm-dv
-
Mikael,
I have ported the code to PIC18FxxK20 series parts that are used on the PICKIT3 Debug Express board and then connected the PICKIT2 in the UART mode. Also ran it on various PIC18Fxxxx parts, mostly with different program memory sizes.
I found where you build the string in code and it looks like the length of the string is defined in the first byte. I'm not sure about the solution...
2009-06-19 21:52:01 UTC by larryhall
