I'm ashamed to say that I was assuming that it had 2K of RAM. (Wishful thinking, I guess.) I also got a strange error at the time that the PLLEN pragma was not recognized, even though I could clearly see it in the PIC library file. All errors cleared up, compiled, programmed, and ran successfully.
Thank you, Rob. Regards, Mike On Saturday, April 4, 2020 at 2:50:56 PM UTC-4, Rob CJ wrote: > > Hi Mike, > > I do not know which sample file you used since I had forgotten to add that > one to the last Jallib release (we are currently at version 1.5.0) so it > was never part of a release. > > Attached the following files that you need for one large byte array: > -) large_array_1 > -) large_byte_array_1_pic14 > -) sample file for pic16f1825 for 1 array. This is a special version for > you, the original sample file uses 3 arrays. This one uses 1 array of 200 > bytes but you can change it to almost 1k (limitation of the memory of the > PIC). > > If you put these files in your directory and compile the sample file it > should work. > > BTW. You get of course out of data space if your array is bigger than the > available memory of the chip which is 1k for the PIC used in the sample > file. > > For bee packages I normally download the zip file from > http://justanotherlanguage.org/downloads unzip it and move the files to a > jallib folder. > > Let me know if it worked. > > Kind regards, > > Rob > > ------------------------------ > *Van:* 'Mike K' via jallib <[email protected] <javascript:>> > *Verzonden:* zaterdag 4 april 2020 20:13 > *Aan:* jallib <[email protected] <javascript:>> > *Onderwerp:* Re: [jallib] Re: Large arrays > > Hi Rob, > > I wasn't able to compile your sample file for 16F1825. It says that it's > out of data space. I did a fresh install > of jallib_full_win_setup-1.3.0.exe. Do I need to use your file with the > latest "bee"? If so, do I just copy the files? I haven't dealt with > "bees" before now. > > Regards, > Mike > > > On Saturday, April 4, 2020 at 3:00:29 AM UTC-4, Rob CJ wrote: > > Hi Mike, > > I made an addition some time ago to the large array that Matt is referring > to since I needed it for a 16f pic. It is in the latest official JAL > release. > > So if you add this to your 16F program it should work: > -- Setup the large array > const dword LARGE_ARRAY_1_SIZE = 200 -- choose number of array > variables > const dword LARGE_ARRAY_1_VARIABLE_SIZE = 1 -- choose size of variables > (byte*1) > include large_array_1 -- include the array library > alias test is large_array_1 -- rename/alias the array to > test > > test[150] = 0x11 -- This should work. > > BTW. I only implemented this for large_array_1 not large_array_2, 3 and 4. > > Kind regards, > > Rob > > ------------------------------ > *Van:* 'Mike K' via jallib <[email protected]> > *Verzonden:* zaterdag 4 april 2020 03:31 > *Aan:* jallib <[email protected]> > *Onderwerp:* [jallib] Re: Large arrays > > Thanks, Matt. I'll have do my own library then. It seems that the large > array library is meant for 18F PICs, as the arrays are allocated in blocks > of 256 bytes and the 16F PICs only have 80-byte blocks. No worries. > > > On Friday, April 3, 2020 at 8:15:27 PM UTC-4, Matthew Schinkel wrote: > > JalV2 doesn't support array's larger the 256 bytes, however, you can use > the large array library. See one of the jallib samples such > as 18f4620_large_array.jal > > I'm not sure of the linear access feature your speaking of, but there is a > way to read & write in a linear way, see jallib sample > 18f67j50_memory_pointer.jal > > Matt. > > On Friday, April 3, 2020 at 7:33:37 PM UTC-4, Mike K wrote: > > I'm trying to implement a large array (512) on a 16F1829. I see in the > datasheet that it has a "Linear Access to GPR" feature. Does JAL take > advantage of this to make it easy on me? > > Regards, > Mike > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/a466c9b5-cc64-42f6-8843-15b5c8bc5b4b%40googlegroups.com > > <https://groups.google.com/d/msgid/jallib/a466c9b5-cc64-42f6-8843-15b5c8bc5b4b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/543cfbdf-4009-477d-b6c0-d303e87a88a9%40googlegroups.com > > <https://groups.google.com/d/msgid/jallib/543cfbdf-4009-477d-b6c0-d303e87a88a9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/adfa4dcd-16e8-47eb-a3d0-8a232fa73f78%40googlegroups.com.
