Firmware

• A

  PySense library on Extension Board 3.1
  • aparcar  

  2
  0
  Votes
  2
  Posts
  44
  Views

  

  @aparcar On expansion Boards you can determine the battery voltage with the internal ADC on Pin P16. There is a voltage divider between the battery an P16, which divides the battery voltage by 2 or by 3.05, depending on the board. So you can use the ADC class (see https://docs.pycom.io/tutorials/all/adc/) with 11dB attenuation to read the input voltage and scale that by the divider. E.g. if the ADC tells 1.9V, and the divider is 2, the the battery voltage is 3.8V. Since the ADC is noisy, you may have to calculate an average over say 100 values taken. If you have an voltage meter, you should take that to obtain the proper scaling value.
• E

  Accuracy of RTC
  esp32 • • Eric24  

  18
  0
  Votes
  18
  Posts
  6148
  Views

  

  @Colateral I used the same circuitry (10 pF capacitors) and a crystal with 12.5 pF load capacitance. The model is called MS1V-T1K from Micro Crystal Switzerland. It was the one easy to get from a local store. The 12.5 pF load capacitor would lead to ~22pF C1 C2 capacitors. Since I have a set-up with the LOPY4 development board + a carrier board +..., there is already a lot of unknown stray capacitance. Therefore the 10 pF work. I did however not run a test over a day yet to see the clock drift. I just measured the frequency of the crystal while running. But I can do this time drift test in the next days.
• I

  Error in the module selection pycom for firmware updating
  • Israelsq  

  1
  0
  Votes
  1
  Posts
  58
  Views

  No one has replied

• A

  [SOLVED] Unable to upgrade PyTrack/FiPy firmware using Pycom Upgrade
  • amkrup  

  3
  0
  Votes
  3
  Posts
  150
  Views

  A

  Was able to update the device using "Flash from local file" and using Fipy-1.18.3.tar which flashed successfully and I got to the confirmation page saying DeviceID, LoRa Mac etc. but SigFox ID and PAC-fields are missing... Is there any other way to get the SigFox ID's in order to register the device on SigFox Backend? Had to downgrade from 1.20.1.r3 to 1.18.3 due to rtc.ntp_sync-simply not working using 1.20.1.r3
• P

  utime.sleep() doesn't work in thread
  • PG  

  1
  0
  Votes
  1
  Posts
  73
  Views

  No one has replied

• E

  When is the TX_PACKET_EVENT interrupt triggered?
  • eranroll  

  3
  0
  Votes
  3
  Posts
  130
  Views

  E

  @jcaron thanks! That is clearly a good way of doing that. How come I didn't think of it sooner? :) Here is what I sent: 24 byte payload (on top of headers, CRC, etc.) SF12 US915 BW500 The time between when I sent it to when I got the interrupt triggered is: ~460 mili seconds The expected time between when I sent it to when I got the interrupt triggered should be: ~450 mili seconds So that means that the interrupt is triggered after the entire message has been sent. Hopes that helps anyone. Regards, Eran
• 

  Pymesh release v1.20.2.r1
  • catalin  

  11
  1
  Votes
  11
  Posts
  491
  Views

  

  @PG This issue of LoRa saturation is valid for any LoRa device, not only Pycom ones. But it isn't discussed/documented by the community as it should.
• K

  micropython exception handling
  • kjm  

  2
  0
  Votes
  2
  Posts
  128
  Views

  J

  @kjm said in micropython exception handling: I mean the Exception in the fn's except OSError is between that fn's try & except Exception No, it´s not, it is outside your try. Try this instead: def _fn(): try: try: raise OSError except OSError: 1/0 except Exception: print('_fn exception handler') try: _fn() except Exception: print('_caller exception handler') Johan
• I

  Wi-Fi functions
  fipy wipy wifi esp32 enhancement • • ingframin  

  7
  0
  Votes
  7
  Posts
  786
  Views

  G

  @ingframin Did you manage to modify the firmware? I would like to have a Wi-Fi advertising per 100 milliseconds; default LoPy-4 seem to send an advertising only if requested by a station.
• 

  Pysense 9uA in sleep
  • catalin  

  1
  3
  Votes
  1
  Posts
  124
  Views

  No one has replied

• A

  How to enable ESP debug output on Pycom modules?
  • achalmers68  

  4
  0
  Votes
  4
  Posts
  207
  Views

  A

  I managed to merge the whole of the Bluetooth component from idf_v3.3 to the v3.2 branch and build the libraries and firmware image. Unfortunately this did not solve my issue. I then tried to build the firmware using idf_v3.3 entirely. As expected there were many build issues. Almost no compile errors. Mostly linker issues. I suspect for someone with more understand of the IDF it may not be that difficult to update the pycom code to IDF_v3.3. I suspect, even if I could update the pycom code , it probably would not fix my issue.
• P

  @micropython.native support? MICROPY_EMIT_XTENSA define?
  esp32 enhancement • • peterson79  

  4
  0
  Votes
  4
  Posts
  617
  Views

  A

  Hi there, we learned only recently that native code generation indeed would be coming to MicroPython for ESP32 [1]. After MicroPython 1.12 arrived a few weeks ago, this even became a real thing: The esp32 port has the following new features: native code generation [2] However, Pycom just upgraded to MicroPython 1.11 a few months ago so we will probably have to wait a bit to see the upgrade to MicroPython 1.12. With kind regards, Andreas. [1] https://community.hiveeyes.org/t/native-modules-in-micropython/2709/2 [2] https://github.com/micropython/micropython/releases/tag/v1.12
• J

  How to update new firmware .elf format with pycom tools?
  • jnko  

  2
  0
  Votes
  2
  Posts
  170
  Views

  

  @jnko I do not think so. For me that just shows the lack of co-ordination in Pycom. Obviously, the elf file is just an intermediate step of creating the tar packages. That is all done by the script application.mk, which uses: esptool.py to create a bin file out of the elf file (line 669 ff), and uses tools/makepkg.sh to make the tar package (line 730 ff). Since the process involves the bootloader and partition files too, it is eventually easier to just completely clone the repository and run the full build process. You could also just use esptool.py to create the bin file and unpack/repack and existing firmware package using tar and gzip. That seems to be easier.
• C

  TimeoutError: Conncetion to AP Timeout!
  • chvl  

  1
  0
  Votes
  1
  Posts
  123
  Views

  No one has replied

• E

  OSError: [Errno -1] ERR_MEM
  • Eric Waai  

  12
  0
  Votes
  12
  Posts
  786
  Views

  H

  @Eric-Waai said in OSError: [Errno -1] ERR_MEM: i also get this problem with mqtt. i'm getting this error quite often especially when i send nothing for a long time. but only check for mesages def wait_msg(self): res = self.sock.read(1) self.sock.setblocking(True) if res is None: return None if res == b"": raise OSError(-1) if res == b"\xd0": # PINGRESP sz = self.sock.read(1)[0] assert sz == 0 return None i found the piece of code where the error occurs but don't know precise what is going wrong. it looks like no response from the server to me. it should just try again if you ask me Any solution to this so far?
• 

  FiPy v1.2 Problems
  • securigy  

  13
  0
  Votes
  13
  Posts
  551
  Views

  

  @securigy I am happy to help. But that should not be our task. Pycom should stop building firmware versions which break existing behavior - and that without announcement or documentation.
• 

  Using pycom-fwtool-cli
  • kodarn  

  10
  0
  Votes
  10
  Posts
  767
  Views

  A

  @robert-hh said in Using pycom-fwtool-cli: if one opens the docs in development view Do you also believe it's better to browse https://github.com/pycom/pycom-documentation/tree/publish/content than stumbling through https://docs.pycom.io/?
• 

  This topic is deleted!
  • securigy  

  1
  0
  Votes
  1
  Posts
  3
  Views

  No one has replied

• S

  Cannot upgrade Fipy firmware over FTP
  • sumanth89  

  11
  0
  Votes
  11
  Posts
  377
  Views

  S

  @robert-hh yup i did that but when i reboot the fipy the wifi hotspot doesn't come up
• J

  Firmware update elf vs tar
  • jason_gladen  

  14
  1
  Votes
  14
  Posts
  1296
  Views

  A

  Just for the records: Instead of identifying as @andreas said in Firmware update elf vs tar: Pycom MicroPython 1.20.1.r1 [d4b4717] on 2019-10-12; FiPy with ESP32 the firmware identifies itself as Pycom MicroPython 1.20.1.r1 [v1.11-3138a13] on 2019-10-08; FiPy with ESP32 Pybytes Version: 1.1.3 after flashing the rebundled tarball using the most recent FiPy-1.20.1.r1-application.elf file from the GitHub release page.