Stacks looks good....Can you resize the picture (or even to cut from it) to fit in a smaller memory bank number? I'm saying to cut it bank by bank from 22787 down. You have to catch the bank border on one cut. If the problem persist no matter the size of the picture, then is not a bank allocation issue but something else...I do not have other idea until I'll play with your display driver. Thx.
On Sat 10 Sep 2022, 1:38 PM Rob CJ <rob...@hotmail.com wrote: > Hi Vasile, > > I do not see much difference in the stack here. > > *Compiled witout picture:* > jal jalv25r6 (compiled Oct 29 2021) > generating p-code > 16680 tokens, 581504 chars; 11716 lines; 18 files > generating PIC code pass 1 > generating PIC code pass 2 > 312 branches checked, 0 errors > 1775 data accesses checked, 0 errors > 192 skips checked, 0 errors > writing result > Code area: 6645 of 32768 used (words) > Data area: 222 of 4096 used > Software stack available: 80 bytes > Hardware stack depth 7 of 16 > 0 errors, 0 warnings > > *Compiled with picture:* > jal jalv25r6 (compiled Oct 29 2021) > generating p-code > 16670 tokens, 581507 chars; 11716 lines; 18 files > generating PIC code pass 1 > generating PIC code pass 2 > 328 branches checked, 0 errors > 1901 data accesses checked, 0 errors > 197 skips checked, 0 errors > writing result > Code area: 22787 of 32768 used (words) > Data area: 229 of 4096 used > Software stack available: 80 bytes > Hardware stack depth 7 of 16 > 0 errors, 0 warnings > > Kind regards, > > Rob > > ------------------------------ > *Van:* jallib@googlegroups.com <jallib@googlegroups.com> namens vsurducan > <vsurdu...@gmail.com> > *Verzonden:* zaterdag 10 september 2022 06:11 > *Aan:* jallib@googlegroups.com <jallib@googlegroups.com> > *Onderwerp:* Re: [jallib] Code does no longer work when program size > increases using mutiplication? > > Hi Rob, if you look after each compilation to software stack and hardware > stack numbers perhaps you may see important differences between numbers > when code is ok and not. I've seen something similar near HW stack fill, > but this is dificult to debug. It looks like a jump elswere that it > shuld...I guess interrupts are disabled in your test code. > > On Fri 9 Sep 2022, 8:13 PM Rob CJ <rob...@hotmail.com wrote: > > Hi Vasile, > > It sometimes goes into reset but sometimes it just hangs.It is > unpredictable so I assume that it runs somewhere out of a range that it > should not. > > How could I check the stack length? > > Thanks. > > Kind regards, > > Rob > > ------------------------------ > *Van:* jallib@googlegroups.com <jallib@googlegroups.com> namens vsurducan > <vsurdu...@gmail.com> > *Verzonden:* vrijdag 9 september 2022 07:03 > *Aan:* jallib@googlegroups.com <jallib@googlegroups.com> > *Onderwerp:* Re: [jallib] Code does no longer work when program size > increases using mutiplication? > > Rob, can you check also the stack length when pic goes in loop reset? > > On Thu 8 Sep 2022, 9:00 PM rob...@hotmail.com <rob...@hotmail.com wrote: > > Hi all, > > I have the following strange problem. I am working on the ILI9341 library > and the graphics was staring to work but I could not manage to write text > to the screen. When I tried that the PIC went haywire and sometimes came > into some kind of constant reset state. > > By accident I discovered that it had to do with the size of the program. > In the program I include a picture. When I do that the program size changes > from 5k to 21k bytes. > > If I do not include the picture, printing text goes OK but when including > the picture the PIC goes haywire again. If I leave out the printing of text > and include only the graphics with the picture then all is well. > > When I look at the assembly, there is a piece of code used for printing > fonts (using pixels) that uses multiplication. If I look at that piece of > code in the asm file the code for multiplication is different. In the > attached screenshot you see the code that goes wrong on the left and the > code that goes right on the right. > > Has anybody experience this kind of problem before so having problems with > a large program in combination with multiplication (I may draw the wrong > conclusion here). > > Any suggestions? > > Hopefully it is not a compiler issue :-( > > Thanks > > Kind regards, > > Rob > > -- > 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 jallib+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/8b0c12cf-3c70-4da6-80f3-1d30264eef9en%40googlegroups.com > <https://groups.google.com/d/msgid/jallib/8b0c12cf-3c70-4da6-80f3-1d30264eef9en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to a topic in the > Google Groups "jallib" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jallib/sx0p79J2U-A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jallib+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/CAM%2Bj4qseDr7%2BTah7FDfmX8%2B6p7GuT%3DxKpAPCfDTA1J7r4EpXAw%40mail.gmail.com > <https://groups.google.com/d/msgid/jallib/CAM%2Bj4qseDr7%2BTah7FDfmX8%2B6p7GuT%3DxKpAPCfDTA1J7r4EpXAw%40mail.gmail.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 jallib+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/GVXP195MB16370E83D82914789B895CE5E6439%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM > <https://groups.google.com/d/msgid/jallib/GVXP195MB16370E83D82914789B895CE5E6439%40GVXP195MB1637.EURP195.PROD.OUTLOOK.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 jallib+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsmMr%3D%3DGFDq46Rrz1AfNotbnkN7AxTcy%3DmwDty-eHyNMQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsmMr%3D%3DGFDq46Rrz1AfNotbnkN7AxTcy%3DmwDty-eHyNMQ%40mail.gmail.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 jallib+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jallib/GVXP195MB163791FAABFAFE907900DB74E6429%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM > <https://groups.google.com/d/msgid/jallib/GVXP195MB163791FAABFAFE907900DB74E6429%40GVXP195MB1637.EURP195.PROD.OUTLOOK.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 jallib+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/CAM%2Bj4quynDYN35CCR2rtx7LgtPasLjycYTooLzGTGwaziahUow%40mail.gmail.com.
