I am using teensy 4.1 latest version with 2.3.3
Arduino is getting stuck and showing this message:
Downloading index: package_teensy_0.60.3_index.json
this showed up when i attempted to upload a program to the teensy 4.1. When I close and restart Arduino it comes up wend restarted. This happened before and i had to uninstall and reinstall Arduino in order to make it work again.
additional information - boards manager was empty of all boards. After several restarts the error cleared.
If you have serial monitor open, close it. This is the usual solution to a bug that was introduced in Ide 2.3.3.
The download of the index files needs to complete before the board manager will show what is installed.
The teensy index takes long to be retrieved for inknown reason; possibly a slowish server or slowish connection from the server to the web.
Thank you. BTW - When the serial monitor is closed, does it actually close the open comm port? I have had issues using realterm on the teensy port while arduino is open after closing serial monitor. It says port is in use and I have to completely close Arduino IDE.
It should. But one never knows. Maybe it's a little (or lot) delayed causing the problem with the 3rd party terminal program.
I haven't experienced that issue but I only use AVR boards.
What procedure did you use to "close" Serial Monitor? If you click the X icon on the "Serial Monitor" tab, then it definitely should close the port:
However, Arduino IDE has some other mechanisms that will hide the panel that is the container for the Serial Monitor view. Doing this might be interpreted by the user as "closing" Serial Monitor, when in fact it remains running even though it is not visible.
Were you using Serial Plotter? There is a bug in the plotter that causes it to leave the port open even after you close the plotter window.
Yes i believe i closed it with the x on the tab but not 100% sure. not using the serial plotter.
Ok I think I figured it out, I had more than once instance running. Even though serial monitor was not opened in the second instance and closed in the first it must have been holding on to the port.