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. Controllers
  3. Can't assign firmware to node in MYSController for OTA

Can't assign firmware to node in MYSController for OTA

Scheduled Pinned Locked Moved Controllers
6 Posts 2 Posters 2.3k Views 1 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.
  • MarcoEM Offline
    MarcoEM Offline
    MarcoE
    wrote on last edited by
    #1

    This is probably a stupid question but why can't I assign firmware to my node in MYScontroller?

    I use a Pro Mini 16MHz with the MYSBootloaderV13pre.hex burned and MYScontroller_1_0_0beta.

    In the context menu of the node I don't get the assign option:

    0_1485191194108_menu.jpg

    I can see the bootloader is communicating with my gateway (RPI Ethernet gateway) and in the controller.

    mysgw: TSF:MSG:FPAR REQ,ID=1
    mysgw: TSF:PNG:SEND,TO=0
    mysgw: TSF:CKU:OK
    mysgw: TSF:MSG:GWL OK
    mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
    mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=1,l=0,sg=0:255
    mysgw: TSF:MSG:BC
    mysgw: TSF:MSG:FPAR REQ,ID=1
    mysgw: TSF:PNG:SEND,TO=0
    mysgw: TSF:CKU:OK
    mysgw: TSF:MSG:GWL OK
    mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
    mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=1,l=0,sg=0:255
    mysgw: TSF:MSG:BC
    mysgw: TSF:MSG:FPAR REQ,ID=1
    mysgw: TSF:PNG:SEND,TO=0
    mysgw: TSF:CKU:OK
    mysgw: TSF:MSG:GWL OK
    mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
    mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
    

    The controller log looks as follows:

    1/23/2017 19:07:58	INFO	BL version=258
    1/23/2017 19:07:58	INFO	No FW assigned
    1/23/2017 19:08:01	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
    1/23/2017 19:08:01	DEBUG	Undefined firmware/type for node=1
    1/23/2017 19:08:01	INFO	BL version=258
    1/23/2017 19:08:01	INFO	No FW assigned
    1/23/2017 19:08:05	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
    1/23/2017 19:08:05	DEBUG	Undefined firmware/type for node=1
    1/23/2017 19:08:05	INFO	BL version=258
    1/23/2017 19:08:05	INFO	No FW assigned
    1/23/2017 19:08:16	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
    1/23/2017 19:08:16	DEBUG	Undefined firmware/type for node=1
    1/23/2017 19:08:16	INFO	BL version=258
    1/23/2017 19:08:16	INFO	No FW assigned
    1/23/2017 19:08:19	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
    1/23/2017 19:08:19	DEBUG	Undefined firmware/type for node=1
    1/23/2017 19:08:19	INFO	BL version=258
    1/23/2017 19:08:19	INFO	No FW assigned
    1/23/2017 19:08:22	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
    1/23/2017 19:08:22	DEBUG	Undefined firmware/type for node=1
    1/23/2017 19:08:22	INFO	BL version=258
    1/23/2017 19:08:22	INFO	No FW assigned
    

    Somewhere I am missing something simple. Please help. I see that when I request info on the node it states the firmware updates are not allowed.

    MarcoEM 1 Reply Last reply
    0
    • MarcoEM MarcoE

      This is probably a stupid question but why can't I assign firmware to my node in MYScontroller?

      I use a Pro Mini 16MHz with the MYSBootloaderV13pre.hex burned and MYScontroller_1_0_0beta.

      In the context menu of the node I don't get the assign option:

      0_1485191194108_menu.jpg

      I can see the bootloader is communicating with my gateway (RPI Ethernet gateway) and in the controller.

      mysgw: TSF:MSG:FPAR REQ,ID=1
      mysgw: TSF:PNG:SEND,TO=0
      mysgw: TSF:CKU:OK
      mysgw: TSF:MSG:GWL OK
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=1,l=0,sg=0:255
      mysgw: TSF:MSG:BC
      mysgw: TSF:MSG:FPAR REQ,ID=1
      mysgw: TSF:PNG:SEND,TO=0
      mysgw: TSF:CKU:OK
      mysgw: TSF:MSG:GWL OK
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=1,l=0,sg=0:255
      mysgw: TSF:MSG:BC
      mysgw: TSF:MSG:FPAR REQ,ID=1
      mysgw: TSF:PNG:SEND,TO=0
      mysgw: TSF:CKU:OK
      mysgw: TSF:MSG:GWL OK
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      mysgw: TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      mysgw: TSF:MSG:READ,1-1-0,s=255,c=4,t=0,pt=6,l=10,sg=0:FFFFFFFF0800DCEF0102
      

      The controller log looks as follows:

      1/23/2017 19:07:58	INFO	BL version=258
      1/23/2017 19:07:58	INFO	No FW assigned
      1/23/2017 19:08:01	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
      1/23/2017 19:08:01	DEBUG	Undefined firmware/type for node=1
      1/23/2017 19:08:01	INFO	BL version=258
      1/23/2017 19:08:01	INFO	No FW assigned
      1/23/2017 19:08:05	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
      1/23/2017 19:08:05	DEBUG	Undefined firmware/type for node=1
      1/23/2017 19:08:05	INFO	BL version=258
      1/23/2017 19:08:05	INFO	No FW assigned
      1/23/2017 19:08:16	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
      1/23/2017 19:08:16	DEBUG	Undefined firmware/type for node=1
      1/23/2017 19:08:16	INFO	BL version=258
      1/23/2017 19:08:16	INFO	No FW assigned
      1/23/2017 19:08:19	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
      1/23/2017 19:08:19	DEBUG	Undefined firmware/type for node=1
      1/23/2017 19:08:19	INFO	BL version=258
      1/23/2017 19:08:19	INFO	No FW assigned
      1/23/2017 19:08:22	RX	1;255;4;0;0;FFFFFFFF0800DCEF0102
      1/23/2017 19:08:22	DEBUG	Undefined firmware/type for node=1
      1/23/2017 19:08:22	INFO	BL version=258
      1/23/2017 19:08:22	INFO	No FW assigned
      

      Somewhere I am missing something simple. Please help. I see that when I request info on the node it states the firmware updates are not allowed.

      MarcoEM Offline
      MarcoEM Offline
      MarcoE
      wrote on last edited by
      #2

      OK, OTA works with MYSController 0.1.2.282, it has the assign firmware in the context menu. But the latest version 1.0.0beta no way. Can't figure out how to assign the firmware.

      1 Reply Last reply
      0
      • MarcoEM Offline
        MarcoEM Offline
        MarcoE
        wrote on last edited by
        #3

        Ok, so I reverted everything to the previous version of the MYSBootloader and the previous version of the MYSController. First time I tried I could assign firmware and do the OTA update.
        I then updated the bootloader to the latest version and OTA still worked. I then opened the latest version of the MYSController and guess what, I can assign firmware.

        SO what did I do? I made sure all files int he MYSController directory was read/write enabled. Was this the problem? I have no idea and clearly no-one else either.

        tekkaT 1 Reply Last reply
        0
        • MarcoEM MarcoE

          Ok, so I reverted everything to the previous version of the MYSBootloader and the previous version of the MYSController. First time I tried I could assign firmware and do the OTA update.
          I then updated the bootloader to the latest version and OTA still worked. I then opened the latest version of the MYSController and guess what, I can assign firmware.

          SO what did I do? I made sure all files int he MYSController directory was read/write enabled. Was this the problem? I have no idea and clearly no-one else either.

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

          @MarcoE The issue you describe occurs when the firmware_config.csv file is corrupted or the formatting is wrong. Have a look at the MYSController log tab.

          MarcoEM 1 Reply Last reply
          1
          • tekkaT tekka

            @MarcoE The issue you describe occurs when the firmware_config.csv file is corrupted or the formatting is wrong. Have a look at the MYSController log tab.

            MarcoEM Offline
            MarcoEM Offline
            MarcoE
            wrote on last edited by
            #5

            @tekka Thanks tekka, have it sorted now! Any idea why I can't reset my nodes from the MYSController? (!TX).

            tekkaT 1 Reply Last reply
            0
            • MarcoEM MarcoE

              @tekka Thanks tekka, have it sorted now! Any idea why I can't reset my nodes from the MYSController? (!TX).

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

              @MarcoE !TX indicates that you are in "RX only" mode.

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


              19

              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