RTEMS Contribution Submission – Devagya Rattan – Documentation Update / Hello World Sample

Programs Google Summer of Code
1
  • Name: Devagya Rattan
  • GitLab Username: Devagya18

I have successfully completed the mandatory task:

  • Architecture: SPARC
  • BSP: erc32

Hello World Output:

Rtems1122
Rtems11221837×1042 98.8 KB

Patch Screenshot:
Patch11
Patch111047×797 120 KB

  • Additional Contribution Summary

Clarify why RTEMS requires the rtemsX-gcc cross-compiler

New users occasionally try to build RTEMS applications using standard cross-compilers from their Linux distributions (for example, riscv64-linux-gnu-gcc or arm-none-eabi-gcc) and find that the build fails. This happens because RTEMS requires a specially configured toolchain, rtemsX-gcc, which is tailored for the RTEMS environment.

The reasons for using rtemsX-gcc include:

  1. Newlib Configuration: Ensures that the C standard library is correctly configured for RTEMS, providing proper POSIX support, libc functions, and system calls. Generic cross-compilers lack these RTEMS-specific configurations.
  2. Threading Support: GCC support libraries are configured for RTEMS threading models. Using a standard cross-compiler can result in incorrect or missing threading behavior.
  3. Preprocessor Definitions: Automatically sets macros like __rtems__ required for RTEMS code and libraries.
  4. Other RTEMS-Specific Features: Ensures proper linking, startup code, and low-level system support.

In summary, the rtemsX-gcc cross-compiler is required to reliably build RTEMS applications. Using a generic distribution cross-compiler will usually fail or produce unexpected behavior due to missing RTEMS-specific configurations.
Merge Request-clarify RTEMS, Newlib, and GCC cross-compiler roles (!213) · Merge requests · RTEMS / Documentation / Documentation · GitLab

GSOC 2026
I am planning to work on Issue #5312: MicroShell port to integrate MicroShell as an alternative shell for RTEMS. The goal is to get MicroShell running with its built-in commands first, ensuring it functions correctly within the RTEMS environment. Once the baseline is working, porting the existing RTEMS commands to MicroShell can be addressed as a separate step. This contribution will provide RTEMS users with an additional lightweight shell option and improve flexibility for RTEMS applications.

2

my updated Patch file

image
image845×604 73.6 KB

3

hi, it looks like your name is incorrect in your git config user.name. Please fix that, and you can add yourself to tracking/2026 · main · RTEMS / Programs / Google Summer of Code · GitLab

You can start a separate topic to discuss the MicroShell port project idea.

4

i need to add username for as per rtems gitlab username right?

5

No, you should provide a legal name as your git config user.name, this is how we track author attribution and confirm copyright.