Jenn's Support Shop

Q: I have installed the BSP for SFK for 5.5.1 on my Linux system, but without installing any of the BSP documentation (I didn't need it and already have a copy of it elsewhere). When I try to build the rtose, I get a "No such file or directory" errors on rtose_defaults.mk and environment.mk.Checking the SFK delivery shows these and other important build files missing - in fact, the /refsys directory only has /rtose in it, and nothing else.

A: There is a weird problem with the installer that causes it to omit a lot of important files if you don't install the BSP documentation. Re-install it with all the documentation checked, which is the default. Then the environment.mk and other files should appear in the distro where they belong.

Labels: BSP, installation, OSE5, sfk

Q: I just got a BSP delivery for my OSE5.5 product. I used the refsys reference build in OSE5 previously; however there isn't a /refsys directory in this BSP at all (!), only an /examples directory, and a /doc directory.

A: Your BSP delivery is actually a new style called "modsys" and is designed to be the new paradigm for reference platforms in OSE systems that support multicore. Starting in OSE5.5, all BSP that support multiple cores will be delivered in the modsys style rather than the refsys one.

To learn how to build in for modsys, refer to the new Modsys User's Guide, delivered with all modsys BSPs in the doc directory. There is a documentation error in the book-installation-guide.pdf delivered with the modsys BSPs for OSE5.5 which omits the mention of this guide, but this is corrected in subsequent OSE5.5.x releases.

Q: I just tried "make all" in my BSP examples/ and it gave this error:

/vobs/ose5/system/gcc_win32_mips_4.4.3/bin/mips-elf-gcc: not found

A: Since BSPs are delivered separately from the OSE delivery, the BSP architecture type must be matched to the OSE one. In this case you tried to build a BSP for a MIPS board using the OSE delivery for PowerPC. (The customization for internal paths doesn't help either.)

1. First verify you have the correct OSE architecture installed.

2. Change dir into $BSP_ROOT/examples//sysmake

3. Edit tools.mk to change this:

OSEROOT_ABS ?= /vobs/ose5/system
to this:
OSEROOT_ABS ?= C:/OSE/OSE5.5_MIPS
or whatever is appropriate.

Q: I don't see the rtose5.conf file either. Or rtose.mk. What happened there?

A: It's sort of been split up. In the modsys way, there are three main make targets now: "kernel", "lmbuild", and "image."

If you "make kernel", your build will extract .conf parameters from a new file called examples//kernel/kernel.conf. This conf file also contains any necessary parameters to make the bare-bones kernel.elf binary (e.g. dda, pm). The kernel.conf however is missing quite a few items that aren't valid for just a kernel build.

If you "make lmbuild" you will end up building all the load modules in the modules directory, for which .conf parameters aren't really valid.

When you "make image", the sys.conf file defines system parameters for all the core extensions along with krn parameters, such as inet, ramdisk, ffx, heap, and so on. However, it won't actually work unless you build the kernel and lmbuild targets first.

So a full build command after make clean is now: "make kernel lmbuild image". This is equivalent to "make all." And it builds rtose_release by default;the "FLAVOR=debug" make option still works though.

The osemain.con is also split among kernel and load modules, as it was in the old refsys.

Labels: BSP, modsys, OSE5, refsys

Q: I installed my new BSP in the correct place (i.e. same level as OSE5.3), but get a compile error for gcc - even though I know that it's there. I'm building from the new refsys/rtose/myhardware directory, and not using the old OSE5.3 refsys. What did I do wrong?

> C:/OSE/BSP_WALNUT_OSE5.3/refsys/rtose
$ make all
echo "--- Building RTOSE for walnut"
--- Building RTOSE for walnut
make -C walnut --unix WARNINGS=no all
make[1]: Entering directory `/cygdrive/c/OSE/OSE5.3/BSP_WALNUT_OSE5.3/refsys/rtose/walnut'
--- Making modules/corecmds
--- Compiling src/cmd_pool.c
../../../gcc_win32_powerpc_3.4.4/bin/powerpc-eabi-gcc: not found
make[3]: *** [obj/powerpc/debug/cmd_pool.o] Error 127
make[2]: *** [corecmds] Error 2
make[1]: *** [mods] Error 2
make[1]: Leaving directory `/cygdrive/c/OSE/BSP_WALNUT_OSE5.3/refsys/rtose/walnut'
make: *** [walnut] Error 2

A: You have a make a slight mod in
OSE/BSP_WALNUT_OSE5.3/refsys/environment.mk
Change
OSEROOT ?= ../../..
to
OSEROOT ?= ../../../../ose5.3

And "make all" in the new BSP rtose should work after that.

Labels: BSP, OSE5.3, rtose