[katadelos]

Originally Posted by hjalfi

Your configuration fails for me because it still doesn't know where to load the binary.

Are you calling imx_usb directly? You need to pass the name of the u-boot binary that you want to load for things to work with the configuration above: ./imx_usb u-boot.bin.

According to this post, you can also specify the binary name within the config file like this:

KindleTouch
hid,1024,0x70000000,256M,0xF8000000,128K
img/main.bin:dcd,plug
img/main.bin:jumpheader

Originally Posted by hjalfi

AFAIK this is a classic symptom of eMMC failure, as it can't read the configuration information and cannot configure the DRAM. Therefore, I can't load u-boot into DRAM.

Possibly, possibly not - all you know for sure is that the eMMC doesn't contain the config info. The output you attached is identical to what you'd get if you'd just soldered on a blank eMMC

Originally Posted by hjalfi

I know that some Kindles have two versions of u-boot: one which is small enough to run from the on-chip RAM, and one which has things like fastboot and bist linked in which are run once the DRAM is set up.

There are 2 versions of u-boot on most Kindles but you're misunderstanding the boot process. AFAIK, the stripped down version is used in almost all cases unless you interrupt the boot process and drop to bist explicitly; the stripped down u-boot doesn't chainload bist.

Originally Posted by hjalfi

So I'm going to guess that I need to reproduce the cut-down uboot which can run from the on-chip RAM and run that. Is this the one called imx50_yoshi_mfgtool_config?

In your case (PW1), you want the imx50_yoshime3_* defconfigs. You should focus on getting to the point where you can load u-boot in the first place though, it might help if you post the exact commands and env variables that you're using to build u-boot.