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

    How to compile the version 3.4 input shaping?

    Scheduled Pinned Locked Moved
    Firmware developers
    3
    5
    351
    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.
    • jazbaatbadalgayeundefined
      jazbaatbadalgaye
      last edited by jazbaatbadalgaye

      I was able to compile the firmware and generate the bin files for the RepRapFirmware-3.4-dev. However when I replace the RepRapFirmware-3.4-dev folder with RepRapFirmware-3.4-input-shaping (and keeping everything same) I cannot compile.

      Can someone tell me how to compile RepRapFirmware-3.4-input-shaping or any other branch which implements input shaping

      PS : I did rename them to RepRapFirmware before compiling

      The log :

      Invoking: Cross G++ Compiler
      arm-none-eabi-g++ -std=gnu++17 -D__SAME70Q20B__ -DRTOS -DDUET3_V06 -D_XOPEN_SOURCE -DUSE_CAN0 -I"C:\Eclipse\Firmware\CoreN2G" -I"C:\Eclipse\Firmware\CoreN2G\src" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf\common\utils" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf\sam\utils\cmsis\same70\include" -I"C:\Eclipse\Firmware\CoreN2G\src\arm\CMSIS\5.4.0\CMSIS\Core\Include" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\SAME70" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf\sam\utils" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf\sam\utils\preprocessor" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf\sam\utils\header_files" -I"C:\Eclipse\Firmware\CoreN2G\src\SAM4S_4E_E70\asf\sam\drivers" -I"C:\Eclipse\Firmware\RepRapFirmware\src" -I"C:\Eclipse\Firmware\RepRapFirmware\src\Hardware\SAME70" -I"C:\Eclipse\Firmware\RepRapFirmware\src\Networking" -I"C:\Eclipse\Firmware\RepRapFirmware\src\Networking\LwipEthernet\Lwip" -I"C:\Eclipse\Firmware\RepRapFirmware\src\Networking\LwipEthernet\Lwip\src\include" -I"C:\Eclipse\Firmware\DuetWiFiSocketServer\src\include" -I"C:\Eclipse\Firmware\FreeRTOS\src\include" -I"C:\Eclipse\Firmware\FreeRTOS\src\portable\GCC\ARM_CM7\r0p1" -I"C:\Eclipse\Firmware\RRFLibraries\src" -I"C:\Eclipse\Firmware\CANlib\src" -O2 -Wall -c -mcpu=cortex-m7 -mthumb -mfpu=fpv5-d16 -mfloat-abi=hard -ffunction-sections -fdata-sections -fno-threadsafe-statics -fno-rtti -fexceptions -nostdlib -Wundef -Wdouble-promotion -Werror=return-type -Wsuggest-override -fsingle-precision-constant "-Wa,-ahl=OutputMemory.s" -fstack-usage -MMD -MP -MF"src/Platform/OutputMemory.d" -MT"src/Platform/OutputMemory.o" -o "src/Platform/OutputMemory.o" "../src/Platform/OutputMemory.cpp"
      ../src/Storage/FileInfoParser.cpp: In member function 'GCodeResult FileInfoParser::GetFileInfo(const char*, GCodeFileInfo&, bool)':
      ../src/Storage/FileInfoParser.cpp:28:6: error: no match for 'operator!' (operand type is 'MutexLocker')
         28 |  if (!lock)
            |      ^~~~~
      ../src/Storage/FileInfoParser.cpp:28:6: note: candidate: 'operator!(bool)' (built-in)
      ../src/Storage/FileInfoParser.cpp:28:6: note:   no known conversion for argument 1 from 'MutexLocker' to 'bool'
      src/Storage/subdir.mk:33: recipe for target 'src/Storage/FileInfoParser.o' failed
      make[1]: *** [src/Storage/FileInfoParser.o] Error 1
      make[1]: *** Waiting for unfinished jobs....
      Finished building: ../src/Storage/FileStore.cpp
       
      Finished building: ../src/Tools/Tool.cpp
      
      dc42undefined 1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @jazbaatbadalgaye
        last edited by

        @jazbaatbadalgaye the 3.4-input-shaping branch is obsolete now. Use 3.4-dev.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 1
        • jazbaatbadalgayeundefined
          jazbaatbadalgaye
          last edited by

          @dc42 Thanks! That compiled for Duet2 config (where I used CoreN2G-3.4-dev) but it fails for Duet 3 config where I used CoreNG-dev. Can you please suggest what version of CoreNG compatiable with RepRapFirmware 3.4 dev?

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @jazbaatbadalgaye
            last edited by

            @jazbaatbadalgaye everything uses coreN2G in 3.4

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            jazbaatbadalgayeundefined 1 Reply Last reply Reply Quote 3
            • jazbaatbadalgayeundefined
              jazbaatbadalgaye @jay_s_uk
              last edited by jazbaatbadalgaye

              @jay_s_uk Thanks! That worked like a charm however I had to include CoreESP8266 and LwipESP8266 in the working directory. @dc42 mentioned in another thread that those files are required if you're building DuetWiFiSocketServer but it gave me errors when I was trying to build CoreN2G-3.4-dev. The build errors were mitigated when I included CoreESP8266 and LwipESP8266 in working directory.

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