|
Hey guys, just some clarifying stuff on the errors. This one:
> # ./flash_erase
> /bin/sh: ./flash_erase: not found
Means the program loader wasn’t able to find libraries needed to start the app. This usually happens when the app is compiled for one distro and is used on another. The program is good, the library versions aren’t.
> Unexpected word bracket thing (on my cell phone where copy + paste is bad)
I had this last week while trying to run binaries on the Kobo Touch. I’m fairly certain this was due to the ARM binaries being built for an unmatching architecture and the program loader once again giving unhelpful text.
Those I/O errors are not promising at all. That Flash chip is done done. I’m hoping it survives a little longer but I’ve got little hope.
For the system not booting on its own, there should be a variable U-boot uses when it starts up. It should be “bootcmd”. You can dump the value using “printenv” and you can likely find a tutorial on how to save it yourself. You’re so used to U-boot at this point that the commands will be obvious (it’s what you’ve been typing over and over to load and boot the kernel).
|