Deploying release throws unhandled exception on FiPy device
-
I created a zip file of simple RGB led blinker test software, created a release for it and tried to deploy it through Pybytes. As soon as deployment is initiated in web interface, device will throw an unhandled exception. I tried this multiple times.
Interestingly I did try OTA firmware update in device section, and that completed successfully.
What could be the issue here? Unhandled exception doesn't seem correct, so this feels like a bug in the firmware.
Firmware: 1.20.2.r2 Pybytes: 1.6.1 Initialized watchdog for WiFi and LTE connection with timeout 1260000 ms LTE connection established connect_lte with start_mqtt is now removed please call communication_protocol or start_mqtt directly Connected to MQTT mqtt.pybytes.pycom.io Pybytes connected successfully (using the built-in pybytes library) Pybytes configuration read from /flash/pybytes_config.json Pycom MicroPython 1.20.2.r2 [v1.11-3a7776d] on 2020-11-23; FiPy with ESP32 Pybytes Version: 1.6.1 Type "help()" for more information. >>> Unhandled exception in thread started by <bound_method> Traceback (most recent call last): File "_msg_handl.py", line 259, in _io_thread_func File "_msg_handl.py", line 197, in _receive_packet File "_mqtt_core.py", line 398, in _recv_callback File "_mqtt_core.py", line 368, in _parse_publish File "_mqtt_core.py", line 341, in _notify_message File "_mqtt.py", line 91, in set_callback File "_pybytes_protocol.py", line 184, in __process_recv_message File "_pybytes_protocol.py", line 833, in deploy_new_release File "_pybytes_protocol.py", line 718, in update_files File "_flash_control_OTA.py", line 42, in update_file_content OSError: [Errno 19] ENODEV -
Hi,
Sorry I must have missed your topic last week,
The ENODEV error occurs when the device is not available, for example like this:>>> open('/sd/file.py','w') Traceback (most recent call last): File "<stdin>", line 1, in <module> OSError: [Errno 19] ENODEV >>> open('/flash/file.py','w') <io.TextIOWrapper 3f94f010> >>> open('/lib/file.py','w')Which is basically the operation where it stops working.
When I try to write a file to the SD card or lib folder on root, which is not there, it will return the error. Similarly,>>>open('/flash/lib/file.py', 'w') Traceback (most recent call last): File "<stdin>", line 1, in <module> OSError: [Errno 2] ENOENTWill give the error for NO ENTRY, as I did not create the lib folder in
/flash/
You are probably supposed to put the files inside a flash or lib folder? Check the pymakr online interface to see if it is correct. Let me know!Gijs
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login