Reboot problem when using LoRa radio at certain intervals!



  • Hi!

    I have searched the forums a bit but I dont believe this error has been reported yet.
    I have two modules and have been able to reproduce this behaviour in both of them.
    I am running the following FW on both of them:

    (sysname='LoPy', nodename='LoPy', release='1.1.1.b1', version='v1.8.6-281-g75e2452 on 2017-01-03', machine='LoPy with ESP32')
    

    When the code looks like this, everything works as expected (serial console writes out "Sending.." every 8900th millisecond and the script sends the specified data using the socket).

    #main.py
    from network import LoRa
    import socket
    import time
    LoRa(mode=LoRa.LORA)
    s = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
    while True:
        uart.write('Sending..\r\n')
        s.send('Hello')
        time.sleep_ms(8900)
    

    However, if I change the amount of sleep in my infinite loop to anything above 8900ms, the modules will reboot the second time the sockets send-method is called:

    #main.py
    from network import LoRa
    import socket
    import time
    LoRa(mode=LoRa.LORA)
    s = socket.socket(socket.AF_LORA, socket.SOCK_RAW)
    while True:
        uart.write('Sending..\r\n')
        s.send('Hello')
        time.sleep_ms(9000)
    

    The ouput from my serial console in this erroneous case looks like this:

    Sending..
    Guru Meditation Error of type LoadProhibited occurred on core  0. Exception was unhandled.
    Register dump:
    PC      : 0x400827ef  PS      : 0x00060630  A0      : 0x800836b0  A1      : 0x3ffe8c00
    A2      : 0x00000000  A3      : 0x00004d56  A4      : 0x00060823  A5      : 0xb33f0000
    A6      : 0xb33fffff  A7      : 0x3ffd1ac8  A8      : 0x800827ea  A9      : 0x3ffe8be0
    A10     : 0x00002329  A11     : 0x00060823  A12     : 0x00060823  A13     : 0xb33f0000
    A14     : 0xb33fffff  A15     : 0x00000000  SAR     : 0x00000016  EXCCAUSE: 0x0000001c
    EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000
    
    Backtrace: 0x400827ef:0x3ffe8c00 0x400836b0:0x3ffe8c20 0x40081875:0x3ffe8c40 0x40087959:0x3ffe8c60 0x4008798c:0x3ffe8c80 0x40087a9b:0x3ffe8cb0
    
                                                                  Rebooting...
    ets Jun  8 2016 00:22:57
    
    rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    configsip: 0, SPIWP:0x00
    clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    mode:QIO, clock div:2
    load:0x3fff9010,len:8
    load:0x3fff9018,len:248
    load:0x40078000,len:4072
    load:0x4009f000,len:940
    entry 0x4009f1ec
    tcpip_task_hdlxxx : 3ffec298, prio:18,stack:2048
    I (2325) wifi: frc2_timer_task_hdl:3ffede48, prio:22, stack:2048
    I (2330) wifi: pp_task_hdl : 3fff06f8, prio:23, stack:8192
    I (3317) wifi: mode : softAP (24:0a:c4:00:b7:1f)
    dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)
    ..
    

    Is this something that has been reported before and is a know problem? Otherwise, I'm reporting it now :)



  • @daniel 1.2.0.b indeed fixed the problem. Great!


  • administrators

    Hey guys,

    Sorry about that, we introduced this bug on an intermediate release that we made on Monday. It's already fixed and the solution will be available later today.

    Cheers,
    Daniel



  • Confirmed! Same behaviour on my LoPy with same FW Version.


Log in to reply
 

Looks like your connection to Pycom Forum was lost, please wait while we try to reconnect.