BPI-R64 Ubuntu 16.04 & AArch64 Linux Lite & Debian 10 Buster Lite Demo Images Release 2019-08-23

Banana Pi Router design BPI-R64(MT7622)
1

BPI-R64 Ubuntu 16.04 & AArch64 Linux Lite & Debian 10 Buster Lite Demo Images Release 2019-08-23

image
image856×610 175 KB

  1. About this release
  • This release is for banana pi R64 board, and it is based on Ubuntu 16.04 & AArch64 Linux Lite & Debian 10 Buster Lite Operation system with kernel 4.19.
  1. AArch64 Linux lite
  1. Debian 10 buster lite
  1. Ubuntu Server 16.04
  1. FAQ
  • username : root/pi
  • password : bananapi
1 Like
2

which board-versions are supported?

I ask because there are 2 different switches (rtl8367 & mt7531)

3

Hello, this switch mt7531

4

Do you use my repo (currently untested mt7531-driver) or have you an own repo?

5

Hello frank, I have a own repo, after the wifi and bt driver work, and we will public the repo soon.

1 Like
6

Images seems to support emmc, which additional steps are needed to get it running on emmc (e.g. preloader to boot0,changing hw-partitions)? Which preloader needs to be written (is this done by bpi-copy)?

7

I would also like to know how to write the image to eMMC as I’ve tried several wais to no avail…

8

i tried with new preloader from oct 2nd

echo 0 > /sys/block/mmcblk1boot0/force_ro
dd if=preloader_evb7622_64_foremmc.bin of=/dev/mmcblk1boot0
unzip -p 2019-08-23-debian-10-buster-lite-preview-bpi-r64-sd-emmc.img.zip | dd of=/dev/mmcblk1 bs=1M

still error in uboot (failing to access emmc)

full bootlog here: Bpi-r64 quick start (boot from eMMC)

are these images really emmc-ready, especially uboot? I see some changes here in config.in which maybe relevant and not yet in the image

|||if [ "$ON_BOARD_SPI_NAND_FLASH_COMPONENT" = "y" ]; then|
| --- | --- | --- |
|||#BPI|
|||define_bool ON_BOARD_NO_FLASH_COMPONENT n|
|||#BPI|
|||#if [ "$ON_BOARD_SPI_NAND_FLASH_COMPONENT" = "y" ]; then|
|||define_bool CONFIG_MTK_MTD_NAND y|
|||define_bool CONFIG_MTK_SLC_NAND_SUPPORT y|
|||define_bool CONFIG_MTK_SPI_NAND_SUPPORT y|
|||fi|
|||#fi|
9

have now booted first time the debian buster image with new r64-board

power consumption is about 4.6w in default configuration (no pcie/wifi/bt active) while running apt upgrade (4.0w in idle)…after powerdown: 4.8w :frowning: something is strange here

first thing i’ve noticed was readonly rootfs because of wrong uuid in /etc/fstab

root@bpi-iot-ros-ai:~# blkid                                                    
/dev/mmcblk1p1: LABEL_FATBOOT="BPI-BOOT" LABEL="BPI-BOOT" UUID="1539-6609" TYPE=
"vfat" PARTUUID="e43da9c5-01"                                                   
/dev/mmcblk1p2: LABEL="BPI-ROOT" UUID="80463388-3170-483b-ac00-378b69a7a277" TYP
E="ext4" PARTUUID="e43da9c5-02"

fstab:

UUID=c1401c29-e4d8-4924-8799-8b0f3a77b79b / ext4 defaults,noatime,nodiratime,com
mit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0

after i’ve fixed this (with vi because nano is currently unusable on serial, also tried with “resize” and changing $TERM) i got a rw-rootfs

on first apt update i got errors about not-yet-valid release file…this is because the system clock is wrong. this can be quick-fixed by

date -s '2019-10-11'

maybe anybody have an idea about nano (and some menus from apt/dpkg looking strange/no cursor/selection visible).

i expect there is any wrong console setting

root@bpi-iot-ros-ai:~# stty -a                                                                                          
speed 115200 baud; rows 24; columns 120; line = 0;                                                                      
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q;      
stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;                             
-parenb -parodd -cmspar cs8 hupcl -cstopb cread -clocal -crtscts                                                        
-ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany imaxbel -iutf8               
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0                                         
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -flusho -extproc

on ssh it works, tried setting same console settings, but this does not help…seems to be another problem…

it should be noted that debian buster is the armbian-version not the debian basic version…maybe nano is broken there

replaced rootfs with bootstrapped rootfs from original debian buster does not show this nano-issue

10
Old content

tried also with changes in config.in for emmc-support (commit above), but still unknown partition table/no mmc card found

other changes in mt7622_evb.h as far as i see are only sd-card-relevant (inside #elif defined(OFF_BOARD_SD_CARD_COMPONENT) )

i guess it’s last one because mmc1 block 0 is printed and not only 0 can i check if the right HW-Partition is read?

BPI-R64> mmc init 1
raise: Signal # 8 caught
ret2 = 1
raise: Signal # 8 caught
ret2 = 1
<= [mmc1 block 0] =>
[0x00000000] 8c 7c f2 7c 00 00 00 00
[0x00000008] 0a 00 00 00 d0 b9 f5 7e
[0x00000010] 0a 00 00 00 ff ff ff ff
[0x00000018] ff ff ff ff 02 00 00 00
[0x00000020] 40 7c f2 7c 0b 7c f6 7e
[0x00000028] c0 c2 f2 7c dc 00 00 00

i had read out my emmc from linux userspace:

root@bpi-r64:~# hd /dev/mmcblk1 | less                                          
00000000  53 44 4d 4d 43 5f 42 4f  4f 54 00 00 01 00 00 00  |SDMMC_BOOT......|  
00000010  00 02 00 00 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|  
00000020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|  

root@bpi-r64:~# hd /dev/mmcblk1boot0 | less                                     
00000000  45 4d 4d 43 5f 42 4f 4f  54 00 00 00 01 00 00 00  |EMMC_BOOT.......|  
00000010  00 02 00 00 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|  
00000020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|  

root@bpi-r64:~# hd /dev/mmcblk1boot1 | less                                     
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|  

root@bpi-r64:~# hd /dev/mmcblk1p1 | less                                        
00000000  eb 58 90 6d 6b 66 73 2e  66 61 74 00 02 01 20 00  |.X.mkfs.fat... .|  
00000010  02 00 00 00 00 f8 00 00  20 00 40 00 00 00 00 00  |........ .@.....|  
00000020  00 00 08 00 c1 0f 00 00  00 00 00 00 02 00 00 00  |................|  

root@bpi-r64:~# hd /dev/mmcblk1p2 | less                                        
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|                                                                            
00000400  f0 c7 06 00 00 1b 1b 00  f3 5a 01 00 2a 78 12 00  |.........Z..*x..|  
00000410  c2 2d 06 00 00 00 00 00  02 00 00 00 02 00 00 00  |.-..............|  

root@bpi-r64:~# hd /dev/mmcblk1rpmb | less                                      
hd: /dev/mmcblk1rpmb: Invalid argument

so none of my emmc-partitions start with the bytes printed by uboot (8c 7c f2 7c 00 00 00 00)

Edit (cannot make new reply):

Got emmc working here

Old uboot always access sdcard. At least the debian-image is affected. But you can flash this and after that replace uboot with one of my binaries (matching your switch-chip)

Hi @Jackzeng @sinovoip does your repo contain wifi-/bt-driver? I have not found it yet…