Jenn's Support Shop

Q: I am trying to install the Chassis Manager for Element 2.3.2. My tar command hangs during the installation of the ATCA pdf file. Where is a good element_cm.tar.gz that I can use?

A: Not sure why the file with size 343741 sometimes does not explode properly (in cygwin). This file is delivered as part of element_2.3.2.tar.gz and also may be delivered separately. There is another version that was delivered to a patched customer on 2.3.2 so that can be used instead.

Labels: Element ChassisMgmt install

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