Whenever trying to update Updating XRPLib… It gets stuck at 64% and will sit there for 20 minutes doing absolutely nothing. Please someone tell me what I can do to get this fixed.
Thank you for reporting this. We have not seen the update hanging in this way. Can you provide some more information?
What type of computer are you running, and what browser?
I am using desktop and I’ve tried chrome browser because this is my second XRP robot and chrome worked fine for my last one. This one though is not even letting me use it though due to it needing the first update after building it.
In Chrome before you attached the XRP, can you go to the three dot menu at the upper right and under “More tools” select “Developer tools” That will bring up a debugging window. Make sure at the top of that window to select the “console” tab. Then go ahead an connect your XRP and let it start updating. When it gets to the 64% it is probably producing an exception. If you can send a screen shot of that exception, that will help us identify the problem.
@Fgrossman I just experienced this as well, got stuck at both 34% and 64%. Using a bare Pico W (Edit - and an XRP Control Board) that I nuked the flash, then uploaded the version of MicroPython that the XRP ships with (1.19). Using Chrome on Windows 10, nothing shows up in the Console:
Edit - should also note that I had very recently clear all site data of XRPCode from Chrome.
Tried refreshing a few times; it usually got stuck at 34%, but it did freeze at 64% once.
I refreshed and ignored both the XRPLib and MicroPython updates, and I saw some files did get uploaded. Here’s what it looked like when getting stuck at 34%:
And when it got stuck at 64%:
I refreshed again and skipped the XRPLib update, but performed the MicroPython update to v1.20. That finished successfully, after which it prompted to update XRPLib again, and then that succeeded. Maybe this is somehow an issue with the MicroPython version? Would it make sense to instead have XRPCode prompt the user to update MicroPython first? That might also help if/when we change to flashing .mpy files (they usually have to be compiled for each version of MicroPython).
@DesteryArnold102 If you’re still having trouble, can you please try skipping the XRPLib update when prompted, and perform the MicroPython update that follows? If that succeeds, then see if it will update XRPLib properly afterwards. Please let us know what you find, thanks!
Our robotics non-profit just got 6 of the XRP kits in. We too are having all kinds of issues with these initial updates. So far we’ve tested on Mac, Windows 11 and ChromeOS. All had issues, the Mac so far being the hardest. Were evaluating these for a robotics bootcamp…
I just updated another one via ChromeOS. When skipping the initial XRPLib update, then doing the Micropython update, and finally going back and letting it do the XRPLib update seems to be the “workaround”.
1 Like
Skipping the initial XRP update and doing the Icropython update first worked for me as well on Windows 10.
I was having the exact same issue, and the suggestion to update Micropython first, then XRPLib solved it for me. Thank you all!
I finally found a board / computer that I can reliably reproduce it and be able to debug the problem. It is a timing problem that we will fix. But, we will also make a release shortly that reverses the order and updates the MicroPython before the XRPLib.