Firmware

• 

  Pymesh wishlist
  pymesh • • catalin  

  18
  2
  Votes
  18
  Posts
  1107
  Views

  

  @catalin Is Pymesh still under development? I wish to have the issue with running out of buffers resolved :) Problem: After a while nodes are unable to send data to each other. To reproduce, start up two nodes, send message until you run out of "free buffer", to check available buffer, run buffer info...
• 

  Pymesh release v1.20.1.r2
  pymesh • • catalin  

  12
  2
  Votes
  12
  Posts
  1047
  Views

  E

  @catalin I did manage to upgrade to the new firmware using the CLI tool. However, when I upload my program, I got the following error: got exception [Errno 95] EOPNOTSUPP OT stack: 7272 Pycom MicroPython 1.20.1.r2 [v1.11-7106c733c] on 2019-11-01; FiPy with ESP32 Type "help()" for more information. All I did was to start a LoRa connection: lora = LoRa(mode=LoRa.LORA, region=LoRa.US915, frequency=928000000, sf=9, bandwidth=LoRa.BW_500KHZ, tx_power=20) And then start a Mesh connection, which results in the error above right away: mesh = lora.Mesh()
• 

  Pymesh updates
  lora enhancement pymesh • • catalin  

  73
  2
  Votes
  73
  Posts
  12657
  Views

  J

  Hello, @catalin, I have the same error, whit the FW 1.20.2.rc11, for pymesh, have you solved it?. Thank you in advance.
• 

  Firmware upgrade troubleshooting - checklist/procedure
  lopy • • rskoniec  

  24
  5
  Votes
  24
  Posts
  16486
  Views

  

  Unfortunately, this is currently not working for upgrading a module through either the Pysense or Pytrack boards using any GNU/Linux distribution.
• T

  'LoRa' object has no attribute 'Mesh'
  • thibault  

  21
  0
  Votes
  21
  Posts
  534
  Views

  A

  Hello! I'm trying to create a LoRa Mesh or PyMesh network. I'm using LoPy4 and FiPy with expansion board 3.1v. After a few problems, I was able to create a PyMesh network using Pybytes. I have a project on Pybytes with WiFi and LoRa added as networks. The devices have the same firmware version (1.20.2.rc11). They connet to Pybytes and they get a role (the rgbled change its color). However, I checked the monitoring tab and they don't find neighbours. Moreover, I set the FiPy as Border Router, but something happened because in the image above it isn't appear as I defined previously. I'm running tests right now, the FiPy is the leader of the network (MAGENTA) and the LoPy4 is a router (GREEN). Do I need another LoPy/FiPy to find neighbours between them? I read the tutorials in the Pycom website, but I'm getting a bit confused because what I found here (https://docs.pycom.io/pymesh/licence/) works, but couldn't find neighbours in the network, and what I also found on the website (https://docs.pycom.io/firmwareapi/pycom/network/lora/pymesh/) doesn't work. It throws an error: Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled. Core 1 register dump: PC : 0x400ff85a PS : 0x00060030 A0 : 0x800ff890 A1 : 0x3ffdd450 A2 : 0x00000000 A3 : 0x00000000 A4 : 0x3f433b18 A5 : 0x3ffdd5b8 A6 : 0x0000002a A7 : 0x0000098a A8 : 0x3f40fc38 A9 : 0x3ffdd430 A10 : 0x00000000 A11 : 0x00060023 A12 : 0x00060020 A13 : 0x00000000 A14 : 0x0000000a A15 : 0x3ffdd5e0 SAR : 0x0000001e EXCCAUSE: 0x0000001c EXCVADDR: 0x00000000 LBEG : 0x4009527c LEND : 0x40095287 LCOUNT : 0xffffffff ELF file SHA256: 0000000000000000000000000000000000000000000000000000000000000000 Backtrace: 0x400ff85a:0x3ffdd450 0x400ff88d:0x3ffdd470 0x40108334:0x3ffdd490 0x40101e71:0x3ffdd4c0 0x400fe299:0x3ffdd4e0 0x4010a251:0x3ffdd500 0x40101f84:0x3ffdd5a0 0x400fe299:0x3ffdd600 0x400fe2c6:0x3ffdd620 0x400e1679:0x3ffdd640 0x400e1908:0x3ffdd6e0 0x400e01bd:0x3ffdd720 The code above had some core dump info but it was a bunch of letters without much sense and I decided not to put it here. So I would appreciate if someone can give me some hints about whats happening or what to do now.
• L

  MicroPython network.WIZNET5K module?
  • leaf  

  3
  2
  Votes
  3
  Posts
  47
  Views

  M

  Were you able to find a solution to the problem? i'm the same way
• M

  Trying to connect wiznet W5500 module to pycom fipy need help :'(
  • Magheck  

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• K

  Firmware updates
  • K K  

  2
  0
  Votes
  2
  Posts
  37
  Views

  

  @K-K The company is under administration, and it's assets are for sale. See the web site. So do not expect any activity from Pycom.
• B

  Cannot connect Lopy to Pybytes
  • BearS  

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• A

  FiPy on Expansionboard 2.1A stopped functioning
  • Antman  

  4
  0
  Votes
  4
  Posts
  17
  Views

  A

  Well - this is embarrassing.. I first tested this at home, I had 3 micro USB cables - the first one I used worked. I travelled to site; bringing 2 micro USB cables with me - and I'm sure you already know where this is going.. Those cable appear to power up the FiPy only - and not allow the comm's to function. I borrowed a 3rd cable yesterday - and it worked immediately.. Thanks for your support - cutting all my "power only" micro-USB's in half..
• T

  LTE on GPY using Arduino IDE for faster boot time
  • Thijs Franssen  

  3
  0
  Votes
  3
  Posts
  50
  Views

  T

  I added an extra line before going to sleep to turn off the modem. The sleep current in this case is 80 uA. Perfect! //Set functionallity to 0 SerialAT.println("AT+CFUN=0");
• D

  Is there any way to kill a specific child thread from the parent thread?
  • danielb  

  1
  0
  Votes
  1
  Posts
  16
  Views

  No one has replied

• D

  fipy no repl after firmware upgrade, safe boot doesn't help
  • David Taylor  

  2
  0
  Votes
  2
  Posts
  23
  Views

  P

  @David-Taylor said in fipy no repl after firmware upgrade, safe boot doesn't help: I've tried the safeboot button and I do get the different LED flash rates, but still no repl. Hi David, It's worth checking what safeboot is doing. You don't say what the LED is doing, but the documentation is here https://docs.pycom.io/gettingstarted/programming/safeboot If that doesn't work you could erase the flash with the cli updater and reflash. https://docs.pycom.io/advance/cli/
• C

  1.20.2.r6 L01 Firmware image size exceeds avialable space
  lopy • • Colateral  

  2
  0
  Votes
  2
  Posts
  20
  Views

  C

  @robert-hh helped me on this. many thanx to him !!!!!! WE need to modify the tools/size_check.sh I did IMG_MAX_SIZE_4MB=1810000 (added in my case increased with ~40000 bytes from1761280 partition size) then go to boards/lopy/script_4MB and change factory and ota_0 size .. then otadata begin adress { "version" : "2.1", "partitions" : { "factory" : ["0x10000", "0x1B9E50"], "ota_0" : ["0x1CBE50", "0x1B9E50"], "otadata" : ["0x1C9E50", "0x1000"] }, "script" : [ ["w", "bootloader", "bootloader.bin"], ["w", "partitions", "partitions_4MB.bin"], ["w", "factory", "lopy.bin"] ] }
• C

  Old release clone 1.20.2.r4
  • Colateral  

  4
  0
  Votes
  4
  Posts
  12
  Views

  

  @Colateral git checkout v1.20.2.r4
• C

  1.20.2.r6 lwip failed during git recursive
  • Colateral  

  2
  0
  Votes
  2
  Posts
  15
  Views

  C

  @Colateral I found: You need to export GIT_SSL_NO_VERIFY=1
• A

  How to re-compile libraries (*.a libs)
  • Andrea Picillo  

  1
  0
  Votes
  1
  Posts
  15
  Views

  No one has replied

• A

  LWIP Debug Options
  • Andrea Picillo  

  1
  0
  Votes
  1
  Posts
  15
  Views

  No one has replied

• A

  Reference update (home/peter/....)
  • Andrea Picillo  

  1
  0
  Votes
  1
  Posts
  17
  Views

  No one has replied

• A

  CORE DUMP - MODETH Lib
  • Andrea Picillo  

  2
  0
  Votes
  2
  Posts
  28
  Views

  A

  I also noticed that somethings different happens into TCP packets: As you can see I received plenty good packets without any errors. Suddenly I start receiving some "TCP Retransmission" or "DUP ACK". The situation doesn't change in time when that happens. I mean that these "abnormal" packets will be received forever. It seems that the at final stage it brings to the stuck of the Pycom Module and the Core Dump or WDT time out.