Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

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

    Open source Licence

    Scheduled Pinned Locked Moved Announcements & News
    27 Posts 9 Posters 17.2k Views 9 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L Offline
      LoneTech @brotherdust
      last edited by LoneTech

      @brotherdust Unlikely; the firmware partitions are 1M large, and your transfer stopped at 256k. OTA updating isn't quite 100% for me; not sure if that readonly flash bug is reoccurring or what, but doing a serial download tends to clear it. Also, on the firmware versions with the watchdog bug OTA almost always triggers that.

      1 Reply Last reply Reply Quote 0
      • N Offline
        nickparrin @LoneTech
        last edited by nickparrin

        Keep getting an error like this:

        developer@developer:~/esp32/pycom-micropython/esp32$ make BOARD=LOPY LORA_BAND=USE_BAND_868
        LINK build/LOPY/release/bootloader/bootloader.elf
        xtensa-esp32-elf-gcc -nostdlib -Wl,-Map=build/LOPY/release/bootloader/bootloader.map -Wl,--no-check-sections -u call_user_start_cpu0 -Wl,-static -Wl,--undefined=uxTopUsedPriority -Wl,--gc-sections -T esp32.bootloader.ld -T esp32.rom.ld -T esp32.peripherals.ld -Wl,--start-group -Llib -L/home/developer/esp32/pycom-esp-idf/components/esp32/ld -Lbuild/LOPY/release/bootloader -L/home/developer/esp32/pycom-esp-idf/components/esp32/lib -Lbootloader -llog -lcore -lspi_flash build/LOPY/release/bootloader/bootloader.a -Wl,--end-group -Wl,-EL -o build/LOPY/release/bootloader/bootloader.elf
        /home/developer/esp32/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/4.8.5/../../../../xtensa-esp32-elf/bin/ld: cannot find -lcore
        collect2: error: ld returned 1 exit status
        application.mk:274: recipe for target 'build/LOPY/release/bootloader/bootloader.elf' failed
        make: *** [build/LOPY/release/bootloader/bootloader.elf] Error 1
        

        I set the IDF_PATH and added gcc to PATH. Tried with the ln command, and without by editing the Makefile directly

        EDiT: fixed it thanks to daniel. I missed to import (inside pycom idf) the needed compontents:

        • git submodule update --init
        1 Reply Last reply Reply Quote 1
        • L Offline
          livius
          last edited by

          Will be good to see port of this
          https://github.com/micropython/micropython/pull/2091/files
          and also enable time_us() which is currently commented out in the code
          but i suppose it is limited by some esp32 IDF? and because of this is commented out?
          https://github.com/pycom/pycom-micropython/blob/master/esp32/mods/modutime.c

          think about people first, then computers

          1 Reply Last reply Reply Quote 0
          • D Offline
            daniel
            last edited by

            @livius yes, machine.time_pulse_us() is very useful and we will implement it for the ESP32. A number of function in the time module are incomplete due to previous limitations of the IDF. The plan is to get back to that and implement them in early January.

            Cheers,
            Daniel

            L 1 Reply Last reply Reply Quote 0
            • L Offline
              livius @daniel
              last edited by

              @daniel
              thank you for the info - especially about time frame

              think about people first, then computers

              1 Reply Last reply Reply Quote 0
              • L Offline
                livius
                last edited by

                @daniel
                Can i ask what is IRAM_ATTR in functions declaration?

                think about people first, then computers

                1 Reply Last reply Reply Quote 1
                • D Offline
                  daniel
                  last edited by

                  @livius that's needed in order to place functions inside the instruction RAM of the ESP32. Otherwise they will reside in flash, which means that they need to be fetched from the SPI flash everytime there's a cache miss. Time critical functions must be placed inside IRAM, as well as interrupt handlers.

                  L 1 Reply Last reply Reply Quote 1
                  • L Offline
                    livius @daniel
                    last edited by

                    @daniel
                    Thank you very much :)
                    I still analyze repo (and learn C which is not my language) and need to understand internals until i change something on my side.

                    think about people first, then computers

                    1 Reply Last reply Reply Quote 0
                    • L Offline
                      livius
                      last edited by

                      We have correlation between
                      pycom/pycom-micropython
                      and
                      https://github.com/pycom/pycom-esp-idf

                      will be good when you send update to new version
                      e.g. 1.3.0.b1 do the same in pycom-esp-idf

                      because i do not know now how to revert firmware to older version.
                      I can simply download pycom-micropython at certain firmware version(commit)
                      but do not know how do this in correlation with esp-idf (do not know which commit)

                      think about people first, then computers

                      1 Reply Last reply Reply Quote 0
                      • D Offline
                        daniel
                        last edited by

                        @livius I was almost sure that we also pushed to Github the latest pycom-esp-idf, but it seems we didn't. That is corrected now and everything us up to date. Thanks for pointing it out.

                        Cheers,
                        Daniel

                        L 1 Reply Last reply Reply Quote 0
                        • L Offline
                          livius @daniel
                          last edited by livius

                          @daniel
                          but i do not talk about this
                          only when you commit to pycom-esp-idf
                          add comment or some file as "version" and write there same string as is for pycom-micropython e.g. `1.3.0.b1'

                          we then can back in commits and download esp-idf and pycom in the same version (older)

                          but thank you for the update

                          think about people first, then computers

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            daniel
                            last edited by

                            @livius good point, we'll start tagging it like this from now on. Thanks!

                            1 Reply Last reply Reply Quote 0
                            • B Offline
                              beyonlo @Fred
                              last edited by

                              I am pleased to confirm that the firmware of Pycom modules is now Open source and can be found here https://github.com/pycom/pycom-micropython

                              I remember to read in the past a topic in the "Announcements & News" about that PyCom and Micropython (Damien George) will work together on ESP32 port. Well, I would like to know some things:

                              1. Where are there this topic? Anyone can past me the URL?
                              2. Is this https://github.com/micropython/micropython-esp32 the official address to MicroPython to ESP32 where PyCom and Damien are working together?
                              3. I remember (via that announcement) that PyCom will be to commit the source code ESP32 project directally to official port (address above), is that happen? Because I checked today that last commit was done more than a month ago and less than a month PyCom released a new firmware with modifications on the MicroPython.

                              Thank you.

                              1 Reply Last reply Reply Quote 0

                              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                              With your input, this post could be even better 💗

                              Register Login
                              • 1
                              • 2
                              • 2 / 2
                              • First post
                                Last post

                              Pycom on Twitter

                              Pycom