Main Page

Illustration for Main Page documentation

Summary

This is the curated hub for the LeMaker Wiki archive. Use it to find stable entry points for common tasks (first boot, login, GPIO work, bootloader/kernel builds) without having to guess which older page is relevant.

If you’re unsure where to start, pick a board hub first, establish reliable access (serial or SSH), then capture a baseline boot report before making changes.

Who this is for

People new to LeMaker boards, developers doing bring-up or kernel work, and anyone migrating from older notes who needs a reliable “start here” index.

What you’ll do

Choose a board hub or a task hub (login, GPIO, bootloader/kernel).
Prepare a minimal bring-up setup that is easy to reproduce.
Capture a baseline boot report and keep it for later comparisons.
Use verification checks after any change to storage, kernel, or networking.
Follow troubleshooting links when you need a quick recovery path.

Topics

Banana Pro / Pi hub — archived GPIO and bootloader notes.
HiKey960 hub — bring-up checks and access tips.
LeMaker Guitar hub — bring-up flow and related topics.
Log in to the Banana Pi — account/access basics.
BananaPro/Pi: GPIO library — GPIO tooling entry point.
BananaPro/Pi: Building U-Boot, script.bin and Linux kernel — bootloader/kernel workflow notes.
WiringPi — GPIO tooling notes (archival).

Common tasks

First boot: verify the image, boot with Ethernet and minimal peripherals, then capture logs.
Login/access: confirm SSH or local console access before you change networking.
GPIO: start with a minimal test, confirm pin numbering, then build up.
Bootloader/kernel: change one variable at a time and keep the last known-good artefacts available.

Quick checklist

Stable PSU and cable.
Known-good storage and a reliable writer.
Ethernet for first boot (recommended).
Optional: serial console adapter for early boot logs and recovery.
A place to save a baseline boot report.

Steps / guidance

Pick the board hub. Start from Banana Pro / Pi, HiKey960, or LeMaker Guitar.
Bring up access. Decide on serial console vs SSH vs local console (or a combination).
Confirm storage layout.
```
lsblk
blkid
```

Capture baseline health output.

uname -a
ip a
systemctl --failed
journalctl -b -p err | tail -n 80
dmesg | tail -n 50

Only then proceed to board-specific work. Use the hub page links so you do not mix incompatible instructions.

Verification checks

Pick at least two after flashing or updating:

uname -a
ip a
lsblk
dmesg | tail -n 50
journalctl -b -p err | tail -n 120

Troubleshooting

No boot: treat power and storage as suspects; capture serial logs if available; re-flash from a verified download.
No network: prefer Ethernet; check ip a and ip r before changing services.
Services failing: use systemctl --failed and journalctl -b -p err.
Inconsistent behaviour: reduce peripherals and swap PSU/cable and storage before deeper debugging.

Common mistakes

Changing several variables at once (image + power + peripherals).
Doing headless updates without a recovery console path.
Assuming an SD card is reliable because it worked once.
Not saving a baseline boot report.

Concrete example (find a topic quickly)

Use your browser search (Ctrl+F) for:
- GPIO
- U-Boot
- login
- kernel
- serial

Author: LeMaker Documentation Team
Last updated: 2026-01-04