Networking examples

Tue Aug 15 18:10:02 UTC 2023

On Tue, Aug 15, 2023 at 11:57 AM Brett Sterling <
brett.sterling at odysseysr.com> wrote:

> Hello all!
>
> To get this out of the way prior to all of the requested debugging
> information - I don't need the legacy stack, any networking stack will do.
> I started with legacy because that was what was shown on the RTEMS
> documentation pages.  We're trying to integrate RTEMS into our system and I
> considered adding the networking stack that had some documentation a big
> enough effort without perhaps trying to integrate another network stack.
> But I'm absolutely glad to go with any suggestion.
>
>
> Now, onto the requested build failure information.
>
> Following
> https://docs.rtems.org/branches/master/legacy-networking/quick_start.html
>
> ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build
> 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc
> RTEMS Source Builder - Set Builder, 6 (8e568b2ca348 modified)
> warning: exe: absolute exe found in path: (__cmake) /usr/bin/cmake
> Build Set: 6/rtems-net-legacy
> config: tools/rtems-net-legacy-6.cfg
> error: config error: rtems-bsp.cfg:104: RTEMS tools not found
> (sparc-rtems6-gcc) found; Please check the --with-tools option or --prefix.
> Build FAILED
> Build Set: Time 0:00:00.012407
> Build FAILED
>
> The error information implies that '--prefix' should specify where the
> 'sparc-rtems6-gcc' should be located, so I tried something different
> (specifying where the build tools are located).
>

The prefix is where it will be installed. Normally${prefix}/bin/ will
contain your cross tools.

--rtems-tools path     : Path to an install RTEMS tool set

And your --with-rtems-bsp is just the architecture. It would need to be
something like sparc/leon3.

Have you built the tools? Is sparc-rtems6-gcc in your $PATH? Can you run
hello world?

And --host normally denotes the host os where you are building. You usually
want --target.

@Vijay should be able to confirm that for sure. I don't think I have built
the legacy stack this way recently.

> prefix=$HOME/src/Toolchains/osr_rtems_6_sparc 6/rtems-net-legacy
> --host=sparc-rtems6 --with-rtems-bsp=sparc
> RTEMS Source Builder - Set Builder, 6 (8e568b2ca348 modified)
> warning: exe: absolute exe found in path: (__cmake) /usr/bin/cmake
> Build Set: 6/rtems-net-legacy
> config: tools/rtems-net-legacy-6.cfg
> error: config error: rtems-bsp.cfg:131: RTEMS BSP not found
> (sparc-rtems6-sparc.pc); Please check the --with-rtems option or --prefix.
>
>
You have to build RTEMS and install it.  The dot pc file has a pattern like
this for the powerpc/psim BSP I had installed

/home/joel/rtems-work/tools/6/bsp-install/lib/pkgconfig/powerpc-rtems6-psim.pc

prefix to RTEMS
configure/install: /home/joel/rtems-work/tools/6/bsp-install/

Note that yours would be something like sparc-rtems6-leon3.pc.

> Build FAILED
> Build Set: Time 0:00:00.014283
> Build FAILED
>
> What I'm guessing is that the networking build still relies on everything
> being in the correct location, but the documentation doesn't indicate where
> the networking repository should be put and how the networking build fits
> in with the tools build and the application builds.  This is probably the
> information I'm currently lacking.  Then again, I may be missing something
> in the documentation that I erroneously overlooked.  If so, just let me
> know.
>
> The "Hello World" failure is documented in this ticket:
> https://devel.rtems.org/ticket/4927
>

OK. I dhave added Chris who I think wrote that section.

Can you build the rtems-examples from that repository?

--joel

>
> Thanks again in advance!
> Brett
>
>
>
> ------------------------------
> *From:* Joel Sherrill <joel at rtems.org>
> *Sent:* Tuesday, August 15, 2023 9:57 AM
> *To:* Brett Sterling <brett.sterling at odysseysr.com>
> *Cc:* users at rtems.org <users at rtems.org>; Vijay Kumar Banerjee <
> vijay at rtems.org>
> *Subject:* Re: Networking examples
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
> I add Vijay since he has been working with this.
>
> On Tue, Aug 15, 2023 at 9:27 AM Brett Sterling <
> brett.sterling at odysseysr.com> wrote:
>
> Hello all,
>
> My goal is to integrate networking into our RTEMS solution, so I started
> here: https://docs.rtems.org/branches/master/legacy-networking/index.html
> <https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Flegacy-networking%2Findex.html&data=05%7C01%7C%7Ca986447e0b18401e8d8108db9da85b8c%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638277118637201789%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=O7Cl3JjG1IGmeX5TzhEdb65bNPtvrK%2BF4Zzqtlw5Zhk%3D&reserved=0>
> .
>
> But, as soon as I had started, I hit a failure.  I tried the 'quick start'
> (https://docs.rtems.org/branches/master/legacy-networking/quick_start.html
> <https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Flegacy-networking%2Fquick_start.html&data=05%7C01%7C%7Ca986447e0b18401e8d8108db9da85b8c%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638277118637358041%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gCplMFshN695pxIZnLZlIxdIjfO9mkjZXsOzmm8R45s%3D&reserved=0>),
> but regardless of which way I tried to build, the build failed.
>
>
> Please post about that. This shouldn't happen.
>
> And Vijay has recent experience testing the legacy stack.
>
>
> Based on the failure of the 'quick-start' for the RTEMS "Hello World"
> example coupled with this failure, I'm starting to consider moving back to
> an older RTEMS version (I've seen networking information for both RTEMS 4 &
> 5), but first wanted to reach out to the user community to get input.
>
>
> Let's see how this failed.
>
>
> Optimally, I would like to find an RTEMS example (any version) *WITH
> NETWORKING* that runs on either an RTEMS simulator, or on a commercially
> available development board so that I can see networking working and then
> evolve it into my system.
>
>
> Do you really want the legacy stack or just a network stack?
>
>
>
> Less optimally, I would like to find an RTEMS example (any version) *WITH
> NETWORKING* that at least completely builds.
>
> If no one has examples of these, I would be glad to try different things
> to get the networking stuff building.  Especially if someone else can show
> that they can build with networking.
>
> Thanks in advance!
> Brett
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
> <https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7C%7Ca986447e0b18401e8d8108db9da85b8c%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638277118637358041%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=emkBfMPRDD5Ncf8xS7x%2BOB3hQwBUEpkMKEh9lK38Mx4%3D&reserved=0>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20230815/49adec3a/attachment.htm>