Re: BSP Nomenclature

--===============8866536217701136594==
Content-Type: multipart/alternative; boundary="000000000000db9295062d019c87"

--000000000000db9295062d019c87
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 31, 2025 at 6:10=E2=80=AFAM Robert W <[email protected]> wrote:

> This might seem like a noob question but I keep running into this
> issue when building rtems tools.
>
> Is there some master list of the  *explicit* bsp option to pass to
> "--with-rtems-bsp"?
> I remember not having the *exact* bsp expression being an issue when
> building tools. Getting
> it wrong (as I recall) causes things to (silently) not work right.
>

Usually this has to be a BSP you have built and installed.

The canonical form is CPU/BSP. At the top of the RTEMS, there
is a script "rtems-bsps". By default, it lists all BSPs for all
architectures.

./rtems-bsps -a m68k

Should give you the list of BSPs available.  This section of the Users Guid=
e
may also have some useful information.


> BTW: having just spent some time debugging my m68k target tool builds
> for both 6.1 and 5.3
> I find in the configs what appears to be an issue where if one does
> not define a bsp for tool
> building the library options for gcc will not be generated. :/
>

This sounds like you might be using the BSP build sets in the RSB. It might
be better for you to build just the tools with the bset 6/rtems-m68k and
then
build and test BSPs individually. That way you can test, tweak, debug,
test,
etc each BSP without having to rebuild the tools.

The tools do not need to change between builds of BSPs within the same
architecture which is why the BSP bsets are good for production deployment
but can be awkward for testing.

--joel

>
> Robert W.
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.rtems.org/mailman/listinfo/users
>

--000000000000db9295062d019c87
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 31,=
 2025 at 6:10=E2=80=AFAM Robert W &lt;<a href=3D"mailto:[email protected]">r=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">This might seem like a noob question but I keep running into=
 this<br>
issue when building rtems tools.<br>
<br>
Is there some master list of the=C2=A0 *explicit* bsp option to pass to<br>
&quot;--with-rtems-bsp&quot;?<br>
I remember not having the *exact* bsp expression being an issue when<br>
building tools. Getting<br>
it wrong (as I recall) causes things to (silently) not work right.<br></blo=
ckquote><div><br></div><div>Usually this has to be a BSP you have built and=
 installed.=C2=A0<br><br>The canonical form is CPU/BSP. At the top of the R=
TEMS, there</div><div>is a script &quot;rtems-bsps&quot;. By default, it li=
sts all BSPs for all architectures.<br><br>./rtems-bsps -a m68k<br><br>Shou=
ld give you the list of BSPs available.=C2=A0 This section of the Users Gui=
de</div><div>may also have some useful information.</div><div><br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">
<br>
BTW: having just spent some time debugging my m68k target tool builds<br>
for both 6.1 and 5.3<br>
I find in the configs what appears to be an issue where if one does<br>
not define a bsp for tool<br>
building the library options for gcc will not be generated. :/<br></blockqu=
ote><div><br></div><div>This sounds like you might be using the BSP build s=
ets in the RSB. It might</div><div>be better for you to build just the tool=
s with the bset=C2=A06/rtems-m68k and then</div><div>build and test BSPs in=
dividually. That way you can test, tweak, debug, test,=C2=A0</div><div>etc =
each BSP without having to rebuild the tools.</div><div><br></div><div>The =
tools do not need to change between builds of BSPs within the same</div><di=
v>architecture which is why the BSP bsets are good for production deploymen=
t</div><div>but can be awkward for testing.</div><div><br></div><div>--joel=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Robert W.<br>
_______________________________________________<br>
users mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><br=
>
<a href=3D"http://lists.rtems.org/mailman/listinfo/users" rel=3D"noreferrer=
" target=3D"_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
</blockquote></div></div>

--000000000000db9295062d019c87--

--===============8866536217701136594==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
users mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/users
--===============8866536217701136594==--