CF card becomes unusable

[GoogleCodeExporter]

What steps will reproduce the problem?

Tried to install 400plus-20120415-10 following your instructions. Firmware 
update to 1.1.1 works without problem. Also the testfir part seems to work 
without problem.

I am running ubuntu 12.04. So, what I do is to format my 4GB CF card using 
gParted to FAT32.

Then I run from the terminal:
echo EOS_DEVELOP | sudo dd of=/dev/sdb1 bs=1 seek=71 count=11
echo BOOTDISK | sudo dd of=/dev/sdb1 bs=1 seek=92 count=8

I copy the autoexec.bin to the CF.

I put the CF back in and see the blue light flashing. I am able to take 
pictures in the regular mode and also to go to the new menu and use the options 
there.

When I look at the pictures on the camera I see the pictures I took and some 
unidentified/not understood files. 

If I turn the camera off and on again it reports that the CF card needs to be 
replaced.

Looking at the CF in gParted again it tells me that the whole disk space is 
unallocated.

This behavior is 100% reproducable. Any ideas or suggestions? Obviously the 
hack loading itself works. Is there something wrong with how I formatted the 
CF, which causes the camera to not be able to write correctly to the disk?

Thanks,
Philip

Original issue reported on code.google.com by philip.d...@gmail.com on 15 Jun 2012 at 4:37

[GoogleCodeExporter]

Hmm, this is strange problem, nothing of the kind was reported so far.
The symptoms looks like a broken CF card.

Few suggestions for you, but before starting with them, please recreate the 
partition on the CF card with "cfdisk -z /dev/sdb" for example.

1. Try formating the CF card with "mkfs.vfat -F32 /dev/sdb1"
2. Try using the card w/o preparing it with "dd" and w/o putting the hack on 
the card. See if the card works w/o the hack at all...
3. Try preparing the card and copy the hack on it, then try to take some photos 
again.

another option would be to try formating the card with FAT16 (mkfs.vfat -F16 
/dev/sdb1) (not sure if it works on 4GB card), then repeat the steps again.

Please report of success/failure.

Original comment by fired...@gmail.com on 15 Jun 2012 at 4:53

• Changed state: Started
• Added labels: Type-Support
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi, 
Following your suggestions I don't see any difference. The card works 
flawlessly if it is formatted by the camera. If I format the camera on the 
computer using gParted or directly mkfs.vfat... the camera reports that there 
is a problem with the card. Again, formatting the card in the camera fixes this 
problem. After that I see the same behavior as before. I can install the hack, 
take a few pictures, everything appears okay, but then after turning it on/off 
the camera reports the same problem. I did not try the 16bit version, but it 
would mean, that I cannot access the whole card, which is not what I want.

Thanks.

Original comment by philip.d...@gmail.com on 16 Jun 2012 at 4:00

[GoogleCodeExporter]

FAT16 can work up to 16GB IIRC, so you can format 4GB with FAT16.
The problem would be the cluster size which in this case should be 64k, not 4K 
like with FAT32. Thus you card will be able to take less photos than with FAT32.
And again: I'm not sure if the camera would take 4GB with FAT16.

From your report I got a bit confused.
So formating the CF on the PC is not working neither with the hack, nor w/o it?
And formating the CF on the camera is working w/o the hack, but not working w/ 
the hack ?

Original comment by fired...@gmail.com on 16 Jun 2012 at 10:19

[GoogleCodeExporter]

Any news on this issue, please?

Original comment by eduardo....@gmail.com on 28 Jul 2012 at 10:32

[GoogleCodeExporter]

No feedback; closing the issue.

Original comment by eduardo....@gmail.com on 26 Sep 2012 at 8:41

• Changed state: Invalid