Thread: Original "Simple" debricking methods for K5-Touch, K4-Mini, & K3-Keyboard
View Single Post
Old 10-19-2012, 04:13 PM   #724
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 eureka View Post
BTW, with U-Boot size about 80kb you're overwriting MMU table (which is located right after OCRAM). But it looks like in this case it's not dangerous at all.
Ha, imx_usb_loader spits out errors if u-boot.bin size goes beyond free OCRAM area. Also, 4kb of u-boot.bin takes not the U-Boot itself, but flash header or something.

Log of errors is here:
Spoiler:
Code:
parse mx50_usb_work.conf
15a2:0052(KindleTouch) bConfigurationValue =1
Interface 0 claimed
report 1, wrote 16 bytes, err=0
report 3, read 5 bytes, err=0
read=56 78 78 56
fastboot.bin
No dcd table, barker=402000d1
dcd_ptr=0x00000000

loading binary file(fastboot.bin) to f8006000, skip=0, fsize=800 type=aa

<<<2048, 2048 bytes>>>
jumping to 0xf8006400
j3 in err=0, last_trans=5  56 78 78 56
j4 in err=-7, last_trans=0  00 00 00 00
report 1, wrote 16 bytes, err=0
report 3, read 5 bytes, err=0
read=56 78 78 56
jump_mode 2 plug=1 err=0
fastboot.bin
header_max=1000

loading binary file(fastboot.bin) to f8007000, skip=0, fsize=1290c type=aa
out err=-9, last_trans=0 c=0x190c max=0x400 transferSize=0x11000 retry=0
out err=-9, last_trans=0 c=0x190c max=0x200 transferSize=0x11000 retry=1
out err=-9, last_trans=0 c=0x190c max=0x100 transferSize=0x11000 retry=2
out err=-9, last_trans=0 c=0x190c max=0x80 transferSize=0x11000 retry=3
out err=-9, last_trans=0 c=0x190c max=0x40 transferSize=0x11000 retry=4
out err=-9, last_trans=0 c=0x190c max=0x20 transferSize=0x11000 retry=5
out err=-9, last_trans=0 c=0x190c max=0x10 transferSize=0x11000 retry=6
out err=-9, last_trans=0 c=0x190c max=0x8 transferSize=0x11000 retry=7
out err=-9, last_trans=0 c=0x190c max=0x10 transferSize=0x11000 retry=8
out err=-9, last_trans=0 c=0x190c max=0x8 transferSize=0x11000 retry=9
out err=-9, last_trans=0 c=0x190c max=0x10 transferSize=0x11000 retry=10

<<<76044, 69632 bytes>>>
3 in err=-7, last_trans=0  00 00 00 00
4 in err=-7, last_trans=0  00 00 00 00
jumping to 0xf800742c
jump_command err=-9, last_trans=0
jump_command err=-9, last_trans=0
jump_command err=-9, last_trans=0
jump_command err=-9, last_trans=0
jump_command err=-9, last_trans=0
jump_command err=-9, last_trans=0
jump_command err=-9, last_trans=0
Did you see that summary line: <<<76044, 69632 bytes>>> (i.e loaded 69632 of 76044 bytes)? 69632 bytes is 68kb. 68kb = 72kb of free OCRAM area - 4kb of flash header in u-boot.bin.

It's just an observation, nothing more.
eureka is offline   Reply With Quote