![]() Self.endheaders(body, encode_chunked=encode_chunked)įile "C:\Program Files (x86)\Thonny\lib\http\client.py", line 1277, in endheaders Self._send_request(method, url, body, headers, encode_chunked)įile "C:\Program Files (x86)\Thonny\lib\http\client.py", line 1328, in _send_request H.request(req.get_method(), req.selector, req.data, headers,įile "C:\Program Files (x86)\Thonny\lib\http\client.py", line 1282, in request !uf2flashingdialog with geometry +367+233Ģ1:12:56.919 ERROR 2dialog: Could not download variants info from įile "C:\Program Files (x86)\Thonny\lib\urllib\request.py", line 1348, in do_open Yes, I'm attaching the contents of frontend.log file.ġ1:55:51.207 INFO thonny: Thonny version: 4.0.1 11:55:51.207 INFO thonny: cwd: C:\Program Files (x86)\Thonny 11:55:51.207 INFO thonny: original argv: 11:55:51.207 INFO thonny: sys.executable: C:\Program Files (x86)\Thonny\pythonw.exe 11:55:51.207 INFO thonny: sys.argv: 11:55:51.207 INFO thonny: sys.path: 11:55:51.207 INFO thonny: sys.flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=1, no_site=0, ignore_environment=1, verbose=0, bytes_warning=0, quiet=0, hash_randomization=1, isolated=1, dev_mode=False, utf8_mode=0, warn_default_encoding=0) 11:55:57.928 INFO thonny.shell: BaseShellText._on_backend_terminated If you definitely, desperately, do need to get a 'main.Could you please send me the error part (or whole content) from frontend.log (Tools => Open Thonny data folder)? If run on a Pico-W it might reformat the file system and lose everything. The file system is smaller, is located in a different place on the Pico-W than it is on the Pico. I have just realised that's not such a great idea on a Pico-W. Note that if using a Pico-W the on-board LED will not flash as described but it should have done its job. You will need to reinstall the Pico or Pico-W firmware after doing that but it should then allow access to the REPL and the old 'main.py' should appear as 'main-1.py'. You will lose the 'main.py' on the Pico so it is recommended to save a copy on your computer.Ī less drastic option is to download the firmware here - viewtopic.php?t=305432 - which will rename any 'main.py'. If the 'main.py' is stopping the REPL from being accessed you may have to nuke everything to gain access to the REPL. You should be able to save an updated 'main.py' over what already exists without nuking anything. I guess my main question is: Once I've put a main.py file on the Pico, do I really have to nuke it every time I want to update it? I've learned my lesson of saving my script on my computer as well as on the Pico. ![]() Am I right in saying the source file isn't actually saved on the Pico as Thonny seems to suggest? I don't seem to be able to connect to my Pico to find my script that was "saved" on it. The script I believe was only saved directly on the Pico and I can't find it on my computer. ![]() Now I'm back in Thonny trying to update my script. Script seems to be running fine but I need to update it. Wrote a script and finally saved it as main.py Pico somewhat seemed to be working properly after using a different USB hub. I used the nuke file and reinstalled the Pico W firmware. Thonny said there was new firmware to install, which I did. ![]() Initially I installed the Pico W firmware. A different hub seems to have solved this. I'm on MacOS and a USB hub was causing me issues with it "hanging". I've just got a Pico W and I'm not sure if it's working properly:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |