Issue Using S3 Dev Kit with Eclipse After Updating Toolchain

[RoseBL]

Hi everyone,
I’m currently working with the QuickLogic S3 Dev Kit, and after updating my RISC-V toolchain to the latest version, Eclipse (from the EOS S3 SDK package) no longer recognizes the build environment. Has anyone experienced this mismatch before? More specifically, is there a recommended toolchain version that ensures full compatibility with the EOS S3 Eclipse setup? Any guidance would be greatly appreciated!

[TrevorMorin]

You may be seeing this because the newer RISC-V toolchain isn’t fully compatible with the EOS S3 Eclipse bundle. The SDK is known to work best with the older toolchain version included in the original package. I’d recommend reverting to that version or using the one specified in the SDK docs. This should restore proper detection in Eclipse.

[smithjohns]

Hi! The EOS S3 Eclipse setup works best with the toolchain included in the SDK. Updating to a newer RISC-V version can break recognition. For full compatibility, stick with the SDK-provided toolchain or manually adjust Eclipse paths, though that may cause build issues.

[Mayarivers]

Hi everyone,
I’m currently working with the QuickLogic S3 Dev Kit, and after updating my RISC-V toolchain to the latest version, Eclipse (from the EOS S3 SDK package) no longer recognizes the build environment. Has anyone experienced this mismatch before? More specifically, is there a recommended toolchain version that ensures full compatibility with the EOS S3 Eclipse setup? Any guidance would be greatly appreciated!

More specifically, is there a recommended toolchain version that ensures full compatibility with the EOS S3 Eclipse setup? Any guidance would be greatly appreciated!