Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login
    1. Home
    2. Tags
    3. frozen

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Log in to post

    • All categories
    • B

      How I built a custom firmware for frozen bytecode

      Watching Ignoring Scheduled Pinned Locked Moved Guides frozen firmware
      4
      0 Votes
      4 Posts
      2k Views
      robert-hhR
      @betterauto I found this redirection of USB to a VM often flaky. VMware works better than Virtualbox.
    • B

      [SOLVED] Errors building frozen bytecode

      Watching Ignoring Scheduled Pinned Locked Moved Getting Started frozen
      2
      0 Votes
      2 Posts
      895 Views
      B
      Found the problem quickly. I read the error message very carefully and found the file name embedded in that long STATIC variable name. Those were some old/unnecessary test code and when I removed them, it compiled.
    • P

      Compile firmware for wipy2.0 success, but after reboot is red light

      Watching Ignoring Scheduled Pinned Locked Moved Discussion firmware compile update frozen modules
      3
      0 Votes
      3 Posts
      1k Views
      P
      @robert-Thank you, worked perfectly
    • L

      Frozen modules - parser could not allocate enough memory

      Watching Ignoring Scheduled Pinned Locked Moved MicroPython frozen
      3
      0 Votes
      3 Posts
      1k Views
      L
      @robert-hh Ok, thank you for the confirmation I must now test this feature :)
    • A

      [Wipy 2.0] How to build firmware release='1.4.0.b1'

      Watching Ignoring Scheduled Pinned Locked Moved Issues & Bugs firmware ble build bytecode frozen
      5
      0 Votes
      5 Posts
      2k Views
      robert-hhR
      @Arkaik In the list of commits, you have to go back to an entry with the title "Bump to version 1.4.0.b1". There you find the fingerprint. It's not a long way. In you first port you mentioned 1.4.0b1. But now you mention 1.0.4b1. About esp-idf. Do use the version indicated by the pycom web site.Try to checkout the most recent version before the date of the wipy firmwar you are using. That might get a little bit of a trial & error game.
    • 1 / 1