Discussion

• A

  Does lora.nvram_restore() clear (delete) the saved lora context?
  lora nvram restore persistence • • arneme

  6
  1
  Votes
  6
  Posts
  247
  Views

  

  @chumelnicu it's not on the board. But to support other means of storage, a lora.nvram_read() and lora.nvram_write() pair could be useful. That could also be used to change individual parameters.
• L

  Changing LoRa parameters - Is necessary to restart device?
  lora lopy loramac lora class • • lsoria

  1
  0
  Votes
  1
  Posts
  75
  Views

  No one has replied

• 

  Pulse control in deep sleep (ULP)
  deepsleep ulp pulse control • • nespressif

  1
  1
  Votes
  1
  Posts
  91
  Views

  No one has replied

• E

  Sigfox downlink and callback
  sigfox downlink blocking • • Eric73

  1
  0
  Votes
  1
  Posts
  119
  Views

  No one has replied

• H

  Deep sleep with Pysense - Different APIs
  fipy pysense deepsleep • • Henning

  3
  0
  Votes
  3
  Posts
  144
  Views

  H

  @jcaron Thanks a lot for the explanation! That solved the question for me.
• D

  NB-IoT support
  nb-iot • • danielm

  7
  4
  Votes
  7
  Posts
  835
  Views

  J

  @jiemde Orange Belgium have Huawei base station so I'm waiting the new firmware for the Monarch chip.
• N

  I2C Causes crashes on FiPy and WiPy
  fipy wipy i2c • • noobiemcfoob

  4
  0
  Votes
  4
  Posts
  140
  Views

  N

  I spoke too soon! >.< From a fresh wipe and firmware upgrade, I was able to run the I2C library. However, once I loaded my own modules onto the device and used them to connect to my network, calling "init" on an I2C instance caused the WiPy to freeze (connected over serial, but I could no longer type into the console). I built a bit-banged version of I2C yesterday and am able to use it on the same pins ("P8", "P9") without issue.
• C

  pyCom Library WifiManager and more
  • constantinos

  3
  1
  Votes
  3
  Posts
  1169
  Views

  C

  I'm still using this library. But I haven't tested for the latest releasy of pyCom firmware. Fill free to use it and recomend any changes. Constantinos
• I

  Security - IP Protection
  wipy 3.0 security encryption protection • • InverseEffect

  14
  0
  Votes
  14
  Posts
  480
  Views

  X

  @robert-hh said in Security - IP Protection: @catalin Don't forget to lock the JTAG interface (if possible). There is a fuse to disable JTAG (JTAG_DISABLE). Furthermore, unless you build a firmware with DEBUG enabled, the JTAG IO pins are re-initialised as inputs with pull-down enabled during micropython startup.
• J

  LoRa NVRAM clear on restore issues
  lora lorawan deep sleep battery powered nvram • • jcaron

  3
  0
  Votes
  3
  Posts
  295
  Views

  J

  @han I usually do the initial join process manually moving to the load/work/send/save/sleep cycle. But if you do a nvram_restore and there's nothing to restore, has_joined will return false and you can do your join as usual. You logic should be something along the lines of: create lora object nvram_restore if has_joined is false, join, and wait for has_joined to become true do the work, send the data nvram_save deep sleep
• S

  Why is Brownout Detection disabled in the firmware
  firmware brownout • • Sympatron

  2
  0
  Votes
  2
  Posts
  159
  Views

  

  I've queried our firmware team about this and the response was: The IDF had a bug there at the beginning, so we disabled it He is welcome to enable it and submit a pull request
• S

  Is it possible to recompile Pycom's ESP IDF with different settings?
  micropython esp-idf compile • • Sympatron

  3
  0
  Votes
  3
  Posts
  254
  Views

  S

  @xykon I just tried it and it seems to work. Thank you very much! Are the settings in examples/wifi/scan/sdkconfig in the Pycom IDF repository exactly what you are building with or do you use a modified version? Is it documented anywhere which version of the IDF was used in a particular version of MicroPython? I assume at lot of the settings in sdkconfig (for example partition table) don't really matter, because they only change the (in this case unused) bootloader and app that are also built with make all. Is this correct? I think a hint in the readme.md of the Pycom IDF would be helpful.
• M

  function removed from LIS2HH12.py library module
  pytrack library lis2hh12 accele • • mrainone

  5
  0
  Votes
  5
  Posts
  399
  Views

  

  @mrainone said in function removed from LIS2HH12.py library module: can you recommend a low cost magnetometer to connect to the lopy I use simple GY-271 (HMC5883L) It working fine for me and is cheap
• M

  Test OTA using current firmware.
  firmware • • misterlisty

  2
  0
  Votes
  2
  Posts
  248
  Views

  

  @misterlisty Youj can dowload images, like https://software.pycom.io/downloads/WiPy-1.15.0.b1.tar.gz or https://software.pycom.io/downloads/LoPy-1.16.0.b1.tar.gz This archives contain a file called appimg.bin, which you have to use for OTA. The files system is kept during OTA, including boot.py and main.py
• M

  How to Program OEM Chips
  oem program • • matt_the_w

  2
  0
  Votes
  2
  Posts
  272
  Views

  

  Hi @matt_the_w The OEM modules should be programmed over the main serial port. I don't know of any other reliable way (WiFi OTA could be an alternative but I don't recommend it for factory programming)
• D

  How to properly build custom FW image (tar.gz)
  custom firmware • • danielm

  18
  1
  Votes
  18
  Posts
  1284
  Views

  T

  awesome, thanks for the clear answer.
• 

  Changing Frequency region after upgrade
  lopy firmware pymakr update update tool • • SakshamaGhoslya

  22
  0
  Votes
  22
  Posts
  4081
  Views

  X

  @dhruv I have changed your device from 868MHz to 915MHz. Please re-run the firmware update tool to flash the new region.
• D

  Arbitrary file in the FS
  firmware build file system • • danielm

  3
  0
  Votes
  3
  Posts
  279
  Views

  D

  @robert-hh I was thinking about that however I am not aware of a straightforward way how individual parameters could be updated by the application. The script would be frozen anyway. I was also thinking to move all parameters to NVS however the config also contains few strings which are not directly supported by the NVS right now. I think that the best solution will be to put default parameter values into Python script which will be frozen during build process. After boot it will be tested if NVS contains "init" flag and if not an initialization method will be called. Within this method individual parameters will be loaded from Python script to a dictionary which will then be dumped into json file stored in the internal file system. This will happen only during first boot after last firmware flashing.
• B

  LoPy external RAM
  update firmware upgrad ram • • binux

  9
  0
  Votes
  9
  Posts
  591
  Views

  N

  @binux @jmarcelino thanks for the clarification
• I

  Is there a firmware version list somewhere?
  latest firmware • • incognico

  3
  0
  Votes
  3
  Posts
  346
  Views

  I

  @livius Ok, thanks, appreciate the reply.