Page 1 of 1

Raspberry Pico connection problem

Posted: Mon Apr 26, 2021 6:15 pm
by matijaz74
Hi! I've been working on the Pico connection all day. First in Windows 10 in Thonny. Now in RaspberryOS also in Thonny. Let me error.

Code: Select all

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/thonny/workbench.py", line 1708, in event_generate
    handler(event)
  File "/usr/lib/python3/dist-packages/thonny/shell.py", line 433, in _handle_program_output
    self._update_visible_io(None)
  File "/usr/lib/python3/dist-packages/thonny/shell.py", line 512, in _update_visible_io
    self._apply_io_event(data, stream_name)
  File "/usr/lib/python3/dist-packages/thonny/shell.py", line 555, in _apply_io_event
    self.active_extra_tags.pop()
IndexError: pop from empty list
I connected the Raspberry Pico to the computer as described. You must first hold down the BOOTSEL key and then download the uf2 file. However, an error still occurs. :roll:
Thank you for your help and response.

Re: Raspberry Pico connection problem

Posted: Mon Apr 26, 2021 6:20 pm
by Roberthh
When you have downloaded the .uf2 file once, there is not need to do that again, unless you want to change tht firmware. What happens if you connect the device without pushing the bootsel button. Then it should be in normal operation mode.

Re: Raspberry Pico connection problem

Posted: Mon Apr 26, 2021 7:39 pm
by matijaz74
This occurs during normal startup. Then I installed a new uf2 file.
I also uploaded a new file rp2-pico-20210418-v1.15.uf2 but without success.
But I got on this page. https://www.micropython.org/download/rp2-pico/.
I don't know what else to do. :(
Thank you for your help and response.

Re: Raspberry Pico connection problem

Posted: Tue Apr 27, 2021 6:14 am
by Roberthh
To be sure, that the Pico works fine, try using a simple terminal emulator like Putty (Windows) or picocom (Raspi).

Re: Raspberry Pico connection problem

Posted: Tue Apr 27, 2021 7:57 am
by matijaz74
Great! I connected to the picocom and noticed that it was running in the second core of the program in the background. I stopped him. Now it works great through Thonny. Thanks!