Quote:
Originally Posted by geekmaster
Well, 2115008 is NOT a multiple of 512, so it DOES need some padding.
Using integer arithmetic:
(2115008+511)/512)*512-2115008 = 64
So you need to append another 64 bytes to your uImage file:
dd if=/dev/zero bs=64 count=1 >> uImage
Then try flashing that...
@hawhill: How about having k3flasher append zeros to the next 512 byte boundary to avoid this problem? |
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