View Single Post
Old 03-09-2012, 08:01 AM   #6
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 7,000
Karma: 6324262
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by wsxhwyy View Post
I flashed a 5.0.4 kernel into my device using dd but it cannot boot.
The u-boot bootable kernels are one of several formats that the kernel build system can turn out plus a "u-boot header".

You should be able to report on the various header values of interest with 'od' (man: od) if there isn't already a tool for the purpose ('file' might 'just do it').

Of course you'll need to look-up the proper offsets to report in the u-boot *.h files.

This should allow you to make checks on any u-boot wrapped, kernel image, before you try to 'copy device' it to storage media.
Interesting things, like: Will it fit?

*nix trivia:
"copy device" goes by the name 'dd' because the name 'cd' was already in use for a recognized purpose when "copy device" was written. So author just bump'd the first letter of the name one character.
knc1 is offline   Reply With Quote