Gedare, Thanks for pointing out that I wasn't specifying a BSP - I will try that later today/tomorrow, along with any other suggestions, and respond. Definitely could be an issue : - )
Thanks, Brett ________________________________ From: Gedare Bloom <ged...@rtems.org> Sent: Thursday, August 17, 2023 8:57 AM To: Brett Sterling <brett.sterl...@odysseysr.com> Cc: Vijay Kumar Banerjee <vi...@rtems.org>; RTEMS Users RTEMS <users@rtems.org>; Chris Johns <chr...@rtems.org> Subject: Re: Networking examples [You don't often get email from ged...@rtems.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] 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. On Thu, Aug 17, 2023 at 8:54 AM Gedare Bloom <ged...@rtems.org> wrote: > > hi Brett, > > On Thu, Aug 17, 2023 at 8:12 AM Brett Sterling > <brett.sterl...@odysseysr.com> wrote: > > > > Hello all, > > > > So I tried a bunch of things and none have worked: > > > > ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build > > 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc > > error: config error: rtems-bsp.cfg:104: RTEMS tools not found > > (sparc-rtems6-gcc) found; Please check the --with-tools option or --prefix. > > > > ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build > > 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc > > --rtems-tools=$HOME/src/Toolchains/osr_rtems_6_sparc > > error: config error: rtems-bsp.cfg:131: RTEMS BSP not found > > (sparc-rtems6-sparc.pc); Please check the --with-rtems option or --prefix. > > > > (so I changed '--with-rtems-bsp=sparc' to '--with-rtems=sparc':) > > ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build > > 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems=sparc > > --rtems-tools=$HOME/src/Toolchains/osr_rtems_6_sparc > > error: config error: rtems-bsp.cfg:51: No RTEMS BSP specified: > > --with-rtems-bsp=bsp > > > > So I tried with both arguments: > > ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build > > 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc > > --rtems-tools=$HOME/src/Toolchains/osr_rtems_6_sparc --with-rtems=sparc > > error: config error: rtems-bsp.cfg:131: RTEMS BSP not found > > (sparc-rtems6-sparc.pc); Please check the --with-rtems option or --prefix. > > > > > > NOTE that all of these options had the sparc tools in the path: > > ~/src/rtems-development/rtems-tools/rtems-source-builder/rtems-net-legacy$ > > echo $PATH > > /home/bsterling/.nvm/versions/node/v16.20.0/bin:/home/bsterling/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/bsterling/src/Toolchains/osr_rtems_6_sparc:/home/bsterling/src/Toolchains/osr_rtems_6_sparc/bin > > > > I understand you are following along > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Flegacy-networking%2Fquick_start.html&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zScqSMWXcMVHIxbW6UN1xLBcSTscuPEN0hO90xfD7Os%3D&reserved=0 > > In there is the command: > ../source-builder/sb-set-builder \ > --prefix=/path/to/rtems/prefix \ > 6/rtems-net-legacy \ > --host=powerpc-rtems6 \ > --with-rtems-bsp=beatnik > > I see you are trying to do this for sparc6, but what BSP are you > wanting to use? "beatnik" is a powerpc BSP. Note: this command example > is wrong with RSB for rtems6, as the --with-rtems-bsp now takes an > arch/bsp pair. @Vijay Kumar Banerjee can you fix? > > The corrected command for you should be something like: > ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build > 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=?? > > "sparc" is not a BSP. I think that you can use --with-rtems to try to > build all the bsps. > Referring to the (other) quick start: > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Fuser%2Fstart%2Fbsp-build.html%23rsb-bsp-build&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WXR08F9QrZEX1Ow0Lp70xgaIb%2Bmz5wo%2FVKJCZylgTzA%3D&reserved=0 > > So, maybe, you want --with-rtems-bsp=sparc/leon3 > You can also specify multiple bsps to build. > > I don't think that "--with-rtems" is a valid command line option to > use. I guess RSB should be a little more noisy about unknown command > line options. > > So, try: > ../source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build > 6/rtems-net-legacy --host=sparc-rtems6 --with-rtems-bsp=sparc/leon3 > Actually, it might be --rtems-bsp= instead of --with-rtems-bsp= I think --rtems-bsp=sparc/leon3 will parse it out to --target=sparc-rtems6 --with-rtems-bsp=leon3 --with-rtems-arch=sparc So, you might try ./source-builder/sb-set-builder --prefix=$HOME/src/rtems-net-build \ 6/rtems-net-legacy --host=sparc-rtems6 --rtems-bsp=sparc/leon3 > > > > I look forward to any further suggestions. By the way, as I mentioned, I > > followed the 'Quick Start' procedure in order to get things working (with > > the one issue mentioned before). I have not yet found a full procedure for > > adding in the networking repositorye. We have to use rtems 6 because we > > want C++17 support. > > > > Thanks again in advance. > > > > Brett > > > > > > > > > > > > ________________________________ > > From: Vijay Kumar Banerjee <vi...@rtems.org> > > Sent: Wednesday, August 16, 2023 4:56 PM > > To: Brett Sterling <brett.sterl...@odysseysr.com> > > Cc: Joel Sherrill <j...@rtems.org>; RTEMS Users RTEMS <users@rtems.org>; > > Chris Johns <chr...@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. > > > > > > On Wed, Aug 16, 2023 at 12:13 PM Brett Sterling > > <brett.sterl...@odysseysr.com> wrote: > > > > > > First off, I want to thank everyone for the fast replies. Second, I want > > > to apologize for the delay responding to the questions - I plan to do > > > better going forward. > > > > > > Here are the responses to the various questions below. If you'd rather I > > > interlace them in the responses, I'm glad to do so (but didn't want it to > > > get too messy :-)). > > > > > > None of the RTEMS tools are in my path - we specify locations when doing > > > builds (i.e. would like to specify this as a parameter to the build) > > > My tools (e.g. sparc-rtems6-gcc) are located at: > > > $HOME/src/Toolchains/osr_rtems_6_sparc/bin > > > > You can add the tools path using: > > > > --rtems-tools=$HOME/src/Toolchains/osr_rtems_6_sparc > > > > If that doesn't work, would it be possible to add > > "$HOME/src/Toolchains/osr_rtems_6_sparc/bin" into your path using > > `export` temporarily just to check if that works? > > > > > My kernel is at: > > > $HOME/src/rtems-development/rtems-hello-world/build/sparc-rtems6-erc32/kernel > > > I'm trying to build for sparc on RTEMS 6 (probably obvious from the > > > previous pieces of information) > > > I'm building on a linux host (cross-building for sparc) > > > I'm using the sparc-rtems6-sis (i.e. the sparc simulator) to test the > > > build > > > With the workaround for issue with the 'Quick Start' process, I can run > > > the "Hello World" example (from the "Quick Start"). Is this what was > > > being referred to with the question "Can you run hello world?", or is > > > there another "hello world" that I should try? > > Great. The RTEMS tools are correctly built then, the issue seems to be > > coming from the command line options. > > > > You can also use the `--help` option to see all the options with a > > brief description with sb-set-builder > > `../source-builder/sb-set-builder --help` > > > > > Per the question "Can you build the rtems-examples from that > > > repository?", can someone clarify which 'repository' that's referring to? > > > Regardless, the answer is "I haven't tried, but I'm glad to give it a > > > shot if there is information somewhere about how to do this". > > > > > `rtems-examples` is a separate repository where we have some example > > applications that can be used as a reference or starting point for > > user application development. Please refer to the following > > repository: > > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fgit.rtems.org%2Frtems-examples%2F&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=q1Ezbldh%2Bflt1MORp8JKwPiV1yiSRH3xl%2Bj09pU3AQo%3D&reserved=0 > > > > > > Best regards, > > Vijay > > > > > Thanks in advance, > > > Brett > > > > > > > > > > > > > > > > > > > > > ________________________________ > > > From: Vijay Kumar Banerjee <vi...@rtems.org> > > > Sent: Tuesday, August 15, 2023 12:53 PM > > > To: Joel Sherrill <j...@rtems.org> > > > Cc: Brett Sterling <brett.sterl...@odysseysr.com>; RTEMS Users RTEMS > > > <users@rtems.org>; Chris Johns <chr...@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. > > > > > > > > > > > > On Tue, Aug 15, 2023, 13:10 Joel Sherrill <j...@rtems.org> wrote: > > > > > > > > > > > > On Tue, Aug 15, 2023 at 11:57 AM Brett Sterling > > > <brett.sterl...@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://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Flegacy-networking%2Fquick_start.html&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zScqSMWXcMVHIxbW6UN1xLBcSTscuPEN0hO90xfD7Os%3D&reserved=0 > > > > > > ../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. > > > > > > > > > I agree with the suggestions above. I am able to reproduce this error > > > with wrong prefix. The following command works for me for a different > > > board: > > > > > > `../source-builder/sb-set-builder --prefix=$PATH_TO_DIR_WITH_BIN > > > --with-rtems-bsp=powerpc/mvme2700 6/rtems-net-legacy` > > > > > > > > > I have the rtems toolset installed in this prefix path. > > > > > > > > > > > > > > > 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. > > > > > > > > > > > > +1 > > > > > > > > > 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://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdevel.rtems.org%2Fticket%2F4927&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=T81iovcI1pu9Ulw%2FCK2q5e601Jz7D4GlzIFWrYEpPqg%3D&reserved=0 > > > > > > > > > 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 <j...@rtems.org> > > > Sent: Tuesday, August 15, 2023 9:57 AM > > > To: Brett Sterling <brett.sterl...@odysseysr.com> > > > Cc: users@rtems.org <users@rtems.org>; Vijay Kumar Banerjee > > > <vi...@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.sterl...@odysseysr.com> wrote: > > > > > > Hello all, > > > > > > My goal is to integrate networking into our RTEMS solution, so I started > > > here: > > > https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Flegacy-networking%2Findex.html&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vQTFld6cloDnZ3JQiyDXy3WaekYc%2FfjWpivbRLkNENw%3D&reserved=0. > > > > > > But, as soon as I had started, I hit a failure. I tried the 'quick > > > start' > > > (https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fdocs.rtems.org%2Fbranches%2Fmaster%2Flegacy-networking%2Fquick_start.html&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zScqSMWXcMVHIxbW6UN1xLBcSTscuPEN0hO90xfD7Os%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@rtems.org > > > https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0LX8N3IVfO%2FVyLJKbSV0auDt9OoMWYLnPk5Cd23W4SY%3D&reserved=0 > > _______________________________________________ > > users mailing list > > users@rtems.org > > https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7C%7Cfa04ba2ce63444c92ac308db9f323ef7%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638278810401317683%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0LX8N3IVfO%2FVyLJKbSV0auDt9OoMWYLnPk5Cd23W4SY%3D&reserved=0
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
