View Single Post
Old 06-08-2017, 09:58 PM   #23
knc1
Going Viral
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: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Hexadecimal View Post
Code:
- - - -
Invalid board id!  Can't determine system type for RAM init.. bailing!
DRAM:   0 kB
- - - -
uboot > bootm 0xE41000
mmc read failed
ERROR: couldn't read boot image from flash address 0x41000
*) Unable to start external RAM.
*) And the 'diags' kernel is too large to run in internal RAM only.

So you have to fix the board ID.
And the fully functional build of u-boot (called: bist) is also too large to run in internal RAM only.
But you should be able to list the available commands in the mini-uboot build that you are running.

Which, if this state was reached solely by an attempt at an image update of the 'main' system can only have happened by failure of the flash chip.

The required data that is missing is stored outside of any image storage area, and is never touched by an image update.

Typically, this state is reached, baring hardware failure, by a person trying the "erase all" selection from the u-boot list of options.

So you need to follow the directions for recovering from the use of "erase all". Even if you didn't select that u-boot action because somehow it did get selected.

Last edited by knc1; 06-08-2017 at 10:02 PM.
knc1 is offline   Reply With Quote