Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Troubleshooting
  3. OTA updates on Arduino Nano

OTA updates on Arduino Nano

Scheduled Pinned Locked Moved Troubleshooting
23 Posts 5 Posters 11.6k Views 4 Watching
  • 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.
  • OitzuO Offline
    OitzuO Offline
    Oitzu
    wrote on last edited by
    #14

    @rvweert: i see no bootloader involved. Could you try to add an wdt_reset(); at the beginning of the setup() routine?

    1 Reply Last reply
    0
    • R Offline
      R Offline
      rvweert
      wrote on last edited by
      #15

      Hi Oitzu,

      Just tried that, same result...

      1 Reply Last reply
      0
      • R Offline
        R Offline
        rvweert
        wrote on last edited by
        #16

        No more news on this?;-)

        1 Reply Last reply
        0
        • OitzuO Offline
          OitzuO Offline
          Oitzu
          wrote on last edited by
          #17

          @rvweert out of ideas by simply looking at the logs.
          Maybe @tekka knows anything.
          Did you try to enable debug on the node and look at the nodes output?

          tekkaT 1 Reply Last reply
          0
          • OitzuO Oitzu

            @rvweert out of ideas by simply looking at the logs.
            Maybe @tekka knows anything.
            Did you try to enable debug on the node and look at the nodes output?

            tekkaT Offline
            tekkaT Offline
            tekka
            Admin
            wrote on last edited by
            #18

            @rvweert I'll look into that in a little bit.

            1 Reply Last reply
            0
            • R rvweert

              Hi Tekka,

              Please see here my log:
              MySensors_20151109-085110.log

              Also yes, all my nodes are running the same version from git.

              Cheers,

              Rene

              tekkaT Offline
              tekkaT Offline
              tekka
              Admin
              wrote on last edited by
              #19

              @rvweert there is potentially an id conflict: was the node previously used as gateway? Anyhow, try clearing the eeprom with the ClearEepromConfig sketch and upload the log again.

              1 Reply Last reply
              0
              • R Offline
                R Offline
                rvweert
                wrote on last edited by
                #20

                Hey Tekka,

                Tried clearing both eeproms, still same problem. Actually tried two completely new nano's and same problem again...

                tekkaT 2 Replies Last reply
                0
                • R rvweert

                  Hey Tekka,

                  Tried clearing both eeproms, still same problem. Actually tried two completely new nano's and same problem again...

                  tekkaT Offline
                  tekkaT Offline
                  tekka
                  Admin
                  wrote on last edited by
                  #21

                  @rvweert Looking at the logs, there is no bootloader involved (@Oitzu already confirmed this).
                  This looks like a bad nRF chip and/or power issues (try with different a cap) since the msgs sent from the GW never reach the node.

                  1 Reply Last reply
                  0
                  • R rvweert

                    Hey Tekka,

                    Tried clearing both eeproms, still same problem. Actually tried two completely new nano's and same problem again...

                    tekkaT Offline
                    tekkaT Offline
                    tekka
                    Admin
                    wrote on last edited by
                    #22

                    @rvweert MY_OTA_FIRMWARE_FEATURE enabled in MyConfig.h? This seems to be the cause of the restarting nodes. Try disabling this option unless you are using the sensebender board...

                    1 Reply Last reply
                    0
                    • R Offline
                      R Offline
                      rvweert
                      wrote on last edited by
                      #23

                      @tekka I checked but MY_OTA_FIRMWARE_FEATURE wasn't enabled. Also I tried Mysensors 1.4.1 and 1.5.2 but same result. Can't get it to work;-(

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      12

                      Online

                      11.7k

                      Users

                      11.2k

                      Topics

                      113.1k

                      Posts


                      Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • MySensors
                      • OpenHardware.io
                      • Categories
                      • Recent
                      • Tags
                      • Popular