Configuring kernel before building

Stephen · March 6, 2019, 7:24am

Pin gpio4-19 is GPIO4_C3 (also pin UART2_RXD). Here gpio4 means GPIO4 group( Others groups are GPIO0 GPIO1 GPIO2 GPIO3). Every group has pins A0~A7 B0~B7 C0~C7 D0~D7.

A0~A7 <---> 0-7
B0~B7 <---> 8-15
C0~C7 <---> 16-23
D0~D7 <---> 24-31

From above, we know that 19 corresponds to C3.

Calculation method such as “32*4 + 19 = 147” is used for controlling the GPIO in userspace. You can check https://wiki.radxa.com/Rockpi4/hardware/gpio.

O635789 · March 6, 2019, 7:33am

So the overlay turning off fiq_debugger somehow is not loaded or not effective, even if it’s configured in hw_intfc.conf. Could you please take a look at the issue? Thanks. I tried both of the methods you provided strictly.

Stephen · March 6, 2019, 8:22am

Hi, @O635789

hw_intfc.config and dtbo files are parsed by u-boot. Can you see the u-boot log? The hw_intfc.config and dtbo files are read.

Is okay to copy the u-boot and kernel log to here?

O635789 · March 7, 2019, 9:10pm

OK, I don’t know how to get u-boot log, but I’m attaching the kernel log from the beginning to UART2 failed to get the pins:

Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ …
Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ Mar 6 18:05:09 linaro-alip kernel: [ 0.000000] Booting Linux on physical CPU 0x0
0.000000] Initializing cgroup subsys cpuset
0.000000] Initializing cgroup subsys cpu
0.000000] Initializing cgroup subsys cpuacct
0.000000] Linux version 4.4.154 (v@mrs-hebe) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #13 SMP Mon Nov 5 18:25:35 CST 2018
0.000000] Boot CPU: AArch64 Processor [410fd034]
0.000000] Reserved memory: failed to reserve memory for node ‘drm-logo@00000000’: base 0x0000000000000000, size 0 MiB
0.000000] On node 0 totalpages: 1015296
0.000000] DMA zone: 15864 pages used for memmap
0.000000] DMA zone: 0 pages reserved
0.000000] DMA zone: 1015296 pages, LIFO batch:31
0.000000] psci: probing for conduit method from DT.
0.000000] psci: PSCIv1.0 detected in firmware.
0.000000] psci: Using standard PSCI v0.2 function IDs
0.000000] psci: MIGRATE_INFO_TYPE not supported.
0.000000] PERCPU: Embedded 21 pages/cpu @ffffffc0f7ed6000 s45800 r8192 d32024 u86016
0.000000] pcpu-alloc: s45800 r8192 d32024 u86016 alloc=21*4096
0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5
0.000000] Detected VIPT I-cache on CPU0
0.000000] CPU features: enabling workaround for ARM erratum 845719
0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 999432
0.000000] Kernel command line: earlyprintk rw root=PARTUUID=b921b045-1d rootfstype=ext4 init=/sbin/init rootwait
0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
0.000000] software IO TLB [mem 0xef400000-0xf3400000] (64MB) mapped at [ffffffc0ef400000-ffffffc0f33fffff]
0.000000] Memory: 3902456K/4061184K available (11646K kernel code, 1706K rwdata, 4408K rodata, 1152K init, 758K bss, 158728K reserved, 0K cma-reserved)
0.000000] Virtual kernel memory layout:
0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)
0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbdbfff0000 ( 246 GB)
0.000000] .init : 0xffffff8009040000 - 0xffffff8009160000 ( 1152 KB)
0.000000] .text : 0xffffff8008080000 - 0xffffff8008be0000 ( 11648 KB)
0.000000] .rodata : 0xffffff8008be0000 - 0xffffff8009040000 ( 4480 KB)
0.000000] .data : 0xffffff8009160000 - 0xffffff800930a808 ( 1707 KB)
0.000000] vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
0.000000] 0xffffffbdc0008000 - 0xffffffbdc3e00000 ( 61 MB actual)
0.000000] fixed : 0xffffffbffe7fb000 - 0xffffffbffec00000 ( 4116 KB)
0.000000] PCI I/O : 0xffffffbffee00000 - 0xffffffbfffe00000 ( 16 MB)
0.000000] memory : 0xffffffc000200000 - 0xffffffc0f8000000 ( 3966 MB)
0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
0.000000] Hierarchical RCU implementation.
0.000000] Build-time adjustment of leaf fanout to 64.
0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=6.
0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=6
0.000000] NR_IRQS:64 nr_irqs:64 0
0.000000] GIC: Using split EOI/Deactivate mode
0.000000] ITS: /interrupt-controller@fee00000/interrupt-controller@fee20000
0.000000] ITS: allocated 65536 Devices @300000 (psz 64K, shr 0)
0.000000] ITS: using cache flushing for cmd queue
0.000000] GIC: using LPI property table @0x0000000000290000
0.000000] ITS: Allocated 1792 chunks for LPIs
0.000000] CPU0: found redistributor 0 region 0:0x00000000fef00000
0.000000] CPU0: using LPI pending table @0x00000000002a0000
0.000000] GIC: using cache flushing for LPI property table
0.000000] GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@1[1] /cpus/cpu@2[2] /cpus/cpu@3[3] }
0.000000] GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@100[4] /cpus/cpu@101[5] }
0.000000] rockchip_mmc_get_phase: invalid clk rate
0.000000] rockchip_mmc_get_phase: invalid clk rate
0.000000] rockchip_mmc_get_phase: invalid clk rate
0.000000] rockchip_mmc_get_phase: invalid clk rate
0.000000] rockchip_clk_register_frac_branch: could not find dclk_vop0_frac as parent of dclk_vop0, rate changes may not work
0.000000] rockchip_clk_register_frac_branch: could not find dclk_vop1_frac as parent of dclk_vop1, rate changes may not work
0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
0.000006] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
0.001361] Console: colour dummy device 80x25
0.003077] console [tty0] enabled
0.003121] Calibrating delay loop (skipped), value calculated using timer frequency… 48.00 BogoMIPS (lpj=24000)
0.003182] pid_max: default: 32768 minimum: 301
0.003365] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
0.003405] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
0.004182] Initializing cgroup subsys devices
0.004225] Initializing cgroup subsys freezer
0.004274] ftrace: allocating 42154 entries in 165 pages
0.111855] sched-energy: Sched-energy-costs installed from DT
0.111904] CPU0: update cpu_capacity 401
0.111978] ASID allocator initialised with 32768 entries
0.115282] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created
0.115862] Platform MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created
0.117237] Detected VIPT I-cache on CPU1
0.117268] CPU1: found redistributor 1 region 0:0x00000000fef20000
0.117297] CPU1: using LPI pending table @0x00000000eed30000
0.117339] CPU1: update cpu_capacity 401
0.117343] CPU1: Booted secondary processor [410fd034]
0.117874] Detected VIPT I-cache on CPU2
0.117894] CPU2: found redistributor 2 region 0:0x00000000fef40000
0.117920] CPU2: using LPI pending table @0x00000000eed50000
0.117947] CPU2: update cpu_capacity 401
0.117950] CPU2: Booted secondary processor [410fd034]
0.118460] Detected VIPT I-cache on CPU3
0.118480] CPU3: found redistributor 3 region 0:0x00000000fef60000
0.118507] CPU3: using LPI pending table @0x00000000eeda0000
0.118533] CPU3: update cpu_capacity 401
0.118537] CPU3: Booted secondary processor [410fd034]
0.119069] Detected PIPT I-cache on CPU4
0.119096] CPU4: found redistributor 100 region 0:0x00000000fef80000
0.119135] CPU4: using LPI pending table @0x00000000eede0000
0.119173] CPU4: update cpu_capacity 1024
0.119176] CPU4: Booted secondary processor [410fd082]
0.119712] Detected PIPT I-cache on CPU5
0.119730] CPU5: found redistributor 101 region 0:0x00000000fefa0000
0.119766] CPU5: using LPI pending table @0x00000000eee10000
0.119793] CPU5: update cpu_capacity 1024
0.119796] CPU5: Booted secondary processor [410fd082]
0.119896] Brought up 6 CPUs
0.120577] SMP: Total of 6 processors activated.
0.120609] CPU features: detected feature: GIC system register CPU interface
0.120647] CPU: All CPU(s) started at EL2
0.120716] alternatives: patching kernel code
0.122144] devtmpfs: initialized
0.138368] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
0.138424] futex hash table entries: 2048 (order: 5, 131072 bytes)
0.138901] pinctrl core: initialized pinctrl subsystem
0.139136] regulator-dummy: no parameters
0.139668] NET: Registered protocol family 16
0.144547] cpuidle: using governor ladder
0.148556] cpuidle: using governor menu
0.148595] Registered FIQ tty driver
0.262984] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV
0.263105] of_get_named_gpiod_flags: parsed ‘gpio’ property of node ‘/vcc5v0-otg-regulator[0]’ - status (0)
0.263146] vcc5v0_otg: no parameters
0.263302] reg-fixed-voltage vcc5v0-otg-regulator: vcc5v0_otg supplying 0uV
0.263875] iommu: Adding device ff650000.vpu_service to group 0
0.264499] iommu: Adding device ff660000.rkvdec to group 1
0.265106] iommu: Adding device ff8f0000.vop to group 2
0.265661] iommu: Adding device ff900000.vop to group 3
0.266251] iommu: Adding device ff910000.cif_isp to group 4
0.268418] SCSI subsystem initialized
0.268945] usbcore: registered new interface driver usbfs
0.269499] usbcore: registered new interface driver hub
0.270063] usbcore: registered new device driver usb
0.270594] media: Linux media interface: v0.10
0.271033] Linux video capture interface: v2.00
0.271496] pps_core: LinuxPPS API ver. 1 registered
0.271962] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it
0.272810] PTP clock support registered
0.274165] Advanced Linux Sound Architecture Driver Initialized.
0.275194] Bluetooth: Core ver 2.21
0.275544] NET: Registered protocol family 31
0.275965] Bluetooth: HCI device and connection manager initialized
0.276545] Bluetooth: HCI socket layer initialized
0.277002] Bluetooth: L2CAP socket layer initialized
0.277477] Bluetooth: SCO socket layer initialized
0.278867] clocksource: Switched to clocksource arch_sys_counter
0.327269] thermal thermal_zone1: power_allocator: sustainable_power will be estimated
0.328231] NET: Registered protocol family 2
0.329074] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
0.329932] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes)
0.331396] TCP: Hash tables configured (established 32768 bind 32768)
0.332115] UDP hash table entries: 2048 (order: 5, 196608 bytes)
0.332825] UDP-Lite hash table entries: 2048 (order: 5, 196608 bytes)
0.333807] NET: Registered protocol family 1
0.334519] RPC: Registered named UNIX socket transport module.
0.335076] RPC: Registered udp transport module.
0.335511] RPC: Registered tcp transport module.
0.335953] RPC: Registered tcp NFSv4.1 backchannel transport module.
0.336555] PCI: CLS 0 bytes, default 64
0.337478] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
0.338331] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
0.342197] Initialise system trusted keyring
0.350489] squashfs: version 4.0 (2009/01/31) Phillip Lougher
0.351795] NFS: Registering the id_resolver key type
0.352296] Key type id_resolver registered
0.352685] Key type id_legacy registered
0.353150] fuse init (API version 7.23)
0.353892] SGI XFS with security attributes, no debug enabled
0.359262] NET: Registered protocol family 38
0.359694] Key type asymmetric registered
0.360088] Asymmetric key parser ‘x509’ registered
0.360686] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
0.361384] io scheduler noop registered
0.361754] io scheduler deadline registered
0.362274] io scheduler cfq registered (default)
0.363581] phy phy-ff770000.syscon:usb2-phy@e450.0: Looking up phy-supply from device tree
0.363680] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e450.0 err -2
0.363999] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up phy-supply from device tree
0.364010] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
0.364232] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up vbus-supply from device tree
0.364242] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
0.364255] phy phy-ff770000.syscon:usb2-phy@e450.1: Failed to get VBUS supply regulator
0.365744] phy phy-ff770000.syscon:usb2-phy@e460.2: Looking up phy-supply from device tree
0.365801] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e460.2 err -2
0.366089] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up phy-supply from device tree
0.366099] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e460/otg-port failed
0.366309] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up vbus-supply from device tree
0.366320] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e460/otg-port failed
0.366332] phy phy-ff770000.syscon:usb2-phy@e460.3: Failed to get VBUS supply regulator
0.368253] phy phy-ff770000.syscon:phy@f780.4: Looking up phy-supply from device tree
0.368264] phy phy-ff770000.syscon:phy@f780.4: Looking up phy-supply property in node /syscon@ff770000/phy@f780 failed
0.369007] phy phy-ff7c0000.phy.5: Looking up phy-supply from device tree
0.369017] phy phy-ff7c0000.phy.5: Looking up phy-supply property in node /phy@ff7c0000/dp-port failed
0.369114] phy phy-ff7c0000.phy.6: Looking up phy-supply from device tree
0.369123] phy phy-ff7c0000.phy.6: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed
0.369573] phy phy-ff800000.phy.7: Looking up phy-supply from device tree
0.369584] phy phy-ff800000.phy.7: Looking up phy-supply property in node /phy@ff800000/dp-port failed
0.369675] phy phy-ff800000.phy.8: Looking up phy-supply from device tree
0.369685] phy phy-ff800000.phy.8: Looking up phy-supply property in node /phy@ff800000/usb3-port failed
0.370053] phy phy-pcie-phy.9: Looking up phy-supply from device tree
0.370064] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
0.371500] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
0.371510] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
0.371538] of_get_named_gpiod_flags: parsed ‘ep-gpios’ property of node ‘/pcie@f8000000[0]’ - status (0)
0.371781] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
0.371791] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
0.371805] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
0.372402] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
0.372412] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
0.372423] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
0.373007] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
0.373017] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
0.373027] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
0.914923] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
0.915679] rockchip-pcie: probe of f8000000.pcie failed with error -110
0.917432] rk-vcodec ff650000.vpu_service: Looking up vcodec-supply from device tree
0.917447] rk-vcodec ff650000.vpu_service: Looking up vcodec-supply property in node /vpu_service@ff650000 failed
0.917471] rk-vcodec ff650000.vpu_service: no regulator for vcodec
0.918437] rk-vcodec ff650000.vpu_service: probe device
0.919246] rk-vcodec ff650000.vpu_service: drm allocator with mmu enabled
0.920622] rk-vcodec ff650000.vpu_service: could not find power_model node
0.921285] rk-vcodec ff650000.vpu_service: init success
0.922182] rk-vcodec ff660000.rkvdec: Looking up vcodec-supply from device tree
0.922197] rk-vcodec ff660000.rkvdec: Looking up vcodec-supply property in node /rkvdec@ff660000 failed
0.922217] rk-vcodec ff660000.rkvdec: no regulator for vcodec
0.923217] rk-vcodec ff660000.rkvdec: probe device
0.923898] rk-vcodec ff660000.rkvdec: drm allocator with mmu enabled
0.924902] rk-vcodec ff660000.rkvdec: could not find power_model node
0.925492] rk-vcodec ff660000.rkvdec: init success
0.927341] dma-pl330 ff6d0000.dma-controller: Loaded driver for PL330 DMAC-241330
0.928049] dma-pl330 ff6d0000.dma-controller: DBUFF-32x8bytes Num_Chans-6 Num_Peri-12 Num_Events-12
0.930314] dma-pl330 ff6e0000.dma-controller: Loaded driver for PL330 DMAC-241330
0.931021] dma-pl330 ff6e0000.dma-controller: DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16
0.932237] pwm-regulator vdd-log: GPIO lookup for consumer enable
0.932246] pwm-regulator vdd-log: using device tree for GPIO lookup
0.932256] of_get_named_gpiod_flags: can’t parse ‘enable-gpios’ property of node ‘/vdd-log[0]’
0.932265] of_get_named_gpiod_flags: can’t parse ‘enable-gpio’ property of node ‘/vdd-log[0]’
0.932273] pwm-regulator vdd-log: using lookup tables for GPIO lookup
0.932281] pwm-regulator vdd-log: lookup for GPIO enable failed
0.932305] pwm-regulator vdd-log: Looking up pwm-supply from device tree
0.932314] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed
0.932357] vdd_log: 800 <–> 1400 mV at 800 mV
0.932518] pwm-regulator vdd-log: Looking up pwm-supply from device tree
0.932528] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed
0.932573] pwm-regulator vdd-log: Looking up pwm-supply from device tree
0.932582] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed
0.932958] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled
0.935184] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 37, base_baud = 1500000) is a 16550A
0.936316] rockchip-pinctrl pinctrl: pin gpio4-19 already requested by fiq-debugger; cannot claim for ff1a0000.serial
0.937296] rockchip-pinctrl pinctrl: pin-147 (ff1a0000.serial) status -22
0.937928] rockchip-pinctrl pinctrl: could not request pin 147 (gpio4-19) from group uart2c-xfer on device rockchip-pinctrl
0.938955] dw-apb-uart ff1a0000.serial: Error applying setting, reverse things back
0.939982] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 38, base_baud = 1500000) is a 16550A
0.941417] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 40, base_baud = 1500000) is a 16550A

O635789 · March 7, 2019, 1:17am

Regardless which console I set in extlinux.conf, or not set at all, ttyFIQ is always registered right after GPIO pins are registered. This is my u-boot version by the way:
libjs-bootstrap/stable,now 3.3.7+dfsg-2+deb9u1 all [installed]
rockpi4b-rk-u-boot-lastest/unknown,now 2017.09-00004-g2920a61 all [installed]
rockpi4b-rk-ubootimg/unknown,now 2017.09-00004-g2920a61 all [installed,automatic]

Stephen · March 7, 2019, 2:08am

Hi, @O635789

I just do the test.

I use rockpi4_debian_stretch_lxde_armhf_20181105_2120-gpt.img. And I install rockchip-overlay , rockchip-fstab and rockpi4-dtbo package. Then update the u-boot and kernel to the newest version. Reboot.

When the contents of /boot/hw_intfc.conf are

intfc:pwm0=off
intfc:pwm1=off
intfc:uart2=on
intfc:uart4=on
intfc:spi1=off
intfc:spi2=off
intfc:i2c2=off
intfc:i2c6=off
intfc:i2c7=off

#intfc:dtoverlay=at24c02
#intfc:dtoverlay=two-color-led
#intfc:dtoverlay=console-disabled
#intfc:dtoverlay=console-on-uart4

And I execute sudo dmesg, it shows the same result as yours.

[    2.242621] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled
[    2.245435] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 35, base_baud = 1500000) is a 16550A
[    2.246630] rockchip-pinctrl pinctrl: pin gpio4-19 already requested by fiq-debugger; cannot claim for ff1a0000.serial
[    2.247599] rockchip-pinctrl pinctrl: pin-147 (ff1a0000.serial) status -22
[    2.248208] rockchip-pinctrl pinctrl: could not request pin 147 (gpio4-19) from group uart2c-xfer  on device rockchip-pinctrl
[    2.249201] dw-apb-uart ff1a0000.serial: Error applying setting, reverse things back
[    2.250295] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 36, base_baud = 1500000) is a 16550A
[    2.251923] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 38, base_baud = 1500000) is a 16550A

When the contents are modified to

intfc:pwm0=off
intfc:pwm1=off
intfc:uart2=on
intfc:uart4=on
intfc:spi1=off
intfc:spi2=off
intfc:i2c2=off
intfc:i2c6=off
intfc:i2c7=off

#intfc:dtoverlay=at24c02
#intfc:dtoverlay=two-color-led
intfc:dtoverlay=console-disabled
#intfc:dtoverlay=console-on-uart4

It shows

[    2.124915] pwm-regulator vdd-log: Looking up pwm-supply from device tree
[    2.124925] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed
[    2.125018] pwm-regulator vdd-log: Looking up pwm-supply from device tree
[    2.125027] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed
[    2.125390] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled
[    2.127009] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 35, base_baud = 1500000) is a 16550A
[    2.127624] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 36, base_baud = 1500000) is a 16550A
[    2.128245] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 38, base_baud = 1500000) is a 16550A
[    2.129252] [drm] Initialized drm 1.1.0 20060810
[    2.132979] [drm] Rockchip DRM driver version: v1.0.1

When uncomment intfc:dtoverlay=console-disabled, the fiq-debugger is not registered.

O635789 · March 7, 2019, 5:04am

Finally it’s working! My Z-Wave HAT works flawlessly! Thank you guys.

The problem is the order of the steps. I need to run ./rockpi4b_upgrade_bootloader.sh AFTER installed rockchip-overlay.

I flashed a new copy of the image to my microSD card, and repeated the steps still didn’t work then I figured the only difference is you upgraded u-boot and kernel after the overlay.

jack · March 7, 2019, 6:15am

Good to hear that. Which Z wave HAT are you using?

O635789 · March 7, 2019, 6:44am

I’m using Z-Wave.Me RaZberry2.

TE999 · March 7, 2019, 11:49am

Hallo Radxa Team,

I’m not so fit on the Linux track yet.
I have the current Debian Images installed and now I try to integrate the Z-Wave.Me 2 RaZberry2.
Is it possible to show the individual installation steps one after the other?
Many Thanks

TE999 · March 7, 2019, 2:40pm

Hello
Can you help me
how do I run an update the u-boot and kernel?
Thomas

O635789 · March 7, 2019, 9:25pm

Here is the steps I did:

add “deb http://apt.radxa.com/stretch/ stretch main” to /etc/apt/sources.list
get the repository key: “wget -O - apt.radxa.com/stretch/public.key | sudo apt-key add -”
update your apps: “sudo apt-get update && sudo apt-get upgrade”
install rockchip-overlay etc:
sudo apt-get install rockchip-overlay
sudo apt-get install rockchip-fstab
sudo apt-get install rockpi4-dtbo
edit /etc/hw_intfc.config, turn on uart2, uart4, and the overlay disables the console.
update kernel:
apt-get install linux-4.4-lastest
update u-boot:
sudo su
apt-get install rockpi4b-rk-u-boot-lastest
cd /usr/local/sbin/
./rockpi4b_upgrade_bootloader.sh
reboot, type “who” in xterm, should shows you as the only user, nobody on ttyFIQ0
In Z-Way server or Home Assistant, change the default uart setting from ttyAMA0 to ttyS2.
reboot. who says you don’t need to reboot Linux often? :-/

Stephen · March 8, 2019, 8:25am

Hello, @TE999

We have a tutorial on updating u-boot and kernel. Please check :https://wiki.radxa.com/Rockpi4/radxa-apt

TE999 · March 9, 2019, 5:08pm

Hello,
Thank you for the information.
Z-wave is running now. The communication with IP-Symcon and Z-Wave on the Rock PI4 is OK.
I am happy

Thomas

lucho · March 9, 2019, 6:26pm

It would be nice to have better instructions on how to build a custom kernel not only for ubuntu and stretch.

Let me start complaining about the debian and ubuntu images. The boot partition is so small, that you can’t have more than one kernel on it.

Second, there HAS to be a way to build the kernel on the board itself. It’s not rocket science.

Third instructions don’t work for the armbian package you provide. Installing the created .deb packages doesn’t update the /boot/Image link. While the dtb directory for the standard kernel is in /boot/dtb-4.4.154-rk3339rockpi4b (with symbolic link to it from dtb), the dtbs for a custom kernel are in /usr/lib/. Why?

Fourth, looking at the kernel messages, it looks that it tries to load firmware from /system directory, which, of course, doesn’t exist. That makes wifi fail. If I make it to point to the right place, the kernel doesn’t boot.

I understand that radxa has a small team, but the distribution and the software support at the moment is awful. I have a lot of experience with the linux kernel on x86 (have few thousands of lines in the kernel source code), and none for arm architectures. I expected more mature ecosystem.

jack · March 11, 2019, 2:40am

Hi, Lucho

Thanks for all your inputs. Some of the issue are from us, some are the vendor kernel specific, moving to mainline kernel will fix it. Some are the ARM linux ecosystem issue, it’s getting better but not as good as x86 in seeing future.

/boot partition is too small. We will fix it, because of adding the initrd, it increase the /boot size a lot.
build kernel on ROCK Pi 4 of course works, we will add a wiki page for that
instructions doesn’t work for armbian, that’s not our issue. we use the standard kernel deb package(only we modify the ARCH to all). Armbian has it’s only kernel building instructions. Maybe we should add that on the wiki. why dtbs are in /usr/lib, we did not modify this, it’s what the kernel 4.4 do by default. If you build on ROCK Pi 4, you can specify the dtbs_install location.
firmware in /system, that’s the vendor kernel issue. We do not change it for easier updating with Rockchip.

For a more mature ecosystem, we need to move to mainline and more standard booting etc.

lucho · March 11, 2019, 2:00pm

Thank you for the answers. I expect at least

make
make modules_install
make install

in the kernel source on the RockPi to make and boot the newly compiled kernel. Right not, it doesn’t.

It is also very annoying to have random features working on this image and not working on another, so we need to shop around for the things we care about. I care about 64-bit, so I chose armbian. Bluetooth wasn’t working so I had to copy some random script from another image (maybe ubuntu, I forgot) to make it work. I still have no idea if I can use opencl on the image I have, I didn’t get to even that far.

TE999 · March 17, 2019, 10:30am

Hallo,
as described above, the UPart works under debian with the z-wave Controller.
I switched to Ubuntu bionic yesterday because some comonets did not run on debian.
As described above, I made the entry in dr sources.list and updated the U-Boot and Kernel.
But now the “/boot/extlinux/extlinux.conf” or “/boot/extlinux/extlinux.config” file does not exist anymore.
Who can help?
Thank you

jolla · March 19, 2019, 1:32pm

“su” and “sudo su” not work

linaro@linaro-alip:~$ su Password: su: Authentication failure

jack · March 18, 2019, 2:11am

Please check your /etc/fstab, if the /boot is proper mount. If not, you should install rockchip-fstab package, which will mount the boot partition on /boot automatically.