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

    Need eclipse build help

    Scheduled Pinned Locked Moved
    Firmware installation
    3
    5
    795
    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.
    • kazolarundefined
      kazolar
      last edited by

      I followed the steps to setup the environment and seems right, but I am running into an issue:
      13:08:33 **** Incremental Build of configuration SAM4E8E for project CoreNG ****
      make all
      process_begin: CreateProcess(C:\Users\Server\AppData\Local\Temp\make8732-1.bat, C:\Users\Server\AppData\Local\Temp\make8732-1.bat, …) failed.
      make (e=267): The directory name is invalid.

      make: *** [variants/duetNG/exceptions.o] Error 267

      I have the path defined correctly I am ale to build duetNG from command line

      this happens if I build from eclipse

      if I open a command prompt and run my env.bat
      set PATH=C:\Arduino-1.5.8\hardware\arduino\sam\system\CMSIS\Examples\cmsis_example\gcc_arm;C:\Arduino-1.5.8\hardware\tools\gcc-arm-none-eabi-4.8.3-2014q1\bin

      then go to
      C:\eclipse\Firmware\CoreNG\SAM4E8E
      and run make all – it works.

      I have the same problem with build RepRapFirmware in eclipse
      make all
      process_begin: CreateProcess(C:\eclipse\Firmware\RepRapFirmware\DuetEthernet\make11596-1.bat, C:\eclipse\Firmware\RepRapFirmware\DuetEthernet\make11596-1.bat, ...) failed.
      make (e=267): The directory name is invalid.

      when I try to build
      from commandline:

      I tried exporting the command line arguments
      set LINK_FLAGS_1=-mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolved-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group
      set LINK_FLAGS_2=-Wl,--end-group -lm -gcc

      then run make all -- it runs to a point and then
      it gives an error:
      'Building target: DuetEthernetFirmware.elf'
      'Invoking: Cross G++ Linker'
      arm-none-eabi-gcc -L"C:\eclipse\Firmware\CoreNG\SAM4E8E" -Os -Wl,--gc-sections -Wl,--fatal-warnings -mcpu=cortex-m4 -TC:\eclipse\Firmware\CoreNG\variants\duetNG\linker_scripts\gcc\flash.ld -Wl,-Map,C:
      \eclipse\Firmware\RepRapFirmware\DuetEthernet/DuetEthernetFirmware.map -o "DuetEthernetFirmware.elf" -mthumb -Wl,--cref -Wl,--check-sections -Wl,--gc-sections -Wl,--entry=Reset_Handler -Wl,--unresolv
      ed-symbols=report-all -Wl,--warn-common -Wl,--warn-section-align -Wl,--warn-unresolved-symbols -Wl,--start-group ./src/Tools/Filament.o ./src/Tools/Tool.o ./src/Storage/FileStore.o ./src/Storage/Ma
      ssStorage.o ./src/Movement/Kinematics/CartesianKinematics.o ./src/Movement/Kinematics/CoreBaseKinematics.o ./src/Movement/Kinematics/CoreXYKinematics.o ./src/Movement/Kinematics/CoreXYUKinematics.o .
      /src/Movement/Kinematics/CoreXZKinematics.o ./src/Movement/Kinematics/Kinematics.o ./src/Movement/Kinematics/LinearDeltaKinematics.o ./src/Movement/Kinematics/ScaraKinematics.o ./src/Movement/BedProb
      ing/Grid.o ./src/Movement/BedProbing/RandomProbePointSet.o ./src/Movement/DDA.o ./src/Movement/DriveMovement.o ./src/Movement/Move.o ./src/Libraries/sha1/sha1.o ./src/Libraries/Math/Isqrt.o ./src/
      Libraries/General/StringRef.o ./src/Libraries/Fatfs/ccsbcs.o ./src/Libraries/Fatfs/diskio.o ./src/Libraries/Fatfs/fattime_rtc.o ./src/Libraries/Fatfs/ff.o ./src/Heating/Sensors/CpuTemperatureSensor.
      o ./src/Heating/Sensors/CurrentLoopTemperatureSensor.o ./src/Heating/Sensors/RtdSensor31865.o ./src/Heating/Sensors/SpiTemperatureSensor.o ./src/Heating/Sensors/TemperatureSensor.o ./src/Heating/Senso
      rs/Thermistor.o ./src/Heating/Sensors/ThermocoupleSensor31855.o ./src/Heating/Sensors/ThermocoupleSensor31856.o ./src/Heating/Sensors/TmcDriverTemperatureSensor.o ./src/Heating/FOPDT.o ./src/Heating/
      Heat.o ./src/Heating/Pid.o ./src/Heating/TemperatureError.o ./src/GCodes/GCodeBuffer.o ./src/GCodes/GCodeInput.o ./src/GCodes/GCodeMachineState.o ./src/GCodes/GCodeQueue.o ./src/GCodes/GCodes.o ./src
      /GCodes/GCodes2.o ./src/GCodes/RestorePoint.o ./src/DuetNG/DuetEthernet/Wiznet/Internet/DHCP/dhcp.o ./src/DuetNG/DuetEthernet/Wiznet/Ethernet/W5500/w5500.o ./src/DuetNG/DuetEthernet/Wiznet/Ethernet
      /WizSpi.o ./src/DuetNG/DuetEthernet/Wiznet/Ethernet/socketlib.o ./src/DuetNG/DuetEthernet/Wiznet/Ethernet/wizchip_conf.o ./src/DuetNG/DuetEthernet/Network.o ./src/DuetNG/DuetEthernet/Socket.o ./src/
      DuetNG/DueXn.o ./src/DuetNG/FirmwareUpdater.o ./src/DuetNG/FtpResponder.o ./src/DuetNG/HttpResponder.o ./src/DuetNG/NetworkBuffer.o ./src/DuetNG/NetworkResponder.o ./src/DuetNG/SX1509.o ./src/DuetNG/T
      MC2660.o ./src/DuetNG/TelnetResponder.o ./src/Fan.o ./src/OutputMemory.o ./src/Platform.o ./src/PortControl.o ./src/PrintMonitor.o ./src/RepRap.o ./src/RepRapFirmware.o ./src/Roland.o ./src/Scanner.o
      -lCoreNG -Wl,--end-group -lm -gcc
      c:/arduino-1.5.8/hardware/tools/gcc-arm-none-eabi-4.8.3-2014q1/bin/../lib/gcc/arm-none-eabi/4.8.3/../../../../arm-none-eabi/lib/armv7e-m\libg.a(lib_a-sbrkr.o): In function _sbrk_r': sbrkr.c:(.text._sbrk_r+0xc): warning: undefined reference to _sbrk'
      collect2.exe: error: ld returned 1 exit status
      make: *** [DuetEthernetFirmware.elf] Error 1

      I saw this brought up elsewhere, bu I can't seem to figure out what I'm doing wrong.

      1 Reply Last reply Reply Quote 0
      • kazolarundefined
        kazolar
        last edited by

        Just re-did everything and it worked. No idea what I changed.

        Now works fine in eclipse – spent a good while trying to get it to work -- no dice...just changed path -- and works!

        1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators
          last edited by

          A few others have hit the undefined _sbrk issue, there is another thread about how to get around this.

          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 0
          • kazolarundefined
            kazolar
            last edited by

            dc42:
            no idea what I did wrong the first time – but it compiles now -- started making changes to the firmware -- I started another thread with what I'm changing -- if it makes sense I'd like to contribute to the code. (I'm a programmer in my day job with 20 years experience) -- just trying to wrap my head around the logic. I've made modifications to my smoothieware firmware based delta by adding an independent Z axis gantry for a platform to wipe the extruder between color changes, so I can generally figure my way around, so I don't have any doubts I'll get the dual-y quad X IDEX setup working. The kinematics build is done, so now it's about wiring and firmware.

            1 Reply Last reply Reply Quote 0
            • FrankNPrinterundefined
              FrankNPrinter
              last edited by

              might try a much shorter path statement. some apps struggle with long paths and especially any sort of space or wild characters(like under score above) in path statement. Anyone beside me remember the old DOS days ? LOL

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