I want to use the new buffered driver for ILI9341.
I tried it before and still I get an error with Option lcd pins.
Do I overlook something?

option lcd spi

Thank you. I took the information from page 3..

@Peter,

Closing MMedit makes no difference. Tried Minicom, Picocom, Putty. Only MMCC has this behaviour. This happens when you close MMCC, and also when you leave MMCC open but DISCONNECT. It has no relation to uploading a program via MMedit (what I thought originally).

Using MMCC as a terminal shows the behaviour, as does GFXterm64 (also both with closing, and using DISCONNECT).

It is something both have in common.

But it results in a change in the pico !! Becuase once MMCC or GFXterm64 cause this problem, re-opening the port in Putty/Picocom , and later closing it, does not fix it. It only gets repaired when the pico is CPU RESTARTed.

So it is caused by something MMCC / GFXterm64 configure into the pico that is restored with a CPU RESTART (and power cycle).

Volhout

EDIT: V60100RC7 also has this behaviour, but V60100b20 does not show this behaviour. I do not have in between versions anymore to pinpoint further in detail where the change occurred.
Edited 2025-10-28 05:32 by Volhout

Peter, could it have Some relation with autosave N?
Where dat is zend to usb first, and only to screen when no N?
Where previous it was sent to screen first, and then to usb.

Blocking usb could have this effect when the order is swapped.

Volhout

Peter, could it have Some relation with autosave N?
Where dat is zend to usb first, and only to screen when no N?
Where previous it was sent to screen first, and then to usb.

Blocking usb could have this effect when the order is swapped.

Volhout

  Volhout said  

EDIT: V60100RC7 also has this behaviour, but V60100b20 does not show this behaviour. I do not have in between versions anymore to pinpoint further in detail where the change occurred.

I saw some strange behavior yesterday.   I was connecting and disconnecting MMCC and Tera Term back and forth.    And all of a sudden I started seeing 'Stack Overflow' messages from MMBasic.    

Power cycling the Pico didn't help.   Doing a 'New' and Reloading the BASIC program did not help.   Reflashing the firmware and doing other things would not get rid of the problem.  I even FlashNuked it several times and that did not help.

What finally broke the cycle was loading B18 onto it.   I only have high confidence in what I just stated.   I do not have any confidence that I know what I did wrong.
Edited 2025-10-28 06:04 by EDNEDN

@Volhout, Peter

MMCC does assert DTR. That was needed for any comms with the picomites.
I could try dropping DTR and wait 100mS when closing the port.
That should definitely stop the data flow.

In Linux I had to do a few register tweaks for baud rates over 115200. I know the baud rate does nothing with the picomite USB but If you have it set high, perhaps a lower setting is worth a try.

I don't have a VGA pico to test with and my Linux is in a VM so not a good test for USB/serial.

Jim

Jim,

I use 115200 baud.

Volhout

I have massively improved USB CDC performance since b18 and don't intend to change back any further than the Linux specific fix incorporated yesterday.