@jay_s_uk Sorry, I meant to say I know this isn't a supported board. I have the board that is made for vorons running klipper and I was hoping to install the duet firmware on it. I thought people were doing this...
@Behrouz-AKT I think you have the wrong version of the DuetWiFiSocketServer project in your workspace. You don't need to build that project but you do need the correct version of the MessageFormats.h file in that project.
@Mohammad I'm glad you got it building. The API to nano-mallocr in associated the C library changed between gcc versions, so the substitute we provide in the 3.4-dev branch doesn't work with gcc 12. In the 3.5-dev branch we changed it to suit the later version of the library.
@dc42 Ah, gotcha. I hadn't thought of doing it that way probably because all of my other Eclipse based projects (I've got about 25 of them) use the Eclipse builder to just run make or ninja, etc. on existing build scripts. Since 3.3 is EOL and you're planning to move 3.4 to gcc 12.2 anyway, it'snot really an issue any more. If it becomes one for 3.6 or later versions I can easily do the separate workspace thing as you do.
@DDD bear in mind that C++ for embedded processors is not the same as C++ for desktop machines and servers. In particular, use of dynamic memory is minimised, so most of the STL classes are avoided.
I think you are using an old version of project DuetWiFiSocketServer. Use the dev branch of that project.
It worked, I used the master branch, and when I selected DEV it compiled. There are 2 errors, but as I understand it, this is no longer a problem, since compilation of this file is not necessary.
alt text
alt text
@ldandoy I kicked out axios a long time ago because it's too buggy IMO (especially when dealing with CORS). From where are you trying to send that request? The underlying backend of the web server in SBC mode is Kestrel (ASP.NET Core).
@dc42 Found the solution, I didn't realize this earlier but the Toolboard firmware I was using had actually been modified by a coworker. We bought a new toolboard and tried to connect CAN (thinking maybe an IC had been fried) and it worked, so we copied that firmware onto the toolboard I had been using and sure enough, works fine. So it was a software issue. Thanks for your help!
@dc42 thank you for the reply. I use commits with tag "3.4.4" in all projects. Non-debug config from the same commits compiles without any problems, I used that as a start point for my modifications.
PS At the same time, checking out 3.4-dev branches at latest commits in all projects works fine - I managed to compile debug config and test the hardware, everything was ok.
