View Single Post
Old 07-12-2012, 04:20 PM   #34
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by arooni View Post
Thanks for the help. I'm not super comfy with dd. I tried this method and arrived at a multiple of 512bytes, but still got the same errors:

LilArooni ~/development/k3flasher: sudo ./k3flasher mx35to2_mmc.bin program 0x00041000 uImage
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
LilArooni ~/development/k3flasher
NOT the SAME results. It is now missing the "I: size is not a multiple of 512" line shown in your previous post. So at least ONE of the problems has been solved.

I do not know the cause of the second "wrong transfer length" message. I do not have time to study the code now. Perhaps somebody else can help you with that one...

EDIT: If the "I" means "information" and the "E" means "error", then it was probably not required to pad the uImage out to 512 (but did not hurt either, just in case it CAUSED the next error). The REAL error is the "wrong transfer length" problem.

Last edited by geekmaster; 07-12-2012 at 04:25 PM.
geekmaster is offline   Reply With Quote