Quote:
Originally Posted by hawhill
My suggestion was a cat photo JPEG. Be sure to chose a healthy, good looking cat.
(SCNR. What knc1 said - but 4kByte is probably enough.)
|
Thanks once again for your help.
Unfortunately flashing those partitions did not help.
Anything else I can do?
Code:
k3flasher$
k3flasher$ dd if=/dev/zero of=4kbimg.img bs=1024 count=4
k3flasher$ sudo ./k3flasher mx35to2_mmc.bin program 0x2adc8000 4kbimg.img
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.
D: flash_program: 0x2adc8000 4kbimg.img 0x00000000
I: continue flashing at address 0x2adc8000 offset 0x00000000
I: flashing 0x00001000 (=4096) bytes
I: downloading 0x00001000 (=4096) bytes, starting at 0x2adc8000
I: different block, read before flash disabled
I: writing 0x00001000 (=4096) bytes to address 0x2adc8000, waiting for completion...
I: wrote 0x00001000 (=4096) bytes, waiting for completion...
I: flashing of 0x00001000 (=4096) bytes complete
I: offset 0x00001000 continue_address 0x2adc9000 100.00%
k3flasher$ sudo ./k3flasher mx35to2_mmc.bin program 0x2a5c8000 4kbimg.img
W: cannot find device (is it in USB loader mode? are you root?) - waiting for it...............
I: success.
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.
D: flash_program: 0x2a5c8000 4kbimg.img 0x00000000
I: continue flashing at address 0x2a5c8000 offset 0x00000000
I: flashing 0x00001000 (=4096) bytes
I: downloading 0x00001000 (=4096) bytes, starting at 0x2a5c8000
I: 0x2a5c8000 verified
I: offset 0x00001000 continue_address 0x2a5c9000 100.00%