Display access from bootloader / Portable binary test

Started by a1ex, March 15, 2015, 07:13:36 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

rbrune

Well, dual iso managed to save 'DUAL2086.CR2' successfully... so that worked.

a1ex

Thanks everybody for the tests.

Here's a follow-up of this experiment: a nice error page if you load ML on a different camera or firmware version.

https://bitbucket.org/hudson/magic-lantern/pull-request/616/portable-error-messages-if-ml-is-loaded-on

g3gg0

Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

Pelican

EOS 7D Mark II, EOS 7D, EOS 5, EOS 100 + lenses (10mm to 300mm), 600EX, 550EX, YN600EX x 3
EOScard, EOS DSLR firmwares, ARMu, NiControl, etc.: http://pel.hu/down

g3gg0

Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

DeafEyeJedi

5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

g3gg0

@DeafEyeJedi:
can you try the one from my last post too?
Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

Walter Schulz

@g3gg0:
Tested your Autoexec.bin with 650D

- Camera: '650D'
- Camera model: ???
- Firmware version: 1.0.4 / 5.6.4 87(28)
- IMG naming: 100?????/IMG_5255.JPG
- User PS: Marvels Advanced 3.4
- Boot flags: FIR=0 BOOT=-1 RAM=-1 UPD=-1
- ROMBASEADDR: 0xFF0C0000
- DONE!

DeafEyeJedi

@g3gg0:

I'm currently at the airport boarding flight to Puerto Rico and won't be back until March 27th.

Until then.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

arrinkiiii


@DeafEyeJedi

That the ML force be with you. Happy rec's  8)

kitor



550d. Later I'll try on my ERR50 50D (I must find cf card)
Too many Canon cameras.
If you have a dead R, RP, 250D mainboard (e.g. after camera repair) and want to donate for experiments, I'll cover shipping costs.

g3gg0

thanks for all the tests :)

and it is totally encouraging to see so many models succeed this test!
someone who can try my posted on on a EOS M ?

Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!


DeafEyeJedi

Thanks @Licaon_Kter for giving us a hand regarding M1.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

Pelican

Is there a solution for the background on 50D, 5D2 and 7D?
EOS 7D Mark II, EOS 7D, EOS 5, EOS 100 + lenses (10mm to 300mm), 600EX, 550EX, YN600EX x 3
EOScard, EOS DSLR firmwares, ARMu, NiControl, etc.: http://pel.hu/down

Walter Schulz

Pelican, a solution requires a problem to be solved. IMO there is no problem. It looks different and I don't care.
There are other priorities, I hope!

g3gg0

Help us with datasheets - Help us with register dumps
magic lantern: 1Magic9991E1eWbGvrsx186GovYCXFbppY, server expenses: [email protected]
ONLY donate for things we have done, not for things you expect!

a1ex

Does this test binary work on external monitors?

Indy

The bootcode can also receive input chars, but how ? using a serial connector through the battery connector or USB ?
On 550D at least, the grip (connected through by battery port) can be upgraded via the camera body.
Canon must have a dedicated device to do low level debugging/finetuning through bootcode.

Indy

bootrom

I would expect USB or HDMI dongle.

Olympus uses a special HDMI dongle. If you connect it to Olympus EMx and power one camera, then it switches into debug mode. This dongle acts as input/output for debug commands (but "output" also changeable to camera display). And private person can't buy HDMI encoder ?

ilex

@A1ex: Can You create a FIR for 40D? Thanks in advance.

a1ex

Sure. VxWorks binaries, not tested:

For 400D/5Dc: autoexec.bin (you can try it if you are already running 400plus on 400D or ML on 5Dc)
For 40D: 40d.fir
For 30D: 30d.fir (not sure I've signed it properly)

Autodetection code is based on the strings from 400D and 5D classic bootloaders (hopefully 40D is similar).

Ottoga

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?
EOS 7D.203, EFS 55-250mm, EF 75-300 III, Tamron 16-300 DiII VC PZD Macro, SpeedLite 580EX II.

kitor

Yep, the card must be prepeared for "normal" MagicLantern boot, you just replace autoexec on working card.
@alex - I'll try on 30D tomorrow.
Too many Canon cameras.
If you have a dead R, RP, 250D mainboard (e.g. after camera repair) and want to donate for experiments, I'll cover shipping costs.

Ottoga

Thanks for the reply. That's what I did,  Just replaced the autoexec.bin on one of my ML CF cards.
EOS 7D.203, EFS 55-250mm, EF 75-300 III, Tamron 16-300 DiII VC PZD Macro, SpeedLite 580EX II.