BSP Nomenclature

[Joel Sherrill]

On Fri, Jan 31, 2025 at 6:10 AM Robert W <rbtwas at gmail.com> 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 Guide
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
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20250131/c8a1271b/attachment.htm>