Discussion

• D

  UPDATE REQUEST: Don't erase lora context on nvram_restore()
  • d.alvrzx  

  1
  0
  Votes
  1
  Posts
  13
  Views

  No one has replied

• P

  Pymesh and RGB LED
  • PG  

  3
  0
  Votes
  3
  Posts
  33
  Views

  P

  Got it @catalin: thank you. I am going to test it soon. For now, I am preparing 3 LoPy4s for their first use (at least for me) in an orienteering event with 200 runners: 800m of meshed radio communication between the start line and the IT head quarter in a hilly forest. I hope it is going to work fine :-)
• M

  Alter lora frequency without reset
  • momo232030  

  23
  0
  Votes
  23
  Posts
  65
  Views

  

  @Gijs said in Alter lora frequency without reset: Also, setting a timeout does not alleviate the issue of the taken semaphore. No, but on timeout the semaphore could be released too.
• B

  Firmware update downgrades?
  • bushbavarian  

  4
  0
  Votes
  4
  Posts
  41
  Views

  B

  Thanks kjm! Wonder what functionalities I lost by accidentally downgrading..
• J

  is there a firmware and nano gateway code to reliable function of LoPy4?
  • jg_spitfire  

  7
  0
  Votes
  7
  Posts
  42
  Views

  J

  @robert-hh Hi, I am using the firmware version you told me and now works, and the nanogateway version I have been using is the provided by pycom
• H

  Problem on updating Expansion board V3.1
  • hiyasbie  

  10
  0
  Votes
  10
  Posts
  959
  Views

  G

  As Catalin mentioned, the issue is with MacOS, any other operating system should work fine!
• D

  Don't erase lora context on nvram_restore()
  lorawan nvram restore nvramsave nvramrestore • • d.alvrzx  

  2
  3
  Votes
  2
  Posts
  40
  Views

  

  @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?
• A

  Pycom with pysens Firmware problem
  • AM  

  1
  0
  Votes
  1
  Posts
  15
  Views

  No one has replied

• R

  This topic is deleted!
  • renaudm  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• M

  change CPU frequency (build firmware)
  • MusQar  

  1
  0
  Votes
  1
  Posts
  31
  Views

  No one has replied

• O

  Failed to start STP mode!
  gpy gpy nbiot sqnsupgrade ubuntu • • oyarzo-pablo  

  7
  0
  Votes
  7
  Posts
  979
  Views

  P

  @aen I had a different experience. This worked for me: >>> import sqnsupgrade >>> sqnsupgrade.info() <<< Welcome to the SQN3330 firmware updater [1.2.6] >>> >>> FiPy with firmware version 1.20.0.rc13 Your modem is in application mode. Here is the current version: UE5.0.0.0d LR5.1.1.0-46470 Then on the terminal: >>> sqnsupgrade.run('/dev/ttyACM0', 'NB1-41019.dup') <<< Welcome to the SQN3330 firmware updater [1.2.5] >>> Firmware file is too big to load via FFF method. Using ON_THE_FLY Attempting AT wakeup... Session opened: version 1, max transfer 8192 bytes Sending 5835531 bytes: [########################################] 100% Waiting for modem to finish the update... <<<=== DO NOT DISCONNECT POWER ===>>> Resetting............................. Your modem has been successfully updated. Here is the current firmware version: UE6.0.0.0 LR6.0.0.0-41019 When I tried your method (to upgrade) the result was an error: Upgrade failed with result failure[diffUpgrade,239] Patch didn't apply! So I figured I'd just upload the final image rather than a diff as the factory shipped firmware appeared to be some unknown number (46470) The documentation on all this is convoluted when its probably quite simple. Philip
• S

  Issue with DFU firmware update using Expansion board 3.0r
  firmware update dfu-util • • skippy  

  3
  0
  Votes
  3
  Posts
  249
  Views

  R

  Hello, I've just tried to update firmware of my Expansion Board v3.0 and faced the same issue. Does anyone knows how to fix it? Thanks in advance, w
• F

  How to create firmware image
  • f2f  

  1
  0
  Votes
  1
  Posts
  94
  Views

  No one has replied

• E

  How to decode CORE DUMP
  • ElinhohHD  

  1
  0
  Votes
  1
  Posts
  69
  Views

  No one has replied

• E

  This topic is deleted!
  • ElinhohHD  

  1
  0
  Votes
  1
  Posts
  12
  Views

  No one has replied

• C

  Adding modules to custom firmware
  • C Reese  

  4
  0
  Votes
  4
  Posts
  246
  Views

  C

  @robert-hh Thanks!
• R

  FiPy LTE Firmware upgrade fails
  • railmonitor  

  1
  0
  Votes
  1
  Posts
  92
  Views

  No one has replied

• P

  Lopy 4 and Pytrack does not wake up from the sleep.
  • pytrackuser1  

  5
  0
  Votes
  5
  Posts
  208
  Views

  

  hi @pytrackuser1 and @jcaron I've run an similar experiment, on Pysense, for some 12-14 hours and it didn't failed (sleep cycles were 20sec). I've used a 2Ah battery, and recharge it once during the experiment. I've met such situation, but the battery was weak, 3.6V showing on pysense.read_battery_voltage(), indeed it did not wake up. You could log into NVS last value of: the battery voltage, number(count) of restart, time from RTC, maybe we notice a pattern. Computer could go into in standby, and minimise USB power source; but you said you've used a power adapter... One question, after the block, you just cycle power and it works fine, isn't it? OK, I will try to monitor power usage, maybe I can detect something. To disable Pybytes: we’ve just released v1.20.2.rc3, which supports the method pycom.pybytes_on_boot(False) for the previous versions, there are 2 commands: >>> pybytes.smart_config(False) >>> pybytes.set_config("pybytes_autostart","false")
• L

  Pymesh collision detection
  • lorenz.bornholdt  

  3
  0
  Votes
  3
  Posts
  158
  Views

  L

  Thank you, that has helped me!
• K

  Can't read nfc chip with pyscan
  pyscan nfc reading errors • • kubohirner  

  1
  1
  Votes
  1
  Posts
  142
  Views

  No one has replied