Messages

I'm not a mod, I'm not an administrator.

You are in second on this forum by the number of posts, so I confused you with moderator. Sorry.
But aren't you tired of answering the same stupid newbie questions over and over again?

I simply wanted to express my opinion that we will see abuse of this gem and we should be prepared to handle it.

I also do not prefer "security by obscurity".
But forcing users to read the FAQ formally shifts the responsibility for the negative consequences of their actions on them.

[Walter Schulz]

Walter Schulz
If this bothers you, why don't you force new users to read the FAQ before they can post on the forum. It would also be possible to hide links and attachments from unregistered visitors.

[Is simply cutting the pin 6 signal enough for not triggering the IRQ signal and shoot forever? (and keep time of the day and date active?)]

Is simply cutting the pin 6 signal enough for not triggering the IRQ signal and shoot forever? (and keep time of the day and date active?)

If it was your question my answer is "no".
The processor has enough timers to count the heat and RTC is needed only when camera is powered off.
On EOS R cameras RTC probably can be used to wake up the camera.
Anyway cutting PCB lines is bad idea. It's better to wait for a software solution.

I should be able to troubleshoot it in QEMU

Please don't forget to commit the QEMU branch to the repository.
The "Source code" link from the main page at this moment leads to the removed repisitory on bitbucket.org

[Walter Schulz]

Walter Schulz
You should understand that EOS M100 uses PowerShot based firmware and Canon Basic command set could be different for EOS R. Finding a string in a ROM dump doesn't mean that it can be easily accessed with Canon Basic, especially without testing it on a real camera.

Probably easier to reverse the rom to find out the reason

I assume that on SDXC cards the system uses a separate driver / library for EXFAT, which is loaded after checking the card for a signature.
I have the opposite situation with the EOS M3: I would not want to buy a SDXC card if it does not work with a CHDK.
Perhaps the same situation will be with ML when (and if) it will be implemented for new cameras.

There need to try SD or SDHC(not SDXC) card first. Is that so hard?

I tried the Kitor card.img on both slots on the R6. Nothing

What is the size of the card you tried?

Okay so I couldn't get EOScard to work. I kept getting the Drive: 1 ERROR Write Failed message so I decided to skip that step after a while and procedded to open up the camera with the help of the guys on discord.

Good job! But I suggest you to try again with EOScard. Maybe there need to run it as administrator?

But anyways, let's look for that bootflag UART port!!

Have you tried to dump firmware?

Assuming Canon didn't disable the UART port, of course.

At least the connector looks similar to R & RP:


and there is a hole in the case for it:


This arc is made of rubber?

However, before attempting to disable these timers, I should get some updated legal advice. If we were to implement this feature, it could raise some eyebrows at Canon

Looks like you got legal advice in spring 2019... 

Does someone feel ready to accomplish such a feat?

You!
Just get CF->SATA adapter and start experimenting.

"If you want a thing well done, do it yourself"

About EOSHD findings: who knows, the value of which temperature sensor  is reported by Canon API? Maybe average?

If it's software limit it probably can be resetted by resetting all camera settings. However, timer values can be stored in battery-backed memory (RTC) and not affected by a reset.

Custom filesystem for storing footage would require custom cardreaders

No custom card readers are required to access the sectors on the disk.

You can use dd to do reddeercity's suggestion of image from Red card, write image to non-Red card.  If that test doesn't work, they're most likely either doing something in HW on the disk, or in SW inside the cam.

Do you think they are so greedy that they have saved on what to order from the manufacturer a customized series of memory cards?
Unlike RED SSD they used the standard CF interface. Maybe they use custom filesystem?

I would like to find the detailed informations of my Cf cards, if anyone has an idea

You can try to use devices like this and special software that can show at least S.M.A.R.T info.

For example look at page 58 to understand what could be inside your CF card.
But it is very likely that you will not be able to change this information.

The camera also can check the name of the card manufacturer or the model name of the card, which are contained in the drive's passport and cannot always be changed.
Some software protection techniques use this information and card's serial number.

[heder]

@heder
How does this mode look in QEMU?

But a1ex hasn't posted on the forum for 4 weeks...

on the latest version of the magic lantern is the focus peaking function implemented?

Not implemented on 450D.

That is really interessing, too bad I don't have time atm to implement your module on 40D, maybe after summer holiday.

You need only modify lines 559, 560, 715 and 755.

Tried to use fast SD Card - Sandisk Extreme Pro 95MB/s (UHS-I U3 V30). CHDK benchmark on Digic6 camera writes at 70+ MB/s.

On 450D ML benchmark in playback mode writes at 19-20 MB/s. The theoretical limit is 48MHz / 2 = 24MB/s.
Can't display benchmark results in LiveView mode because canon code refreshes the bitmap buffer continiously and ML texts are flickering or disappear. How to fix it?

Now MotionJPEG recording is more stable at ~29.7FPS (dual write buffering - 2x8MB).
But frame drops still occur when the frame size exceeds 400kB for a long time.
In some very spetial situations frame size can exceed 700kB. For example: https://i.stack.imgur.com/YbUvO.gif

The experimental build is there

Is config_raw_liveview supported on this camera??
Thank you,
Damiano

Not yet. There are no changes since 2019.

The problem is that ML is not fully ported for 450D. Many functions are not yet implemented and therefore should not work properly.
Last year I was trying to implement "silent capture" module without success. I also stucked with raw_info.