Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Duet2Wifi firmware flashing issue

    Firmware installation
    2
    5
    27
    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.
    • mgcrea
      mgcrea last edited by

      Hey all,

      I just received a Duet2Wifi that I tried to upgrade to v3.x via bossac USB, board was working on some v1.x revision on arrival and successfully connected to the wifi but got an HTTP error when tried to access the IP, thought an USB upgrade would be the quickest way, god was I wrong!!

      Anyway, I can switch the board to program mode and tried to flash the latest firmware 3.1.1 (Duet2CombinedFirmware.bin).

      Board does reboot and I can connect to it but M115 gives me "v1.0 May 10 2012 18:12:25"!! Not sure if there is some kind of fallback somewhere.

      What is strange is that I tried to flash V3.0, V2.0.5 & V1.21 and board does not seem to leave PROGRAM mode when using these images.

      Any ideas?

      Thanks!

      A Former User 1 Reply Last reply Reply Quote 0
      • A Former User
        A Former User @mgcrea last edited by

        @mgcrea said in Duet2Wifi firmware flashing issue:

        thought an USB upgrade would be the quickest way, god was I wrong!!

        and board does not seem to leave PROGRAM mode when using these images.

        you have removed the erase jumper before starting writing the update, and pressed the reset button after the write was complete?

        1 Reply Last reply Reply Quote 0
        • mgcrea
          mgcrea last edited by

          Yes I did remove the jumber and pressed reset, tried M997 S0 once connected to this "1.0" version but no luck so far.

          1 Reply Last reply Reply Quote 0
          • mgcrea
            mgcrea last edited by

            Found out my issue, was missing the --boot=1 flag (--help says its a default) but it finally worked once added to the bossac command.

            1 Reply Last reply Reply Quote 0
            • A Former User
              A Former User last edited by

              so just -b wasn't sufficient as pr the documentation?

              which version of bossac were you using?

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA