MicroPython Forum (Archive)

jmi2

While writing bug report i realized it works. As i see in my previous post, i have inconsistent version and firmware link ...probably i messed up a test boards. Seems it works again with 1.19.1 https://micropython.org/resources/firmware/esp8266-20220618-v1.19.1.bin Actually already with v1.11-8-g48d...

jmi2

i came back to micropython and tried to find FW, which works ... and came back also to this issue. I just found it crashes even with latest esp8266 fw v1.10-45-g67689bfd7 https://micropython.org/resources/firmware/esp8266-20220618-v1.19.1.bin but found a reason/"workaround" Difference is, if i do se...

jmi2

As uasyncio is pure python implementation as i know and hence believe, that there won't be any problem. I expect asyncio will make reference to self.run method, which must hold reference to context and hence to object instance itself. Hence there i don't see a problem. Problem is, when reference it ...

jmi2

Thanks Peter, after your message, i started to have feeling, that REPL is a problem. But after some more tests, i have a feeling, that problem is elsewhere. Actually I suspect, that there is problem with Timers, which are not reachable from user-code anymore and hence are subject for garbage collect...

jmi2

even simpler case, which is failing on Fatal exception 0(IllegalInstructionCause):

Code: Select all

from machine import Timer

def onTimer1(timer):
    print(str(123))

Timer(-1).init(period=10, mode=Timer.PERIODIC, callback=onTimer1)

Timer(-1).init(period=10000, mode=Timer.ONE_SHOT, callback=None)

jmi2

strage is, that error code (0 - IllegalInstructionCause or 9 -LoadStoreAlignmentCause) depends on presense on print command. from machine import Timer class MyClass(object): timer1 = Timer(-1) eventSeq = 0 def __init__(self): self.timer1.init(period=20, mode=Timer.PERIODIC, callback=self.onTimer) # ...

jmi2

problem with same code exists also on latest v1.10-45-g67689bfd7 on 2019-02-01;
and also on oldest avaiable: esp8266-20170108-v1.8.7.bin

jmi2

Hi, i tested on two boards so far. Came to this as more-less minimal code causing issues. It's not even using GPIO and NETWORK. Only timers and print function. There are inline comments telling, what changes will lead to "fixing" it, but they are so trivial, that i don't understand, why they should ...

jmi2

Updated: If Timer is used and it's reference is not saved on place, where it's still reachable, then expect errors. Such timer is then subject for garbage collection and will be removed. Unfortunatelly underlaying implementation is still trying to reference this memory, so it leads to Fatal exceptio...

jmi2

tested with few more version:

v1.9.4-762-gfa50047bb -> fatal exception 28(LoadProhibitedCause)

v1.9.4-272-g46091b8a on 2018-07-18 -> OK

v1.9.4-8-ga9a3caad0 on 2018-05-11 -> OK

MicroPython Forum (Archive)

Search found 21 matches

Re: polling tcp socket leads to Fatal exception 28(LoadProhibitedCause) on v1.10-23-g1fa8f977f

Re: polling tcp socket leads to Fatal exception 28(LoadProhibitedCause) on v1.10-23-g1fa8f977f

Re: 8266 - use of multiple timers leads to Fatal exception 28(LoadProhibitedCause)

Re: 8266 - use of multiple timers leads to Fatal exception 28(LoadProhibitedCause)

Re: 8266 - use of multiple timers leads to Fatal exception 28(LoadProhibitedCause)

Re: 8266 - use of multiple timers leads to Fatal exception 28(LoadProhibitedCause)

Re: 8266 - use of multiple timers leads to Fatal exception 28(LoadProhibitedCause)

Re: 8266 - use of multiple timers leads to Fatal exception 28(LoadProhibitedCause)

[workaround found] ESP8266 - use of Timer without storing reference leads to Fatal exception 28(LoadProhibitedCause)

Re: polling tcp socket leads to Fatal exception 28(LoadProhibitedCause) on v1.10-23-g1fa8f977f