Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Magnetic Filament Sensor - Firmware Update Error

    Scheduled Pinned Locked Moved Solved
    Filament Monitor
    2
    7
    362
    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.
    • Shotfireundefined
      Shotfire
      last edited by Shotfire

      My sensor is on version 2 and I'm trying to update to version 3
      Using latest github download 44a
      And, since it successfully erased the chip it won't work at all now
      Probably something simple I'm missing but when I try to update the firmware I get this error with or without the ":e" at the end
      V1.7 sensor , Adafruit USBtinyISP

      ***avrdude -p t44 -c usbtiny -U flash:w:FilamentSensor.elf

      avrdude: AVR device initialized and ready to accept instructions

      Reading | ################################################## | 100% 0.02s

      avrdude: Device signature = 0x1e9207
      avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
      To disable this feature, specify the -D option.
      avrdude: erasing chip
      avrdude: reading input file "FilamentSensor.elf"
      avrdude: input file FilamentSensor.elf auto detected as invalid format
      avrdude: invalid input file format: -1
      avrdude: write to file 'FilamentSensor.elf' failed

      avrdude: safemode: Fuses OK

      avrdude done. Thank you.***

      alankilianundefined 1 Reply Last reply Reply Quote 0
      • alankilianundefined
        alankilian @Shotfire
        last edited by

        @shotfire It's been a while for me, but doesn't avrdude take HEX files which are produced by objcopy or something like that?

        SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

        1 Reply Last reply Reply Quote 0
        • Shotfireundefined
          Shotfire
          last edited by

          Not sure, I was just following the command line in the WiKi

          alankilianundefined 1 Reply Last reply Reply Quote 0
          • alankilianundefined
            alankilian @Shotfire
            last edited by alankilian

            @shotfire Oh I see it's documented HERE.

            Well, I'm not sure then.

            Here's what I get when I download from Release-44a: Does it match your binary?

            kilian@AlanDesktop ~/Downloads
            $ file FilamentSensor.elf
            FilamentSensor.elf: ELF 32-bit LSB executable, Atmel AVR 8-bit, version 1 (SYSV), statically linked, with debug_info, not stripped
            
            kilian@AlanDesktop ~/Downloads
            $ ls -l FilamentSensor.elf
            -rwx------+ 1 kilian None 32364 Feb  5 15:19 FilamentSensor.elf
            

            SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

            1 Reply Last reply Reply Quote 0
            • Shotfireundefined
              Shotfire
              last edited by Shotfire

              @alankilian I'm on Windows 10 so I'm not sure how to reproduce what your getting from Linux, on Windows it does show it as a 32kb file

              alankilianundefined 1 Reply Last reply Reply Quote 0
              • alankilianundefined
                alankilian @Shotfire
                last edited by

                @shotfire Use the dir command

                02/05/2022  03:19 PM            32,364 FilamentSensor.elf
                

                Anyway, it looks like you've got the same file I got, so I'm stumped.

                Someone will jump in and help soon I bet.

                SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

                Shotfireundefined 1 Reply Last reply Reply Quote 1
                • Shotfireundefined
                  Shotfire @alankilian
                  last edited by

                  @alankilian Switched over to a Linux machine running POP_OS and it flashed ok, shows V4 for the version

                  1 Reply Last reply Reply Quote 1
                  • Shotfireundefined Shotfire marked this topic as a question
                  • Shotfireundefined Shotfire has marked this topic as solved
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA