-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 4.40 of rk30xxnand.ko requires updated bootloader #2
Comments
Hello, The kernel freeze might be related to the version of the bootloader you are using. There is several versions available, here is a complete collection of bootloaders released for the Rockchip platforms: http://www.arctablet.com/blog/forum/firmware-development/rockchip-bootloader-collection-rk29xxloader-rk30xxloader-rk3168loader-rk3188loader/ You can update your board to the latest version of the bootloader, but you will have to do a 'lower format' of the NAND, then flash parameter and boot image again:
Hoping this will help you... |
Thanks. |
I haven't found any changelog anywhere, nor any source (the bootloader is delivered by Rockchip in binary form). The standard Radxa Rock comes with version 1.24, available here: http://dl.radxa.com/rock/images/loader/ There are some interesting informations about unpacking the bootloader and obtaining the bootrom: https://gist.github.com/sarg/5028505 |
I upgraded to bootloader 2.10, as you suggested. Once I did this, I found that the old rk30xxnand.ko stopped working -- however the newer 4.40 version from this initrd started working So, perhaps you can add a note to the initrd that you must upgrade the bootloader before using it? |
I will update the bootloader in pack-tools On Wed, Feb 12, 2014 at 1:18 PM, Toby Corkindale
radxa rock - quad core arm computer that rocks radxa.com |
As per my comment in pull request #1 , the current 4.40 version of rk30xxnand.ko just causes a kernel freeze when booting.
Rolling back to 3.38 allows normal booting behaviour.
This is the output printed after "insmod rk30xxnand-3.0.36+.ko":
The kernel seems to be semi-active still -- it will notice USB connects and disconnects and I can use the magic sysrq key. However the insmod command just hangs and never returns to the console.
The text was updated successfully, but these errors were encountered: