I thought I'd make a subject for the Picomite, which runs on the Raspberry Pi Pico 1/2, which Granz, thanks btw, has shown me to, so here is everything I know, so far that is.
https://geoffg.net/picomite.html (https://geoffg.net/picomite.html)
The main information.
https://geoffg.net/Downloads/picomite/PicoMite_User_Manual.pdf (https://geoffg.net/Downloads/picomite/PicoMite_User_Manual.pdf)
User's manual by itself.
https://geoffg.net/Downloads/picomite/PicoMite_Firmware.zip (https://geoffg.net/Downloads/picomite/PicoMite_Firmware.zip)
Firmware and user's manual D/L.
https://mmbasic.com/ (https://mmbasic.com/)
MMBasic.
https://mmbasic.com/Download/MMBasic%20Language%20Manual.pdf (https://mmbasic.com/Download/MMBasic%20Language%20Manual.pdf)
MM Basic Language Manual
https://teratermproject.github.io/index-en.html (https://teratermproject.github.io/index-en.html)
Tera Term for Windows, for editing the programs and updating firmware or another Virtual Terminal Emulator program.
It appears as if this is programmed VERY similar to the Basic Stamp chips, if there's anything I've missed, feel free to add it or, I will as I check this out.
Interesting..... it seams as if the editor for Picomite is on the chip itself and just run in the terminal, not to mention different settings like to autorun or not. Theres also its pretty much like P Basic, and has some stuff in common, not to mention different versions i think. Like I said interesting.
Quote from: JKnightandKARR on Mar 06, 2025, 09:37 AMInteresting..... it seams as if the editor for Picomite is on the chip itself and just run in the terminal...
Yes, just remember that in order to write an actual program, you need to enter that editor (just type "edit" at the command prompt.) I forgot that, and was trying to type in a program at the command prompt - didn't work. ::) Anyway, once I remembered that, the programing started working right. 8)
Quote from: granz on Mar 06, 2025, 05:09 PMQuote from: JKnightandKARR on Mar 06, 2025, 09:37 AMInteresting..... it seams as if the editor for Picomite is on the chip itself and just run in the terminal...
Yes, just remember that in order to write an actual program, you need to enter that editor (just type "edit" at the command prompt.) I forgot that, and was trying to type in a program at the command prompt - didn't work. ::) Anyway, once I remembered that, the programing started working right. 8)
Yeah, I saw that. Quite an oddball one, but whatever works. lol
I think I might design a development board for the Pico, maybe something similar to the PDB n PPDB. Think there'd be interest? I saw 2 diff ones on Amazon, but nothing really impressive.
Quote from: JKnightandKARR on Mar 09, 2025, 10:54 AMI think I might design a development board for the Pico, maybe something similar to the PDB n PPDB. Think there'd be interest? I saw 2 diff ones on Amazon, but nothing really impressive.
I's have to see links to all three items to make a comparison / give a useful answer.
Quote from: Chris Savage on Mar 09, 2025, 07:57 PMQuote from: JKnightandKARR on Mar 09, 2025, 10:54 AMI think I might design a development board for the Pico, maybe something similar to the PDB n PPDB. Think there'd be interest? I saw 2 diff ones on Amazon, but nothing really impressive.
I's have to see links to all three items to make a comparison / give a useful answer.
These are all I could locate.
Version 1 (https://www.amazon.com/GeeekPi-Raspberry-BreadBoard-Half-Size-Breadboard/dp/B093GXJ64J/ref=pd_ci_mcx_mh_mcx_views_2_image?pd_rd_w=2uncM&content-id=amzn1.sym.bb21fc54-1dd8-448e-92bb-2ddce187f4ac%3Aamzn1.symc.40e6a10e-cbc4-4fa5-81e3-4435ff64d03b&pf_rd_p=bb21fc54-1dd8-448e-92bb-2ddce187f4ac&pf_rd_r=3CQHB82SP5SR3P58F92F&pd_rd_wg=v1JdP&pd_rd_r=0df32120-6e5b-4091-b0a3-fe74ca9df52d&pd_rd_i=B093GXJ64J)
Version 2 (https://www.amazon.com/dp/B0C98G37PW/ref=sspa_dk_hqp_detail_aax_0?psc=1&sp_csd=d2lkZ2V0TmFtZT1zcF9ocXBfc2hhcmVk)
Quote from: granz on Mar 06, 2025, 05:09 PMQuote from: JKnightandKARR on Mar 06, 2025, 09:37 AMInteresting..... it seams as if the editor for Picomite is on the chip itself and just run in the terminal...
Yes, just remember that in order to write an actual program, you need to enter that editor (just type "edit" at the command prompt.) I forgot that, and was trying to type in a program at the command prompt - didn't work. ::) Anyway, once I remembered that, the programing started working right. 8)
Ok, I has an issue. I did the tests the manual shows, even the Edit, made the demo program with option autorun on, and while it worked when i unplugged and plugged back in, it worked, I am unable to enter text anymore to edit the program or do anything else.... suggestions??
Quote from: JKnightandKARR on Mar 10, 2025, 03:31 AMOk, I has an issue. I did the tests the manual shows, even the Edit, made the demo program with option autorun on, and while it worked when i unplugged and plugged back in, it worked, I am unable to enter text anymore to edit the program or do anything else.... suggestions??
When you set up the autorun, it will start running that program every time that you boot (turn on) the Pico (including when you plug it into a computer's USB port. What you need to do is to plug it in to your computer, then establish a connection (screen, hyperterminal, etc.) and send it a CTRL-C to break out of the autorunning program. That should put it back to the command prompt, where you can edit the program.
Quote from: JKnightandKARR on Mar 10, 2025, 12:45 AMThese are all I could locate.
Version 1 (https://www.amazon.com/GeeekPi-Raspberry-BreadBoard-Half-Size-Breadboard/dp/B093GXJ64J/ref=pd_ci_mcx_mh_mcx_views_2_image?pd_rd_w=2uncM&content-id=amzn1.sym.bb21fc54-1dd8-448e-92bb-2ddce187f4ac%3Aamzn1.symc.40e6a10e-cbc4-4fa5-81e3-4435ff64d03b&pf_rd_p=bb21fc54-1dd8-448e-92bb-2ddce187f4ac&pf_rd_r=3CQHB82SP5SR3P58F92F&pd_rd_wg=v1JdP&pd_rd_r=0df32120-6e5b-4091-b0a3-fe74ca9df52d&pd_rd_i=B093GXJ64J)
Version 2 (https://www.amazon.com/dp/B0C98G37PW/ref=sspa_dk_hqp_detail_aax_0?psc=1&sp_csd=d2lkZ2V0TmFtZT1zcF9ocXBfc2hhcmVk)
I have the second one. It works, but the LCD uses a controller chip which PicoMite BASIC does not recognize. PicoMite does have a close match, but I have not tried that yet. In addition, PicoMite allows you to create your own LCD driver, which I have also not gotten around to trying. The only other issue with this is that the joystick is so small that it is difficult to work with any accuracy.
PM me your address, and I will ship it out to you (Joe, or Chris.)
Quote from: JKnightandKARR on Mar 10, 2025, 12:45 AMThese are all I could locate.
Yeah, neither of those options offers a very robust development platform, though I was surprised at how much comes in this similar kit (https://a.co/d/7apHEqe).
Quote from: granz on Mar 10, 2025, 07:42 AMPM me your address, and I will ship it out to you (Joe, or Chris.)
Sounds like Joe is currently working on this. ;) I'm still involved in my new project based on Arduino Nano.
Quote from: Chris Savage on Mar 10, 2025, 08:32 AMQuote from: JKnightandKARR on Mar 10, 2025, 12:45 AMThese are all I could locate.
Yeah, neither of those options offers a very robust development platform, though I was surprised at how much comes in this similar kit (https://a.co/d/7apHEqe).
Thats like whatbi found only with added parts, NICE! The only other thing I found was developement kits that looked like parts could be cut away from the board amd wired up with cables, or left connected. Like this. (https://a.co/d/3oZBy0u) No, I'm not already working on it, was a recent idea to make a decent one like the PPDB.
Quote from: granz on Mar 10, 2025, 07:42 AMQuote from: JKnightandKARR on Mar 10, 2025, 12:45 AMThese are all I could locate.
Version 1 (https://www.amazon.com/GeeekPi-Raspberry-BreadBoard-Half-Size-Breadboard/dp/B093GXJ64J/ref=pd_ci_mcx_mh_mcx_views_2_image?pd_rd_w=2uncM&content-id=amzn1.sym.bb21fc54-1dd8-448e-92bb-2ddce187f4ac%3Aamzn1.symc.40e6a10e-cbc4-4fa5-81e3-4435ff64d03b&pf_rd_p=bb21fc54-1dd8-448e-92bb-2ddce187f4ac&pf_rd_r=3CQHB82SP5SR3P58F92F&pd_rd_wg=v1JdP&pd_rd_r=0df32120-6e5b-4091-b0a3-fe74ca9df52d&pd_rd_i=B093GXJ64J)
Version 2 (https://www.amazon.com/dp/B0C98G37PW/ref=sspa_dk_hqp_detail_aax_0?psc=1&sp_csd=d2lkZ2V0TmFtZT1zcF9ocXBfc2hhcmVk)
I have the second one. It works, but the LCD uses a controller chip which PicoMite BASIC does not recognize. PicoMite does have a close match, but I have not tried that yet. In addition, PicoMite allows you to create your own LCD driver, which I have also not gotten around to trying. The only other issue with this is that the joystick is so small that it is difficult to work with any accuracy.
PM me your address, and I will ship it out to you (Joe, or Chris.)
Cool, thanks bud! Will send after work. I have 2 Pico H's, only 1 with PicoMite installed. Ok will try Ctrl+C. Wasn't sure what was the problem. Thanks.
Quote from: granz on Mar 10, 2025, 07:37 AMQuote from: JKnightandKARR on Mar 10, 2025, 03:31 AMOk, I has an issue. I did the tests the manual shows, even the Edit, made the demo program with option autorun on, and while it worked when i unplugged and plugged back in, it worked, I am unable to enter text anymore to edit the program or do anything else.... suggestions??
When you set up the autorun, it will start running that program every time that you boot (turn on) the Pico (including when you plug it into a computer's USB port. What you need to do is to plug it in to your computer, then establish a connection (screen, hyperterminal, etc.) and send it a CTRL-C to break out of the autorunning program. That should put it back to the command prompt, where you can edit the program.
Yup, that did it. Thanks! Though playing with the Pause command didn't seam todo anything.... If what I read was right Pause 1000 = 1 second. I changed it to various values inc 1, 10, 100, 1000 & 10000 and nothing changed on the blinking rate. Did I do something wrong?? PM sent btw.
Edit, I think I know the issue.... I was using the only option at this moment GP0 for the built in LED...
Quote from: JKnightandKARR on Mar 10, 2025, 11:24 PMYup, that did it. Thanks! Though playing with the Pause command didn't seam todo anything.... If what I read was right Pause 1000 = 1 second. I changed it to various values inc 1, 10, 100, 1000 & 10000 and nothing changed on the blinking rate. Did I do something wrong?? PM sent btw.
Edit, I think I know the issue.... I was using the only option at this moment GP0 for the built in LED...
Which Pico are you using, Pico or Pico W?
The Pico has the built-in heartbeat LED at GP25, not GP0 (unless you are talking about an external LED, rather than the built-in one.) If you are using the Pico W, the heartbeat LED is not attached to a GPIO pin, the heartbeat is turned on, or off, by the OPTION HEARTBEAT ON/OFF statements.
Quote from: granz on Mar 11, 2025, 06:48 AMQuote from: JKnightandKARR on Mar 10, 2025, 11:24 PMYup, that did it. Thanks! Though playing with the Pause command didn't seam todo anything.... If what I read was right Pause 1000 = 1 second. I changed it to various values inc 1, 10, 100, 1000 & 10000 and nothing changed on the blinking rate. Did I do something wrong?? PM sent btw.
Edit, I think I know the issue.... I was using the only option at this moment GP0 for the built in LED...
Which Pico are you using, Pico or Pico W?
The Pico has the built-in heartbeat LED at GP25, not GP0 (unless you are talking about an external LED, rather than the built-in one.) If you are using the Pico W, the heartbeat LED is not attached to a GPIO pin, the heartbeat is turned on, or off, by the OPTION HEARTBEAT ON/OFF statements.
Its Pico H is whats printed, the first info i got said 0 not 25, so guess that info is wrong. Which would explain it. Lol
Quote from: granz on Mar 11, 2025, 06:48 AMQuote from: JKnightandKARR on Mar 10, 2025, 11:24 PMYup, that did it. Thanks! Though playing with the Pause command didn't seam todo anything.... If what I read was right Pause 1000 = 1 second. I changed it to various values inc 1, 10, 100, 1000 & 10000 and nothing changed on the blinking rate. Did I do something wrong?? PM sent btw.
Edit, I think I know the issue.... I was using the only option at this moment GP0 for the built in LED...
Which Pico are you using, Pico or Pico W?
The Pico has the built-in heartbeat LED at GP25, not GP0 (unless you are talking about an external LED, rather than the built-in one.) If you are using the Pico W, the heartbeat LED is not attached to a GPIO pin, the heartbeat is turned on, or off, by the OPTION HEARTBEAT ON/OFF statements.
Yeah, as I thought the info I found was wrong. Using the Heartbeat command shut it off on GP25 and now I can use that as an example till I get something else to use with it. I guess I could shove it in my PPDB with a custom designed pin adapter to sock it in place of the Peopeller IC, since I can't program this board, USB port got ripped off, ext programmer rigged up needed.
However on a side note. The manual on Pg 9, says "SETPIN 32, DOUT" and SETPIN GP27, DOUT" refer to the same pin and operate the same. I can see this as VERY confusing, so maybe just do one or the other and keep it simple. Also noticed there isn't any GP23, GP24 or GP25, physical pins, but are Ref to other built in functions that aren't used the same way as the other pins.
Quote from: JKnightandKARR on Mar 11, 2025, 10:01 AMIts Pico H is whats printed, the first info i got said 0 not 25, so guess that info is wrong. Which would explain it. Lol
The "H" suffix refers to the addition of male header pins on the board. That can be on the Pico H, or the Pico WH; those two already have the male headers soldered to the boards - at an additional ~$1 (which is why I recommend those options, unless you need female headers, or something else.)
Quote from: JKnightandKARR on Mar 11, 2025, 12:27 PMHowever on a side note. The manual on Pg 9, says "SETPIN 32, DOUT" and SETPIN GP27, DOUT" refer to the same pin and operate the same. I can see this as VERY confusing, so maybe just do one or the other and keep it simple.
That is so that you can use the named GPIO pins, or the equivalent pin numbers on the DIP board itself. Yes, it can be a bit confusing - I tend to use the GP pin numbers, but it's not too hard to convert, if someone else uses the opposite nomenclature.
Quote from: JKnightandKARR on Mar 11, 2025, 12:27 PMAlso noticed there isn't any GP23, GP24 or GP25, physical pins, but are Ref to other built in functions that aren't used the same way as the other pins.
That is explained on the next page (page 10.) Those pins are used for internal functions for the microcontroller board.
Quote from: granz on Mar 11, 2025, 03:34 PMQuote from: JKnightandKARR on Mar 11, 2025, 10:01 AMIts Pico H is whats printed, the first info i got said 0 not 25, so guess that info is wrong. Which would explain it. Lol
The "H" suffix refers to the addition of male header pins on the board. That can be on the Pico H, or the Pico WH; those two already have the male headers soldered to the boards - at an additional ~$1 (which is why I recommend those options, unless you need female headers, or something else.)
Got ya, makes sence, the wifi ver could make interesing projects.
Quote from: granz on Mar 11, 2025, 03:40 PMQuote from: JKnightandKARR on Mar 11, 2025, 12:27 PMHowever on a side note. The manual on Pg 9, says "SETPIN 32, DOUT" and SETPIN GP27, DOUT" refer to the same pin and operate the same. I can see this as VERY confusing, so maybe just do one or the other and keep it simple.
That is so that you can use the named GPIO pins, or the equivalent pin numbers on the DIP board itself. Yes, it can be a bit confusing - I tend to use the GP pin numbers, but it's not too hard to convert, if someone else uses the opposite nomenclature.
Quote from: JKnightandKARR on Mar 11, 2025, 12:27 PMAlso noticed there isn't any GP23, GP24 or GP25, physical pins, but are Ref to other built in functions that aren't used the same way as the other pins.
I'll just stick to the GP##, keep it simple.
That is explained on the next page (page 10.) Those pins are used for internal functions for the microcontroller board.
I saw that, not sure they'll be much use to me, but never know.
Ok...... got ANY IDEA WHATSOEVER on HOW in the heck you use the Device WS2812 command???????? I've used EVERY idea on stuff I find, all I get is errors..... Expression syntax stuff...
The WS28xx usage is described on page 43 of the manual (ver 5.08). The trick is to know that the WS28xx series takes three 8-bit numbers (for red, green and blue - and white if it is an RGBW LED.) PicoMite BASIC includes codes for those numbers, as RGB(xxxx) - like RGB(red) for red. This is shown in the example on that page, but the list is given on page 54, second paragraph. These are just the main colors, but you can use numbers (from H000000 through &HFFFFFF - or &HFFFFFFFF for LEDs with white,) to create your own colors also; see page 94 of the manual.
If you are using the LED on that GeeekPi board, then you would use 1 for the nbr parameter (since it is a single LED, and not a string.) So on that board, to turn the WS2812 LED red, you would use:
DEVICE WS2812 O, GP12, 1, RGB(red)
or you could use:
DEVICE WS2812 O, GP12, 1, &HFF0000
The hex number is all on (FF) for the red, and all off (00) for the green and blue.
The hex numbers that you would send out would be in the format: &Hrrggbb - where each pair is a number between &H00 and &HFF (or 0 through 255) for that color (i.e. rr is the intensity of red, gg is the intensity of green and bb is the intensity of blue.)
If you were to use a string of those WS2812 LEDs, you would need to set up an array of 24-bit numbers. You would need one 24-bit number in each element of that array. The example on page 43 of the manual shows code for a string of five WS2812 LEDs, and how you would set up the array B% (the dimension command in the example sets up the array, and then fills it with 24-bit numbers for red, green, blue, yellow and cyan) on the first line. On the second line the example sets up pin GP5 (the pin which has the LED string attached) as an output. Then on the third line, the Pico sends out the numbers to light up the string of LEDs with the colors defined in the array in the first line of the example.
The real trick of PicoMite BASIC is to get the really get to know the manual. I just enjoy reading through the manual, and then try out each new thing that I come across.
Quote from: granz on Mar 15, 2025, 06:55 AMThe WS28xx usage is described on page 43 of the manual (ver 5.08). The trick is to know that the WS28xx series takes three 8-bit numbers (for red, green and blue - and white if it is an RGBW LED.) PicoMite BASIC includes codes for those numbers, as RGB(xxxx) - like RGB(red) for red. This is shown in the example on that page, but the list is given on page 54, second paragraph. These are just the main colors, but you can use numbers (from H000000 through &HFFFFFF - or &HFFFFFFFF for LEDs with white,) to create your own colors also; see page 94 of the manual.
If you are using the LED on that GeeekPi board, then you would use 1 for the nbr parameter (since it is a single LED, and not a string.) So on that board, to turn the WS2812 LED red, you would use:
DEVICE WS2812 O, GP12, 1, RGB(red)
or you could use:
DEVICE WS2812 O, GP12, 1, &HFF0000
The hex number is all on (FF) for the red, and all off (00) for the green and blue.
The hex numbers that you would send out would be in the format: &Hrrggbb - where each pair is a number between &H00 and &HFF (or 0 through 255) for that color (i.e. rr is the intensity of red, gg is the intensity of green and bb is the intensity of blue.)
If you were to use a string of those WS2812 LEDs, you would need to set up an array of 24-bit numbers. You would need one 24-bit number in each element of that array. The example on page 43 of the manual shows code for a string of five WS2812 LEDs, and how you would set up the array B% (the dimension command in the example sets up the array, and then fills it with 24-bit numbers for red, green, blue, yellow and cyan) on the first line. On the second line the example sets up pin GP5 (the pin which has the LED string attached) as an output. Then on the third line, the Pico sends out the numbers to light up the string of LEDs with the colors defined in the array in the first line of the example.
The real trick of PicoMite BASIC is to get the really get to know the manual. I just enjoy reading through the manual, and then try out each new thing that I come across.
I actually tried DEVICE WS2812 O, GP12, 1, &HFF0000 last night from my laptop and didn't work, just got errors, but on my desktop it did work. Odd... I looked in all the manuals I had, and nothing I tried helped. Even did internet searches. I tried ALL diff ways, but RGB{color). nothing worked
Strange.
There is a Wiki page that I found which may help:
https://wiki.52pi.com/index.php?title=EP-0172
This is about that Geeek board, and you may find answers to other questions there (I have not really done more than glancing through it, though.)
Quote from: granz on Mar 15, 2025, 08:27 PMStrange.
There is a Wiki page that I found which may help:
https://wiki.52pi.com/index.php?title=EP-0172
This is about that Geeek board, and you may find answers to other questions there (I have not really done more than glancing through it, though.)
Tell me about it... Thanks, I'll keep that site for ref. I got the RGB led working now. Shifting between 6 diff colors now.
Quote from: JKnightandKARR on Mar 16, 2025, 04:31 PM...I got the RGB led working now. Shifting between 6 diff colors now.
Sweet smell of success. Yay! 8)
Quote from: granz on Mar 16, 2025, 08:43 PMQuote from: JKnightandKARR on Mar 16, 2025, 04:31 PM...I got the RGB led working now. Shifting between 6 diff colors now.
Sweet smell of success. Yay! 8)
If I wanted to play sound files, would I need an SD card or could file(s) be loaded on PicoMite?
Quote from: JKnightandKARR on Mar 18, 2025, 09:51 AMIf I wanted to play sound files, would I need an SD card or could file(s) be loaded on PicoMite?
Yes, you can play files uploaded to the onboard flash (page 35 of manual.) You can treat the flash as a disk using the Flash Filesystem (bottom of page 17 & top of 18.) To upload files (sound, picture, anything) you can use XModem (top of page 21.)
Like I said, get to know the manual. Spend a few hours just perusing the manual, or at least skim through it. That way you will have an idea if something can be done, then, when you need to know something use the search in your PDF reader (CTRL-F).
Cool, thanks!
I am getting close to trying basic on a pi pico, I was looking for a ready made picomite vga board to try some retro computing. This video was interesting and their board is just $12, I would find it hard to build one for less than that price
https://www.tindie.com/products/land_boards/raspberry-pi-pico-card-with-vga-sound-keyboard/
Are there any thoughts on this or a link to any alternatives.
I have had my eye on that for quite a while. Land Boards seems like a pretty cool company (and that is one of my favorite products from them.)
There is another version of that board; version 2 (https://www.tindie.com/products/land_boards/raspberry-pi-pico-card-with-vga-sound-kbd-ver-2/) that costs the same (note that the $12 is only for the bare board - you will need to pay for everything else) but has more external GPIO (from the MCP23017 Port Expanders.) Actually, the assembled price ($60) is pretty good, unless you have a very well stocked parts bin. Also, consider replacing the Pico with the Pico 2W - that is what I am doing with my PicoCalc.
Also, apparently some of the newer MCP23017s do not have all of their IO pins available for input (https://electronics.stackexchange.com/questions/661173/output-only-io-expander-question).
If you just want to try PicoMite BASIC, you can just put a Pico onto a breadboard, then load that BASIC onto the Pico and get a feel for the BASIC via the USB serial link (use minicom if using Linux, or Tera Term if you use Windows.) This will let you get familiar with the system, and is still a lot of fun. But, I still recommend a full system like that Land Board system that you found.
Thanks for the correction and feedback @granz , I have a bad habit of skimming the details sometimes. Still worth considering even the V 03 board is appealing.
I will definitely begin with a bare system connected over USB but I have a monitor just begging for a vga connected device 😁
Quote from: Jeff_T on May 28, 2025, 10:17 AMThanks for the correction and feedback @granz , I have a bad habit of skimming the details sometimes. Still worth considering even the V 03 board is appealing.
Yeah, like I said, that Land Boards seems to be pretty good. I also just found out that they are in Connelsville, which is pretty close to me. I will try to get in touch with them and invite them to our meetup - although, then I may go broke, buying their stuff. ;D
Quote from: Jeff_T on May 28, 2025, 10:17 AMI will definitely begin with a bare system connected over USB but I have a monitor just begging for a vga connected device 😁
Like I said, just plugging a Pico into a breadboard, and loading the PicoMite .UF2 firmware file, gives you a working system.
(https://files.granzeier.com/Downloads/SavageCircuits/SuperCap.jpg)
This is pretty much my first working with a Pico - except that I used a Pico, rather than this Pico 2W.Even without the super cap, it works pretty well. How are you for the basic components? If you want, I can send you a couple of my old component packs.
@granz
Quotealthough, then I may go broke, buying their stuff
that is too funny but I know the feeling.
QuoteI can send you a couple of my old component packs.
that is a kind offer, I don't keep a lot of parts laying around I just buy as needed and I am not sure where I am going next :-\
I read about a meet up in another post and I think it will be a lot of fun but I can't see it happening with me, this year anyway. I'm in TN btw.
I'll keep posting on the pico and basic stuff.
Ok, need help..... Playing with the Picomite on the Pico Breadboard Kit Plus Verion tonight, and I keep getting this:
[7] Option AUDIO 17, 0
Error : Invalid in a program
I've been up n down all the manuals for Picomite and the MMBasic ones, I can NOT find what's wrong... Whole code below, any help appreciated.
SetPin GP12, DOUT
SetPin GP13, DOUT
Dim a%=(RGB(Red))
Dim b%=(RGB(Green))
Dim c%=(RGB(Blue))
OPTION AUDIO GP13, GP13
Do
'Option Audio GP13, GP13
Device WS2812 O, GP12, 1, &Hff0000
Pause 500
Play TONE 697, 1209, 500
Device WS2812 O, GP12, 1, &Hffff00
Pause 500
Play TONE 770, 1336, 500
Device WS2812 O, GP12, 1, &H00ff00
Pause 500
Play TONE 852, 1477, 500
Device WS2812 O, GP12, 1, &H00ffff
Pause 500
Play TONE 941, 1336, 500
LoopAll I've done to the previous code was add the stuff to try n play the tones, which is pin GP13 on the board, the previous code, just to flash diff LED colors on the built in RGB LED, which works, but as far as the audio, NO IDEA what's wrong... I've commented out Option and it says, "Audio not enabled". Current ver of the system btw. Thanks.
Quote from: JKnightandKARR on Jan 26, 2026, 11:13 PMOk, need help..... Playing with the Picomite on the Pico Breadboard Kit Plus Verion tonight
Is this the board that you are using?
(https://productimages.microcenter.com/669708_608968_01_front_comping.jpg)
Quote from: JKnightandKARR on Jan 26, 2026, 11:13 PM, and I keep getting this:
[7] Option AUDIO 17, 0
Error : Invalid in a program
That won't work for your board (if it is the one above.) Pin 17 (GP13) is for the speaker, but there is no pin 0. As the manual says, it is best to stick with the GPxx nomenclature, rather than the pin number.
Quote from: JKnightandKARR on Jan 26, 2026, 11:13 PMI've been up n down all the manuals for Picomite and the MMBasic ones, I can NOT find what's wrong... Whole code below, any help appreciated.
SetPin GP12, DOUT
SetPin GP13, DOUT
Dim a%=(RGB(Red))
Dim b%=(RGB(Green))
Dim c%=(RGB(Blue))
OPTION AUDIO GP13, GP13
Do
'Option Audio GP13, GP13
Device WS2812 O, GP12, 1, &Hff0000
Pause 500
Play TONE 697, 1209, 500
Device WS2812 O, GP12, 1, &Hffff00
Pause 500
Play TONE 770, 1336, 500
Device WS2812 O, GP12, 1, &H00ff00
Pause 500
Play TONE 852, 1477, 500
Device WS2812 O, GP12, 1, &H00ffff
Pause 500
Play TONE 941, 1336, 500
LoopAll I've done to the previous code was add the stuff to try n play the tones, which is pin GP13 on the board, the previous code, just to flash diff LED colors on the built in RGB LED, which works, but as far as the audio, NO IDEA what's wrong... I've commented out Option and it says, "Audio not enabled". Current ver of the system btw. Thanks.
Sound from the PicoMite can be a bit complicated.
If you take a look at the OPTION AUDIO command (pg 48 of the 6.01.00 manual) you are to define the A and the B channels (or the left and the right channels) of a
single PWM port. On page 16, of the above version manual, you can see (on the outer-most labels, in brown) the PWM ports. You may use GP0 with,
and only with GP1 for PWM 1. For your board, you can use GP13 for the right channel, but
only with GP12, for the left channel.
In your
Option Audio GP13, GP13 you are trying to make GP13
both the left, and the right sound channels.
Try using OPTION AUDIO GP12, GP13 and then when you want to make sound, use
Play TONE 0, 1336, 500 specifying only a frequency for the right channel (channel B.) Now, that may/will cause some troubles with the WS2812 LED, since that is tied to GP12. It seems that, with that particular board, you may use either the speaker, or the WS2812, but not both at the same time.
I have seen similar design "errors" in other boards. That is one thing that I don't really care for with the Pico - not the Pico itself, but designers who ignore the pin restrictions of the PicoMite implementation of the Raspberry Pi Pico chip. PicoMite BASIC is a fantastic development environment, but some limitations make it more difficult to use - and I don't know if it is the language (from the little that I have seen, MicroPython does not have these restrictions) or the designs using the Pico chip ignoring PicoMite limitations.
Quote from: granz on Jan 27, 2026, 08:23 AMQuote from: JKnightandKARR on Jan 26, 2026, 11:13 PMOk, need help..... Playing with the Picomite on the Pico Breadboard Kit Plus Verion tonight
Is this the board that you are using?
(https://productimages.microcenter.com/669708_608968_01_front_comping.jpg)
Yes, that's the board.
Quote from: granz on Jan 27, 2026, 08:23 AMQuote from: JKnightandKARR on Jan 26, 2026, 11:13 PM, and I keep getting this:
[7] Option AUDIO 17, 0
Error : Invalid in a program
That won't work for your board (if it is the one above.) Pin 17 (GP13) is for the speaker, but there is no pin 0. As the manual says, it is best to stick with the GPxx nomenclature, rather than the pin number.
According to the manual(s), setting the OPTION AUDIO PG13, 0, which I also tried, 0 sets the 2nd pin to disable, but I also removed it and just had OPTION AUDIO GP!3, all yield the same error message.
Quote from: granz on Jan 27, 2026, 08:23 AMQuote from: JKnightandKARR on Jan 26, 2026, 11:13 PMI've been up n down all the manuals for Picomite and the MMBasic ones, I can NOT find what's wrong... Whole code below, any help appreciated.
SetPin GP12, DOUT
SetPin GP13, DOUT
Dim a%=(RGB(Red))
Dim b%=(RGB(Green))
Dim c%=(RGB(Blue))
OPTION AUDIO GP13, GP13
Do
'Option Audio GP13, GP13
Device WS2812 O, GP12, 1, &Hff0000
Pause 500
Play TONE 697, 1209, 500
Device WS2812 O, GP12, 1, &Hffff00
Pause 500
Play TONE 770, 1336, 500
Device WS2812 O, GP12, 1, &H00ff00
Pause 500
Play TONE 852, 1477, 500
Device WS2812 O, GP12, 1, &H00ffff
Pause 500
Play TONE 941, 1336, 500
LoopAll I've done to the previous code was add the stuff to try n play the tones, which is pin GP13 on the board, the previous code, just to flash diff LED colors on the built in RGB LED, which works, but as far as the audio, NO IDEA what's wrong... I've commented out Option and it says, "Audio not enabled". Current ver of the system btw. Thanks.
Sound from the PicoMite can be a bit complicated.
If you take a look at the OPTION AUDIO command (pg 48 of the 6.01.00 manual) you are to define the A and the B channels (or the left and the right channels) of a single PWM port. On page 16, of the above version manual, you can see (on the outer-most labels, in brown) the PWM ports. You may use GP0 with, and only with GP1 for PWM 1. For your board, you can use GP13 for the right channel, but only with GP12, for the left channel.
In your Option Audio GP13, GP13 you are trying to make GP13 both the left, and the right sound channels.
Try using OPTION AUDIO GP12, GP13 and then when you want to make sound, use Play TONE 0, 1336, 500 specifying only a frequency for the right channel (channel B.) Now, that may/will cause some troubles with the WS2812 LED, since that is tied to GP12. It seems that, with that particular board, you may use either the speaker, or the WS2812, but not both at the same time.
I have seen similar design "errors" in other boards. That is one thing that I don't really care for with the Pico - not the Pico itself, but designers who ignore the pin restrictions of the PicoMite implementation of the Raspberry Pi Pico chip. PicoMite BASIC is a fantastic development environment, but some limitations make it more difficult to use - and I don't know if it is the language (from the little that I have seen, MicroPython does not have these restrictions) or the designs using the Pico chip ignoring PicoMite limitations.
Ok, I can try that. Why would they make restrictions, I wonder?? So it's the Picomite firmware that has these restrictions?? I can always consider MicroPython an option, I guess.
EDIT:I made the mods as you suggested. SAME error still.... Even tried it with GP0 & GP1... no change...
Quote from: JKnightandKARR on Jan 27, 2026, 08:44 AMAccording to the manual(s), setting the OPTION AUDIO PG13, 0, which I also tried, 0 sets the 2nd pin to disable, but I also removed it and just had OPTION AUDIO GP!3, all yield the same error message.
Where did you find that in the manual? The only thing that I can find about disabling audio is on page 99, in the 6.00.00 manual, where it talks about OPTION AUDIO DISABLE, but that is to disable audio entirely.
Quote from: JKnightandKARR on Jan 27, 2026, 08:44 AMOk, I can try that. Why would they make restrictions, I wonder?? So it's the Picomite firmware that has these restrictions?? I can always consider MicroPython an option, I guess.
I don't know that it is so much a PicoMite BASIC restriction, as fitting more in line with the hardware. The Raspberry Pi Foundation designed the Pico with the matching PWM channels, and PicoMite BASIC just follows that design. Like I said, I'm not overly familiar with Python (Micro-, or Circuit-) and do not know if they use special tricks to get around that, or...?
Did you see where I posted the changes you mentioned didn't work?
Quote from: granz on Jan 27, 2026, 08:55 AMQuote from: JKnightandKARR on Jan 27, 2026, 08:44 AMAccording to the manual(s), setting the OPTION AUDIO PG13, 0, which I also tried, 0 sets the 2nd pin to disable, but I also removed it and just had OPTION AUDIO GP!3, all yield the same error message.
Where did you find that in the manual? The only thing that I can find about disabling audio is on page 99, in the 6.00.00 manual, where it talks about OPTION AUDIO DISABLE, but that is to disable audio entirely.
Quote from: JKnightandKARR on Jan 27, 2026, 08:44 AMOk, I can try that. Why would they make restrictions, I wonder?? So it's the Picomite firmware that has these restrictions?? I can always consider MicroPython an option, I guess.
I don't know that it is so much a PicoMite BASIC restriction, as fitting more in line with the hardware. The Raspberry Pi Foundation designed the Pico with the matching PWM channels, and PicoMite BASIC just follows that design. Like I said, I'm not overly familiar with Python (Micro-, or Circuit-) and do not know if they use special tricks to get around that, or...?
It's mentioned here https://geoffg.net/WindowsMMBasic.html (https://geoffg.net/WindowsMMBasic.html)
but they are on this page: https://mmbasic.com/ (https://mmbasic.com/)
Here is the language manual: https://mmbasic.com/Download/MMBasic%20Language%20Manual.pdf (https://mmbasic.com/Download/MMBasic%20Language%20Manual.pdf)
and the other manual I found: https://mmbasic.com/Download/MMBasic%20DOS%20Version%20Manual.pdf (https://mmbasic.com/Download/MMBasic%20DOS%20Version%20Manual.pdf)
General downloads: https://mmbasic.com/downloads.html (https://mmbasic.com/downloads.html)
Solution below:
https://yamavu.github.io/PicoMite_User_Manual/options_audio.html (https://yamavu.github.io/PicoMite_User_Manual/options_audio.html)
I FINALLY found the issue.... One I didn't see in the documentation or is not there..... anyhow solution is:
Option Audio GP##, GP##
is run on the command prompt NOT in the program..... once set it apparently remains set, even if power is removed, to remove it, type Option Audio Disable. Now I gotta see if the pins are 5v or 3.3v and create a speaker circuit to use with this....
Quote from: JKnightandKARR on Jan 31, 2026, 12:39 AMSolution below:
https://yamavu.github.io/PicoMite_User_Manual/options_audio.html (https://yamavu.github.io/PicoMite_User_Manual/options_audio.html)
I FINALLY found the issue.... One I didn't see in the documentation or is not there..... anyhow solution is:
Option Audio GP##, GP##
is run on the command prompt NOT in the program..... once set it apparently remains set, even if power is removed, to remove it, type Option Audio Disable. Now I gotta see if the pins are 5v or 3.3v and create a speaker circuit to use with this....
So, are you able to use the single GP13, or do you need to use both channels in the one
OPTION command?
Quote from: granz on Jan 31, 2026, 07:12 AMQuote from: JKnightandKARR on Jan 31, 2026, 12:39 AMSolution below:
https://yamavu.github.io/PicoMite_User_Manual/options_audio.html (https://yamavu.github.io/PicoMite_User_Manual/options_audio.html)
I FINALLY found the issue.... One I didn't see in the documentation or is not there..... anyhow solution is:
Option Audio GP##, GP##
is run on the command prompt NOT in the program..... once set it apparently remains set, even if power is removed, to remove it, type Option Audio Disable. Now I gotta see if the pins are 5v or 3.3v and create a speaker circuit to use with this....
So, are you able to use the single GP13, or do you need to use both channels in the one OPTION command?
I can try that. Setting PWMA to 0 should disable that pin
Quote from: granz on Jan 31, 2026, 07:12 AMSo, are you able to use the single GP13, or do you need to use both channels in the one OPTION command?
Well, have a discovery, setting Option Audio PWM-A, PWM-B to anything other then something like Option Audio GP12, GP13 won't work, so stuff like Option Audio 0, GP13 or Option Audio GP13, 0 will NOT work. Ok, I did notice that there is added constant noise that starts when setting the audio up, and this is before I even get to Play Tone ##, ##, duration. Maybe need to use the filter on Pg 35 of the manual...
@Chris SavageI've got links to the PPDB and PDB, now I measured the Raspberry Pi Pico and got 3.3v on the output, now what I need is, how can I modify the audio amp on the PDB to work better on 3.3v , not to mention putting the 2 audio ch into 1 ch or should I try the circuit on the PPDB even though I am using an ext speaker? The Picomite manual, on pg 35 shows a low-passfilter, that shouldn't be an issue using SMD right off the pins, but its the amplifier I'll need some help with.
https://forums.parallax.com/uploads/FileUpload/53/fd27a771f96245b341cff1c4eb02e5.pdf (https://forums.parallax.com/uploads/FileUpload/53/fd27a771f96245b341cff1c4eb02e5.pdf)
https://forums.parallax.com/uploads/FileUpload/d1/6d174a41da887b2bbe09ce860bed6c.pdf (https://forums.parallax.com/uploads/FileUpload/d1/6d174a41da887b2bbe09ce860bed6c.pdf)
Picomite manual:
https://geoffg.net/Downloads/picomite/PicoMite_User_Manual.pdf (https://geoffg.net/Downloads/picomite/PicoMite_User_Manual.pdf)
Quote from: JKnightandKARR on Jan 31, 2026, 11:19 AMI've got links to the PPDB and PDB, now I measured the Raspberry Pi Pico and got 3.3v on the output, now what I need is, how can I modify the audio amp on the PDB to work better on 3.3v , not to mention putting the 2 audio ch into 1 ch or should I try the circuit on the PPDB even though I am using an ext speaker? The Picomite manual, on pg 35 shows a low-passfilter, that shouldn't be an issue using SMD right off the pins, but its the amplifier I'll need some help with.
Well, the amplifier on the PPDB is stereo. It is designed to use headphones.
I didn't find any filter circuit on page 35. In your last link, I did find one on page 49, for which the output could be connected to external stereo amplifier speaker systems, such as computer speakers, which can be obtained cheap, like these (https://irdrive.com/products/new-enjoy-beige-180w-amplified-multimedia-pc-speaker-system-model-ep-691).
Quote from: Chris Savage on Jan 31, 2026, 06:36 PMQuote from: JKnightandKARR on Jan 31, 2026, 11:19 AMI've got links to the PPDB and PDB, now I measured the Raspberry Pi Pico and got 3.3v on the output, now what I need is, how can I modify the audio amp on the PDB to work better on 3.3v , not to mention putting the 2 audio ch into 1 ch or should I try the circuit on the PPDB even though I am using an ext speaker? The Picomite manual, on pg 35 shows a low-passfilter, that shouldn't be an issue using SMD right off the pins, but its the amplifier I'll need some help with.
Well, the amplifier on the PPDB is stereo. It is designed to use headphones.
I didn't find any filter circuit on page 35. In your last link, I did find one on page 49, for which the output could be connected to external stereo amplifier speaker systems, such as computer speakers, which can be obtained cheap, like these (https://irdrive.com/products/new-enjoy-beige-180w-amplified-multimedia-pc-speaker-system-model-ep-691).
That's it, diff doc, so I might wanna download it so I got it... Anyhow, that shouldn't be hard on either todo, but I need a single speaker, for my voice display.
Quote from: JKnightandKARR on Jan 31, 2026, 07:27 PMThat's it, diff doc, so I might wanna download it so I got it... Anyhow, that shouldn't be hard on either todo, but I need a single speaker, for my voice display.
Well, you don't need to use both channels. You could minimize circuitry and ignore a whole channel. On Arduino projects, I have often used one channel, because some of the lesser expensive MP3 Player boards and amplifier boards only have one channel. In that case I can make a
mono MP3 and save space there as well.
Quote from: Chris Savage on Jan 31, 2026, 10:16 PMQuote from: JKnightandKARR on Jan 31, 2026, 07:27 PMThat's it, diff doc, so I might wanna download it so I got it... Anyhow, that shouldn't be hard on either todo, but I need a single speaker, for my voice display.
Well, you don't need to use both channels. You could minimize circuitry and ignore a whole channel. On Arduino projects, I have often used one channel, because some of the lesser expensive MP3 Player boards and amplifier boards only have one channel. In that case I can make a mono MP3 and save space there as well.
it's for DTMF tones, so I'll need both.
Quote from: JKnightandKARR on Jan 31, 2026, 10:28 PMit's for DTMF tones, so I'll need both.
Is this a limitation of the PicoMite? I'm asking because the lowly BASIC Stamp 2 can generate DTMF tones using a single I/O pin. Two channels aren't necessary to create a DTMF tone, unless the MCU is incapable of doing it without two channels.
At the same time, DTMF tones can be recorded and played back just like any other sound; again, with a single channel.
Quote from: Chris Savage on Jan 31, 2026, 10:50 PMQuote from: JKnightandKARR on Jan 31, 2026, 10:28 PMit's for DTMF tones, so I'll need both.
Is this a limitation of the PicoMite? I'm asking because the lowly BASIC Stamp 2 can generate DTMF tones using a single I/O pin. Two channels aren't necessary to create a DTMF tone, unless the MCU is incapable of doing it without two channels.
At the same time, DTMF tones can be recorded and played back just like any other sound; again, with a single channel.
Yes, it requires both ch to make 1 duel tone, and what I want todo is match the tones in the show and the timing and not have the extra background noise, such as engine, or what not. If it was just for me, I'd just use the BS2, sadly, it's something at some point I want to try and sell.
Quote from: JKnightandKARR on Jan 31, 2026, 11:56 PMYes, it requires both ch to make 1 duel tone, and what I want todo is match the tones in the show and the timing and not have the extra background noise, such as engine, or what not. If it was just for me, I'd just use the BS2, sadly, it's something at some point I want to try and sell.
I'll be honest, I'm shocked that's the case. Nonetheless, you can still mix two channels. In the schematic on page 49, remove one of the 22nF caps and tie the two outputs together after the 680Ω resistors on the right. I still think I would record the tones as WAV / MP3 files and play them back as samples, but that's just me.
Quote from: Chris Savage on Feb 01, 2026, 12:33 AMQuote from: JKnightandKARR on Jan 31, 2026, 11:56 PMYes, it requires both ch to make 1 duel tone, and what I want todo is match the tones in the show and the timing and not have the extra background noise, such as engine, or what not. If it was just for me, I'd just use the BS2, sadly, it's something at some point I want to try and sell.
I'll be honest, I'm shocked that's the case. Nonetheless, you can still mix two channels. In the schematic on page 49, remove one of the 22nF caps and tie the two outputs together after the 680Ω resistors on the right. I still think I would record the tones as WAV / MP3 files and play them back as samples, but that's just me.
I'll consider that, but I do have other buttons to hook up and might have them random DTMF tones, which I can just create a bus of somekind to connect to. Meantime, looks like the PDB used Op Amp I think and the chip on the PPDB is obsolete, but there are other similar options available. Haver to breakout my books from school on figuring out voltages on Op Amps. Thanks for the help.
Quote from: JKnightandKARR on Feb 01, 2026, 02:32 PMI'll consider that, but I do have other buttons to hook up and might have them random DTMF tones, which I can just create a bus of somekind to connect to. Meantime, looks like the PDB used Op Amp I think and the chip on the PPDB is obsolete, but there are other similar options available. Haver to breakout my books from school on figuring out voltages on Op Amps. Thanks for the help.
Well, if you use the schematic on page 49, you can simply run that output into an LM386 amplifier using the reference schematic in the datasheet.
Quote from: Chris Savage on Feb 01, 2026, 02:37 PMQuote from: JKnightandKARR on Feb 01, 2026, 02:32 PMI'll consider that, but I do have other buttons to hook up and might have them random DTMF tones, which I can just create a bus of somekind to connect to. Meantime, looks like the PDB used Op Amp I think and the chip on the PPDB is obsolete, but there are other similar options available. Haver to breakout my books from school on figuring out voltages on Op Amps. Thanks for the help.
Well, if you use the schematic on page 49, you can simply run that output into an LM386 amplifier using the reference schematic in the datasheet.
That shouldn't be too hard. I think you said before that the bs circuit needs optimized for 3.3 so that shouldn't be too hard.
Quote from: JKnightandKARR on Feb 02, 2026, 11:26 AMThat shouldn't be too hard. I think you said before that the bs circuit needs optimized for 3.3 so that shouldn't be too hard.
Actually, the supply voltage for the LM386 can be 4V–12V or 5V–18V, depending on the version of the IC. The supply voltage on this IC has nothing to do with the input voltage of the audio signal.
EDIT: Use the
reference schematic in the datasheet for the LM386,
not the schematic for the PPDB. The extra circuitry you need is already a part of the circuit on page 49 we talked about. Remember, the LM386 can be set between 20 and 200 gain.