MobileRead Forums - View Single Post

hjalfi · 03-15-2021, 03:49 PM

Yeah, I'm hoping that this eMMC had a vague moment and corrupted itself. But if I can get u-boot working at all, I can get some work out of this thing.

Thanks for the link --- there's some useful stuff there. The impression I get is that the DRAM gets configured by writing the DCD to the chip as part of the download process, but the only reference to this in the u-boot source is in board/imx50_yoshi/flash_header.S, and there's a magic number which appears in it, which I can't find in the binary.

To build u-boot, I'm doing this:

Code:

make CROSS_COMPILE=arm-linux-gnueabihf- -j imx50_yoshime3_mfgtool_config
make CROSS_COMPILE=arm-linux-gnueabihf- -j

This matches the instructions in the eMMC replacement thread. This outputs u-boot, an ELF file; u-boot.bin, the binary file I'm trying to upload; and an S-record file. Looking inside the S-record file just shows addresses in the 0x798xxxxx range. I've tried all the imx50_yoshi* configs and they all produce binaries linked at that address.

So, given that (a) there appears to be no DCD information in the binary and (b) imx_usb can't find the file header containing the load and execute addresses (I have to specify them manually), I'm guessing I'm trying to upload the wrong file.

Any ideas?

03-15-2021, 03:49 PM	#9
hjalfi Member Posts: 24 Karma: 10 Join Date: Apr 2011 Device: Kindle 3g	Yeah, I'm hoping that this eMMC had a vague moment and corrupted itself. But if I can get u-boot working at all, I can get some work out of this thing. Thanks for the link --- there's some useful stuff there. The impression I get is that the DRAM gets configured by writing the DCD to the chip as part of the download process, but the only reference to this in the u-boot source is in board/imx50_yoshi/flash_header.S, and there's a magic number which appears in it, which I can't find in the binary. To build u-boot, I'm doing this: Code: make CROSS_COMPILE=arm-linux-gnueabihf- -j imx50_yoshime3_mfgtool_config make CROSS_COMPILE=arm-linux-gnueabihf- -j This matches the instructions in the eMMC replacement thread. This outputs u-boot, an ELF file; u-boot.bin, the binary file I'm trying to upload; and an S-record file. Looking inside the S-record file just shows addresses in the 0x798xxxxx range. I've tried all the imx50_yoshi* configs and they all produce binaries linked at that address. So, given that (a) there appears to be no DCD information in the binary and (b) imx_usb can't find the file header containing the load and execute addresses (I have to specify them manually), I'm guessing I'm trying to upload the wrong file. Any ideas?