Index of the Moto Mods Developer project:

Moto Mods Developer Part 1 - Getting Started - Virtual Machine Setup and Linux Install

Moto Mods Developer Part 2 - Getting Started - SDK Setup & Android Studio Install

Moto Mods Developer Part 3 - Firmware Setup

Moto Mods Developer Part 4 - Getting Started - Make Build-Folder, add Utility and OS files

Moto Mods Developer Part 5 - Flashing Firmware with MDK Utility

Moto Mods Developer Part 6 - Blinking an LED on the Moto Mods Perfboard

Moto Mods Developer Part 7 - Modifying the C file for the perfboard LED

Moto Mods Developer Part 8 - Configure Nuttx

Moto Mods Developer Part 9 - Updating the Hardware Manifests file

Moto Mods Developer Part 10 - Cont’d Configure and Compile Nuttx

Moto Mods Developer Part 11 - Load newly created Nuttx Firmware onto Reference Board

Moto Mods Developer Part 12 - Soldering the Test Points to use the perfboard

Moto Mods Developer Part 13 - Making custom App to control the Firmware

 

Switch to the new target, this will configure the defconfig in the blinky folder when we launch the Nuttx config tool. At the beginning we created the blinky folder.

 

$ cd $BUILD_TOP/nuttx/nuttx/tools
$ ./configure.sh hdk/muc/blinky

 

Enter the commands

 

nuttx.JPG

 

In the Nuttx configuration we have to set up a few things to get the communication between the STM32 micro to work. First we turn on “Vendor Raw Support”. Navigate to each from the top menu and check

 

Device Drivers  ---> 
  [*] Greybus support  --->
    [*]   Vendor Raw Support

 

 

 

 

 

System Type  --->
  STM32 Peripheral Support  --->
    [*] TIM6

 

 

 

 

 

Board Selection  --->
  Select target board (Motorola HDK MuC)  --->
    [*] Blinky LED Mods Raw support

 

 

 

Back. Scroll Down

 

 

 

After checking “Blinky LED Mods Raw support”. Exit

 

Next we will copy the “hdk-powered.mnfs” Hardware Manifest file and name it to “hdk-blinky.mnfs” Then configure it.

 

nuttx2.JPG

 

Enter the commands above.

 

 

Cabe

http://twitter.com/Cabe_e14