Navigation

    Welcome to the Pycom forum

    Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Tags
    3. firmware
    Log in to post

    • S

      Wipy img max size
      Discussion • firmware wipy 3.0 • • serafimsaudade  

      15
      0
      Votes
      15
      Posts
      175
      Views

      robert-hh

      @kiltedpython There is also size_check.sh, application.mk. You have to create board subdirectories and change the respective partition map files to get actually space for larger images. For WiPy3, you can use e.g. LoPy4 as template.
    • J

      WiPy3 on Expansion3.1: Unable to Update WiPy's Firmware
      WiPy 2&3 • firmware expansion board firmware update wipy3.0 3.1 • • jc_serg  

      9
      0
      Votes
      9
      Posts
      417
      Views

      robert-hh

      @jc_serg That looks bad then. Since 3.3V is an output of the board, it means that the board is not working. Are you sure you plugged in the board in the right orientation?
    • S

      Fipy crashing when using Loramesh
      FiPy • fipy lora firmware pymkr loramesh • • shadi  

      9
      0
      Votes
      9
      Posts
      431
      Views

      S

      @catalin Ok, I will try the licensing then. Thank you very much.
    • K

      File system problems & solutions
      GPy • firmware file system littlefs fat • • kjm  

      9
      0
      Votes
      9
      Posts
      548
      Views

      A

      @kjm said in File system problems & solutions: the windows version of this CLI The CLI program should probably just be the same .exe file which is also the graphical thing. According to [1], its default location might be c:\Program Files (x86)\Pycom\Pycom Firmware Update\pycom-fwtool-cli.exe. [1] https://community.hiveeyes.org/t/setup-commandline-based-micropython-development-environment-on-linux-macos-and-windows/1639/15
    • S

      Firmware Flashing Documentation Insufficient Information
      Enhancements • firmware documentation • • Sn3akyP3t3  

      2
      0
      Votes
      2
      Posts
      408
      Views

      O

      Pybytes (2.0) / Pybytes-legacy (1.0) is a cloud-based device management platform. You can use it to visualize the sensors data, see the status and geolocation of your devices and you can also perform Firmware Over the Air updates. Pybytes version 1.0 and 2.0 are built on top of the low-level firmware. The legacy firmware contains the old low-level modules of the Pycom devices without pybytes. It contains the micropython interface, FreeRTOS and all the drivers (LTE, Wifi, Bluetooth, i2c, sockets, Lora, etc).
    • I

      Firmware Release v1.20.1
      Announcements & News • firmware • • iwahdan  

      68
      1
      Votes
      68
      Posts
      11077
      Views

      R

      @robert-hh I am using a L01 (4MB SPIRAM + 8MB Flash)
    • I

      New Release Candidate v1.20.0.rc13
      Beta Announcements & Development News • firmware • • iwahdan  

      16
      1
      Votes
      16
      Posts
      1170
      Views

      A

      Reminder: Giving or asking for exam content is not allowed. Asking what should I study is ok.
    • K

      Firmware speeds
      Support & Troubleshooting • gpy firmware • • kjm  

      3
      0
      Votes
      3
      Posts
      225
      Views

      C

      @kjm I never worked with Gpy, but with LoPys the speed of the firmware is nearly the same. What changed are the windows when the i2c module is ready to communicate. So you can start some i2c stuff before the whole system was completly initialized. But these windows/frames moved between firmware versions and became larger or smaler. So it was not reliable to use them. Maybe pycom moved some of their internal i2c stuff into more reliable regions. I do not recommend to stay on older firmware versions and optimise the timings for them. The ESP32 and the IDF cause too many problems. IMHO pycom is on the development branch too far behind the actual IDF version. If you have huge scripts, you can save some time by using precompiled or frozen modules. If you have some complicated stuff to do, you can do this before the Modem is ready. Yes, fast boot times will be fine, but I preferre signals, callback or variables which tell me, if the hardware is ready to use. I wasted too many time to find windows inbetween init states :)
    • T

      Find out firmware loaded on a given pysense/pytrack
      Discussion • pytrack firmware pysense • • tomsoft  

      1
      0
      Votes
      1
      Posts
      193
      Views

      No one has replied

    • I

      Stable Firmware Release v1.18.2.r4
      Announcements & News • firmware sequans • • iwahdan  

      2
      1
      Votes
      2
      Posts
      1045
      Views

      P

      Are there any release notes for the new sequans firmware? Any indication of feature changes or bug fixes?
    • I

      Stable Firmware Release v1.18.2.r2
      Announcements & News • firmware • • iwahdan  

      9
      1
      Votes
      9
      Posts
      1103
      Views

      P

      That resolved all issues. Thanks.
    • I

      Firmware Release Candidate v1.20.0.rc8
      Announcements & News • firmware pymesh • • iwahdan  

      3
      2
      Votes
      3
      Posts
      712
      Views

      I

      @rfinkers the Pymesh Docs page is under that link : https://docs.pycom.io/firmwareapi/pycom/network/lora/pymesh.html , it will be updated shortly with the Border router documentation.
    • rskoniec

      WPA3 is coming...
      Enhancements • firmware wifi security feature wpa3 • • rskoniec  

      1
      0
      Votes
      1
      Posts
      372
      Views

      No one has replied

    • J

      FiPy LTE not connecting after Upgrade Firmware
      FiPy • fipy firmware modem sequans • • Jordan Reyes  

      32
      1
      Votes
      32
      Posts
      5075
      Views

      I

      @steve-williams , I did some power mesurements here on the same setup I mentioned in my previous post to give you a clear picture about the current consumption while the modem is trying to attach so as to help you identifying the problem , in first trial I intentionally powered off the CAT-M1 network in office and run a script on GPY trying to attach you can see that the modem current consumption increases after sending attach request and keep trying to attach periodically, you can see that the Avg.current consumption when trying to attach can reach 285mA (150mA more than normal). The following image is when CAT-M1 network is back online and attaching is successful :
    • I

      New Stable Firmware Release v1.18.2
      Announcements & News • firmware • • iwahdan  

      16
      2
      Votes
      16
      Posts
      1901
      Views

      M

      @paul-thornton Sorry Paul, I never saw your reply until today. Unfortunately our load is pretty complicated; we have one thread for each I2C bus we configure (1 or 2 depending on the system) and two threads doing socket communication (one for outgoing and one watching for incoming). We're keeping track of resets and will monitor the systems. If it doesn't improve with later firmware releases then I'll have to look at debugging the crash. Do you have instructions on how to go about that? -- Mike
    • I

      New v1.20.0 Release candidate v1.20.0.rc7
      Beta Announcements & Development News • firmware pymesh • • iwahdan  

      28
      3
      Votes
      28
      Posts
      5141
      Views

      robert-hh

      @reidfo The connection was between P23 and Reset (what else). And yes, it did reset the board and the board booted in a normal fashion. The board should have an RC lowpass at Reset to suppress bouncing of the push button.
    • P

      New v3.1 Expansion Board Firmware: v0.0.11
      Announcements & News • firmware expansionboard update • • Paul Thornton  

      9
      1
      Votes
      9
      Posts
      1569
      Views

      G

      v0.0.11 will lock your Expansion Board in DFU mode. Goodbye serial console. https://forum.pycom.io/topic/4684/exit-from-dfu-mode/13
    • A

      How to find out which modem firmware a FiPy has installed?
      FiPy • fipy firmware lte sequans • • arneme  

      6
      0
      Votes
      6
      Posts
      974
      Views

      P

      @arneme Yup. Thats Correct.
    • Y

      PySense Firmware Upgrade - Device Not Recognized
      Getting Started • firmware pysense dfu-util zadig • • YNGVV  

      4
      0
      Votes
      4
      Posts
      553
      Views

      M

      @paul-thornton The timing is rather critical. Couldn't you extend the time window for updating to let's say 30s?
    • R

      Some confusion on the Pin_out layout.
      LoPy • lopy4 firmware pinout pinouts • • researcher  

      4
      0
      Votes
      4
      Posts
      513
      Views

      M

      See also my post here https://forum.pycom.io/topic/4130/pinout-pysense-etc
    • 1
    • 2
    • 3
    • 4
    • 5
    • 8
    • 9
    • 1 / 9