Moto Mod the Future Hackathon New York City Webex Presentation

1. Pre-Hackathon Webex Meeting
12.7.16

2. AGENDA
/ Schedule
/ Rules
/ Challenges
/ Hello Moto
/ Prizes
/ Partners
/ Judges
/ Judging Criteria
/ Hackathon.io
/ Registration Info
/ General Q&A

3. SCHEDULE
SATURDAY, DEC. 10
9 am / Doors Open & Breakfast
10 am / Opening Ceremony & Presentations
11 am / Hackathon Begins
12 pm / Lunch
1 pm / Breakout Sessions
6 pm / Dinner
12 am / Midnight Snack
12 am - 8 am / Hack through the night
SUNDAY, DEC. 11
7 am / Breakfast
12 pm / Lunch
1 pm / Submission Deadline
2 pm / Demos & Judging Begins
3 pm / Judge Deliberation
3:30 pm / Awards
4 pm / Closing

4. RULES
1 / Teams of up to 5 humans are allowed.
2 / All demo no slideware. 2 minute presentation, 1 minute Q&A from Judges.
3 / Each hackathon has its individual hackathon.io page, and projects should be
submitted on it. Submission time is 13:00 Sunday.
4 / Winning teams will be subject to a code-review following the event or immediately
before winning.
5 / Fresh Code Enforced: We all start coding at the same time. This is done to keep
things fair. Please don’t come in and build on top of previous projects if you want to win.
6 / Every participant must agree to this participation agreement.

5. Measuring your heart rate and
counting your steps are great.
But built-in health apps can be
taken to a whole new level. If you
had the ability to add whatever
sensor you wanted, what could
you build to make health
diagnosis easier? Or workouts
better, faster, stronger...
HEALTH & FITNESS
From in-store services and
promotions to inventory
management, retail has changed
dramatically over the past few
years. How could a Moto Mod
change the way people experience
their favorite stores and
restaurants?
RETAIL
The digital revolution changed
the way we interacted with
multimedia forever. Now imagine
you could upgrade your phone’s
hardware to better suit your
media preferences? What would
those Mods look like?
MULTIMEDIA
CHALLENGES

7. / Focused on compelling consumer experiences
/ Open ecosystem to enable developers
/ App store for hardware
MOTO MODS JOURNEY
BEST OF INNOVATIONS:
WIRELESS HANDSET
ACCESSORIES

8. MOTO MODS PURCHASE RATES
40% 40% 10% 10%
50% Attach Rate with Moto Z
#1 Driver of Moto Z Purchase Intent

9. hours hours hours hours
37 14 10 6
CONSUMERS ARE USING THEIR MODS
50% use weekly
(or more)

10. Positive
Sentiment
Average
Smartphone
Sentiment
80-95% 65%
CONSUMERS LOVE THEIR MODS

11. MOTO MODS DEVELOPMENT KIT
The Moto Mods Development Kit (or MDK) contains everything you
need to begin your project. Virtually any Moto Mod you can
imagine can be initially prototyped using the MDK.
Beyond the MDK, all you need
to develop is a Moto Z, a USB
Type C cable, and Linux.
MDK Contents:
Cover
Perforated Board
Reference Moto Mod

12. REFERENCE MOTO MOD
The Reference Moto Mod was designed to hide the hard parts and
allow you to focus on your specific solution.
Computing System Both the MuC and Moto High Speed Bridge
80-pin Header Interface to your Moto Mod’s peripherals
Dip Switches Enable the Reference Moto Mod to support your specific solution
Battery/Charging Enable your project to run independent from Moto Z
Debugging Type C support provides Serial Wire Debug and logging
capabilities without expensive external tools, like JTAG
Data/Display Output USB Ports provide USB2 and USB3 interfaces, and MyDP

13. DEVELOPMENT BOARDS
Hardware invariably needs iterations to get correct. And people like to
work on multiple projects. As a result, Moto did not want to force you to
purchase a new MDK for each project. Instead, Moto has created two
boards that attach to the 80-pin connector for hardware prototypes.
The Perforated Board provides solder point access to the 80-pin, as
well as power rails and test points.
The HAT Adapter Board is mechanically and electrically compliant with
Raspberry Pi. As a result, 100s of existing hardware projects can be
used for your prototyping. A breadboard area and 80-pin access are
available as well.

14. PERSONALITY CARDS
To help provide examples for more common or complex protocols,
Moto has built a variety of Personality Cards that snap into the MDK.
Each of these has open source electrical schematics, and application
and firmware code. Additionally, the Developer Portal provides
Example pages for each of these, walking through the firmware and
software development.
Audio Battery DSI Display Sensor

15. EXAMPLE AND DEVELOPER MODES
To make using the Personality Cards easy, Moto has
created “Example Mode.” When in this mode,
swapping Cards automatically downloads and installs
its specific firmware.
When performing your own development, the MDK
should be transitioned into “Developer Mode.” When
in this mode, the bootloader expects VID=0x42,
PID=0x1. This will prevent the Moto Z from potentially
overwriting your firmware, since it will never match an
actual product.
Switching between Modes is performed using the MDK Utility.
https://play.google.com/store/apps/details?id=com.motomodsdev.mdkutility

16. FLASHING YOUR FIRMWARE
For full details on Example/Developer Mods and flashing firmware,
please refer to the Developer Portal:
https://developer.motorola.com/build/tools/flashing-firmware
MDK Utility Method
Once in Developer Mode, you can select your
compiled firmware (.tftf) file and flash directly
from the utility. After you compile your
firmware, copy it to your Moto Z (or Google
Drive). You can then select and flash the file.
OpenOCD Method
OpenOCD provides direct Serial Wire Debug
access. After attaching the Type C cable to the
USB1 port:
$ openocd -f board/moto_mdk_muc_reset.cfg -c "program nuttx.tftf 0x08008000 reset exit"

17. DEBUGGING AND LOGGING
For full details on Debug and Logging, please refer to the Developer
Portal: https://developer.motorola.com/build/tools/debug-and-log
Debugging and logging support are provided by the USB1 connector
on the Reference Moto Mod. These interfaces are accessed via
OpenOCD and enumerate as USB devices in Linux.
MuC Serial Wire Debug A (if00) /dev/ttyUSB<n>
APBE JTAG B (if01) /dev/ttyUSB<n+1>
MuC Nuttx Shell C (if02) /dev/ttyUSB<n+2>
APBE-MuC IPC D (if03) /dev/ttyUSB<n+3>
To help identify the correct tty, use this command to match the FTDI port with it’s ttyUSB device:
$ ls /dev/ttyUSB* | xargs -I{} bash -c 'echo -n {}": "; udevadm info --name={} |grep "
serial/by-id" |tail --bytes +21'

18. DEBUGGING AND LOGGING continued
Debugging is done with GDB, which attaches through the OpenOCD
MuC Serial Wire Debug interface:
$ arm-none-eabi-gdb
(gdb) target extended-remote localhost:3333
(gdb) set can-use-hw-watchpoints 1
To load the symbol table, the elf file is “nuttx”, generated in nuttx/nuttx:
(gdb) file nuttx
Logging is done a dumb terminal (like picocom), and attaches
through the OpenOCD MuC Nuttx Shell:
$ picocom -l -b 115200 /dev/ttyUSB{x}

19. PRIZES
GRAND PRIZE - 1 team
/ $5,000 cash prize for the Winning Team
/ Invitation to pitch your Moto Mod concept at
Moto HQ for Lenovo Capital investment
/ Entry into the Moto Mods Partner program
/ Dedicated Business Development Mentor
/ 1 Moto Mods Development kit per Team
/ 1 Moto Z phone per Team Member
RUNNER-UP PRIZE - 1 team
/ 1 Moto Mods Development kit per Team
/ 1 Moto Z phone per Team Member

20. PARTNERS
SILEGO SPONSOR PRIZE
● Challenge:
○ Best use of Silego Configurable
Mixed-signal IC in your hack
● Prize:
○ $250 Amazon Gift Card
○ 1x Tile Bluetooth Trackers per team member
○ 1x Silego Developers Kit per team member
○ 3000 Silego CMIC production ready devices
pre-programmed with your custom design
EBUYNOW IN PARTNERSHIP WITH
REBOOT WITH JOE SPONSOR PRIZE
● Challenge:
○ Create a hack that delivers better health
monitoring and feedback to evaluate the
impact of healthier changes between diet,
routine and fitness.
● Prize:
○ 1x Amazon Echo per team member
○ Opportunity to partner with eBuyNow to
further develop and launch your concept

21. JARRETT SIMERSON
DEVICE INNOVATION
LEAD OF MOTOROLA
AND CHIEF ARCHITECT
CHRISTOPHER MERKLE
FOUNDER OF RAZUR, A
BORN-DIGITAL AGENCY
BUILT FOR TODAY'S
CONNECTED WORLD
JUDGES
CRAIG SMITH
CHIEF EXECUTIVE
OFFICER, EBUYNOW
ECOMMERCE LIMITED
REZA CHOWDHURY
FOUNDER AND CEO AT
ALLEYWATCH
HEIDI FARRELL
SENIOR MECHANICAL
ENGINEER AT RINGLY

22. JUDGING CRITERIA
Each submission will be scored in each round based on the following criteria with a
minimum score of 0 and maximum score of 25 points, with the final score being the
average of the judges’ scores:
1 / Create New Category Use Case: How creative was the team in developing an innovative
solution for the challenge? Is the mod simple to use and can the team explain it clearly in
three sentences or less? (5 Points)
2 / Leverages or Improves Upon Brand Equity (5 Points)
3 / Solves Consumer Painpoint (5 Points)
4 / Feasibility: Is the mod technically feasible and scalable? (5 Points)
5 / Viability: Is the mod marketable? Does commercial viability exist? Does it answer a need or
demand? (5 Points)

23. HACKATHON.IO
1 / Go to
2 / Click “Join Event”
3 / Click “Projects”
4 / Click “List Your Project” - by 1 pm on Sunday
5 / Fill out form, click “Submit”

24. Q&A

25. INVITE YOUR FRIENDS