Search found 31 matches

Yes it did the trick. Thank you!

I am trying to read a simple ADC value but it does not work. The loop stops after trying to to read_adc(), no printouts. Am I missing something? compiler v5.103
thanks
#include <33CH512MP505.h> ...

I got it working by not using LOCATION=0x4000 as a physical address interpretation rather as a label id e.g. LOCATION=ph1 and then use this label into the function retrieving the data from the ROM. M ...

Thanks MrTT, the only way I could make it work is to look in the lst file to see where the compiler put the ROM data and use that address as starting range as in "locn".
There is no correla ...

No luck, I compiled this program where "test1_16.raw" was either 1kB or 16 bytes size and the compiler puts the data in the #015xxx address area for some reason. However I changed the proces ...

At 0x16000 I think there is some memory violation...the chip is resetting in a loop.

Thanks Mr TT, I made some progress with your math. For a full screen resolution I do have some sort of image showing somewhere in the middle and squeezed...
However I wanted to get some grasp on this ...

Thanks, it is a picture in my case 128w x 151h pixels.
I tried the #import way but it draws some garbage, sort of horizontal
bands.
Since I have an int16 for each pixel, it means I have 256 byte ...

Thanks for your solution, I'll try it.
So, index variable is total number of bytes from the raw file and basically in 8 bytes used in ROM I can retrieve 3 x int16 data.
I could also try to boost th ...

I am using a dspic33ch128mp505 with 128k flash to display on a ST7735 GLCD 128x160 resolution (compiler 5.097)
On full resolution the data takes 20.5k pixels x 16bit space.It is declared as ROM unsig ...

Thank you, I was hoping to use the entire 16-bit PortB structure ...looks like I have to chnge the processor.

I can not set the IO SOSC pins RB4/RA4 on 24FJ64GA004, compiler 5.093.
I have tried different fuses configurations but no luck. In the lst file there is always SOSC_SEC fuse set. I have a LED on RA8 ...

Yes, it worked. You are the expert !
thank you very much!

wow, thanks for your effort. Do you think is a compiler bug? or a weird chip?

I wonder if it is the extra crypto engine from this chip which is the culprit in manipulating the data somehow, althoug ...

I tried to lower the speed but it does not work, and it does not make sense in this case because OLED_text(text,strlen(text)) works on GB202. It is only OLED_BigText functions which display a white s ...