SAM9X60-EK – Copy MPLAB® Harmony 3 Application and at91bootstrap to SD Memory Card

Introduction

In this training topic, you will copy two binary images, harmony.bin (an MPLAB® Harmony 3 Software Framework application) and boot.bin (Second-stage bootloader, at91bootstrap), to an SD memory card for booting on the SAM9X60-EK Evaluation Kit. Once the images are copied, the SD memory card is inserted, and upon reset, the SAM9X60 will boot and run the application.

For this exercise, you will write the binaries that were created in the training topics:

Prerequisites

Hardware

For this training, you will use the SAM9X60-EK Evaluation Kit.

SAM9X60-EK Evaluation Kit

Set up the SAM9X60-EK as listed below to the host computer.

Jumpers

Power

Console Serial Communications

SD Memory Card

The SAM9X60-EK has a MultiMediaCard (MMC) or Secure Digital (SD) memory card slot (J4) that can be used for booting the system. It is connected to the SDMMC port 0 (SDMMC0) peripheral of the SAM9X60-EK.

For this training topic, you will need an SD memory card formatted with the FAT file system.

​

Ensure that no other bootable Non-Volatile Memory (NVM) on the SAM9X60-EK contains a bootable image. Ensure there are no bootable images in NAND Flash (U9) or NOR Flash (U8). For information on the default boot sequence of the SAM9X60, see Section 12 – Boot Strategies in the SAM9X60 Datasheet.

Copy boot.bin to SD memory card

In this section, you will copy the at91bootstrap binary image, boot.bin, to an SD memory card with a FAT formatted partition.

1

Change directory to the location of boot.bin:

<project_directory>\at91bootstrap\build\binaries\boot.bin

2

Copy boot.bin to SD memory card.

Write harmony.bin to SD Memory Card

In this section, you will copy the MPLAB Harmony 3 Software Framework application binary image, harmony.bin, to the SD memory card into the same FAT formatted partition as you copied boot.bin into.

1

Change the directory to the location of harmony.bin:

C:\Users\<user>\Harmony3\csp_apps_sam_9x60\apps\rtt\rtt_periodic_timeout\firmware\sam_9x60_ek.X\dist\sam_9x60_ek\production\

2

Copy harmony.bin to SD memory card.

Run MPLAB Harmony 3 Application on the Target

1

Insert the SD memory card into the SD card slot (J4).

2

To run the application, press the nRST (Reset) (SW3) push button. Observe the RGB LED (LD1) flashes blue. You can also observe the at91bootstrap reading from the SD memory card on the console.

console_harmony_bin_run_sd_rtt_periodic_timeout.png

Summary

In this training topic, you copied the binary files harmony.bin and boot.bin to an SD memory card for booting on the SAM9X60-EK and ran the application on the target.

What’s Next?

For training topics on configuring at91boostrap for other NVM, see:

Second-Stage Bootloader at91bootstrap

Writing to NVM

SAM9X60-Curiosity Development Board
If you would like to learn how to migrate an MPLAB Harmony 3 application example initially developed for the SAM9X60-EK Evaluation Kit to the SAM9X60-Curiosity Development Board, see: "Migrating an MPLAB® Harmony 3 Application from the SAM9X60-EK to SAM9X60-Curiosity: rtt_periodic_timeout"

  Return to Top

© 2024 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.