MicroPython Forum (Archive)

I am using an ESP32 on a WIPY 3.0.
When I try to use uasyncio module i get the following error:

Traceback (most recent call last):
File "main.py", line 80, in <module>
File "asyncio_priority.py", line 128, in run_forever
File "uasyncio/__init__.py", line 69, in wait
AttributeError: 'poll' object has no attribute 'ipoll'
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; WiPy with ESP32

Would anyone be able to explain this error please?

Funny thing. I got this error sometimes too with an ESP32 on loboris's fork. Have never tested main esp32 repo though..
On loboris fork the solution (so far) was to let micropython run only on one core.

Apart from that you should really build the firmware from current github, the version you are using is ancienct! You are running micropython v.1.8.6, the recent one is 1.9.3.
I guess in your case that's the problem.

Hi,
Thanks for the reply.
I am using the Pycom Firmware Upgrade tool and that is what it is telling me the latest software version is.
I will try and upgrade, but I am worried version 1.93 is not compliant with Wipy 3.0.

Seems like ipoll is not supported by WIPI 3.0, changing that to poll removes error, but software gets stuck in the wait method in _init_.py of uasyncio. Is there an up to date fork for uasyncio on Pycom WIPY 3.0 or should the latest one work with that too?

Can't help you with that, sorry :/
I don't have any Pycom Wipy devices.

donikuy wrote: ↑

Fri Mar 23, 2018 12:10 pm

...
I am using an ESP32 on a WIPY 3.0.
When I try to use uasyncio module i get the following error:

Traceback (most recent call last):
File "main.py", line 80, in <module>
File "asyncio_priority.py", line 128, in run_forever
File "uasyncio/__init__.py", line 69, in wait
AttributeError: 'poll' object has no attribute 'ipoll'
MicroPython v1.8.6-849-83e2f7f on 2018-03-19; WiPy with ESP32
...

I see you're using my micropython-async library. If you're using the current code, this is dependent on uasyncio V2 which, as stated in the docs, requires MicroPython firmware dated 22nd Feb 2018 or later. I'm not familiar with the PyCom codebase but if this has not been synchronised to a recent build you may want to take it up with PyCom.

Hi Peter,

Thank you. I will get in touch with them.