Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login
    1. Home
    2. Tags
    3. nvramsave

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Log in to post

    • All categories
    • E

      lora.nvram_restore() OSError: [Errno 122] EMSGSIZE

      Watching Ignoring Scheduled Pinned Locked Moved FiPy fipy pytrack lorawan nvramsave nvramrestore
      14
      0 Votes
      14 Posts
      112 Views
      J
      @robert-hh Thank you
    • D

      Don't erase lora context on nvram_restore()

      Watching Ignoring Scheduled Pinned Locked Moved Discussion lorawan restore nvram nvramsave nvramrestore
      2
      4 Votes
      2 Posts
      82 Views
      robert-hhR
      @d-alvrzx I strongly support this request. I see, that restoring some of the data may cause trouble, if restore is executed multiple time w/o a save in between. Like the packet counters. But that is less cumbersome than loosing all data. See also my notes here to retrieve individual elements: https://forum.pycom.io/topic/5922/an-alternative-to-nvram_save-restore-using-the-sd-card/6?
    • B

      Multiple JOIN

      Watching Ignoring Scheduled Pinned Locked Moved LoPy lora join nvramsave lorawan
      13
      0 Votes
      13 Posts
      2k Views
      B
      @brunos ! With s.setblocking (True) before s.send(), it's OK !!
    • 1 / 1