Frequently Asked Questions
Q: Can I connect a serial cable (TTL) to a Raspberry Pi (or Rock64)?
A: Yes, there are TTL pins in the GPIO pins. They are as follows
VCC → RPi Pin 02 (5V) GND → RPi Pin 06 RXD → RPi Pin 08 TXD → RPi Pin 10
You will also need to configure Rasbian to output information on these pins. To do so add this to your config.txt file located on your boot partition.
Note: U-boot will not appear on serial, only once kernel starts to boot do you see output
Q: What are the instructions to install an Armbian?
A: Install the OS and prepare the board as follows.
Make sure you have the following items:
- Armbian-compatible board
- SD card
Flash the SD card with the appropriate Armbian image (usually the Nightly for your board, refer to Hardware Table).
Plug the SD card into the board.
Plug the board into your router, so it has connectivity to the Internet.
SSH into the board with the username root and password 1234. Default hostnames are similar to your boards name. For example orangepizero for an Orange Pi Zero espressobin for an Espressobin etc.
When prompted, enter the password 1234 again.
When prompted, enter a new password, this will be your new root password.
When prompted, enter your new password again.
When prompted, enter a non-root username for your board.
When prompted, enter a password for your new non-root user.
When prompted, enter the password for the non-root user again.
Answer the rest of the prompts about the new non-root user, or simply press enter at each prompt to skip.
Continue with Prototype Installation.
Q: Why do my Orange Pi Zero USB headers not work?
A: Some images are missing the USB overlay. Simply add the following to the /boot/armbianEnv.txt file and restart the Pi.
Q: Why do I get an error about a locked file when I try to install the node on an Orange Pi?
A: The daily apt upgrade sometimes starts up in the background locking the apt database. This will cause the script to fail as it tries to install the required software. Wait for the upgrade to finish.
Q: Seems all my mac addresses are the same across multiple boards. How do I fix this?
Seems some of the Armbian images have a hardcoded machine id. Generate a new one using the following script
if [ `cat /etc/machine-id` == "f3f0aa4383b442e6ae0b889a10144d76" ]; then echo Generating new ID sudo mv /etc/machine-id /etc/machine-id.old dbus-uuidgen | sudo tee /var/lib/dbus/machine-id sudo cp /var/lib/dbus/machine-id /etc/machine-id fi
Q: What is the baud rate for the Rock64?
A: U-boot baud rate seems to be 1500000. Once ubuntu starts it is 115200
Q: How do I upgrade the U-boot on Espressobin?
A: Manual flashing to latest U-boot is mandatory! Download the right boot flash for your board: 512,1G,2G, number of RAM chips (one at the bottom or 2 one on each side of the board) and appropirate memory speeds. You can obtain numbers from current boot prompt. Copy this flash-image-MEM-RAM_CHIPS-CPU_DDR_boot_sd_and_usb.bin to your FAT formatted USB key, plug it into USB3.0 port and execute from U-boot prompt:
bubt flash-image-MEM-CPU_DDR_boot_sd_and_usb.bin spi usb
Q: How do I boot Armbian on an Espressobin from an sd card?
A: First update the U-boot (above). Then run the following in U-boot.
setenv initrd_addr 0x1100000 setenv image_name boot/Image setenv load_script 'if test -e mmc 0:1 boot/boot.scr; then echo \"... booting from SD\";setenv boot_interface mmc;else echo \"... booting from USB/SATA\";usb start;setenv boot_interface usb;fi;if test -e \$boot_interface 0:1 boot/boot.scr;then ext4load \$boot_interface 0:1 0x00800000 boot/boot.scr; source; fi' setenv bootcmd 'run get_images; run set_bootargs; run load_script;booti \$kernel_addr \$ramfs_addr \$fdt_addr' saveenv
Q: Can I use the on board wireless of my RaspberryPi/OrangePi/etc to mesh?
On board wireless we have seen so far
- Do NOT support 802.11s/meshpoint
- Do report to support Ad-Hoc mode
- Do NOT support 40Mhz width
- Will only connect to other devices using Ad-Hoc and not using 40Mhz
- May or may not work. Protocol is not usually maintained as part of drivers
- Install Ad-Hoc mesh module
- Do NOT install Access Point
- After install remove
If you have success using ad-hoc with on board cards please let us know your experience.