[BPI-R64] PCIe issues

frank-w · August 6, 2020, 12:58pm

as far as i see you use official image (e.g. debian jessie), i don’t think you can upgrade to a recent glibc here…

afair linux-kernel also compiles a libc-package as deb…maybe this helps else you could try with my debian buster

but please move this in new thread…it’s no PCIe Issue

batul.rangwala · August 7, 2020, 4:05am

Yes, sure, I can move this thread once I can confirm it.

As per the support team from Google Coral, they also suggest Debian Buster. Is this 5.8-r64 branch a debian buster.

Also additionally please suggest the commands to compile libc-package using the linux kernel

frank-w · August 7, 2020, 5:11am

My repo is only kernel (and some tools).

My buster-image is on my gdrive

I see libc deb when using pack_debs option from build.sh

batul.rangwala · August 7, 2020, 5:55am

Hi,

Can you please share the buster image. Does it have the pcie related changes from mtk that is included in the 5.8-rc version I am using. Also while compiing the 5.8-rc image I had enable the CONFIG_DMA_SHARED_BUFFER.

Alternatively if I can recompile my 5.8-rc kernel for debian-buster what all I need to set up in the config and build.sh.

Also as per the build.sh following is the pack_debs

function pack_debs {
	get_version
	echo "pack linux-headers, linux-image, linux-libc-dev debs..."
    echo "LOCALVERSION=${gitbranch} board=$board ARCH=$ARCH CROSS_COMPILE=$CROSS_COMPILE"
	LOCALVERSION="${gitbranch}" board="$board" make bindeb-pkg
	ls ../*.deb
}

Is there a way we can add a specific version like 2.27.

frank-w · August 7, 2020, 6:08am

Link to gdrive is in first post of that thread. You have to replace kernel like you did it with your current image

Compiling with pack_debs creates a libc deb,but i don’t know if this enough. So i suggest using debian buster and install your currrent built kernel there

wernervx · May 16, 2021, 8:10am

I have a new issue compiing the kernel for R64. It seems to exist across all versions in this repo:

I have tried 5.4 through to 5.10 and to the latest. The R64 boots fine with any Ubuntu pre-built image. I am currently trying with this one: https://download.banana-pi.dev/d/3ebbfa04265d4dddb81b/files/?p=%2FImages%2FBPI-R64%2FUbuntu18.04%2F2020-12-20-ubuntu-18.04.3-bpi-r64-5.4-sd-emmc.img.zip

The R64 boots fine with the above image but as soon as I create a new kernel (even with no additional config options just what importconfig creates), I get the following booting into BPI:

'Unsupported Architecture 0x16 ERROR: can’t get kernel image! bootm flag=0, states=70f

Booting kernel from Legacy Image at 4007ff28 …

Image Name: Linux Kernel 5.10.34-main Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 15165448 Bytes = 14.5 MiB Load Address: 40080000 Entry Point: 40080000 Verifying Checksum … OK Unsupported Architecture 0x16 ERROR: can’t get kernel image!’

I have re-compiled on different trees and branches with default and different options to no avail. When changes uENV back to Uimage and standard dtb all goes well, but I need some addidiontal kernel configs. Anyone had this issue before?

frank-w · May 16, 2021, 8:28am

For images with old bootchain (imho all except my new debian image) you need to generate armhf (32bit) uImage (with aarch64 kernel) and load dtb separately. So only change board in build.conf and not uimagearch

github.com

frank-w/BPI-R2-4.14/blob/5.4-main/build.conf#L12


uploadserver=r2
uploaddir=/var/lib/tftp
#uploaduser=root
#uploadserver=192.168.0.11
#uploaddir=/boot/bananapi/bpi-r2/linux


#builddir=../build
#ramdisksize=3G


board=bpi-r2
#board=bpi-r64
#r64 uses 2 ethernet-chips (setting choose which dtb is used)
#boardversion=1.0
#mainline uboot for r64 needs 64bit uImage
#uimagearch=arm64

Then install not fit but uImage and dtb

Have tried new way with fit in last time…need to look if i have an old card somewhere ready

But it looks like you have enabled the uimagearch=aarch64 option,so uImage container is 64bit instead of 32bit

Just for explaination:

Old uboot (and my if built for old bootchain) is 32bit,unpacks uImage (container) into memory,elevates to 64bit-mode (jumparch target in old atf) and the boot 64bit linux kernel.

New bootchain is always in 64bit mode (uboot itself is packed as fip). So there is no elevation and here container (fit image) is 64bit too.

Another way was using a other atf which can boot 64bit uboot that can load only 64bit uimage

wernervx · May 19, 2021, 12:41am

Thank you very much for the detailed explanation. Your solution worked perfectly.

alga_kbk · December 7, 2021, 4:11pm

On the BPI-R64 specification confused me, telling only one mini PCIe interface. Does the both mini PCIe port works, if I attach the 4G modem and WIFI module on both ports, or two wifi mini pcie modules?

frank-w · December 7, 2021, 4:35pm

first r64 had only one pcie-slot (second was used for builtin mt7615 which was dropped due heat), i guess it is an old information…

you can use both pcie-slots, if you do not use sata-port (shared with cn8)

alga_kbk · December 8, 2021, 3:33am

Thank you for your reply, good to know that sata and cn8 use same pcie lanes

frank-w · December 10, 2021, 7:14pm

You need to configure this in dts. There is a gpio-hog for gpio90 to choose the mode…in my repo it is set to sata,so cn8 is disabled

github.com

frank-w/BPI-R2-4.14/blob/55eb4725e16f1ff0322a63757eceda80c3c7c014/arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts#L302


	status = "okay";
};


&pio {
	/* Attention: GPIO 90 is used to switch between PCIe@1,0 and
	 * SATA functions. i.e. output-high: PCIe, output-low: SATA
	 */
	asm_sel {
		gpio-hog;
		gpios = <90 GPIO_ACTIVE_HIGH>;
		output-low;
	};


	/* eMMC is shared pin with parallel NAND */
	emmc_pins_default: emmc-pins-default {
		mux {
			function = "emmc", "emmc_rst";
			groups = "emmc";
		};


		/* "NDL0","NDL1","NDL2","NDL3","NDL4","NDL5","NDL6","NDL7",

To use cn8 set it to output-high;