Kt3 bootloop continues... Help

[Kus]

Not sure if it's a good idea to start a new thread because old one was closed so had to start a new one. It seems that I'm having problem getting into recovery mode in KT3, tried fastboot too but that too seems to be not working and file "uImage" sent through xy modem doesn't seem to be working since after execution of command "mmc write 0x80800000 0x208 0x2600" it responds with a failed message like this

MMC write: dev # 0, block # 520, count 9728... Card did not respond to voltage select!
0 blocks write in 2 msec: ERROR

I was using uImage file from 'update_KT3_5.8.0_initial.bin'
Help please

[pdurrant]

Here's the original thread for reference.

[knc1]

Originally Posted by Kus

Not sure if it's a good idea to start a new thread because old one was closed so had to start a new one.

Sometimes reading the fine print helps.
Message just above second blue bar on this forum's first index page:
"Page 1 of 186"

That isn't a total of 186 pages for the forum, that is 186 pages index.
(The exact number depends on how many rows you have set in your User CP to show at a single time, but the principle remains.)

Just because your first thread has fallen off the first page doesn't mean your thread was "closed".

After I described how you should continue, you posted:

If that's the case then I must keep my fear of screwing things-more-than-they-already-are aside and start debricking it.
Soldering is not a problem but I guess a untouched pcb looks better than a soldered one, if that's even a thing.
Thanks again everyone for replies. I may have to pop up here again if I get stuck somewhere.

Peace out

I do not see how your going silent for four months can be considered that we are ignoring you.

The least you could do now is bring us up to date on what you have done since your prior post 4 months ago.

[Kus]

I wanted to debrick my kindle as soon as possible but circumstances had me put it aside for a while but I'm back at it with full force, ready to pull all nighter if need to. Other than that I didn't thought I would need to bug anyone for issues I ran into such as serial connection. I thought I would find everything in forum section and would eventually find answers by reading enough of it. But here I am asking for your help again

[Kus]

Hmm where do I start then?
I'm using PL2303 USB -TTL converter
With Geekmaster's level shifter circuit(thanks to him) for receiving data from kindle and simple voltage divider to send data through tx pin over ExtraPutty application
I will provide some log of printenv and booting process tomorrow, it's night here so I need to wait.


Here is update

U-Boot 2014.04 (Oct 04 2017 - 23:27:49)

CPU:   Freescale i.MX6SL rev1.3 at 792 MHz
CPU:   Temperature 27 C, calibration data: 0x59a51f5f
Reset cause: POR
FRED::: EXTCSD177=0, 179=48FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Board: Heisenberg
Board Id: P001180XXXXXXXXXX
S/N: G000K9XXXXXXXXXXX
I2C:   ready
DRAM:  MR5=0x6,MR6=0x3 512 MiB
WARNING: Caches not enabled
MMC:   FRED::: EXTCSD177=0, 179=48FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
REBOOTMODE: 0
using default bootcmdNormal Boot
Hit any key to stop autoboot:  0


uboot > iminfo



## Checking Image at 80800000 ...
Unknown image format!
uboot > <INTERRUPT>
uboot > printenv
baudrate=115200
boot_fdt=no
bootcmd=mmc dev ${mmcdev};if mmc rescan; then run testboot; fi;
bootdelay=3
console=ttymxc0
diags_boot=echo BOOTing diags from mmc ...; run setmmcdev; run loadkernel_diags; run loaddt_diags; run mmcargs_diags; bootm ${loadaddr} - ${fdt_addr}
fdt_addr=0x83000000
loadaddr=0x80800000
loaddt=mmc read 0x83000000 0x208 0x100;
loaddt_diags=mmc read 0x83000000 0x7208 0x100;
loadkernel=mmc read 0x80800000 0x2D0 0x7000;
loadkernel_diags=mmc read 0x80800000 0x72D0 0x7000;
mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot} uart_at_4M
mmcargs_diags=setenv bootargs console=${console},${baudrate} root=/dev/mmcblk0p2 rootwait rw
mmcautodetect=yes
mmcdev=1
mmcpart=2
mmcroot=/dev/mmcblk0p1 rootwait rw
setmmcdev=mmc dev 1 0;
stderr=serial
stdin=serial
stdout=serial
testboot=echo BOOTing from mmc ...; run setmmcdev; run loadkernel; run loaddt; run mmcargs; bootm ${loadaddr} - ${fdt_addr}

Environment size: 982/8188 bytes


uboot > bist


U-Boot 2014.04 (Oct 04 2017 - 23:27:55)

CPU:   Freescale i.MX6SL rev1.3 at 792 MHz
CPU:   Temperature 32 C, calibration data: 0x59a51f5f
Reset cause: unknown reset
FRED::: EXTCSD177=0, 179=48FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Board: Heisenberg
Board Id: P00118xxxxxxxx
S/N: G000K9XXXXXXXXXX
I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
MMC:   FRED::: EXTCSD177=0, 179=48FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
REBOOTMODE: 0
using default bootcmdflash target is MMC:1
Net:   CPU Net Initialization Failed
No ethernet found.
Normal Boot
Hit any key to stop autoboot:  0


bist > loadx
## Ready for binary (xmodem) download to 0x80800000 at 115200 bps...
CC## Total Size      = 0x004c0000 = 4980736 Bytes

bist > mmc write 0x80800000 0x208 0x2600

MMC write: dev # 0, block # 520, count 9728 ... Card did not respond to voltage select!
0 blocks write in 2 msec: ERROR
bist >

[Kus]

If I missed something, please do let me know.
Thank you