This sure looks like a compiler bug. Create two sets of files with/without the one line of calculation that makes the difference. If you post them as zip files, I can put them in the svn for reference and we (you) can inform Kyle.
Joep 2010/10/27 K-4U <[email protected]>: > Hi Joep, > > The modifications i made: > I added a function to write pixels but keep them buffered. (So that > you don't call the write_pixel 8 times, to fill the same row) (Should > have no consequences for the font array) > > In glcd_common. i added several functions, yet none actually refering > to the font array. > 2 functions to create progressbars(horizontal and vertical) > 'lcd_filled_rect'. To draw a rectangle that is filled. > all three of these functions call to the buffer-function(mentioned > above). > > > The font i am using is the regular one, but with added chars (i added > 11 more) > > In the meantime. I commented some of the code from my project. > When i start using some calculations, the font goes haywire again(3 > stripes). > When i comment out those calculations, the font is back to normal. > > Also.. i think it's related as well. > i try to print a number on the GLCD. That calculation all works fine, > the lcd_write_char function gets called.. but the cx variable is 0.. > the indx variable gets calculated correctly, but it just can't get the > value out of the array. > > Is it possible that there is an overflow somewhere, that i have to > much data? > > The output of my compiler window: > > C:\Program Files\Notepad++>C:\PICjal\JAL\Compiler\jalv2.exe -Wno-all - > long-start > -clear -s c:\PICjal\JAL\Libraries; "D:\My Documents\My Dropbox > \Elektronica\glcd > \main.jal" > jal 2.4n (compiled Jun 2 2010) > generating p-code > 0 errors, 0 warnings > 1165 tokens, 268687 chars; 7125 lines; 16 files > generating PIC code pass 1 > generating PIC code pass 2 > writing result > Code area: 4197 of 8192 used (words) > Data area: 123 of 352 used > Software stack available: 96 bytes > Hardware stack depth 3 of 8 > > > > Oh.. by worse.. i meant that i have 4 stripes.. one at the top, one at > the center and 2 at the bottom(stacked together) > > Koen > > On Oct 27, 11:47 am, Joep Suijs <[email protected]> wrote: >> Hi Koen, >> >> You don't give us much to go on. >> > I tried the glcd_ks0108.jal with succes.. I modified some things and >> > added my own code.. >> >> So you changes something, but don't tell us what. And please tell us >> what compiler version you use (with date). >> >> > Now.. Here's a problem. >> > My font is broken. >> >> What font? A standard one? One you modified, created? Has it worked before? >> >> > instead of showing the letters. It shows something like an "=" sign.. >> > (only with 3 stripes.. 1 top, 1 center, 1 bottom) >> >> That's clear! >> >> > I removed the "pragma inline" from the "lcd_write_char" which actually >> > made it worse. >> >> This is not. What is worse? I guess the worst that can happen is that >> each pixel is inverted to what it is supposed to be, but that would be >> an achievment for a bug ;) >> >> > But.. when i put it back.. it also doesn't work! >> >> What do you mean? Does it behave like before? Or is there other >> behavior? Did you change anything else? >> >> > Also.. when i use the same module in a different project. Nothing is >> > wrong! >> >> Did you use all the same features of this library in an other project >> on exactly the same hardware? And with the same modifications made to >> this library? >> >> If the exact library code you use works in an other configuration, >> there is probably something wrong with your new project (something >> you're doing different) or you might have run into a compiler bug. >> If it is a compiler bug, the best way to proceed is to take your >> non-working project, and (in steps) remove code that is not essential >> for glcd to work. Once you have a working verions, go back one step to >> the last non-working verion and remove less code. Repeat this until >> you have two versions that have little difference and one of which is >> working and one not. >> Then, compile both versions with -debug option and suppy all files >> (source, library files and 2 asm files). >> >> Of course you can work the other way around: take your working project >> and extend it to the new one. >> >> Joep > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
