Interfacing the PIC32 with an Android device - Revision history

Lynch at 11:36, 16 January 2016

2016-01-16T11:36:54Z

← Older revision		Revision as of 06:36, 16 January 2016
Line 1:		Line 1:
			'''THIS PAGE REFERS TO A PRE-RELEASE VERSION OF THE NU32 PIC32 DEVELOPMENT BOARD. FOR INFORMATION, SAMPLE CODE, AND VIDEOS RELATED TO THE PRODUCTION VERSION (2016 AND LATER), AND TO THE CORRESPONDING BOOK "EMBEDDED COMPUTING AND MECHATRONICS WITH THE PIC32 MICROCONTROLLER," VISIT [[NU32\|THE NU32 PAGE]].'''


	[[Image:PICAndroid.jpeg\|thumb\|500 px\|The touchscreen demo in action\|right]]		[[Image:PICAndroid.jpeg\|thumb\|500 px\|The touchscreen demo in action\|right]]
	__TOC__		__TOC__

ShengWu: /* Introduction */

2013-04-22T16:28:50Z

Introduction

← Older revision		Revision as of 11:28, 22 April 2013
Line 7:		Line 7:
	Learn to connect an Android device and a PIC32 microprocessor. This guide was developed with the NU32 (2012 version).		Learn to connect an Android device and a PIC32 microprocessor. This guide was developed with the NU32 (2012 version).

	Get the starter code: [[Media:Android_PIC_starter_code.zip]]		Get the starter code: [[Media:Android_PIC_starter_code.zip]] or on [https://github.com/shengwu/android-pic32 Github]

	== Getting Started ==		== Getting Started ==

ShengWu: /* Credits */

2013-02-11T10:25:59Z

Credits

← Older revision		Revision as of 05:25, 11 February 2013
Line 169:		Line 169:
	In Eclipse: if you're getting compiler errors with the projects, right click the project name at left > Android Tools > Fix Project Properties. If there are still errors, go to right click > Properties and check the following. In the Android tab, make sure you're building for Android 2.3.3 or for a version that's at least 2.2. In the Java compiler tab, make sure the compiler compliance level is 1.6.		In Eclipse: if you're getting compiler errors with the projects, right click the project name at left > Android Tools > Fix Project Properties. If there are still errors, go to right click > Properties and check the following. In the Android tab, make sure you're building for Android 2.3.3 or for a version that's at least 2.2. In the Java compiler tab, make sure the compiler compliance level is 1.6.

	== ~~Credits~~ ==		== Credit ==

	The firmware uses Ytai Ben-Tsvi's libadb, libbtstack, libconn, and libusb libraries from the [https://github.com/ytai/ioio/wiki ioio project]. The application code uses server libraries from [http://code.google.com/p/microbridge/ microbridge].		This project adapts code from two projects for the PIC32. The firmware uses Ytai Ben-Tsvi's libadb, libbtstack, libconn, and libusb libraries from the [https://github.com/ytai/ioio/wiki ioio project]. The application code uses server libraries from [http://code.google.com/p/microbridge/ microbridge].

ShengWu: /* Things you need */

2012-11-14T20:18:39Z

Things you need

← Older revision		Revision as of 15:18, 14 November 2012
Line 28:		Line 28:
	* Android SDK (download from the [http://developer.android.com/sdk/index.html Android website])		* Android SDK (download from the [http://developer.android.com/sdk/index.html Android website])

	Follow the instructions to get the ADT Plugin for Eclipse and to link the SDK Manager to Eclipse. In Eclipse, this requires going to the Help menu at the very left and selecting "Install New Software". You'll need to open the SDK Manager (probably as administrator) and download the appropriate packages. For my Nexus S 4G, I downloaded the Android 2.3.3 and the Google USB Driver packages. Turn on USB debugging on your Android device in Settings > Applications > Development > USB debugging. It's optional, but you'll want the HD44780, a 2 by 16 character LCD with libraries available for the PIC32.		Follow the instructions to get the ADT Plugin for Eclipse and to link the SDK Manager to Eclipse. In Eclipse, this requires going to the Help menu at the very left and selecting "Install New Software". '''You must install the ADT Plugin to develop Android applications with Eclipse.''' After doing that, you'll need to open the SDK Manager (probably as administrator) and download the appropriate packages. For my Nexus S 4G, I downloaded the Android 2.3.3 and the Google USB Driver packages. Turn on USB debugging on your Android device in Settings > Applications > Development > USB debugging. It's optional, but you'll want the HD44780, a 2 by 16 character LCD with libraries available for the PIC32.

	You'll need the starter code associated with this documentation (linked above), [[Media:Android_PIC_starter_code.zip]]. The code includes the '''String Passing Demo''', a firmware/application pair that passes raw sequences of bytes back and forth, interpreted as strings. There's also the '''Android Sensor Demo''', a firmware/application pair that shows you how to access the GPS, camera, touchscreen, and microphone of the Android device to collect data that may be useful for the PIC.		You'll need the starter code associated with this documentation (linked above), [[Media:Android_PIC_starter_code.zip]]. The code includes the '''String Passing Demo''', a firmware/application pair that passes raw sequences of bytes back and forth, interpreted as strings. There's also the '''Android Sensor Demo''', a firmware/application pair that shows you how to access the GPS, camera, touchscreen, and microphone of the Android device to collect data that may be useful for the PIC.

ShengWu: /* Things you need */

2012-10-24T18:43:30Z

Things you need

← Older revision		Revision as of 13:43, 24 October 2012
Line 28:		Line 28:
	* Android SDK (download from the [http://developer.android.com/sdk/index.html Android website])		* Android SDK (download from the [http://developer.android.com/sdk/index.html Android website])

	Follow the instructions to get the ADT Plugin for Eclipse and to link the SDK Manager to Eclipse. You'll need to open the SDK Manager (probably as administrator) and download the appropriate packages. For my Nexus S 4G, I downloaded the Android 2.3.3 and the Google USB Driver packages. Turn on USB debugging on your Android device in Settings > Applications > Development > USB debugging. It's optional, but you'll want the HD44780, a 2 by 16 character LCD with libraries available for the PIC32.		Follow the instructions to get the ADT Plugin for Eclipse and to link the SDK Manager to Eclipse. In Eclipse, this requires going to the Help menu at the very left and selecting "Install New Software". You'll need to open the SDK Manager (probably as administrator) and download the appropriate packages. For my Nexus S 4G, I downloaded the Android 2.3.3 and the Google USB Driver packages. Turn on USB debugging on your Android device in Settings > Applications > Development > USB debugging. It's optional, but you'll want the HD44780, a 2 by 16 character LCD with libraries available for the PIC32.

	You'll need the starter code associated with this documentation (linked above), [[Media:Android_PIC_starter_code.zip]]. The code includes the '''String Passing Demo''', a firmware/application pair that passes raw sequences of bytes back and forth, interpreted as strings. There's also the '''Android Sensor Demo''', a firmware/application pair that shows you how to access the GPS, camera, touchscreen, and microphone of the Android device to collect data that may be useful for the PIC.		You'll need the starter code associated with this documentation (linked above), [[Media:Android_PIC_starter_code.zip]]. The code includes the '''String Passing Demo''', a firmware/application pair that passes raw sequences of bytes back and forth, interpreted as strings. There's also the '''Android Sensor Demo''', a firmware/application pair that shows you how to access the GPS, camera, touchscreen, and microphone of the Android device to collect data that may be useful for the PIC.

ShengWu: /* Overview of an Android application */

2012-10-08T01:30:18Z

Overview of an Android application

← Older revision		Revision as of 20:30, 7 October 2012
Line 96:		Line 96:
	== Overview of an Android application ==		== Overview of an Android application ==

	[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when certain member functions are called in an Activity's lifecycle. Activities are exited when a user presses "back" but are only paused when a user presses "home." ~~From the~~ [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]		[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when certain member functions are called in an Activity's lifecycle. Activities are exited when a user presses "back" but are only paused when a user presses "home." Source: [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]

	The '''Activity''' is the basic building block of an Android application. There's an Activity for each screen in an app. The String Passing Demo is an application that consists of a single Activity because there's only one screen. The Android Sensor Demo has one Activity for the menu and four Activities for the four sensor demos. To create your own activity, you create ClassName.java file containing a subclass of Android's <tt>Activity</tt> class. In the String Passing Demo, the file is called <tt>StringPassing.java</tt> and the class declaration is <tt>public class StringPassing extends Activity</tt>.		The '''Activity''' is the basic building block of an Android application. There's an Activity for each screen in an app. The String Passing Demo is an application that consists of a single Activity because there's only one screen. The Android Sensor Demo has one Activity for the menu and four Activities for the four sensor demos. To create your own activity, you create ClassName.java file containing a subclass of Android's <tt>Activity</tt> class. In the String Passing Demo, the file is called <tt>StringPassing.java</tt> and the class declaration is <tt>public class StringPassing extends Activity</tt>.

ShengWu: /* Overview of an Android application */

2012-10-08T01:30:01Z

Overview of an Android application

← Older revision		Revision as of 20:30, 7 October 2012
Line 96:		Line 96:
	== Overview of an Android application ==		== Overview of an Android application ==

	[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when certain member functions are called in an Activity's lifecycle. From the [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]		[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when certain member functions are called in an Activity's lifecycle. Activities are exited when a user presses "back" but are only paused when a user presses "home." From the [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]

	The '''Activity''' is the basic building block of an Android application. There's an Activity for each screen in an app. The String Passing Demo is an application that consists of a single Activity because there's only one screen. The Android Sensor Demo has one Activity for the menu and four Activities for the four sensor demos. To create your own activity, you create ClassName.java file containing a subclass of Android's <tt>Activity</tt> class. In the String Passing Demo, the file is called <tt>StringPassing.java</tt> and the class declaration is <tt>public class StringPassing extends Activity</tt>.		The '''Activity''' is the basic building block of an Android application. There's an Activity for each screen in an app. The String Passing Demo is an application that consists of a single Activity because there's only one screen. The Android Sensor Demo has one Activity for the menu and four Activities for the four sensor demos. To create your own activity, you create ClassName.java file containing a subclass of Android's <tt>Activity</tt> class. In the String Passing Demo, the file is called <tt>StringPassing.java</tt> and the class declaration is <tt>public class StringPassing extends Activity</tt>.

ShengWu: /* Overview of an Android application */

2012-10-08T01:28:57Z

Overview of an Android application

← Older revision		Revision as of 20:28, 7 October 2012
Line 96:		Line 96:
	== Overview of an Android application ==		== Overview of an Android application ==

	[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when ~~the~~ member functions are called in an Activity's lifecycle. From the [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]		[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when certain member functions are called in an Activity's lifecycle. From the [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]

	The '''Activity''' is the basic building block of an Android application. There's an Activity for each screen in an app. The String Passing Demo is an application that consists of a single Activity because there's only one screen. The Android Sensor Demo has one Activity for the menu and four Activities for the four sensor demos. To create your own activity, you create ClassName.java file containing a subclass of Android's <tt>Activity</tt> class. In the String Passing Demo, the file is called <tt>StringPassing.java</tt> and the class declaration is <tt>public class StringPassing extends Activity</tt>.		The '''Activity''' is the basic building block of an Android application. There's an Activity for each screen in an app. The String Passing Demo is an application that consists of a single Activity because there's only one screen. The Android Sensor Demo has one Activity for the menu and four Activities for the four sensor demos. To create your own activity, you create ClassName.java file containing a subclass of Android's <tt>Activity</tt> class. In the String Passing Demo, the file is called <tt>StringPassing.java</tt> and the class declaration is <tt>public class StringPassing extends Activity</tt>.

ShengWu: /* Basics of Android programming */

2012-10-08T01:28:35Z

Basics of Android programming

← Older revision		Revision as of 20:28, 7 October 2012
Line 94:		Line 94:
	This activity uses <tt>AudioRecord</tt> to access raw data from the microphone rather than <tt>MediaRecorder</tt>, which is designed to record audio and/or video for saving to files.		This activity uses <tt>AudioRecord</tt> to access raw data from the microphone rather than <tt>MediaRecorder</tt>, which is designed to record audio and/or video for saving to files.

	== ~~Basics~~ of Android ~~programming~~ ==		== Overview of an Android application ==

	[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when the member functions are called in an Activity's lifecycle. From the [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]		[[Image:Activity_lifecycle.png\|thumb\|400 px\|This describes when the member functions are called in an Activity's lifecycle. From the [http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle Activity documentation].\|right]]

ShengWu: /* Microphone demo */

2012-10-08T01:27:38Z

Microphone demo

← Older revision		Revision as of 20:27, 7 October 2012
Line 90:		Line 90:
	=== Microphone demo ===		=== Microphone demo ===

	The microphone demo captures data from the Android device's microphone but doesn't do much with it. The level bar in the application shows the maximum amplitude found in the previous sample. It sends up to ~~100~~ ~~bytes~~ of ~~each~~ ~~sample~~ to ~~the~~ ~~PIC,~~ ~~which~~ comments on the loudness.		The microphone demo captures data from the Android device's microphone but doesn't do much with it. The level bar in the application shows the maximum amplitude found in the previous sample. It sends this maximum amplitude to the PIC as an integer. The PIC comments on the loudness.

	This activity uses <tt>AudioRecord</tt> to access raw data from the microphone rather than <tt>MediaRecorder</tt>, which is designed to record audio and/or video for saving to files.		This activity uses <tt>AudioRecord</tt> to access raw data from the microphone rather than <tt>MediaRecorder</tt>, which is designed to record audio and/or video for saving to files.