Effective ways for storing multiple string variables within PBP code?

[CuriousOne]

PIC16F887, 16F917, 16F1939, basically any with built in oscillator, 44 pin tqfp case and at least 8k memory.

Why does this matters? above code uses some chip specific magic?

[richard]

chip has to able to read its code space, pic18 needs different treatment


there is a couple of typo's
;lang 2
da "Jahr einstellen", 0 ;6+ 0
da "Set Month" ;6+ 1
da "Set Date", 0 ; 2
da "Set day of week" ; 3
da "Set Hour", 0 ; 4
da "Set Minute", 0 ; 5
;lang 3 ;semi colon missing
da "Definir l'annee" ; 12+ 0 ;extra comma
da "Set Month" ; 12+ 1
da "Set Date", 0 ; 2
da "Set day of week" ; 3
da "Set Hour", 0 ; 4
da "Set Minute", 0 ; 5

[CuriousOne]

No I'm not using 18F series.
Regarding that "own code reading"
how it is named in datasheet, so I can have a look for appropriate models?

[mpgmike]

You said that if the EEPROM were larger, you could easily store the strings there, then find them with a look-up index. Newer PICs have the ability to write directly to Flash (HEF is one example, but not the limit). The mechanics of it are essentially the same as writing to EEPROM. PBP has no convenient command code for it (that I'm aware of), as it didn't exist when PBP was created. However, look at some of the PIC16F1xxxx chips (or PIC18FxxK40/42). You can treat Flash memory like EEPROM memory. Be aware that with Flash you must first erase an entire page before writing to it. If you intend to change the content periodically, you'll need temporary variables to store the entire page, alter what you wish to change, erase the page, then re-write back to the same addresses with the revised data.

[CuriousOne]

So I'm not asking for any direct-hardware-access methods. I just asked, whenever it is possible, using built-in abilities of PBP, structure all this in more simple to use way? Basically, I can hook a external EEPROM chip to my device, but I was not able to make to work any EEPROM with PBP, I2C or SPI.

[richard]

Regarding that "own code reading"
how it is named in datasheet

look for "read flash" or "read program flash", there is no consistency i have ever found in how microchip assemble datasheet info

So I'm not asking for any direct-hardware-access methods. I just asked, whenever it is possible, using built-in abilities of PBP

and it is , i "fancied up" my code a bit and can change language with one var



mikes suggestion would be useful to allow a common set of string messages to read into hef in chosen language from a
pg-flash coded larger multi-lingual data set.

its all doable