Migrating an MPLAB® Harmony v3 Software Framework Application from the SAM9X60-EK to SAM9X60-Curiosity: rtt_periodic_timeout

From MPLAB X IDE, select File > Open project. An Open Project window will open.

Locate the following project in the MPLAB Harmony v3 path:

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

Click on the Open Project button. The rtt_periodic_timeout_sam_9x60_ek project loads into MPLAB X IDE.

In the Categories pane, select Config: [sam_9x60_ek].

Select the version of DFP, CMSIS, and MPLAB XC32 compiler you need for the application. This may be the versions used when the application was originally developed or you may use the latest versions available at the time of migration.

In the Connected Hardware Tool drop-down menu, select the debug probe. In the accompanying figure, we are select the J-32 Debug Probe.

In the Categories pane, select Bootstrap.

Ensure Use Bootstrap is checked.

Click on the Load button and locate and select the at91bootstrap.elf that was compiled as shown in the "SAM9X60-EK – Configure and Build at91bootstrap for an MPLAB® Harmony v3 Project with MPLAB X IDE" page.

In the Categories pane, select J-32.

Click on the Options categories drop-down box and select Communication.

Click on the JTAG Method drop-down box and select 4-wire JTAG.

Click the Apply and the OK button.

From the MPLAB X IDE menu, select Tools > Options.

From the Options window, select Plugins from the ribbon.

Click on the MPLAB Code Configurator 5.x tab.

Under Harmony Content Path, click on the finder and select the path of the Harmony Content.

Click on Apply and the OK button.

Start MCC by clicking on the MCC shield in the toolbar. A Package Versions Used vs Available dialog may appear if the MPLAB Harmony package versions that the project was developed with does not match the versions available locally. You will roll-back the versions in the following steps.

Click on the Continue button. MCC is active and displayed in the IDE.

In the Device Resources pane, click on the Content Manager button. Roll-back the packages that you were alerted to in Step 5.2., which is , csp and dev_packs in this example.

Click on the Apply button. The package versions will be downloaded and installed and MCC will restart.

From the Plugins dropdown box, select Pin Configuration. A Pin Settings tab will be displayed.

From the Order dropdown box, select Ports. This will order the pins by Pin ID (Ports). The pin configurations displayed are those for the SAM9X60-EK. 

Scroll down to Pins PB11, PB12, and PB13. These are the pin assignments for the RGB LED (LD1) on the SAM9X60-EK. You need to change them to the pins on the SAM9X60-Curiosity.

Refer to the SAM9X60-Curiosity users guide (DS60001783) Section 3.5.4 RGB LED. Note the pin assignments for the Curiosity RGB LED (D1). The table below summarizes the pin assignments for the SAM9X60-EK and Curiosity.

To change pin assignments, first select Function: Available for PB11, PB12, and PB13. This will remove the pin assignments.

Next, scroll down to pin PD17, PD19, and PD21 and select Function: GPIO.

Finally, click on the Direction to toggle In to Out and Latch to Low.

Change the Custom Name field to the RGB Pin Names listed in the table in Step 6.4 and shown in the accompanying figure.

In the Project Resources pane (upper left), click on the Generate button. This will generate new source code with the Curiosity’s RGB LED pin assignments.

If a merge window is displayed, merge all. You will observe in the source code the changes in pin assignments.

Close MCC by clicking on the MCC shield in the toolbar.

Set debug reset and startup options:

• In MPLAB X IDE, click on Tools > Options. An Options window opens.
• Click on the Embedded icon at the top and the Generic Settings tab.
• Configure the settings for:
  • Debug Reset @: Main
  • Debug startup: Halt at Main
    
• Click on the OK button.

Click on the Debug Project icon on the toolbar. The project will build with debugging parameters, load the application binary to the SAM9X60-Curiosity Development Board using the AT91Bootstrap to initialize DRAM, and Halt at Main. Once the build is complete and the application binary is loaded into the target, the toolbar expands to show additional debugging icons.

Click on the Continue button. The application binary runs within the target. Observe the RGB LED D1 flashes blue at a 1 Hz rate.

Congratulations! You migrated an MPLAB Harmony v3 application developed for the SAM9X60-EK Evaluation Kit to the SAM9X60-Curiosity Development Board. You can now pause, insert breakpoints, and continue running the project.

If you change the source code, don’t forget to (re)build the project.