@kids-taxi NOTE this is a python only procedure.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
Thanks Ron but ...
Still no port at Step 7
I appreciate all the help but I am giving up on the Pico and Arduino IDE combination. I'll try the micropython route but but in the end I am a hobbyist and all the projects I would like to do are nice to have but not essential. Most of what I have done is simply copying and pasting existing code from examples people have posted and filling in a few blanks to meet my specific needs. If I cannot get what I want that way then I can live without them. If it turns out to be too complicated then there are lots of other things to spend time on.
Again, thanks for your help and best of luck on your future projects.
Mike
Well that was painless and it worked. This seems to be the route to go for someone like me. Thanks again.
Sorry, I should be clear on the last post. The Thonny copy paste procedure offered by kids-taxi worked like a charm.
@nsshore Then you must not have followed the instructions EXACTLY. I have used the procedure on two boards. Once completed, they are no longer needed, this is a one time special procedure.
Good luck.
p.s. Since you will be using a language I am not trained in, please don't bother me with any further questions.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
Hi Ron,
Last night I downloaded the updated version of the Arduino IDE 2.0.3 the board file from Phil Hower is not present and the Arduino offering for Pico boards is only for Pico not Pico W and then of the two listed one is deprecated and the other not. The IDE recognizes the Pico but will not upload to it. Changing the board to PicoW the IDE will not recognize the change and still shows a Pico attached.
I also checked out my existing Arduino IDE 1.8.19, when I opened it up the update boards box opened up, I updated and after it provided me with the same options as for the new IDE.
As a side issue, whilst checking out the links last night I noticed that RPi have stated that the Pico will be in manufacture till at least 2028.
Non Sibi Sed Omnibus
@kids-taxi The board file comes form a different spot, it is
https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json
Yes, there are several other 2040 board entries, that chip is used to build many boards. OnlyPhil's is the right one for a PICO or PICOW however. I am usig the right now.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@kids-taxi I used arduino 1 IDE as it is easier to read, but both 1 and 2 share the same core libraries. I did a few searches, they are visible in the attached screen shots. Quite a bit to be learned from these. Use the boards from the github link above and you will be able to use the PICO and PICOW fine. YES there is a one time (unless you hold the boot button again) procedure to go through, but then it is the same as any arduino or ESP board. YES the WiFi version of the board killed the built in blinking LED. There is supposed to be some way to get it back but I have not looked into it yet.
YES, The Pi foundation is one of the few organizations that publishes how long their products will be at least manufactured, but could be supported for much longer. The PICOW will maybe be a bit longer? I hope this information clears up some questions you had, if not let me know.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@kids-taxi Here are my full boards spec for esp8266 and esp32 and PICO all those also contain similar related boards, the esp32 and PICO board lists are really long.
https://raw.githubusercontent.com/espressif/arduino-esp32/gh-pages/package_esp32_index.json
https://arduino.esp8266.com/stable/package_esp8266com_index.json
https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json
Attached are screenshots of what that looks like in IDE2. That github location above for PICO contains a wealth of information, I have yet to dig into much of it as my reading ability is severely impacted due to my brain issues.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
If you have previously gone through the procedure to put MicroPython on the Pico W, is there a way to "reset" it back to the configuration that allows you to use the Arduino IDE and C++?
SteveG
@codecage Ah, good question, I haven't watched the video yet but would assume
if Bill (@dronebot-workshop) shows us how to install the Python firmware he also shows us how to either re-install the standard firmware or how to have both installed at the same time. Maybe the board selection triggers the correct firmware to be used?
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
I believe I have discovered the answer, but before I experiment with what I have found, I'd rather have some positive feed back on how it is accomplished. I'm watching Bill's video again, but don't remember anything in his video about a reset back to using the Arduino IDE. And I'm pretty sure they can't coexist.
SteveG
@codecage I am only interested in python as an intellectual exercise since the idea of interpreted code and no access to the bare iron makes that language pretty much useless to me. I have looked at the language a bit and don't see a substantial difference from C. Almost ALL the modern languages are just derivatives of C, each with a small set of improvements and a set of disadvantageous. I will stick with C, it's not my favourite, but I can work with it. If I ever need some C++ I am sure this group will help me out, otherwise, I avoid it like the plague.
All that aside, please let us know if/when you find a way to change the firmware back and forth.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting