Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

Can not boot up the kernel [RK3128]

15

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
15

Can not boot up the kernel [RK3128]

Posted at 2/13/2018 16:43:27      View:2721 | Replies:2        Print      Only Author   [Copy Link] 1#
Hi, all.

My company is running beam projector product which uses the RK3128. We met a kernel booting up problem as log below:

Connecting to COM14...
Connected.

tDDR Version 2.01 201401008
In
1A1A1B1B   3
DDR3
1A1B1B1B   F
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=8 Size=1024MB
mach:2
OUT
2.20 1
ChipType = a
No.1 FLASH ID:2c 64 44 4b a9 0
DDR Version 2.01 201401008
In
1A1A1B1B   3
DDR3
1B1B1B1B   F
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=8 Size=1024MB
mach:2
OUT
2.20 1
ChipType = a
No.1 FLASH ID:2c 64 44 4b a9 0
*Y[[¬R+Wj¤4E½Ʌ%1¥сz-胂2jCCUK¡뉗&|LMLK©©|L&NKLK.+%TԬ¤L$&LL- 19:03:12)

CPU: rk3128
CPU's clock information:
    arm pll = 300000000HZ
    periph pll = 594000000HZ
    ddr pll = 600000000HZ
    codec pll = 400000000HZ
Board:        Rockchip platform Board
Uboot as second level loader
DRAM:  Found dram banks:1
Adding bank:0000000060000000(0000000040000000)
128 MiB
rk dmat.]KWՖ¤-+Ѫ*RH¨ԗ-锒VV¬RʗK؋««WH¨H璖a,®X[C,ZY¬-H\X1X[YoY1success
Unknow param: MACHINE_MODEL:rk312x!
Unknow param: MACHINE_ID:007!
Unknow param: MANUFACTURER:RK30SDK!
failed to prepare fdt from boot!
power key: bank-3 pin-23
can't find dts node for ricoh619
can't find dts node for act8846
can't find dts node for rk808
++++ LDO3 write 0x03 to regular
cpu_det GPIO pull up
pmic:rk818
Can't find dts node for fuel guage cw201x
can't find dts node for ADC
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 2015-01-16#2.20
empty serial no.
checkKey
vbus = 1
use dc chg rk818_charger_setting iset1:0x79 chgiset:0x75 current 2
read logo_on switch from dts [1]
can't find power_ctr node for lcdc0
failed to find part:logo
ERROR: [get_entry_ram]: Cannot find logo.bmp!
ERROR: [show_resource_image]: Failed to load image:logo.bmp
got recovery cmd from misc.
load fdt from resouce.
ERROR: [get_entry_ram]: Cannot find logo_kernel.bmp!
Secure Boot state: 0
kernel   @ 0x62000000 (0x006909e0)
ramdisk  @ 0x65bf0000 (0x0029bc54)
bootrk: do_bootm_linux...
   Loading Device Tree to 65600000, end 65616996 ... OK
Add bank:0000000060000000, 0000000040000000

Starting kernel ...

<hit enter to activate fiq debugger>
[    0.000000] Booting Linux on physical CPU 0xf00
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.0 (H600@Samsung) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Dec 11 16:09:31 KST 2017
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Rockchip RK3128, model: rockchip,rk3128
[    0.000000] rockchip_uboot_logo_setup: mem: 2000000@9dc00000, offset:0
[    0.000000] rockchip_uboot_mem_reserve: reserve 2000000@9dc00000 for uboot logo
[    0.000000] rockchip_ion_reserve
[    0.000000] ion heap(cma): base(0) size(800000) align(0)
[    0.000000] ion heap(vmalloc): base(0) size(0) align(0)
[    0.000000] cma: CMA: reserved 8 MiB at 9d400000
[    0.000000] ion_reserve: cma reserved base 9d400000 size 8388608
[    0.000000] cma: CMA: reserved 16 MiB at 7f000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] Boot mode: RECOVERY (2) flag: RECOVER (0xc3524203)
[    0.000000] PERCPU: Embedded 9 pages/cpu @c1646000 s14016 r8192 d14656 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 261120
[    0.000000] Kernel command line: vmalloc=496M rockchip_jtag console=ttyFIQ0 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.hardware=rk30board androidboot.console=ttyFIQ0 init=/init  mtdparts=rk29xxnand:0x00002000@0x00000000(parameter),0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00006000@0x0000E000(kernel),0x00006000@0x00


The log shows a litte information it is not enough in order to find out the problem comes from where. If you have any suggestion for this issue please let me know. Addition to, if you know the way to get other logs which have more information please point to me.

Thank you so much !
Reply

Use props Report

15

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
15
Posted at 2/14/2018 13:48:15        Only Author  2#
Anypeople can help me
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 2/23/2018 14:36:36        Only Author  3#
Phatv Posted at 2/14/2018 13:48
Anypeople can help me

suggest u use the official SDK to build.
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list