
MenuI think the bottleneck will be the serial interface speed (SPI) which is normally used in small OLEDs. I could not find this display WS0010B on searching for it. Unless the PIC supports a SPI DMA...
Jerson Yesterday, 15:41
try an
echo/ after the mpasm line in your batch file
Pretty much any external ram is going to be slower than internal storage.
tumbleweed - 20th February 2026, 19:03
I'm now using MPASMWIN.EXE (even if the assembler's window says "MPASM v5.14") which solved the problem about the warnings.
Now, is there a way, like for Microcode Studio, to close this...
Hello.
I'm doing a graphic project, where content of WS0010b OLED display will be updated really fast, 50fps at least.
The framebuffer size is 160 bytes. Will PBPs arraywrite/arrayread operations...
I tried to move my batch file in the PBP folder but the problem still perists.
flotulopex - 18th February 2026, 17:02
pll only works with primary clock sources , if you set the int-osc as primary clock then it works as expected
DEFINE OSC 32
OSCCON =% 01110000 '8MHz INTOSC
OSCTUNE=% 01000000 '
No, still not solved yet :frown:
When the batch file is launched with admin rights (I made a shortcut file to my batch to be able to launch it with admin rights), all HEX, ASM, etc files are not...
Problem solved: just needed to run the BATCH file with administrator's rights.
flotulopex - 17th February 2026, 19:03

Re: 160 byte framebuffer at 50 fps, internal RAM or external SRAM?
160bytes @ 50Hz is only 64kbits/s (average). Even SHIFTOUT should be able to handle that.
HenrikOlsson Yesterday, 16:54Running the SPI or MSSP module at a moderate 1Mbit/s will transfer those 160bytes in less than 2ms leaving...