Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 23:06 28 Oct 2025 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : PicoMite V6.01.00 release candidates

     Page 10 of 10    
Author Message
dddns
Guru

Joined: 20/09/2024
Location: Germany
Posts: 675
Posted: 06:04pm 27 Oct 2025
Copy link to clipboard 
Print this post

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?

PicoMite MMBasic USB RP2350B Edition V6.01.00RC9
OPTION SERIAL CONSOLE COM2,GP8,GP9
OPTION FLASH SIZE 16777216
OPTION COLOURCODE ON
OPTION KEYBOARD US
OPTION PICO OFF
OPTION CPUSPEED (KHz) 200000

> option lcd pins gp2,gp3,gp0
Error : Invalid Option
> option lcd pins gp14,gp15,gp12
Error : Invalid Option
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10533
Posted: 06:18pm 27 Oct 2025
Copy link to clipboard 
Print this post

option lcd spi
 
dddns
Guru

Joined: 20/09/2024
Location: Germany
Posts: 675
Posted: 06:40pm 27 Oct 2025
Copy link to clipboard 
Print this post

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

Joined: 05/03/2018
Location: Netherlands
Posts: 5398
Posted: 07:17pm 27 Oct 2025
Copy link to clipboard 
Print this post

@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
PicomiteVGA PETSCII ROBOTS
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5398
Posted: 07:46pm 27 Oct 2025
Copy link to clipboard 
Print this post

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
PicomiteVGA PETSCII ROBOTS
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5398
Posted: 07:46pm 27 Oct 2025
Copy link to clipboard 
Print this post

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
PicomiteVGA PETSCII ROBOTS
 
EDNEDN
Senior Member

Joined: 18/02/2023
Location: United States
Posts: 229
Posted: 07:51pm 27 Oct 2025
Copy link to clipboard 
Print this post

  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
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6338
Posted: 08:36pm 27 Oct 2025
Copy link to clipboard 
Print this post

@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
VK7JH
MMedit
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5398
Posted: 09:05pm 27 Oct 2025
Copy link to clipboard 
Print this post

Jim,

I use 115200 baud.

Volhout
PicomiteVGA PETSCII ROBOTS
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10533
Posted: 10:14pm 27 Oct 2025
Copy link to clipboard 
Print this post

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.
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5398
Posted: 07:00am 28 Oct 2025
Copy link to clipboard 
Print this post

Peter,

Jim fixed it in MMCC, pulling DTR low 100ms before closing the CDC channel.
A similar fix may be needed in GFXterm64.

Volhout
PicomiteVGA PETSCII ROBOTS
 
     Page 10 of 10    
Print this page


To reply to this topic, you need to log in.

The Back Shed's forum code is written, and hosted, in Australia.
© JAQ Software 2025