search

rockchip-linux / kernel

BSP kernel source
Other
917 stars 1.07k forks source link

Booting problem with RK3066 #75

Closed sziszi closed 6 years ago

sziszi commented 6 years ago

I try to boot an RK3066 device with this kernel and i cannot succeed. I tried two scenarios:

1: I followed the guide from here http://opensource.rock-chips.com/wiki_Rockchip_Kernel

After i successfully build a boot image and flash it to the boot partition i got an error like this:

DDR Version 1.04 20140217 In SRX DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=8 Size=1024MB OUT BUILD=====2 No.1 FLASH ID:ec d7 94 7a 54 43 OK! 252353 unsigned! SecureBootEn = 0 0 Boot ver: 2014-06-27#2.15 start_linux=====259477 E:Invaid tag(0x4D524150)! Load failed! E:Invaid tag(0x4D524150)! Load failed! UsbBoot 265826 UsbHook ...920093 powerOn 920119 1075219 UsbConnected 1189061 UsbConnected

2: My second approach is the following

cat linux/arch/arm/boot/zImage linux/arch/arm/boot/dts/rk3066a-marsboard.dtb > flash/zImage-dtb

mkbootimg --kernel flash/zImage-dtb --ramdisk /dev/null --base 60800000 -o flash/boot.img

mv flash/boot.img flash/boot.img-old rkcrc flash/boot.img-old flash/boot.img

Then flash the boot.img to the device and get the following log..

start_linux=====281959 2430047 Starting kernel...@0x60808000

[ 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.103 (root@ubuntu-docker) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #1 SMP Thu Mar 22 17:12:31 EET 2018 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: MarsBoard RK3066 [ 0.000000] cma: Reserved 16 MiB at 0x9f000000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] PERCPU: Embedded 14 pages/cpu @ef7c2000 s24728 r8192 d24424 u57344 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608 [ 0.000000] Kernel command line: console=tty0 console=ttyS2,115200n8 earlyprintk root=/dev/mtdblock2 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00040000 mtdparts=rk29xxnand:0x00002000@0x00000000(parameter),0x00002000@0x00002000(boot),0x00002000@0x00004000(loader2),0x00002000@0x00006000(atf),0x00038000@0x00008000(boot:bootable),-@0x0040000(rootfs) bootver=2014-06-27#2.15 firmware_ver=6.0.0 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1002656K/1048576K available (12288K kernel code, 942K rwdata, 3252K rodata, 1024K init, 633K bss, 29536K reserved, 16384K cma-reserved, 245760K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc0d00000 (13280 kB) [ 0.000000] .init : 0xc1200000 - 0xc1300000 (1024 kB) [ 0.000000] .data : 0xc1300000 - 0xc13ebbd8 ( 943 kB) [ 0.000000] .bss : 0xc13ed000 - 0xc148b7b0 ( 634 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] L2C-310: enabling full line of zeros but not enabled in Cortex-A9 [ 0.000000] L2C-310 ID prefetch enabled, offset 15 lines [ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled [ 0.000000] L2C-310 cache controller enabled, 16 ways, 512 kB [ 0.000000] L2C-310: CACHE_ID 0x4100c0c8, AUX_CTRL 0x76050001 [ 0.000012] sched_clock: 64 bits at 102MHz, resolution 9ns, wraps every 4398046511102ns [ 0.000037] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x17863a1e30, max_idle_ns: 440795202667 ns [ 0.000806] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.001405] Console: colour dummy device 80x30 [ 0.002450] console [tty0] enabled [ 0.002495] Calibrating delay loop... 1626.93 BogoMIPS (lpj=8134656) [ 0.090204] pid_max: default: 32768 minimum: 301 [ 0.090335] Security Framework initialized [ 0.090367] Yama: becoming mindful. [ 0.090446] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.090486] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.091332] Initializing cgroup subsys devices [ 0.091385] Initializing cgroup subsys freezer [ 0.091437] CPU: Testing write buffer coherency: ok [ 0.091499] ftrace: allocating 43001 entries in 127 pages [ 0.172712] CPU0: update cpu_capacity 1024 [ 0.172756] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.172998] rockchip_smp_prepare_cpus: ncores 2 [ 0.173148] Setting up static identity map for 0x60100000 - 0x60100058 [ 0.210167] CPU1: update cpu_capacity 1024 [ 0.210175] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.210301] Brought up 2 CPUs [ 0.210373] SMP: Total of 2 processors activated (3253.86 BogoMIPS). [ 0.210396] CPU: All CPU(s) started in SVC mode. [ 0.211472] devtmpfs: initialized [ 0.220244] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.220704] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.220771] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.222067] pinctrl core: initialized pinctrl subsystem [ 0.223287] NET: Registered protocol family 16 [ 0.225902] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.250200] cpuidle: using governor ladder [ 0.280195] cpuidle: using governor menu [ 0.280243] Registered FIQ tty driver [ 0.281082] Failed to find PMU node [ 0.292161] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.292211] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.292602] fiq-debugger is missing in device tree! [ 0.363094] SCSI subsystem initialized [ 0.363470] usbcore: registered new interface driver usbfs [ 0.363564] usbcore: registered new interface driver hub [ 0.363707] usbcore: registered new device driver usb [ 0.363872] Linux video capture interface: v2.00 [ 0.363937] pps_core: LinuxPPS API ver. 1 registered [ 0.363962] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it [ 0.364017] PTP clock support registered [ 0.364936] Advanced Linux Sound Architecture Driver Initialized. [ 0.365769] Bluetooth: Core ver 2.21 [ 0.365843] NET: Registered protocol family 31 [ 0.365867] Bluetooth: HCI device and connection manager initialized [ 0.365898] Bluetooth: HCI socket layer initialized [ 0.365926] Bluetooth: L2CAP socket layer initialized [ 0.365978] Bluetooth: SCO socket layer initialized [ 0.367830] clocksource: Switched to clocksource arm_global_timer [ 0.430760] NET: Registered protocol family 2 [ 0.431511] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.431639] TCP bind hash table entries: 8192 (order: 5, 163840 bytes) [ 0.431917] TCP: Hash tables configured (established 8192 bind 8192) [ 0.432039] UDP hash table entries: 512 (order: 2, 24576 bytes) [ 0.432111] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes) [ 0.432452] NET: Registered protocol family 1 [ 0.432985] RPC: Registered named UNIX socket transport module. [ 0.433020] RPC: Registered udp transport module. [ 0.433042] RPC: Registered tcp transport module. [ 0.433063] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.433386] Trying to unpack rootfs image as initramfs... [ 0.433680] rootfs image is not initramfs (junk in compressed archive); looks like an initrd [ 0.434754] Freeing initrd memory: 256K [ 0.437497] Initialise system trusted keyring [ 0.449329] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.451610] NFS: Registering the id_resolver key type [ 0.451689] Key type id_resolver registered [ 0.451713] Key type id_legacy registered [ 0.451758] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 0.452546] fuse init (API version 7.23) [ 0.458275] NET: Registered protocol family 38 [ 0.458347] Key type asymmetric registered [ 0.458380] Asymmetric key parser 'x509' registered [ 0.458486] bounce: pool size: 64 pages [ 0.458748] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248) [ 0.458794] io scheduler noop registered [ 0.458822] io scheduler deadline registered [ 0.458883] io scheduler cfq registered (default) [ 0.459264] rockchip-usb-phy phy: vbus_drv is not assigned! [ 0.462501] dma-pl330 20018000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.462554] dma-pl330 20018000.dma-controller: DBUFF-32x8bytes Num_Chans-6 Num_Peri-12 Num_Events-12 [ 0.465156] dma-pl330 20078000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.465207] dma-pl330 20078000.dma-controller: DBUFF-64x8bytes Num_Chans-7 Num_Peri-20 Num_Events-14 [ 0.465992] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled [ 0.468429] 10124000.serial: ttyS0 at MMIO 0x10124000 (irq = 23, base_baud = 1500000) is a 16550A [ 0.489429] 10126000.serial: ttyS1 at MMIO 0x10126000 (irq = 24, base_baud = 1500000) is a 16550A [ 0.490455] console [ttyS2] disabled [ 0.510629] 20064000.serial: ttyS2 at MMIO 0x20064000 (irq = 31, base_baud = 1500000) is a 16550A [ 1.390042] console [ttyS2] enabled [ 1.414959] 20068000.serial: ttyS3 at MMIO 0x20068000 (irq = 32, base_baud = 1500000) is a 16550A [ 1.425936] [drm:drm_core_init] Initialized drm 1.1.0 20060810 [ 1.433571] rockchip-drm display-subsystem: No available vop found for display-subsystem. [ 1.442926] usbcore: registered new interface driver udl [ 1.451017] brd: module loaded [ 1.462204] loop: module loaded [ 1.466637] zram: Added device: zram0 [ 1.470785] lkdtm: No crash points registered, enable through debugfs [ 1.478655] tun: Universal TUN/TAP device driver, 1.6 [ 1.484260] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com [ 1.492452] PPP generic driver version 2.4.2 [ 1.497597] usbcore: registered new interface driver rndis_wlan [ 1.504474] usbcore: registered new interface driver rt2800usb [ 1.511070] Rockchip WiFi SYS interface (V1.00) ... [ 1.516630] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver [ 1.524927] usbcore: registered new interface driver pegasus [ 1.531302] usbcore: registered new interface driver rtl8150 [ 1.537633] usbcore: registered new interface driver r8152 [ 1.543800] usbcore: registered new interface driver asix [ 1.549867] usbcore: registered new interface driver ax88179_178a [ 1.556676] usbcore: registered new interface driver cdc_ether [ 1.563218] usbcore: registered new interface driver dm9601 [ 1.569489] usbcore: registered new interface driver smsc75xx [ 1.575940] usbcore: registered new interface driver smsc95xx [ 1.582392] usbcore: registered new interface driver net1080 [ 1.588745] usbcore: registered new interface driver rndis_host [ 1.595365] usbcore: registered new interface driver MOSCHIP usb-ethernet driver [ 1.603685] usbcore: registered new interface driver cdc_ncm [ 1.610038] usbcore: registered new interface driver cdc_mbim [ 1.616669] 10180000.usb supply vusb_d not found, using dummy regulator [ 1.624106] 10180000.usb supply vusb_a not found, using dummy regulator [ 1.837857] dwc2 10180000.usb: 128 invalid for host_nperio_tx_fifo_size. Check HW configuration. [ 1.847605] dwc2 10180000.usb: 256 invalid for host_perio_tx_fifo_size. Check HW configuration. [ 1.977877] dwc2 10180000.usb: EPs: 10, dedicated fifos, 972 entries in SPRAM [ 1.986389] dwc2 10180000.usb: DWC OTG Controller [ 1.991675] dwc2 10180000.usb: new USB bus registered, assigned bus number 1 [ 1.999539] dwc2 10180000.usb: irq 25, io mem 0x00000000 [ 2.005635] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.013186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.021212] usb usb1: Product: DWC OTG Controller [ 2.026426] usb usb1: Manufacturer: Linux 4.4.103 dwc2_hsotg [ 2.032711] usb usb1: SerialNumber: 10180000.usb [ 2.038697] hub 1-0:1.0: USB hub found [ 2.042907] hub 1-0:1.0: 1 port detected [ 2.048130] 101c0000.usb supply vusb_d not found, using dummy regulator [ 2.055533] 101c0000.usb supply vusb_a not found, using dummy regulator [ 2.238113] dwc2 101c0000.usb: DWC OTG Controller [ 2.243373] dwc2 101c0000.usb: new USB bus registered, assigned bus number 2 [ 2.251254] dwc2 101c0000.usb: irq 26, io mem 0x00000000 [ 2.257435] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.264988] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.273016] usb usb2: Product: DWC OTG Controller [ 2.278245] usb usb2: Manufacturer: Linux 4.4.103 dwc2_hsotg [ 2.284515] usb usb2: SerialNumber: 101c0000.usb [ 2.290472] hub 2-0:1.0: USB hub found [ 2.294680] hub 2-0:1.0: 1 port detected [ 2.300522] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.307775] ehci-platform: EHCI generic platform driver [ 2.313785] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.320682] ohci-platform: OHCI generic platform driver [ 2.326714] usbcore: registered new interface driver cdc_acm [ 2.333008] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2.341966] usbcore: registered new interface driver cdc_wdm [ 2.348378] usbcore: registered new interface driver usb-storage [ 2.355163] usbcore: registered new interface driver usbserial [ 2.361706] usbcore: registered new interface driver usbserial_generic [ 2.368996] usbserial: USB Serial support registered for generic [ 2.375715] usbcore: registered new interface driver cp210x [ 2.381946] usbserial: USB Serial support registered for cp210x [ 2.388602] usbcore: registered new interface driver ftdi_sio [ 2.395006] usbserial: USB Serial support registered for FTDI USB Serial Device [ 2.403428] usbcore: registered new interface driver keyspan [ 2.409774] usbserial: USB Serial support registered for Keyspan - (without firmware) [ 2.418512] usbserial: USB Serial support registered for Keyspan 1 port adapter [ 2.426652] usbserial: USB Serial support registered for Keyspan 2 port adapter [ 2.434819] usbserial: USB Serial support registered for Keyspan 4 port adapter [ 2.443024] usbcore: registered new interface driver option [ 2.449260] usbserial: USB Serial support registered for GSM modem (1-port) [ 2.457179] usbcore: registered new interface driver oti6858 [ 2.463517] usbserial: USB Serial support registered for oti6858 [ 2.470254] usbcore: registered new interface driver pl2303 [ 2.476476] usbserial: USB Serial support registered for pl2303 [ 2.483122] usbcore: registered new interface driver qcserial [ 2.489546] usbserial: USB Serial support registered for Qualcomm USB modem [ 2.497330] usbcore: registered new interface driver sierra [ 2.503693] usbserial: USB Serial support registered for Sierra USB modem [ 2.512450] usbcore: registered new interface driver iforce [ 2.518776] usbcore: registered new interface driver xpad [ 2.525233] usbcore: registered new interface driver usbtouchscreen [ 2.532658] i2c /dev entries driver [ 2.538879] gpiochip_find_base: cannot find free range [ 2.544587] gpiochip_add: GPIOs -1..4 (tps65910) failed to register [ 2.551573] tps65910-gpio tps65910-gpio: Could not register gpiochip, -28 [ 2.559125] tps65910-gpio: probe of tps65910-gpio failed with error -28 [ 2.568106] vrtc: supplied by vsys [ 2.575608] vio: supplied by vsys [ 2.580260] sdmmc-supply: supplied by vcc_io [ 2.585647] vdd1: supplied by vsys [ 2.591360] vdd2: supplied by vsys [ 2.597890] vdig1: supplied by vcc_io [ 2.603332] vdig2: supplied by vcc_io [ 2.608777] vpll: supplied by vcc_io [ 2.614120] vdac: supplied by vcc_io [ 2.619477] vaux1: supplied by vsys [ 2.624723] vaux2: supplied by vsys [ 2.630149] vaux33: supplied by vsys [ 2.635285] vmmc: supplied by vsys [ 2.640506] vbb: supplied by vsys [ 2.653237] tps65910-rtc tps65910-rtc: rtc core: registered tps65910-rtc as rtc0 [ 2.661715] rk3x-i2c 2002f000.i2c: Initialized RK3xxx I2C bus at f08aa000 [ 2.669953] usbcore: registered new interface driver uvcvideo [ 2.676328] USB Video Class driver (1.1.1) [ 2.682563] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com [ 2.692005] usb 2-1: new high-speed USB device number 2 using dwc2 [ 2.699152] Bluetooth: Virtual HCI driver ver 1.5 [ 2.704619] Bluetooth: HCI UART driver ver 2.3 [ 2.709610] Bluetooth: HCI UART protocol H4 registered [ 2.715303] Bluetooth: HCI UART protocol LL registered [ 2.721018] Bluetooth: HCI UART protocol ATH3K registered [ 2.727119] usbcore: registered new interface driver bfusb [ 2.733314] usbcore: registered new interface driver btusb [ 2.739696] ------------[ cut here ]------------ [ 2.744836] WARNING: CPU: 1 PID: 1 at drivers/base/power/opp/core.c:2050 dev_pm_opp_of_add_table+0x3c0/0x48c() [ 2.755946] Modules linked in: [ 2.759361] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.103 #1 [ 2.766012] Hardware name: Rockchip (Device Tree) [ 2.771252] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) [ 2.779849] [] (show_stack) from [] (dump_stack+0x84/0xa0) [ 2.787866] [] (dump_stack) from [] (warn_slowpath_common+0x98/0xc4) [ 2.796840] [] (warn_slowpath_common) from [] (warn_slowpath_null+0x2c/0x34) [ 2.806582] [] (warn_slowpath_null) from [] (dev_pm_opp_of_add_table+0x3c0/0x48c) [ 2.816810] [] (dev_pm_opp_of_add_table) from [] (cpufreq_init+0xdc/0x358) [ 2.826363] [] (cpufreq_init) from [] (cpufreq_online+0x264/0x6b4) [ 2.835146] [] (cpufreq_online) from [] (cpufreq_add_dev+0x4c/0xa0) [ 2.844026] [] (cpufreq_add_dev) from [] (subsys_interface_register+0xac/0xd8) [ 2.853964] [] (subsys_interface_register) from [] (cpufreq_register_driver+0x10c/0x1cc) [ 2.864859] [] (cpufreq_register_driver) from [] (dt_cpufreq_probe+0xb8/0xe8) [ 2.874698] [] (dt_cpufreq_probe) from [] (platform_drv_probe+0x60/0xb0) [ 2.884059] [] (platform_drv_probe) from [] (driver_probe_device+0x120/0x2a4) [ 2.893896] [] (driver_probe_device) from [] (driver_attach+0x78/0x9c) [ 2.903252] [] (__driver_attach) from [] (bus_for_each_dev+0x7c/0xa0) [ 2.912321] [] (bus_for_each_dev) from [] (driver_attach+0x28/0x30) [ 2.921195] [] (driver_attach) from [] (bus_add_driver+0xe0/0x1f4) [ 2.929975] [] (bus_add_driver) from [] (driver_register+0xac/0xf0) [ 2.938852] [] (driver_register) from [] (platform_driver_register+0x40/0x54) [ 2.948887] [] (__platform_driver_register) from [] (dt_cpufreq_platdrv_init+0x18/0x20) [ 2.959689] [] (dt_cpufreq_platdrv_init) from [] (do_one_initcall+0x114/0x1c8) [ 2.969627] [] (do_one_initcall) from [] (kernel_init_freeable+0x198/0x264) [ 2.979277] [] (kernel_init_freeable) from [] (kernel_init+0x18/0x118) [ 2.988445] [] (kernel_init) from [] (ret_from_fork+0x14/0x3c) [ 2.996886] ---[ end trace da155825878b99a2 ]--- [ 3.002028] cpu cpu0: couldn't find opp table for cpu:0, -2 [ 3.008223] cpu cpu0: dev_pm_opp_get_opp_count: OPP table not found (-19) [ 3.015766] cpu cpu1: cpufreq_init: failed to get clk: -2 [ 3.019174] usb 2-1: New USB device found, idVendor=05e3, idProduct=0608 [ 3.019184] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.019190] usb 2-1: Product: USB2.0 Hub [ 3.029885] hub 2-1:1.0: USB hub found [ 3.030190] hub 2-1:1.0: 4 ports detected [ 3.050262] cpu cpu0: Failed to get cpu_reg [ 3.055174] cpufreq-dt cpufreq-dt: failed register driver: -17 [ 3.061749] cpufreq-dt: probe of cpufreq-dt failed with error -17 [ 3.068637] sdhci: Secure Digital Host Controller Interface driver [ 3.075485] sdhci: Copyright(c) Pierre Ossman [ 3.080341] Synopsys Designware Multimedia Card Interface Driver [ 3.087582] dwmmc_rockchip 10214000.dwmmc: num-slots property not found, assuming 1 slot is available [ 3.097907] dwmmc_rockchip 10214000.dwmmc: Using PIO mode. [ 3.103993] dwmmc_rockchip 10214000.dwmmc: Version ID is 240a [ 3.110432] dwmmc_rockchip 10214000.dwmmc: DW MMC controller at irq 28,32 bit host data width,256 deep fifo [ 3.121436] dwmmc_rockchip 10214000.dwmmc: No vqmmc regulator found [ 3.257861] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 400000Hz, actual 386718HZ div = 4) [ 3.288936] dwmmc_rockchip 10214000.dwmmc: 1 slots initialized [ 3.298602] sdhci-pltfm: SDHCI platform and OF driver helper [ 3.305101] hidraw: raw HID events driver (C) Jiri Kosina [ 3.312365] usbcore: registered new interface driver usbhid [ 3.318601] usbhid: USB HID core driver [ 3.323404] ashmem: initialized [ 3.327378] rknandbase v1.1 2016-11-08 [ 3.332489] usbcore: registered new interface driver snd-usb-audio [ 3.341199] u32 classifier [ 3.344228] Netfilter messages via NETLINK v0.30. [ 3.349586] nf_conntrack version 0.5.0 (15926 buckets, 63704 max) [ 3.356945] ctnetlink v0.93: registering with nfnetlink. [ 3.363055] ip_set: protocol 6 [ 3.366463] IPVS: Registered protocols () [ 3.370970] IPVS: Connection hash table configured (size=4096, memory=32Kbytes) [ 3.379230] IPVS: Creating netns size=1104 id=0 [ 3.384301] IPVS: ipvs loaded. [ 3.388237] ip_tables: (C) 2000-2006 Netfilter Core Team [ 3.394415] Initializing XFRM netlink socket [ 3.400265] NET: Registered protocol family 10 [ 3.406406] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 3.412818] sit: IPv6 over IPv4 tunneling driver [ 3.418801] NET: Registered protocol family 17 [ 3.423781] NET: Registered protocol family 15 [ 3.428797] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 300000Hz, actual 257812HZ div = 6) [ 3.439251] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 3.453294] Bridge firewalling registered [ 3.457946] Bluetooth: RFCOMM socket layer initialized [ 3.463700] Bluetooth: RFCOMM ver 1.11 [ 3.467912] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 3.474497] Bluetooth: HIDP socket layer initialized [ 3.480090] 8021q: 802.1Q VLAN Support v1.8 [ 3.484762] lib80211: common routines for IEEE802.11 drivers [ 3.491136] [WLAN_RFKILL]: Enter rfkill_wlan_init [ 3.496530] [BT_RFKILL]: Enter rfkill_rk_init [ 3.501547] Key type dns_resolver registered [ 3.507288] ThumbEE CPU extension supported. [ 3.512102] Registering SWP/SWPB emulation handler [ 3.518389] Loading compiled-in X.509 certificates [ 3.524928] rockchip_emac 10204000.ethernet: ARC EMAC detected with id: 0x7fd02 [ 3.533095] rockchip_emac 10204000.ethernet: IRQ is 27 [ 3.538882] rockchip_emac 10204000.ethernet: MAC address is now ba:7e:c0:ef:d3:1f [ 3.547482] libphy: Synopsys MII Bus: probed [ 3.587869] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 200000Hz, actual 193359HZ div = 8) [ 3.747866] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 100000Hz, actual 96679HZ div = 16) [ 3.747873] rockchip_emac 10204000.ethernet: connected to Generic PHY phy with id 0x7c0f1 [ 3.748954] [ 3.748957] ======================================================= [ 3.748960] ==== Launching Wi-Fi driver! (Powered by Rockchip) ==== [ 3.748963] ======================================================= [ 3.748967] Realtek 8188EU USB WiFi driver (Powered by Rockchip,Ver v5.2.2.3_24783.20171030) init. [ 3.748973] [WLAN_RFKILL]: rockchip_wifi_power: 1 [ 3.748976] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 3.748979] RTW: module init start [ 3.748982] RTW: rtl8188eu v5.2.2.3_24783.20171030 [ 3.748986] [WLAN_RFKILL]: rockchip_wifi_get_oob_irq: Enter [ 3.748990] [WLAN_RFKILL]: rockchip_wifi_get_oob_irq: rfkill-wlan driver has not Successful initialized [ 3.749158] usbcore: registered new interface driver rtl8188eu [ 3.749161] RTW: module init ret=0 [ 3.749391] dhd_module_init: in Dongle Host Driver, version 1.579.77.41.2 (r) [ 3.749398] ======== dhd_wlan_init_plat_data ======== [ 3.749402] dhd_wlan_init_gpio: GPIO(WL_REG_ON) = -1 [ 3.749406] dhd_wlan_init_gpio: GPIO(WL_HOST_WAKE) = -1 [ 3.749409] [WLAN_RFKILL]: rockchip_wifi_get_oob_irq: Enter [ 3.749414] [WLAN_RFKILL]: rockchip_wifi_get_oob_irq: rfkill-wlan driver has not Successful initialized [ 3.749416] dhd_wlan_init_gpio: host_oob_irq: -1 [ 3.749420] dhd_wlan_init_gpio: host_oob_irq_flags=0x414 [ 3.749422] dhd_wifi_platform_load: Enter [ 3.749450] Power-up adapter 'DHD generic adapter' [ 3.749497] wifi_platform_set_power = 1 [ 3.749502] ======== PULL WL_REG_ON(-1) HIGH! ======== [ 3.749505] [WLAN_RFKILL]: rockchip_wifi_power: 1 [ 3.749509] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 3.858567] tps65910-rtc tps65910-rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801) [ 3.868506] I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 414; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '', rk_ko_ver is '5', built at '17:00:42', on 'Mar 22 2018'. [ 3.868761] Mali: Mali device driver loaded [ 3.869002] ALSA device list: [ 3.869005] No soundcards found. [ 3.982197] RAMDISK: Couldn't find valid RAM disk image starting at 0. [ 3.989689] VFS: Cannot open root device "mtdblock2" or unknown-block(0,0): error -6 [ 3.998321] Please append a correct "root=" boot option; here are the available partitions: [ 4.007615] 0100 4096 ram0 (driver?) [ 4.012773] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Please help i have no more ideas

Laszlo-Fiat commented 6 years ago

Hello, The first approach cannot work because rk3066 is not supported by u-boot. The second approach is OK, it started to boot, it just couldn't find your rootfs: [ 3.989689] VFS: Cannot open root device "mtdblock2" or unknown-block(0,0): error -6

mtdblock* would the the on-board NAND chip, but that would have to be configured from DTS/DTB, and I am not sure it works, I have never tried it.

I suggest you follow this approach: put your rootfs on the 1st partition of the SD-Card. Correct the CMDLINE: root=/dev/mmcblk0p1 rootwait

It works for me that way.

sziszi commented 6 years ago

Thanks Laszlo

Unfortulately my sd card reader is not mounting also. I do not understand why...

.......................................................... 3.193497] Mali: Mali device driver loaded [ 3.193750] ALSA device list: [ 3.193753] No soundcards found. [ 3.318291] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 100000Hz, actual 96679HZ div = 16) [ 3.339305] wifi_platform_bus_enumerate device present 1 [ 3.339308] ======== Card detection to detect SDIO card! ======== [ 3.339312] sdio: host isn't initialization successfully. [ 3.508283] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 400000Hz, actual 386718HZ div = 4) [ 3.552003] ttyS2 - failed to request DMA [ 3.556707] RAMDISK: Couldn't find valid RAM disk image starting at 0. [ 3.564055] Waiting for root device /dev/mmcblk0p1... [ 3.658288] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 300000Hz, actual 257812HZ div = 6) [ 3.759600] usb 2-1: New USB device found, idVendor=05e3, idProduct=0608 [ 3.767040] usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.774972] usb 2-1: Product: USB2.0 Hub [ 3.780286] hub 2-1:1.0: USB hub found [ 3.784757] hub 2-1:1.0: 4 ports detected [ 3.818293] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 200000Hz, actual 193359HZ div = 8) [ 3.978290] mmc_host mmc0: Bus speed (slot 0) = 3093750Hz (slot req 100000Hz, actual 96679HZ div = 16) [ 5.328287] failed to power up DHD generic adapter, 1 retry left [ 5.351016] wifi_platform_set_power = 0 [ 5.355263] ======== PULL WL_REG_ON(-1) LOW! ======== [ 5.360896] [WLAN_RFKILL]: rockchip_wifi_power: 0 [ 5.366109] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 5.375963] wifi_platform_bus_enumerate device present 0 [ 5.381862] ======== Card detection to remove SDIO card! ======== [ 5.388626] sdio: host isn't initialization successfully. [ 5.394772] wifi_platform_set_power = 1 [ 5.399045] ======== PULL WL_REG_ON(-1) HIGH! ======== [ 5.404738] [WLAN_RFKILL]: rockchip_wifi_power: 1 [ 5.409964] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 5.728278] wifi_platform_bus_enumerate device present 1 [ 5.734165] ======== Card detection to detect SDIO card! ======== [ 5.740933] sdio: host isn't initialization successfully. [ 5.898277] vendor storage:20160801 ret = -1 [ 7.738282] failed to power up DHD generic adapter, 0 retry left [ 7.761002] wifi_platform_set_power = 0 [ 7.765256] ======== PULL WL_REG_ON(-1) LOW! ======== [ 7.770876] [WLAN_RFKILL]: rockchip_wifi_power: 0 [ 7.776089] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 7.785940] wifi_platform_bus_enumerate device present 0 [ 7.791844] ======== Card detection to remove SDIO card! ======== [ 7.798611] sdio: host isn't initialization successfully. [ 7.804688] failed to power up DHD generic adapter, max retry reached [ 7.812117] unregister wifi platform drivers [ 7.816852] wifi_platform_bus_enumerate device present 0 [ 7.822767] ======== Card detection to remove SDIO card! ======== [ 7.829538] sdio: host isn't initialization successfully. [ 7.835615] ======== dhd_wlan_deinit_plat_data ======== [ 7.841426] dhd_module_init: Failed to load the driver, try cnt 0 [ 7.848224] dhd_module_init: Failed to load driver max retry reached [ 7.855477] dhd_module_init: Exit err=-19

On Sun, Mar 25, 2018 at 1:25 PM, Laszlo-Fiat notifications@github.com wrote:

Hello, The first approach cannot work because rk3066 is not supported by u-boot. The second approach is OK, it started to boot, it just couldn't find your rootfs: [ 3.989689] VFS: Cannot open root device "mtdblock2" or unknown-block(0,0): error -6

mtdblock* would the the on-board NAND chip, but that would have to be configured from DTS/DTB, and I am not sure it works, I have never tried it.

I suggest you follow this approach: put your rootfs on the 1st partition of the SD-Card. Correct the CMDLINE: root=/dev/mmcblk0p1 rootwait

It works for me that way.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-375959835, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5Yr3qCIIUBvHtIXR8kEt1aJ0y_ZQks5th3CAgaJpZM4S3mJL .

wzyy2 commented 6 years ago

rk3066 is not supported in 4.4 kernel

sziszi commented 6 years ago

Jacob Chen sorry but...you are outside of your own box?

http://opensource.rock-chips.com/wiki_Rockchip_Kernel

Rockchip kernel 4.4 supports:

RK3036, RK3066, RK312X, RK3188, RK322X,RK3288 http://opensource.rock-chips.com/wiki_RK3288, RK3328 http://opensource.rock-chips.com/wiki_RK3328, RK3368, RK3399 http://opensource.rock-chips.com/wiki_RK3399

I see the RK3066 here!

Also when i look inside rockchip_linux_defconfig i see CONFIG_ROCKCHIP_RK3066_HDMI=y

What about the rk3066 device tree in 4.4 kernel? You have 3 devices there!

On Mon, Mar 26, 2018 at 6:31 AM, 陈豪 | Jacob Chen notifications@github.com wrote:

rk3066 is not supported in 4.4 kernel

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-376036876, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5d68ruC1Qb-xk2k5nn5BJiOQcUc7ks5tiGEegaJpZM4S3mJL .

Laszlo-Fiat commented 6 years ago

Hello sziszi, rk3066 and rk3188 support came into rockchip-linux kernel via mainline/kernel.org kernel. There is a basic support for these old SOCs in mainline kernel, cpu, usb, sd-card works, hdmi, vpu, nand does not work. This support was mainlined by the linux-rockchip guys, who may have used the leaked rockchip 3.0.8+ and 3.0.36+ kernel sources as reference to write their drivers for mainline linux. Rockchip-linux mainly focuses adding support for new SOCs, currently rk3328, rk3399, rk3308. That is why I was quite surprised to see HDMI code appearing for RK3066 in rockchip-linux. I am thankful for it. sziszi: What kind of hardware do you have? What do you want to use it for? I ask because one DTS file describe one type of board, with GPIOs, and Power Management IC (voltages), that can be different on each type of board. If you use a DTS/DTB file that is not for your board, you may damage your hardware.

Regarding your SD-Card problem, I managed to solve it a few months ago. The rk3066a-marsboard.dts came directly from mainline linux, and it was not customized for rockchip-linux. You should base your DTS file on rk3066a-rayeager.dts, as it has much more components enabled. In case of SD-Card, please look at both DTS files, look for the &mmc0 definition, and copy the missing lines from rayeager to marsboard. It should find the rootfs on your SD-Card after that. It did find it for me.

Regarding HDMI (if you want that): HDMI console worked for me, but I couldn't manage to start X in 1920x1080, I got an out of memory error (surely some bug), it worked for 1280x720. The rockchip rk3066 hdmi driver only likes TV timing modes (CEA modes), and not monitor timing modes (DMT modes). So it worked with a native HDMI display (in 720p), but it rejected all the modes of my DVI monitor. I managed to make it work on my monitor by adding video=HDMI-A-1:1920x1080@60 to the CMDLINE, that way the driver got a resolution, and it worked out a mode that was close enough to a CEA mode timing, something like 1920x1080@52. That was around mid-February, with rockchip-linux v4.4.112. Maybe it would work better since then, but I haven't tried.

sziszi commented 6 years ago

Hi Laszlo

Maybe we can chat about this on a private channel to not pollute this thread? My email address is palczaszilard@gmail.com. Please drop an email if you are kind to help me with this.

Thank you!

On Wed, Mar 28, 2018 at 8:31 PM, Laszlo-Fiat notifications@github.com wrote:

Hello sziszi, rk3066 and rk3188 support came into rockchip-linux kernel via mainline/ kernel.org kernel. There is a basic support for these old SOCs in mainline kernel, cpu, usb, sd-card works, hdmi, vpu, nand does not work. This support was mainlined by the linux-rockchip guys, who may have used the leaked rockchip 3.0.8+ and 3.0.36+ kernel sources as reference to write their drivers for mainline linux. Rockchip-linux mainly focuses adding support for new SOCs, currently rk3328, rk3399, rk3308. That is why I was quite surprised to see HDMI code appearing for RK3066 in rockchip-linux. I am thankful for it. sziszi: What kind of hardware do you have? What do you want to use it for? I ask because one DTS file describe one type of board, with GPIOs, and Power Management IC (voltages), that can be different on each type of board. If you use a DTS/DTB file that is not for your board, you may damage your hardware.

Regarding your SD-Card problem, I managed to solve it a few months ago. The rk3066a-marsboard.dts came directly from mainline linux, and it was not customized for rockchip-linux. You should base your DTS file on rk3066a-rayeager.dts, as it has much more components enabled. In case of SD-Card, please look at both DTS files, look for the &mmc0 definition, and copy the missing lines from rayeager to marsboard. It should find the rootfs on your SD-Card after that. It did find it for me.

Regarding HDMI (if you want that): HDMI console worked for me, but I couldn't manage to start X in 1920x1080, I got an out of memory error (surely some bug), it worked for 1280x720. The rockchip rk3066 hdmi driver only likes TV timing modes (CEA modes), and not monitor timing modes (DMT modes). So it worked with a native HDMI display (in 720p), but it rejected all the modes of my DVI monitor. I managed to make it work on my monitor by adding video=HDMI-A-1:1920x1080@60 to the CMDLINE, that way the driver got a resolution, and it worked out a mode that was close enough to a CEA mode timing, something like 1920x1080@52. That was around mid-February, with rockchip-linux v4.4.112. Maybe it would work better since then, but I haven't tried.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-376969918, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5dcjwkrPWGj7reKMzo0x6XkUaA4Xks5ti8jhgaJpZM4S3mJL .

sziszi commented 6 years ago

I managed to bring to life the device! Thanks for your help Laszlo

On Wed, Mar 28, 2018 at 8:31 PM, Laszlo-Fiat notifications@github.com wrote:

Hello sziszi, rk3066 and rk3188 support came into rockchip-linux kernel via mainline/ kernel.org kernel. There is a basic support for these old SOCs in mainline kernel, cpu, usb, sd-card works, hdmi, vpu, nand does not work. This support was mainlined by the linux-rockchip guys, who may have used the leaked rockchip 3.0.8+ and 3.0.36+ kernel sources as reference to write their drivers for mainline linux. Rockchip-linux mainly focuses adding support for new SOCs, currently rk3328, rk3399, rk3308. That is why I was quite surprised to see HDMI code appearing for RK3066 in rockchip-linux. I am thankful for it. sziszi: What kind of hardware do you have? What do you want to use it for? I ask because one DTS file describe one type of board, with GPIOs, and Power Management IC (voltages), that can be different on each type of board. If you use a DTS/DTB file that is not for your board, you may damage your hardware.

Regarding your SD-Card problem, I managed to solve it a few months ago. The rk3066a-marsboard.dts came directly from mainline linux, and it was not customized for rockchip-linux. You should base your DTS file on rk3066a-rayeager.dts, as it has much more components enabled. In case of SD-Card, please look at both DTS files, look for the &mmc0 definition, and copy the missing lines from rayeager to marsboard. It should find the rootfs on your SD-Card after that. It did find it for me.

Regarding HDMI (if you want that): HDMI console worked for me, but I couldn't manage to start X in 1920x1080, I got an out of memory error (surely some bug), it worked for 1280x720. The rockchip rk3066 hdmi driver only likes TV timing modes (CEA modes), and not monitor timing modes (DMT modes). So it worked with a native HDMI display (in 720p), but it rejected all the modes of my DVI monitor. I managed to make it work on my monitor by adding video=HDMI-A-1:1920x1080@60 to the CMDLINE, that way the driver got a resolution, and it worked out a mode that was close enough to a CEA mode timing, something like 1920x1080@52. That was around mid-February, with rockchip-linux v4.4.112. Maybe it would work better since then, but I haven't tried.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-376969918, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5dcjwkrPWGj7reKMzo0x6XkUaA4Xks5ti8jhgaJpZM4S3mJL .

llvasconcellos commented 5 years ago

@sziszi did you get kernel 4.x to run on rk3066? HDMI is working?

sziszi commented 5 years ago

Yes 4.x is running on rk3066 but no HDMI. That was almost a year ago... did not tried recently.

On Sun, Jan 20, 2019 at 3:01 AM Leonardo Lima de Vasconcellos < notifications@github.com> wrote:

@sziszi https://github.com/sziszi did you get kernel 4.x to run on rk3066? HDMI is working?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-455828307, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5RN62f4rWRmCcDN48DEHdxtuXdmnks5vE7_rgaJpZM4S3mJL .

lntrx commented 5 years ago

Hey guys, is there any source to make it work on NAND-chip instead of SD-Card. I made it work on SD-Card, but I really need to get it work on NAND. I tried to port older version of rknand driver, but no luck

sziszi commented 5 years ago

Yes i succeded with it. It was too long ago and i do not have the sources anymore but i remember that after many weeks of trial and error i just enabled it in the dts file and it worked. It worked with the default nand driver from the kernel.

On Fri, Mar 1, 2019 at 9:50 PM Emrah Demir notifications@github.com wrote:

Hey guys, is there any source to make it work on NAND-chip instead of SD-Card. I made it work on SD-Card, but I really need to get it work on NAND. I tried to port older version of rknand driver, but no luck

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-468789970, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5Yu6JFJfdaYBpDWM7g8E_82GaNKcks5vSYSagaJpZM4S3mJL .

lntrx commented 5 years ago

&nandc { u-boot,dm-spl; status = "okay";

address-cells = <1>;

#size-cells = <0>;

};

Did you add something like this?

sziszi commented 5 years ago

Yes a nandc section but without u-boot.dm-spl for sure

On Sun, Mar 3, 2019 at 3:43 PM Emrah Demir notifications@github.com wrote:

&nandc { u-boot,dm-spl; status = "okay";

address-cells = <1>;

size-cells = <0>;

};

Did you add something like this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-469024070, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5fNYdIe4fcrKyAZE9kat4Kd8SIi-ks5vS9FugaJpZM4S3mJL .

lntrx commented 5 years ago

Do you remember if you add any driver for it. I couldn't make it work

sziszi commented 5 years ago

I did not add any drivers as far as i remember. But i tried with many kernel versions. It was a painful experience :) I also tried with mainstream kernel. Some things worked with Rockchip kernel other things with mainstream.Maybe i used mainstream in the latest working version. Also beware of the GPIO pins. It is really hardware dependant. It is not enough to enable a component you also need to power it. Without creating a proper dts file for your specific device it is almost impossible. Creating a proper dts without the schematics is like walking in the dark. I used the ryeager dts already existing in the linux kernel. That was the most featured one and i managed to bring to life some components. I was not succesful with the GPIO of wireless. I enabled just the driver and i gave the Vcc voltage directly from PCB Vin by soldering a wire. I managed to bring up also the wireless that way.

On Thu, Mar 7, 2019 at 8:08 PM Emrah Demir notifications@github.com wrote:

Do you remember if you add any driver for it. I couldn't make it work

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-470633595, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5czR7DubnJps6yaKtFNAYoIlzJzzks5vUVWygaJpZM4S3mJL .

lntrx commented 5 years ago

I found somewhere this entry and tried didn't work for me 

nandc: nandc@10500000 {
    compatible = "rockchip,rk-nandc";
    reg = <0x10500000 0x2000>;
    interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
    clock-names = "hclk";
    clocks = <&cru HCLK_NANDC0>;
    status = "disabled";
};
sziszi commented 5 years ago

Well with status="disabled" why you expect it to work? And even if you change it to enabled? Why do you expect that all those settings will fit your device? As i said before it is a little bit of gambling. What works for a device will not work for other devices. You can also have a high chance damaging your device while messing with those settings. Just a warning.

On Thu, Mar 7, 2019 at 8:58 PM Emrah Demir notifications@github.com wrote:

I found somewhere this entry and tried didn't work for me

nandc: nandc@10500000 { compatible = "rockchip,rk-nandc"; reg = <0x10500000 0x2000>; interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>; clock-names = "hclk"; clocks = <&cru HCLK_NANDC0>; status = "disabled"; };

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-470650996, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5a9WNbL6KlvFp7Z-Q-mEo8_TUBfTks5vUWFygaJpZM4S3mJL .

lntrx commented 5 years ago

Thanks for warning mate. This is in main .dts something like rk3xx.dts in marsboard.dts I make it status=okay. I am really not sure, I tried lots of things I am even not sure where I got this part. There's no official sources. If you remember or find your dts conf somehow even which kernel version you tried that would be really nice. Device seems okay for now. I am still able to boot

lntrx commented 5 years ago

http://u-boot.10912.n7.nabble.com/PATCH-v4-00-19-add-support-for-rk3066-platform-td303420.html

This is where I got the idea

sziszi commented 5 years ago

You can forget it totally. I even contacted Pavel Jarosz a year ago about it. He confirmed that u-boot is not working for RK3066. I cannot find my dts anymore. I can help you with my latest kernel image if you want. But tell me what kind of device you have exactly?

On Thu, Mar 7, 2019 at 10:03 PM Emrah Demir notifications@github.com wrote:

http://u-boot.10912.n7.nabble.com/PATCH-v4-00-19-add-support-for-rk3066-platform-td303420.html

This is where I got the idea

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-470673223, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5RPgD-tSg5XJDHXbertTCIUlooqIks5vUXB_gaJpZM4S3mJL .

lntrx commented 5 years ago

That would be really nice mate. I have Marsboard RK3066

http://www.marsboard.com/marsboard_rk3066_feature.html

sziszi commented 5 years ago

Your email address please

On Thu, Mar 7, 2019 at 10:18 PM Emrah Demir notifications@github.com wrote:

That would be really nice mate. I have Marsboard RK3066

http://www.marsboard.com/marsboard_rk3066_feature.html

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-470678045, or mute the thread https://github.com/notifications/unsubscribe-auth/AD_F5Z9oh42jnjiDZA8HfSxXw-5C2b1Iks5vUXQAgaJpZM4S3mJL .

lntrx commented 5 years ago

demire801 [at] gmail

darkalexpp commented 3 years ago

For use nand in rk3066:

arch/arm/boot/dts/rk3xxx.dtsi

nandc: nandc@10500000 {
        compatible = "rockchip,rk-nandc";
        reg = <0x10500000 0x4000>;
        interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
        nandc_id = <0>;
        clocks = <&cru HCLK_NANDC0>;
        clock-names = "hclk_nandc";
        status = "disabled";
    };

arch/arm/boot/dts/rk3066a-xxxxx.dts:


&nandc {
    status = "okay";

    nand@0 {
        reg = <0>;
        nand-is-boot-medium;
    };
};

Partitions mount in /dev/rknand_"label"

lntrx commented 3 years ago

https://github.com/lntrx/rk3066_kernel4-4 checky my repo. Back then I made changes and create a script to completely build image

On Sun, Oct 4, 2020 at 6:47 PM darkalexpp notifications@github.com wrote:

Hi, I am trying to get the 4.4 kernel to work on a rk3066 clone, some things are different but it is similar to the marshboard, I'm trying to get nand to work, I don't know what the dts settings are for it.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rockchip-linux/kernel/issues/75#issuecomment-703274403, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2PDN23DTRTX3S6AEHWNO3SJCKKJANCNFSM4EW6MJFQ .

-- @lntrx

darkalexpp commented 3 years ago

Hello sziszi, rk3066 and rk3188 support came into rockchip-linux kernel via mainline/kernel.org kernel. There is a basic support for these old SOCs in mainline kernel, cpu, usb, sd-card works, hdmi, vpu, nand does not work. This support was mainlined by the linux-rockchip guys, who may have used the leaked rockchip 3.0.8+ and 3.0.36+ kernel sources as reference to write their drivers for mainline linux. Rockchip-linux mainly focuses adding support for new SOCs, currently rk3328, rk3399, rk3308. That is why I was quite surprised to see HDMI code appearing for RK3066 in rockchip-linux. I am thankful for it. sziszi: What kind of hardware do you have? What do you want to use it for? I ask because one DTS file describe one type of board, with GPIOs, and Power Management IC (voltages), that can be different on each type of board. If you use a DTS/DTB file that is not for your board, you may damage your hardware.

Regarding your SD-Card problem, I managed to solve it a few months ago. The rk3066a-marsboard.dts came directly from mainline linux, and it was not customized for rockchip-linux. You should base your DTS file on rk3066a-rayeager.dts, as it has much more components enabled. In case of SD-Card, please look at both DTS files, look for the &mmc0 definition, and copy the missing lines from rayeager to marsboard. It should find the rootfs on your SD-Card after that. It did find it for me.

Regarding HDMI (if you want that): HDMI console worked for me, but I couldn't manage to start X in 1920x1080, I got an out of memory error (surely some bug), it worked for 1280x720. The rockchip rk3066 hdmi driver only likes TV timing modes (CEA modes), and not monitor timing modes (DMT modes). So it worked with a native HDMI display (in 720p), but it rejected all the modes of my DVI monitor. I managed to make it work on my monitor by adding video=HDMI-A-1:1920x1080@60 to the CMDLINE, that way the driver got a resolution, and it worked out a mode that was close enough to a CEA mode timing, something like 1920x1080@52. That was around mid-February, with rockchip-linux v4.4.112. Maybe it would work better since then, but I haven't tried.

@Laszlo-Fiat hi, how could you get the hdmi working? What configuration to use in the kernel to compile? I've been trying but I only get a black screen

Yaksinikos commented 10 months ago

Hello sziszi, rk3066 and rk3188 support came into rockchip-linux kernel via mainline/kernel.org kernel. There is a basic support for these old SOCs in mainline kernel, cpu, usb, sd-card works, hdmi, vpu, nand does not work. This support was mainlined by the linux-rockchip guys, who may have used the leaked rockchip 3.0.8+ and 3.0.36+ kernel sources as reference to write their drivers for mainline linux. Rockchip-linux mainly focuses adding support for new SOCs, currently rk3328, rk3399, rk3308. That is why I was quite surprised to see HDMI code appearing for RK3066 in rockchip-linux. I am thankful for it. sziszi: What kind of hardware do you have? What do you want to use it for? I ask because one DTS file describe one type of board, with GPIOs, and Power Management IC (voltages), that can be different on each type of board. If you use a DTS/DTB file that is not for your board, you may damage your hardware. Regarding your SD-Card problem, I managed to solve it a few months ago. The rk3066a-marsboard.dts came directly from mainline linux, and it was not customized for rockchip-linux. You should base your DTS file on rk3066a-rayeager.dts, as it has much more components enabled. In case of SD-Card, please look at both DTS files, look for the &mmc0 definition, and copy the missing lines from rayeager to marsboard. It should find the rootfs on your SD-Card after that. It did find it for me. Regarding HDMI (if you want that): HDMI console worked for me, but I couldn't manage to start X in 1920x1080, I got an out of memory error (surely some bug), it worked for 1280x720. The rockchip rk3066 hdmi driver only likes TV timing modes (CEA modes), and not monitor timing modes (DMT modes). So it worked with a native HDMI display (in 720p), but it rejected all the modes of my DVI monitor. I managed to make it work on my monitor by adding video=HDMI-A-1:1920x1080@60 to the CMDLINE, that way the driver got a resolution, and it worked out a mode that was close enough to a CEA mode timing, something like 1920x1080@52. That was around mid-February, with rockchip-linux v4.4.112. Maybe it would work better since then, but I haven't tried.

@Laszlo-Fiat hi, how could you get the hdmi working? What configuration to use in the kernel to compile? I've been trying but I only get a black screen

Does someone have an Idea of what kernel version supports Rockchip RK3066 ANGW734 1326 with HMDI, best possible adding support for MT5931SA (MTK5931) & MT6622N (MTK6622) - would like to update my HTC-T011-V4 based SoC.