Author Topic: Display access from bootloader / Portable binary test (Read 131834 times)

kitor · « **Reply #50 on:** April 04, 2015, 12:10:34 AM »

30D no luck (so I guesss signature is bad)

rpt · « **Reply #51 on:** April 04, 2015, 07:01:36 PM »

I have a 5D3 and a 7D2. This I first tried it on the 5D3. I dont know what I am doing wrong but I get this screen when I put the card in and close the card slot door:

20150404_215330 by Rustom, on Flickr

The procedure I followed on the 5D3 was:
1. So I copied my ML card over to a test card and verified that it worked right (could un-install ML and reinstall ML).
2. Replaced the autoexec.bin from the link in the first post onto this test card.
3. Placed the card in the slot and closed the door.
4. I got the above screen.
5. Removed the battery.
6. Replaced the original ML card.
7. Camera booted with ML and it worked.

So I thought that may be the other ML files were not needed So I removed the ML folder and the .FIR file but got the same result.

What am I doing wrong?

Do you want me to try something on the 7D2?

Pelican · « **Reply #52 on:** April 04, 2015, 09:14:03 PM »

Quote from: Ottoga on April 03, 2015, 01:31:18 AM

Loaded this onto my cf card (7D). When I turned on the camera, the led flashed a couple of times and nothing.

That is:
- no image appeared on the screen
- ML didn't load
- canon menu operational

The autoexe.bin used was downloaded from the link in Alex's 1st post.

Should I be doing anything else to "run' it?

Use the autoexec from g3gg0's link.

a1ex · « **Reply #53 on:** April 04, 2015, 09:52:22 PM »

@rpt: my fault, I probably uploaded the VxWorks experiment by mistake (solved, download again).

The binary from first post should now work on 7D as well.

rpt · « **Reply #54 on:** April 04, 2015, 10:55:04 PM »

A1ex, Thanks, that sorted out the 5D3 issue. Here is the image from the 5D3:

20150405_015915 by Rustom, on Flickr

However, it did not install on the 7D2. Please note I have a 7D2 and not the 7D. I tried to load it using the firmware update but got the following message. Attached are the two images - one before starting the firmware update and the other when it tried to do the firmware update.
Before selecting firmware update on the 7D2:

20150405_020525 by Rustom, on Flickr

After doing the firmware update on the 7D2:

20150405_020557 by Rustom, on Flickr

Is there something else I need to do? Do you want me to do any other test?

Licaon_Kter · « **Reply #55 on:** April 04, 2015, 11:10:19 PM »

7D2 is not (yet) supported: http://builds.magiclantern.fm/#/features

rpt · « **Reply #56 on:** April 04, 2015, 11:15:25 PM »

Thanks. I kind of knew that but was hoping for a miracle. You guys are great at miracles

Ottoga · « **Reply #57 on:** April 05, 2015, 06:33:51 AM »

Done.

https://www.dropbox.com/s/lrcyydx5re98ysq/7D_Magic_Rescue_screenshot.jpg?dl=0

My original attempt failed due to the CF card having had its bootflag reset (probably something that I did the last time I used it)

For the above screenshot, the image was displayed without my needing to power on the camera. (is this how it should work?). I had to remove and reinsert the battery in order to get the camera working again.

Cheers

kitor · « **Reply #58 on:** April 24, 2015, 12:21:42 AM »

My broken ERR50 50D

dukeonee · « **Reply #59 on:** November 09, 2015, 04:29:34 PM »

Hello,

I am at a time where my 5D2 is bricked. The LCD screen and top right screen is blank/black; when turning it on the red light flashes erratically. One thing is that when I press the shutter it will take a photo.. (sounds like a half attempt of a shuttler and doesn't save a photo). When I press the liveview the mechanism inside turns on but the screen is blank.

My cards were reformatted. I don't remember what build I was using. How do I create a FIR to use for autoexec.bin file.

I hope people can help me here or lead me to reviving my camera. very much appreciate it.

Walter Schulz · « **Reply #60 on:** November 09, 2015, 04:33:47 PM »

You don't have to use FIR to enable cards. Run EOScard or MacBoot to make card bootable. Wipe Autoexec.bin and ML directory and replace it with latest nightly build or put diagnostic Autoexec.bin to card for "Screen test".

justenS · « **Reply #61 on:** January 14, 2016, 04:09:32 PM »

So this is what I get.
What can I do now, my camera won't start up.
There is only a red light flickering when I insert the battery.

Walter Schulz · « **Reply #62 on:** January 14, 2016, 04:21:13 PM »

First: Rescale pic.
Second: It works exactly this way.

Format the card in cardreader now. -> ML deleted from card
Or delete autoexec.bin and copy extracted nightly build contents to card. If you want to use ML ...

a1ex · « **Reply #63 on:** January 25, 2016, 08:55:39 AM »

I did a small update to display initialization routine (noticed Canon actually calls those from RAM, not from ROM).

Do you mind checking if it still works? No need to upload new screenshots, just a confirmation (works or not).

Link is the same (first post).

Oswald · « **Reply #64 on:** January 25, 2016, 09:36:20 AM »

100d b version.

nikfreak · « **Reply #65 on:** January 25, 2016, 06:40:50 PM »

I can confirm the new autoexec.bin is working for 100D.100B & 70D.111A:

100D.100B isn't able to print the "Camera Model" text [? ? ?] as seen in pic before my post.

Licaon_Kter · « **Reply #66 on:** February 02, 2016, 10:27:57 PM »

EOS M

what's that 9.9.8 somethingsomething ?

a1ex · « **Reply #67 on:** February 03, 2016, 12:49:38 PM »

Some internal sub-version number. For example, what we call 70D 111A/111B have the main version number 1.1.1 and the other numbers differ.

Nikfreak used these extra numbers to identify the firmware sub-version from modules, for example.

veeman · « **Reply #68 on:** March 04, 2016, 03:53:27 AM »

I've run the diagnostic tool and have attached a pic of the screen. The tool runs fine, but when the regular autoexec.bin is replaced, the screen is blank when turned on. The red led on the bottom right blinks once every time I open card door or insert battery.

Thanks for your help.

Licaon_Kter · « **Reply #69 on:** March 04, 2016, 09:59:42 AM »

You've just replaced AUTOEXEC.BIN and not deleted ML-SETUP.FIR (or whatever the FIR is named), right?

Walter Schulz · « **Reply #70 on:** March 04, 2016, 10:03:45 AM »

It doesn't matter if a FIR is located there or not in this situation. FIR is used only during installation (Firmware Update in Canon menu).

Make sure to have all other ML files there, too. Autoexec.bin + ML directory (with contents there, of course).

a1ex · « **Reply #71 on:** March 04, 2016, 10:21:43 AM »

Hint: check other posts from the same user before replying

a1ex · « **Reply #72 on:** July 15, 2016, 11:54:08 PM »

Portable display test updated for DIGIC 6 cameras - FIR files available on request.

Licaon_Kter · « **Reply #73 on:** July 16, 2016, 01:19:18 AM »

So 750D, 760D, 80D, EOS M3, 7D Mark II, 5DS and 5DS R ?

ddelreal · « **Reply #74 on:** July 16, 2016, 03:07:36 AM »

Quote from: Licaon_Kter on July 16, 2016, 01:19:18 AM

So 750D, 760D, 80D, EOS M3, 7D Mark II, 5DS and 5DS R ?

7D Mark II would be incredible. Good news that there is progress on the DIGIC 6.

News:

Author Topic: Display access from bootloader / Portable binary test (Read 131834 times)