How to build the bin file?

dc42

@Jimmykc said in How to build the bin file?:

I don’t know what the meaning of “Then clean and build RepRapFirmware (the clean step is needed to make Eclipse notice that the output library files in the other projects have been built)” is.

Right click on the project and select Clean form the drop-down menu.

Jimmykc

@dc42 I refer to your suggestions, but I have a questions.

Do I need to import to the file “DuetWiFiSocketServer” if I want to use Duet3 MB6HC and expansion board 3HC as a standalone board. (No Pi) ?

dc42

You don't need DuetWiFiSocketServer to build Duet 3 firmware.

Latest RRF 3.01-RC source is currently on branch v3.01-dev of RepRapFirmware. The v3 branch is a few commits older.

Jimmykc

@dc42 I import the v3.01-dev of RepRapFirmware.
I right click on the project and select build configuration -> Set Active -> Duet3_V06_CAN0.

I build it, but I fail.
log.txt

dc42

The versions of the CoreNG and RepRapFirmware projects you are using are slightly mismatched. Try updating both of them.

Jimmykc

@dc42 I update CoreNG and RepRapFirmware projects. The previous problem has be fixed but show a new error.

log2.txt

I re-build the project again, and the error will not appear.

dc42

You can find crc32appender.exe under the Tools folder of the RepRapFirmware repository. Copy it on to your PC and add it to the PATH.

Jimmykc

@dc42 I paste the crc32appender.exe on my path.

I fixed all problems. Thank you, but I have the last question.
Is the bin file for main board if I select build configuration -> Set Active -> Duet3_V06?
Is the bin file for expansion board if I select build configuration -> Set Active -> Duet3_V06_CAN0 ?

dc42

The _CAN0 one is just a test configuration so that we can test the second CAN port, which the standard firmware doesn't use. Use the Duet3_V06 configuration.

To build expansion board firmware, import project Duet3Expansion into your workspace and build that project.

Jimmykc

@dc42 Now I know how to build the bin file. Thanks you so much.

arhi

@dc42 this still stands for RRF3.1 ?

to build firmware version 2.03beta3 and later use version 2018-q4-major

or you moved to 2020 version maybe?

dc42

For 3.1.1 I used version 9-2019q4-major. But I see that 9-2020-q2-update is now available, so I'll probably switch to that for 3.2.

arhi

@dc42 nice, I recompiled it on mac, was faster to get everything up and running without messing out working envinronments for other stuff on my main win desktop and compiling is fast enough that the speed of the mac is not that important .. brew is a nice addon to osx .. brew installs (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599] so exactly what you say you are using for 3.1.1 and the issue is only with src/GCodes/GCodeBuffer/ExpressionParser.cpp the conv.Accumulate is called with wrong number of parameters .. probbly ReprapFirmware:v3-dev vs RRFLibraries:dev at point I was doing a clone were out of sync (I see that whole section is new) ... I just needed to do the quick read of the ADC so I removed that whole section and compiled without a problem .. got data I needed I returned release 3.1.1. ..

I moved to 2020 myself for few projects and so far did not notice any issues