← Back to the chapter · Next detail →
Technical detail · Hardware Prototyping: Board and Breadboard Bring-Up
Prove GPIO access on the installed image
A software development kit (SDK) supplies tools and libraries for building software for a platform. Android Debug Bridge (ADB) lets a computer send commands to an Android device. Exporting a GPIO pin makes a supported pin available through an operating-system interface. Remounting /system changes how that system partition is mounted, such as making it writable where the image permits it. Gradle is a build tool that can repeat the steps needed to build an Android project. These steps depend on the image and privileges; use the board documentation and record exactly what worked.
First, check how the operating system exposes the intended pin and what permissions are needed. Some older images use /sys/class/gpio; their steps can include exporting the pin and setting direction and value access. Android images may need a privileged setup through ADB and a boot script, but the exact path depends on the image. Record the OS, pin map, privilege step, and any startup file changed.
Next, have the application access that pin through a documented library or interface. Gradle can build an Android app; on Linux, a small Python program can test a GPIO library. Finally, verify a read or write on the real pin, record the library and build version, and release the pin when done. This separates permission failures from application errors and electrical faults.