Thursday, July 07, 2011
No /refsys directory in OSE5 BSP delivery
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/
/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/
3. Edit tools.mk to change this:
OSEROOT_ABS ?= /vobs/ose5/systemto 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/
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
free invisible web counter
