- Oct 28, 2014
- Reaction score
I can see a couple of problems.if you can see the meaning of error please tell me, here below is the log:
But first: Hint - for logs and code, use the Code tags to hold the content, under the + in the edit menu. This is easier for you, and easier for the readers.
Here is what I notice:
I'm curious where you got the set of commands at the start of the log from.
Generally, these could be used to boot a kernel (uImage) over the network on a device where the kernel and/or the root file system has been erased or corrupted, allowing a minimum environment from which to do repairs.
They are not really relevant to what you are trying to do - the primary problem has not as yet been identified.
This is just plain wrong as a bootcmd setting.
The file digicap.dav is an encoded, encrypted firmware distribution file and has no place being loaded into memory as part of a bootcmd.
In fact, that is why there is a data abort just after it's loaded in - it's not an executable file.
But all that doesn't really matter, as the environment variables (at least in this log) have not been saved, such that the hardware reset that follows starts from scratch again.
But that does beg the question - what are the values in the bootargs and other variables?
These are used to inform the uImage kernel how to start, and where some items are located.
A couple of questions on this:
What were the very original environment variables, in particular bootargs and bootcmd?
Hopefully before making changes you interrupted the bootloader and used
to see them and record their values. That is important.
And secondly, what are the values of the environment variables now?
Are any changed from the original?
To see the problem properly, they should be returned to their original values.
This is important, because it looks like the main partition, probably mtdblock2 has invalid or corrupt data in it.
The kernel, uImage, is booting OK (though it could still be the wrong kernel for this model).
It's executing startup commands, but when it gets to the point where it's decrypting the various encrypted archives, the ded program doing the decryption finds corrupted data. This is the web server data, there are similar encrypted archives for libraries and programs.
ded in[/home/hik/gui_res.tar.lzma]/out[/home/app/gui_res.tar.lzma] ioctl faild. errno tar: unexpected EOF tar: short read
In summary - the firmware that's been loaded is corrupt, and there is a question about whether the bootloader environment variables are still valid.