@Kruix yes, it's needed.

@mbtobeca that code was part of a bug fix commit cherry picked from the 3.5-dev branch into the 3.4-dev branch. Cherry picking commits from one branch to another sometimes causes these build issues. We pick them up next time we compile the 3.4-dev branch.

@EdChamberlain It's working but I've taken small breaks to build some other hardware.

The core of the SB2040 toolboard is working great. I am looking into I2C in order to add an LIS3DH accelerometer, but the I2C libs aren't wired up into the RP2040 yet.

I had a few issues with my environment and now can compile both the 3.5 code for RP2040 and Jay's branch.

Does anyone know when I2C might be ready to test on the RP2040? I'm digging around but I'm getting a little lost.

Good morning @droftarts,

I apologize for any mistakes I made in mentioning the electronics I was using during the tests. I thought it was important to include that information in the thread title, as I didn't intend to describe the problem. However, I have created a new thread with a more general title as I have more information to add and I find it difficult to express myself in English. Additionally, I sometimes struggle to select the correct categories.

Thank you for your understanding.

Best regards,
Aitor

Good morning @HERVE_SMITH and @PHAEDRUX,

I greatly appreciate your response, as it allowed me to solve my problem. The truth is that I was unaware of many of the parameters offered by M569. Thank you again.

Best regards,
Aitor

@dc42 We've been waiting over a year for this, so I figured I'd try to help.

@Thugmek No, there is no tool to do sync the OM definitions automatically. I guess you forgot to add your key to the Tool class and if not, perhaps you haven't updated the DCS build on your SBC yet.

@RonanLoberg you may want to look at the 3.5 branch. MAX31865 support has already been added in for toolboards so it may just be as easy as defining the pins correctly.

@dc42
Thanks for taking the time for this detailed response.
I appreciate that you've got better things to do than teach noobs.

@dc42 Thanks a lot! Now it compiles 👍

Vielen Danke jetzt weiß ich schon etwas mehr.
dann muss ich mich an Eclipse ran tasten.
Danke noch mal

Ok, it all works

I had to add the PATH in Eclipse.

Project > Properties > C/C++ Build > Environment

Not sure why I had to do that, since the application is accessible in a terminal window

@jml nevermind - I had to sign in in order for github to show Code results. Thanks!
(is there a way to mark this post solved?)

If this form of gcode parameter is generally adopted, it would give a wider range of uses. For example, you could pass a structure that includes a set of parameters and return values. As to me, this form is quite natural and corresponds to the usual way of passing a variable by reference. If I'm not mistaken, the current gcode interface and implementation of meta variables allow this without difficulty.

@dc42 Yes, i added ${EXTRA_FLAGS} in linker command but it did not fix the issue.

I'm having a similar issue, noting that we have to build picosdk, I followed the instructions linked above and I continually get this error (amongst others) but I'll start here...

I should have the pre-reqs done and when I run make-libpico.bat I get errors:

C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk>make-libpico.bat C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk>rmdir /S /Q build The system cannot find the file specified. C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk>mkdir build C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk>cd build C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk\build>cmake .. -DIPV6=0 -G "MSYS Makefiles" PICO_SDK_PATH is C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/pico-sdk Defaulting PICO_PLATFORM to rp2040 since not specified. Defaulting PICO platform compiler to pico_arm_gcc since not specified. -- Defaulting build type to 'Release' since not specified. PICO compiler is pico_arm_gcc -- The C compiler identification is GNU 10.3.1 -- The CXX compiler identification is GNU 10.3.1 -- The ASM compiler identification is GNU -- Found assembler: C:/Program Files (x86)/GNU Arm Embedded Toolchain/10 2021.10/bin/arm-none-eabi-gcc.exe Build type is RelWithDebInfo PICO target board is pico. Using board configuration from C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/pico-sdk/src/boards/include/boards/pico.h -- Found Python3: C:/msys64/usr/bin/python3.10.exe (found version "3.10.9") found components: Interpreter TinyUSB available at C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/pico-sdk/lib/tinyusb/src/portable/raspberrypi/rp2040; enabling build support for USB. cyw43-driver available at C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/pico-sdk/lib/cyw43-driver lwIP available at C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/pico-sdk/lib/lwip -- Configuring done -- Generating done -- Build files have been written to: C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/Tools/Build-pico-sdk/build C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk\build>set OLDPATH=C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\windows\System32\OpenSSH\;C:\Program Files\PuTTY\;C:\Program Files\Microchip\xc8\v2.36\bin;C:\Program Files\Git\cmd;C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2021.10\bin;C:\Program Files\GNU ARM Eclipse\Build Tools\2.6-201507152002\bin;C:\Users\Chris Thompson\AppData\Local\Microsoft\WindowsApps;C:\msys64\mingw64\bin;C:\msys64\usr\bin C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk\build>PATH C:\msys64\usr\bin;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\windows\System32\OpenSSH\;C:\Program Files\PuTTY\;C:\Program Files\Microchip\xc8\v2.36\bin;C:\Program Files\Git\cmd;C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2021.10\bin;C:\Program Files\GNU ARM Eclipse\Build Tools\2.6-201507152002\bin;C:\Users\Chris Thompson\AppData\Local\Microsoft\WindowsApps;C:\msys64\mingw64\bin;C:\msys64\usr\bin C:\Users\Chris Thompson\git\CoreN2G\src\RP2040\Tools\Build-pico-sdk\build>c:\msys64\usr\bin\make -j [[ 2 %2]% ] CreBautiilndgi ndgi rAeScMt oorbijeesc tf opri c'o-Psidoka/ssmrBcu/irlpd2'_c ommon/boot_stage2/CMakeFiles/bs2_default.dir/compile_time_choice.S.obj [ 3%] Linking ASM executable bs2_default.elf [ 4%] No download step for 'PioasmBuild' [ 5%] No update step for 'PioasmBuild' [ 5%] Built target bs2_default [ 6%] No patch step for 'PioasmBuild' [ 7%] Generating bs2_default.bin [ 8%] Performing configure step for 'PioasmBuild' [ 10%] Generating bs2_default_padded_checksummed.S loading initial cache file C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/Tools/Build-pico-sdk/build/pico-sdk/src/rp2_common/cyw43_driver/pioasm/tmp/PioasmBuild-cache-RelWithDebInfo.cmake /C/msys64/usr/bin/python3.10: can't open file '/C/Users/Chris Thompson/git/CoreN2G/src/RP2040/Tools/Build-pico-sdk/build/pico-sdk/src/rp2_common/boot_stage2/C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/pico-sdk/src/rp2_common/boot_stage2/pad_checksum': [Errno 2] No such file or directory make[2]: *** [pico-sdk/src/rp2_common/boot_stage2/CMakeFiles/bs2_default_padded_checksummed_asm.dir/build.make:73: pico-sdk/src/rp2_common/boot_stage2/bs2_default_padded_checksummed.S] Error 2 make[1]: *** [CMakeFiles/Makefile2:1460: pico-sdk/src/rp2_common/boot_stage2/CMakeFiles/bs2_default_padded_checksummed_asm.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... -- The CXX compiler identification is GNU 11.3.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: C:/msys64/usr/bin/c++.exe - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done -- Generating done -- Build files have been written to: C:/Users/Chris Thompson/git/CoreN2G/src/RP2040/Tools/Build-pico-sdk/build/pioasm [ 11%] Performing build step for 'PioasmBuild' [ 10[% ] 2[0B%u ]i3 l0[Bd %[ui5nil ]g0 [ %]5 6 0%C0BBd]X%uui X]iinB ldguolBi nbduiCgjiinX ClldXX dXioeig nbcn ogjt Cb eg CXCcjXXXt C oXMb ajokebecjFtei clCteM saC/keFiMplCeXaies/pkoMc ieasm.oFdaii[rls /mt 7age.o[C0kedsb M%eni/j8a]F/rpe0k ip/ic%elBagot]Feurea isisnsCl/Ble/mMepudrl.asiii.edk/eldcxiopaiiperFnsonpr/igmag..cl .s oCbeCdmc_XjsXi.psX /Xrdpd p /i.koiomro_boba/bpjasimji jno.ueoe.[dtc_cc pptats9pu.i s0 torCe%C.b/Mm]M apabclkBikjpe uoeperi_F.F.ldioicdilblpiseepjnass. gs//o bppiCjX oisXaoeas msbommlb..ejddreii.cctrrp //pChp.Meyoaxtbk_hon_output.cepp.obj ojF uitlpeust/.pcipopa.somb.jd ir/ada_output.cpp.obj [100%] Linking CXX executable pioasm.exe [100%] Built target pioasm [ 12%] No install step for 'PioasmBuild' [ 13%] Completed 'PioasmBuild' [ 13%] Built target PioasmBuild make: *** [Makefile:91: all] Error 2

Any ideas?

@Thugmek with regard to your first question, the Debug build configurations of RRF leave the SWD pins for SWD use. So you should use the Duet3_Debug build configuration for debugging.

The Debug build configurations also enable generation of debug information in the compiler settings, which may go some way towards addressing your second question.

@achrn thanks for reporting this, it is now fixed in the RRF 3.5 source code.