Quote:
Originally Posted by littelbro14
So I've searched this entire thread for a solution to this issue. I'm not sure if I'm missing something, but I still haven't found one. I'm on Ubuntu 12.10, 64-bit. I compiled k3flasher from source (couldn't get the provided binary to work, not sure why), and I extracted the RAM kernel myself, directly from the latest ATK exe. Here's my in/output.
Code:
root@TARDIS:/home/colten/Downloads/k3flasher# ./k3flasher mx35to2_mmc.bin program 0x00041000 kernel.bin
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.
Any help on this would be fantastic.... |
I recall GM saying something about this kind of thing. but don't recall what.
Assumedly you built the latest one from GIT so it's not an old version.
Ram kernel should be fine. it would just bork much earlier otherwise.
Hopefully one of the heavyweights can step up and guide you better.
EDIT: Is there any reason you are not just saying:
./k3flasher mx35to2_mmc.bin program kernel kernel.bin
???