Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - NerveGas

#1
If you build an autoexec.bin you can make a bootable SD.
#2
I've run all kinds of stuff with Alpha 3, as well as the latest repo head, and had no problems. Someone warned me to stay away from legacy focus points.
#3
Nightly builds don't have 5D3 built in. You need to download the source tree and compile it with 'make 5D3', then copy the autoexec.bin to a bootable SD card, along with the other files from the 5D3 release. You can build it quite easily if you grab one of the virtual machines set up with the dev environment.

I have uploaded a 5D3 autoexec.bin from latest source head here:

http://www.freefilehosting.net/autoexec_1

I take no responsibility if this damages your camera.
#4
I've got a license for IDA and Hex Rays; I need to set it up. If it would help, I should be able to decompile the firmware to C using hex rays... how do you get the firmware to dump? I ran the dev kit file and it dumped a file named ROM DAT but it was only 16k.
#5
What are you using to decompile? hex rays?
#6
Thanks for the replies.. Where in the code are the existing stubs? I can take a look and see if I can find the 5D3 stubs for the audio detection.
#7
Some functions in audio.c appear to be turned off for CONFIG_5D3, such as audio_configure. I wonder if this is part of the issue. Was this turned off just because it's experimental, or because something was incompatible?
#8
Trap focus working nicely. Intervalometer working. Bulb Timer working. Audio Remote Shoot NOT working. Motion detect working. Mirror lockup working.
#9
Got it working with a standard SD card. Verified motion detection and focus stacking work. Will test some other features. Are there any particularly dangerous features that write to the camera that I should be worried about?
#10
So I'm confused then; does a custom autoexec.bin disable auto-boot or disable the boot flag, or both? From what I've read, these are two separate things.
#11
a1ex, could you maybe post a second firmware file that disables the auto-boot bit, so we can get to doing some dev without losing the ability to back out of ML if necessary?
#12
a1ex, so when you say the full installer, do you mean if I create my own custom build of autoexec.bin and boot it, that it has an option to remove the boot flag? I've got it built; I'm just trying to find a way to boot it without making what appear to be at the moment permanent modifications to the camera...
#13
Would be great if a1ex could clear this up; I'm ready to dive right into dev but would like to make sure I can back out of the boot flag change on the 5D3 if I ever want to sell the camera. Will restoring the 1.1.3 firmware reset the boot flag (and will it allow you to restore the same FW already on the device)? If not, is there some other way to turn OFF the boot flag later on?
#14
Is this documented anywhere? What dial are you referring to?
#15
Because as I understand it if you don't have an auto exec file from that moment on, the camera won't boot.
#16
I have my own build compiled, before I turn on the boot flag with the provided firmware file: how do i turn it off later on?
#17
I have my own build compiled, before I turn on the boot flat with this file: how do i turn it off later on?
#18
Where is this Dev Kit VM you speak of?
#19
Just digging into the project (and the source later on tonight). Great job. Working well on my 5D III. Am thinking about recompiling with the focus menus enabled for testing. Has anyone tried focus stacking or trap focus yet? Is there any way to enable the menu through the UI or does it require a recompile? Thanks!
#20
General Help Q&A / Testing 5D MKIII
March 02, 2013, 11:09:21 PM
So far so good. Running Alpha 3 with no issues. Does anyone know if the focus menu can be activated somehow, or if it just hasn't been added in yet?