View Single Post
Old 06-06-2015, 10:21 AM   #10
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Quote:
Originally Posted by chefchens View Post
To confirm my approach I have the following questions:
- Is the logged behavior expected? – I think the answer is ‘no’
- Is the logged timeout triggered because of a wrong u-boot version (that was compiled for the K5-Touch and not for the K5-PW1) and do I only need a correct U-Boot for the PW1?
- Do I have a hardware fault on the PW1 board – maybe an EMMC hardware fault?
Take my words with a grain of salt, I'm not an expert, just did some grepping/reading of sources and googling.

Your error happened in phase of internal storage initialization. CPU sent command to storage and polled DAT0 line of storage's interface to wait when "busy" (busy with command execution) signal ends. And after 25 seconds timeout, waiting was stopped with timeout error (number -19 is defined in source as TIMEOUT).

Here PW1 owner got at least after storage initialization stage by using precompiled U-Boot from this forum, so the problem is not in wrong U-Boot, I think.
eureka is offline   Reply With Quote