Yes, I have been "up against the wall" program space wise for quite a while. I have been begging MChip for a 256K part - because I could really use it. No luck so far.
Yes, I have been "up against the wall" program space wise for quite a while. I have been begging MChip for a 256K part - because I could really use it. No luck so far.
Charles Linquist
Hi Charles,
Would it work to use 2 PICs, one to run the program and the other as a display server, where it only has to fetch from program space or eeprom the strings and display them ? At least you would get your 256k. You could drive them both from and EXT OSC so they would clock together.
If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
.
Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
.
There simply is no "Happy Spam" If you do it you will disappear from this forum.
It would work - but it would require a lot of recoding. Unfortunately, my code doesn't have the outgoing strings in arrays. That would make life a lot easier and I should do that some day.
I have managed to compact the code to fit in 119K. Believe it or not, that gives me a fair amount of "breathing room", since all the little code blocks have been written, and now I can just call them up when I need something new.
If I could just get that elusive "Hserinx/Hseroutx" routine running it would solve a whole bunch of trouble. It looks like I'm going to have to modify PBPPIC18.LIB - AGAIN!
Charles Linquist
I don't think you will ever see anything larger than 128K (they do go up to 256k with the 24-bit core) in a PIC18. Probably has to do with die size. Since you are using a 80-pin device, could you possibly use external program memory in the extended microcontroller mode to get up to 2MB of program space?
No chance. That takes pins. I'm using all of them already.
Charles Linquist
Without knowing more about you application, I would say that you are running out resources with a PIC18. May be time to look at more powerful hardware and/or software.
What if...and this is a big ol' what if...
Since you're already using the first UART for serial, that pin is taken up...
The 2nd serial port is 'free' for the moment but you want to use it, but can't because there's not enough space for the code.
How about you use that second serial port pin as an I/O and use it to 'steer' the 1st UART's output (and/or input if need be).
I think the code impact would be minimal, just set a pin high or low depending on where the serial has to go...
You won't believe this, but I do that trick already. I use a 74HCT125 as a data selector to switch between an RS-232 port, and a Lantronix XPORT (which does telnet).
What I really need is HSERINx/HSEROUTx !!!
Charles Linquist
Bookmarks