Hi!
Just in case it might be useful for somebody else. For me, building for Duet2 required explicit copying DuetWiFiSocketServer/src/include/MessageFormats.h to RepRapFirmware/src/, although that was outlined in the official build manual as an optional action. Building for Duet3 did not required that action and went smoothly in the same Workspace in Eclipse (version 3.4-dev)
Hi, our little company still uses RRF2.05.1 in our printers. We have been using precompiled binaries so far. Now we need now to make small changes in the basic code.
Unlike the 3.x family, it turned out to be a more complicated task, since there are no specific version tags in other projects than the main RRF, at least if I'm not missing anything. By trials and errors, I found such a combination of commits, which is compiled without errors. Can anybody confirm if this more or less corresponds to the original precompiled binary from release 2.05.1, or how can I check that?
CoreNG: 55dfcf0441adf01ab7bc2ae6a638e395ef018595, 10.12.2019, 17:09:25
FreeRTOS: 83d87c0f61618f5a471f2d52ca75590d67c7a616, 25.01.2020, 13:55:26
RRFLibraries: c3b754a423ce8eb67958c77a8afe54fc5755ae15, 6.01.2020, 22:13:13
RepRapFirmware: eec61ee0d5df8d3b4b556e8854216cee2038f045, tag "2.05.1", 9.02.2020, 13:41:34
Thank you
@dc42 Sorry for the late response, I've needed to switch to some other tasks. Will come back to the topic within two weeks, and if you'll be able to continue then - it would be great! Thank you. Artem
@dc42 Thank you for the reply! My main concerns were about RRFLibraries, because in there the commits made between 6 Jan and 9 Feb (the date of main RRF project's tag 2.05.1) are not compilable =( So the question is, could it be so that those changes were not included in the official binary, or am I missing something else.
Hi, our little company still uses RRF2.05.1 in our printers. We have been using precompiled binaries so far. Now we need now to make small changes in the basic code.
Unlike the 3.x family, it turned out to be a more complicated task, since there are no specific version tags in other projects than the main RRF, at least if I'm not missing anything. By trials and errors, I found such a combination of commits, which is compiled without errors. Can anybody confirm if this more or less corresponds to the original precompiled binary from release 2.05.1, or how can I check that?
CoreNG: 55dfcf0441adf01ab7bc2ae6a638e395ef018595, 10.12.2019, 17:09:25
FreeRTOS: 83d87c0f61618f5a471f2d52ca75590d67c7a616, 25.01.2020, 13:55:26
RRFLibraries: c3b754a423ce8eb67958c77a8afe54fc5755ae15, 6.01.2020, 22:13:13
RepRapFirmware: eec61ee0d5df8d3b4b556e8854216cee2038f045, tag "2.05.1", 9.02.2020, 13:41:34
Thank you
@jazbaatbadalgaye sorry for late response, I used CoreN2G
Hi!
Just in case it might be useful for somebody else. For me, building for Duet2 required explicit copying DuetWiFiSocketServer/src/include/MessageFormats.h to RepRapFirmware/src/, although that was outlined in the official build manual as an optional action. Building for Duet3 did not required that action and went smoothly in the same Workspace in Eclipse (version 3.4-dev)
@dc42 Thank you! That's answered my question.
@oliof said in Firmware's entry point:
@arplyu check out the FreeRTOS library which provides the entry point as far as I understand.
That's also a useful hint, I definitely should pay more attention to FreeRTOS. Thank you!
Hi everyone
I'd like to study RepRapFirmware to (possibly) add some modifications in it in the future. I am sorry for a stupid question, but where is the entry point to the firmware? I was looking for a traditional C/C++' "int main()" or "int loop()" (as in Arduino's programs) function, but couldn't find it. I couldn't find this info on the forum neither. Thank you.