os.uname() causes core dump using firmware 1.1.12b on fopy
-
os.uname() causes core dump using firmware 1.1.12b on fopy
-
@robert-hh thanks :)
-
@misterlisty It works, If you need just a specific element of it, like uos.uname()[0].
-
I have used the latest firmware upgrader, using pytrack and its says update successful, yet..the same issue is present. I have commented out my code that uses os.uname() until the next update..wasted enough time on this part.
-
@misterlisty
the latest version of the update-tool is: pycom_firmware_update_1.1.4.b1
if you use it, you will get the latest firmware-update. dont use older update-tools!
gz!
-
@misterlisty The problem is, that the fixed version and the old one have the same version number. I use to make my own build, so I do not know what is installed by the updater tool. Maybe it's still the old version. And there was a server trouble last night, impact unknown.
-
@robert-hh I'm confused..do i just run the firmware updater or do i have to download the firmware bin? I ran the firmware updater tool and it did the update..i assume it installs the latested without me having to select the firmware version?
-
@misterlisty The bug was fixed on 4th of January.
-
Pretty sure i have the latest... MicroPython v1.8.6-849-fcbbfe3 on 2018-01-03; FiPy with ESP32
-
@misterlisty That should have been fixed three days ago by an update with the same version number(!). So if you update the firmware now, it should be gone. I hope it did not reappear.
