| Menu | JAQForum Ver 26.09 |
Forum Index : Microcontroller and PC projects : PicoMite V7.00.00b8 and release candidates
Understood, but then there can only be one BMP in the flash slot. I was trying to create individual small images, and append these to the previous ones in the flash slot. And then, in a player routine play them quickly after another. But maybe now I have to do the appending in a framebuffer F (matrix view), and copy the framebuffer to flash. And then playback would be to restore framebuffer, and blit sections from F to N view window. Volhout |
||||||
Look at the tilemap manual. |
||||||
G'day Peter, Further to previous post, the gamepad / keyboard lockup is seen on 2 different keypad/mouse units with the Gamepad plugged in, testing with another gamepad is not possible, I only have this type. After the lockup, the PC3 is still working via the console. Unplugging USB items makes no difference Sometimes the USB HUB LED's extinguish, sometimes not Sometimes the last key is on auto-repeat, sometimes not Switching the USB disable switch to DISABLE resets the problem, indicating it might be the HUB locking up (if thats possible) Another niggle. After using the editor and exiting, the autowrap of lines at the console will no longer go past the end of the first line. On the HDMI it is still working as normal. This was found testing the gamepad problem. Option list as per previous post. Very nice work on the Mather.host website and many thanks for making it available for us all Regards, Lyle. |
||||||
I can't reproduce the lockup and I have tried. I don't have a composite keyboard/mouse device if that is the route of the issue What version of the firmware? |
||||||
Peter, I was testing to see if it was the Keyboard/Mouse or the GamePad causing the problem, I'm going to assume gamepad but I have had random but rare lockups before. > option list PicoMitePC3 MMBasic USB RP2350B Edition V7.00.00RC9 OPTION SERIAL CONSOLE COM2,GP8,GP9 OPTION SYSTEM I2C GP20,GP21 OPTION FLASH SIZE 16777216 OPTION COLOURCODE ON OPTION MOUSE SENSITIVITY 1.0000 OPTION KEYBOARD US OPTION PICO OFF OPTION RESOLUTION 640x480 @ 315000KHz OPTION HDMI PINS 1, 3, 5, 7 OPTION GUI CONTROLS 63 OPTION SDCARD GP33, GP30, GP31, GP28 OPTION AUDIO I2S GP10,GP22', ON PWM CHANNEL 11 OPTION RTC AUTO ENABLE OPTION COUNT GP34,GP35,GP36,GP37 OPTION PLATFORM PICO COMPUTER 3 OPTION PSRAM PIN GP47 > Also tested at 1024x600 resolution. This was tested with TeraTerm 5.7.1 on WIN10 Regards, Lyle. Edited 2026-11-17 23:49 by mozzie |
||||||
What firmware are you seeing the "niggle" on? |
||||||
Peter, PicoMitePC3 MMBasic USB RP2350B Edition V7.00.00RC9 The problem is seen typing a line longer than the console width after exiting the editor. Hence the term "Niggle". Line is OK on HDMI output. Tested PicoMiteHDMI MMBasic USB RP2350A Edition V6.03.01 and it works ok. Using TeraTerm 5.7.1 on WIN10 in case this is a problem. Regards, Lyle. |
||||||
Mozzie please do as follows from the serial console after a freeze, before touching the switch: PRINT MM.INFO(USB 1), MM.INFO(USB 2), MM.INFO(USB 3), MM.INFO(USB 4) — zeros mean the stack removed the devices (candidates 3 or 4); non-zero means they are still mounted and transfers stopped (1 or 2). PRINT HEX$(PEEK(WORD &H50110048)) twice — if SOF_RD is not advancing, the controller has stopped sending frames, which matches the LEDs going out. PRINT HEX$(PEEK(WORD &H5011004C)), HEX$(PEEK(WORD &H50110050)), HEX$(PEEK(WORD &H50110054)), HEX$(PEEK(WORD &H50110058)), HEX$(PEEK(WORD &H50110098)) — SIE_CTRL, SIE_STATUS (latched error bits), INT_EP_CTRL, BUFF_STATUS and INTS. Also please confirm if the combo dongle is low or full speed, and whether a COM port is open on the CDC device when it happens. |
||||||
Hi Peter, Just converted one of my Picos back to an LCD and have found a problem with background update, without background update all is fine, with background update all the active pixels on the screen occasionally flash blue, then back to normal. I have just found this only happens once you have inserted and used the SD card. Test program attached. PicoMite MMBasic USB RP2350A Edition V7.00.00RC9 OPTION SERIAL CONSOLE COM2,GP8,GP9 OPTION SYSTEM SPI GP18,GP19,GP16 OPTION SYSTEM I2C GP20,GP21 OPTION FLASH SIZE 4194304 OPTION COLOURCODE ON OPTION KEYBOARD ES, 0, 0, 170, 100 OPTION CPUSPEED (KHz) 420000 OPTION LCDPANEL CONSOLE 7,,, 75,NOSCROLL OPTION DISPLAY 40, 80 OPTION LCDPANEL ST7796S, LANDSCAPE,GP12,GP13,GP14,GP15 OPTION LCD BACKLIGHT 75 OPTION TOUCH GP17,GP7 GUI CALIBRATE 0, 3944, 3891, -1289, -857 OPTION SDCARD GP22, GP2, GP3, GP4 OPTION KEYBOARD REPEAT 170,100 OPTION AUDIO GP10,GP11', ON PWM CHANNEL 5 OPTION RTC AUTO ENABLE OPTION COMPILE ON OPTION MODBUFF ENABLE 200 OPTION DEFAULT FONT 7, 1 bubble2350lcd.zip |
||||||
Peter, I will test again and report back shortly. At this point testing has confirmed that the problem occurs from PICOMITE HDMIUSB V6.03.02b2, prior to this firmware I have been unable so far to replicate the fault. Regards, Lyle. |
||||||
Lyle, you can also try this version which has one change that may improve things PicoMiteHDMIUSBV7.00.00.zip |
||||||
Peter, Thanks for trying to diagnose this, I realise you (and Claude) have been rather busy. Can you please advise how to test the USB dongle for low or full speed. In the following tests the HUB LED's can remain on or turn off at random, off more often with the USB CDC plugged in. In all tests, generally the faster the mouse is moved the quicker the fault occurs, but it is not always the case. TESTED NEW PicoMite HDMIUSB V7.00.00 as posted on Pico Computer, results are similar except: TEST 5: Keyboard / Mouse + Gamepad HUB LED's REMAIN ON > fgf [USB CRC 1] ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff Error : Variable name too long > ? mm.info(usb 1) 1 > ? mm.info(usb 2) 2 > ? mm.info(usb 3) 130 > ? mm.info(usb 4) 0 > print hex$(peek(word &h50110048),8) 0000035A > print hex$(peek(word &h50110048),8) 0000045C > print hex$(peek(word &h50110048),8) 0000023D > print hex$(peek(word &h5011004c),8) 20008208 > print hex$(peek(word &h50110050),8) 50001205 > print hex$(peek(word &h50110054),8) 0000001E > print hex$(peek(word &h50110058),8) 00000000 > print hex$(peek(word &h50110098),8) 00000000 > TESTED WITH PicoMite PC3 V7.00.00.rc9 on PC3 TEST 1: Keyboard / Mouse + Gamepad HUB LEDS REMAIN ON > Generic Gamepad Connected on channel 3 > US USB Keyboard Connected on channel 1 > Mouse Type: Standard 8-bit X/Y bits: 8/8 Buttons: 5 Report length: 8 bytes Has wheel: Yes (byte 3) Has pan: No Decode: descriptor layout USB Mouse Connected on channel 2 > jfkljjjjjjjjjjjjjjjjjjjjjjjjjjjjjj (KEYBOARD NOT RESPONDING / AUTOREPEAT STUCK ON) Error : Variable name too long > ? mm.info(usb 1) 1 > ? mm.info(usb 2) 2 > ? mm.info(usb 3) 130 > ? mm.info(usb 4) 0 > print hex$(peek(word &h50110048),8) 0000039B > print hex$(peek(word &h50110048),8) 000002D9 > print hex$(peek(word &h50110048),8) 000004E2 > print hex$(peek(word &h5011004c),8) 20008208 > print hex$(peek(word &h50110050),8) 51001205 > print hex$(peek(word &h50110054),8) 0000001E > print hex$(peek(word &h50110058),8) 00000000 > print hex$(peek(word &h50110098),8) 00000000 > TEST 2: Keyboard / Mouse + Gamepad + USB CDC not opened HUB LEDS REMAIN ON > Generic Gamepad Connected on channel 3 > USB CDC Device Connected on channel 5 (COM3) > US USB Keyboard Connected on channel 1 > Mouse Type: Standard 8-bit X/Y bits: 8/8 Buttons: 5 Report length: 8 bytes Has wheel: Yes (byte 3) Has pan: No Decode: descriptor layout USB Mouse Connected on channel 2 > fghgfhfghfghfghfghgggggggggggggggggggggggggggggggg (KEYBOARD NOT RESPONDING / AUTOREPEAT STUCK ON) Error : Variable name too long > ? mm.info(usb 1) 1 > ? mm.info(usb 2) 2 > ? mm.info(usb 3) 130 > ? mm.info(usb 4) 0 > print hex$(peek(word &h50110048),8) 0000049D > print hex$(peek(word &h50110048),8) 000000F2 > print hex$(peek(word &h50110048),8) 0000021D > print hex$(peek(word &h5011004c),8) 20008208 > print hex$(peek(word &h50110050),8) 51001205 > print hex$(peek(word &h50110054),8) 0000001E > print hex$(peek(word &h50110058),8) 00000000 > print hex$(peek(word &h50110098),8) 00000000 > TEST 3: Keyboard / Mouse + Gamepad + USB CDC not opened HUB LEDS TURNED OFF > USB CDC Device Connected on channel 5 (COM3) > Generic Gamepad Connected on channel 3 > US USB Keyboard Connected on channel 1 > Mouse Type: Standard 8-bit X/Y bits: 8/8 Buttons: 5 Report length: 8 bytes Has wheel: Yes (byte 3) Has pan: No Decode: descriptor layout USB Mouse Connected on channel 2 > fdhth (KEYBOARD NOT RESPONDING / AUTOREPEAT STUCK ON) Error : Unknown command > ? mm.info(usb 1) 1 > ? mm.info(usb 2) 2 > ? mm.info(usb 3) 130 > ? mm.info(usb 4) 0 > print hex$(peek(word &h50110048),8) 000004DF > print hex$(peek(word &h50110048),8) 000005AE > print hex$(peek(word &h50110048),8) 00000139 > print hex$(peek(word &h5011004c),8) 20008208 > print hex$(peek(word &h50110050),8) 51001205 > print hex$(peek(word &h50110054),8) 0000001E > print hex$(peek(word &h50110058),8) 00000000 > print hex$(peek(word &h50110098),8) 00000000 > Test 4: Keyboard / Mouse + Gamepad + USB CDC opened as #1 HUB LEDS REMAIN ON > USB CDC Device Connected on channel 5 (COM3) > Generic Gamepad Connected on channel 3 > US USB Keyboard Connected on channel 1 > Mouse Type: Standard 8-bit X/Y bits: 8/8 Buttons: 5 Report length: 8 bytes Has wheel: Yes (byte 3) Has pan: No Decode: descriptor layout USB Mouse Connected on channel 2 > open "com3:115200" as #1 > dfdfdfghghdghgfhfghthgdhtghgfhjgjfggjfgghfgjfjrjfsjrjjrryryjtttjfgjfjfgjfjhjjjfgjgfjfgjjfgjgfjfjjfgjfgfgjfgjfjgfjfgjfgjjfgggggggggggggggggggggggggg (KEYBOARD NOT RESPONDING / AUTOREPEAT STUCK ON) Error : Variable name too long > > ? mm.info(usb 1) 1 > ? mm.info(usb 2) 2 > ? mm.info(usb 3) 130 > ? mm.info(usb 4) 0 > print hex$(peek(word &h50110048),8) 000006BE > print hex$(peek(word &h50110048),8) 00000015 > print hex$(peek(word &h50110048),8) 0000074D > print hex$(peek(word &h5011004c),8) 20008200 > print hex$(peek(word &h50110050),8) 51801205 > print hex$(peek(word &h50110054),8) 0000001E > print hex$(peek(word &h50110058),8) 00000000 > print hex$(peek(word &h50110098),8) 00000000 > Tested during fault condition: > open "com3:115200" as #1 Error : COM3: USB device did not accept the baud rate > print bin$(device(gamepad 3,b),16) 0000000000000000 (WITH 2 BUTTONS HELD DOWN) > Any further testing will be later today, already way past bed time..... Regards, Lyle. |
||||||
Hello all, In the PM v7 RC 8 Manual Page 35, there is a statement I have a variable called fIX - I'm using it as the name of an index file - it seems to work OK in spite of there being a FIX( function. It seems to be clever enough to work out the distinction in usage. It also correctly prohibits me doing say "DIM FIX(23)" - (gives Error : Variable Name) but does allow "DIM FIX {AS whatever}" Question is - can I rely for now on this behaviour not changing? - and if so, does the distinction need documenting? Regards Phil Edited 2026-11-18 17:36 by flip |
||||||
May be of interest to some of us: There was sometimes the question what speed a certain USB device is running. The tool "USB device tree viewer" gives a lot of detailed information about the USB configuration on windows machines. There are also some useful actions you can perform on an USB port/device. It runs IMHO very reliable, you may give it a try. USB device tree viewer Edited 2026-11-18 17:35 by ville56 |
||||||
G'day, Peter, the dongle is reported as: USB2.0 (but 12 Mbit/s FullSpeed only) Ville56, thanks for the link, another very handy program Regards, Lyle. |
||||||
Just to confirm the tests you posted were on the firmware version in my post above on this thread? |
||||||
Lyle I've found a combo device and tested thoroughly. I can't make the firmware lock up in any way. I can only conclude that there is either an electrical or usb protocol problem in your environment - you have checked power? I'm going to release V7.00.00 based on the last version I posted above because there is nothing further I can do -sorry |
||||||
Peter, Fair enough, it is only a problem when the Gamepad is plugged in with the keyboard, I will try and use the BT version. The first test shown (TEST5) was conducted with the software posted (V7.00.00), the others shown where conducted with V7.00.00rc9 on a PC3, as they where done prior to you posting the later version. This was introduced in the changes between V6.03.02b1 and V6.03.02b2 and is possibly confined to RII wireless combo Keyboard / Trackpad. Testing the same hardware on V6.03.01 I cannot make it fault, power supply is 4.98V at the USB connectors. I now know the symptoms so can recognize when it happens. Thanks again for the whole PicoMite ecosystem Regards, Lyle. |
||||||
| The Back Shed's forum code is written, and hosted, in Australia. |