Now that we have the utilities setup for flashing and Debugging the firmware, we need to build and compile the firmware for the MuC. The Firmware runs Nuttx OS which is an RTOS with STMicro STM32L476 support.

Make Build Folder, Add utility and OS files

Make directory called “MotoModsFirmware” with ownership to store build files:

$ mkdir /home/username/MotoModsFirmware

Download the Source code into your directory. We need to give our username ownership of the clone folders so we can access them.

$ cd ./MotoModsFirmware/
$ export BUILD_TOP=`pwd`
$ git clone https://github.com/MotorolaMobilityLLC/nuttx

$ git clone https://github.com/MotorolaMobilityLLC/manifesto

$ git clone https://github.com/MotorolaMobilityLLC/muc-loader

$ git clone https://github.com/MotorolaMobilityLLC/bootrom-tools

$ git clone https://github.com/MotorolaMobilityLLC/mdkutility

Build kconfig-mconf, Nuttx uses the same configuration editor that is used to build the Linux Kernel.

$ cd /home/<username>/MotoModsFirmware/nuttx/misc/tools/kconfig-frontends
$ ./configure --enable-mconf --disable-nconf --disable-gconf --disable-qconf
$ make
$ sudo make install
$ sudo ldconfig

$ cd /home/<username>/MotoModsFirmware

$ export PATH=$PATH:/home/<username>/MotoModsFirmware/manifesto:/home/<username>/Moto

ModsFirmware/bootrom-tools
$ cd ./nuttx/nuttx
$ make distclean
$ cd ./tools
$ ./configure.sh hdk/muc/base_unpowered

At this point the configs/hdk/muc/base_unpowered/defconfig will be copied to ./MotoModsFirmware/nuttx/nuttx/.config and the setenv.sh and Make.defs file from that same directory will be copied up to ./MotoModsFirmware/nuttx/nuttx.

$ cd ./nuttx/nuttx
$ make

The firmware output is located in the nuttx.bin, nuttx.hex and nuttx.tftf files in the /MotoModsFirmware/nuttx/nuttx Directory. We will use these later.

Have a story tip? Message me at: cabe(at)element14(dot)com

http://twitter.com/Cabe_Atwell

Top Comments

soviet_steve over 7 years ago +1

Great tutorial, one mistake on this page which can cause some headaches export PATH=$PATH:home/<username>/MotoModsFirmware/manifesto:/home/<username>/Moto ModsFirmware/bootrom-tools should be export PATH…

yileku over 7 years ago in reply to vamshireddy

I am getting the same error.
Y-
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
vamshireddy over 7 years ago

I have a small issue while making after entering into nuttx it says that manifest.inc No such file or directory a fatal error it seems can you please guide me?
tools/version.sh -v 0.1 -b 31da121-dirty .version; \
chmod 755 .version; \

LN: include/arch/board to configs/hdk/muc/include
LN: include/arch/chip to arch/arm/include/stm32
LN: arch/arm/src/chip to arch/arm/src/stm32
LN: include/apps to ../apps/include
make[3]: Nothing to be done for 'context'.
make[3]: Nothing to be done for 'context'.
make[3]: Nothing to be done for 'context'.
make[3]: Nothing to be done for 'context'.
make[3]: Nothing to be done for 'context'.
make[3]: Nothing to be done for 'context'.
make[2]: Nothing to be done for 'depend'.
make[2]: Nothing to be done for 'depend'.
manifesto manifests/hdk.mnfs 0x00000042 0x00000001
make[2]: manifesto: Command not found
Makefile:143: recipe for target 'manifests/hdk.mnfb' failed
make[2]: *** [manifests/hdk.mnfb] Error 127
Makefile:158: recipe for target 'greybus-utils_depend' failed
make[1]: *** [greybus-utils_depend] Error 2
make[1]: Nothing to be done for 'depend'.
make[1]: 'libsched.a' is up to date.
make[1]: 'libc.a' is up to date.
make[1]: 'libmm.a' is up to date.
make[1]: 'libarch.a' is up to date.
make[1]: 'libcxx.a' is up to date.
CC: nsh_parse.c
AR:   nsh_init.o nsh_parse.o nsh_console.o nsh_script.o nsh_command.o nsh_fscmds.o nsh_ddcmd.o nsh_proccmds.o nsh_mmcmds.o nsh_envcmds.o nsh_dbgcmds.o nsh_session.o nsh_builtin.o nsh_timcmds.o nsh_mntcmds.o nsh_consolemain.o nsh_test.o
make[2]: Nothing to be done for 'all'.
CC: sysinfo.c
AR:    sysinfo.o
CC: manifest.c
manifest.c:76:24: fatal error: manifest.inc: No such file or directory
#include "manifest.inc"
                        ^
compilation terminated.
Makefile:136: recipe for target 'manifest.o' failed
make[2]: *** [manifest.o] Error 1
Makefile:155: recipe for target 'greybus-utils_all' failed
make[1]: *** [greybus-utils_all] Error 2
LibTargets.mk:157: recipe for target '../apps/libapps.a' failed
make: *** [../apps/libapps.a] Error 2

This is what i am getting there
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
motomodsdev over 7 years ago in reply to sharples

Fixed, thank you. The original post also had a lot of unnecessary sudo's.
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
sharples over 7 years ago in reply to soviet_steve

Benjamin,
Thank you for providing this comment! I was stuck here and the '/' made all the difference.
Regards,
-Michael
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
soviet_steve over 7 years ago

Great tutorial, one mistake on this page which can cause some headaches

export PATH=$PATH:home/<username>/MotoModsFirmware/manifesto:/home/<username>/Moto
ModsFirmware/bootrom-tools
should be
export PATH=$PATH:/home/<username>/MotoModsFirmware/manifesto:/home/<username>/Moto
ModsFirmware/bootrom-tools
it's just a forward slash but it makes a difference
thanks for the help
- Cancel
- Vote Up +1 Vote Down
- Sign in to reply
- More
- Cancel