This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Getting stuck in "Starting Kernel" after u-boot with rockchip linux SDK.
#11
(09-21-2018, 03:51 AM)benjamin.weng Wrote:
(09-21-2018, 02:01 AM)jamess Wrote: Hi, benjamin
    Do you connect any peripheral on your tinker board? and what kind of the power adaptor do you use? 5V/3A ?

Hi jamess
Many thanks for your help, I changed the power supply source from usb port of PC to a 5V/2A one, and now the problem is solved.
But I'm embarrassed that I encountered th other problem now...
The booting log shows that it cannot mount to rootfs which I want it to mount (mmcblk0p5)
And I upload the full log in the attachment file.
Feel very sorry to ask so much questions and thank you for your kind reply again.

[    8.846242] VFS: Cannot open root device "mmcblk0p5" or unknown-block(0,0): error -6
[    8.857405] Please append a correct "root=" boot option; here are the available partitions:
[    8.869273] 0100            4096 ram0  (driver?)
[    8.876993] b300        31166976 mmcblk0  driver: mmcblk
[    8.885459]   b301            4000 mmcblk0p1 3cbbe972-ec1a-4b2d-8f26-5c4e1ad1b54c
[    8.896365]   b302            4096 mmcblk0p2 dfdef0ee-9a52-40fc-96b5-730ea54443e6
[    8.907281]   b303            4096 mmcblk0p3 697479df-8946-4401-8bd4-817fb7c5c1d0
[    8.918216]   b304          114688 mmcblk0p4 12e313ac-9191-4239-9e1d-73ee48fd2e36
[    8.929105]   b305         2513903 mmcblk0p5 69dad710-2ce4-4e3c-b16c-21a1d49abed3
[    8.939967] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Your log shows that
...
...
reading /zImage
7953288 bytes read in 352 ms (21.5 MiB/s)

append: earlyprintk console=tty1 console=ttyS2,115200n8 rw root=mmcblk0p5 rootfstype=ext4 init=/sbin/init
Retrieving file: /rk3288-miniarm.dtb
...
...

I think the red word should be modified as root=/dev/mmcblk0p5 something like that, can you give it a try ?
Reply
#12
Hi jamess
Thank you very much!!
Now I can boot successfully after modifying root=/dev/mmcblk0p5.
Thank you for your help again.
May I ask one more question here?
After booting was done and the console log stop at root@linaro-alip:~#,
I cannot type anything under uart-terminal tools like 'screen' or 'minicom'.
And I also checked the USB-TTL device is OK.
Are there any possible problems or clues for me, please?
Thank you again!!
Reply
#13
(09-21-2018, 08:59 AM)benjamin.weng Wrote: Hi jamess
Thank you very much!!
Now I can boot successfully after modifying root=/dev/mmcblk0p5.
Thank you for your help again.
May I ask one more question here?
After booting was done and the console log stop at  root@linaro-alip:~#,
I cannot type anything under uart-terminal tools like 'screen' or 'minicom'.
And I also checked the USB-TTL device is OK.
Are there any possible problems or clues for me, please?
Thank you again!!

Hi, benjamin
    Did you connect these 3 pins (TX/RX/GND) to Tinker Board with your usb-to-uart adaptor ?
    or
    Did you try to re-plugin your usb-to-uart adaptor to PC again ?
Reply
#14
Code:
append: earlyprintk console=tty2 console=ttyS2,115200n8 rw root=/dev/mmcblk0p5 rootfstype=ext4 init=/sbin/init
Try this.
Otherwise you might see this thread.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)