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.

mir66

I'm confused. What must I doing?
Thank you for your help
Soft ML for 5Dc - Beta 4
Debug
1. Don't click me
2. Stability tests
3.Show tasks
4. Image Buffers: 540x426, 540X426
5. Free memory 2525K
6. CMOS Temprat: 141 (raw)
7. Snap Simulation: Take real pic

a1ex

My bad, didn't notice it wasn't enabled back then; will send you a test binary by PM.

mir66

Thank You.
Now, dump ROM is enabled in menu ML.
After pressing SET only black screen. Screen on top camera normal working. It is possible now take the picture. Nothing written to the card.
What now. Any idea?
Regards

chakawa

Hello,

My 5dmkII who had been long running with ML without probs, just froze suddenly.
I have placed the autoexec file (portable display test) on the card ; and got a long log. Don;t understand any of it and does not look like I can attach it to my post (can I ?)
Basically there was an almost non visible dark screen with dark small grey lines horizontal. And when I turn the camera off and on again, it did not repeat the display.
Then I placed the second autoexec file (LED blink test) ; and there was no blink happening.

Assuming I needed to remove the original ML Autoexec manually from the card : is that right ?

Any advice would be greatly greatly appreciated

Thanks in advance
Chakawa

Walter Schulz

Did you remove/insert battery before/after running tests?

chakawa

Thanks for your reply.
Yes I did.

Also, I just replaced the battery with a new one and all what's happening is it is blinking red (kind of same as it does normally) but nothing showing up on LCD and camera does not boot.

Also pls note that the camera does not do anything (not even blinking) without any CF card inserted (with new battery).

What next step should I take ? Should I re-install ML completely ?

Thanks in advance
Chakawa

Brian Blagowsky

After having my camera lock up yesterday when I tried to insert a new CF card after receiving a prompt that the one I was using was full, I have been trying everything to get my 5DII to recognize my CF cards. I have tried erasing them using my Mac since I can't get the camera to format them or even recognize them.
After hours of messing with it, I finally got a card that I had reformatted as MS-DOS FAT, and then loaded the auto exec.bin file and the latest ML folder from the nightly builds, along with the DCIM and MISC folders, to do something other than lock up. I got a Magic Lantern Rescue screen upon startup.  I have tried to drag and drop, or upload the photo I took, but can't get either to work, so I will type out what was on the screen:

Magic Lantern Rescue
------------------------------------
- Model ID: 0x218 5D2
- Camera model: Canon EOS 5D Mark II
- Firmware version: 2.1.2 / 6.9.8 A1(00)
- IMG naming: 100EOS5D/IMG_0000.JPG
- User PS:      Cinestyle
- Boot flag: FIR=0 BOOT=-1 RAM=-1
- ROMBASEADDR: 0xFF010000
- ROMBASEADDR: 0xFF810000
- DONE!

You may now remove the battery.

a1ex

Here's a small experiment that applies to all EOS cameras from DIGIC 2 to 6, as long as they have the boot flag enabled. I'm trying to autodetect the ROM layout, as - at least on DIGIC 6 - there seem to be another memory region, unknown to us at the time of writing.

autoexec.bin

In particular, I'm interested in test results on the following models:
- 5D, 400D (DIGIC 2)
- 1000D (DIGIC 3, 64MB RAM - applied the fix discussed earlier in this thread)
- 7D
- any small DIGIC 5
- 6D, 70D
- all DIGIC 6 models with boot flag already enabled

Levas

Tried it on my 1000d, with bootflag enabled, but nothing happens  ???

I've put the autoexec.bin on a bootable SD card and put in the 1000d, turn it on and nothing special seemed to happen ?

a1ex

What exactly do you mean by "nothing happens" ?

- camera loads Canon firmware? (if yes: either card is not bootable, or camera doesn't have the boot flag enabled)
- black screen? (if yes: that's a bug in the display init routine)
- something else?

dfort

Looks like it worked on the EOSM2



The test didn't save anything to the card--assume that it only prints to the LCD?

Levas

On 1000d it loads canon firmware...
The same card in my 6d works, so it isn't the card...
On 6d:


Hmm, I had boot flag on 1000d enabled in the past, not sure if I kept it that way  ???

Levas

Wait, I'm not sure that I enabled boot flag on the 1000d, the testing from years ago was with FIR files, not with autoexec.bin files...
How do I enable bootflag on the 1000d, is there a FIR file for that ?

dfort

More cameras

EOSM


500D


700D


7D


Wondering if the 7D is showing the address for the Master processor?

Ant123


a1ex

Looks like it worked :D

It identifies unused areas (1 byte repeated many times) and actual ROM size (unique size x number of repetitions).

Not touching master on 7D yet. The memory map configured at startup app references 0xE0000000, so I thought it must be something there. 80D references 0xEE000000, but locked up on both 0xEE000000 and 0xE0000000.


7D:
FFFF2374: MCR p15,0,Rd,cr6,cr2,0:  946_PRBS2 <- 0xE0000039 (E0000000 - FFFFFFFF, 0x20000000)

80D:
[CPU0] FE0258E4: MCR p15,0,Rd,cr6,cr2,0:       RGNR <- 0x5       
[CPU0] FE0258EC: MCR p15,0,Rd,cr6,cr1,0:      DRBAR <- 0xEE000000
[CPU0] FE0258F4: MCR p15,0,Rd,cr6,cr1,4:      DRACR <- 0x329      (P:RW U:RW; Inner Write-back, write-allocate; Outer Write-back, write-allocate; Non-shared)
[CPU0] FE0258FC: MCR p15,0,Rd,cr6,cr1,2:       DRSR <- 0x31       (0x2000000)

ArcziPL

70D:



700D (slightly different output than posted by dfort):
M50.110 [main cam] | G7X III [pocket cam] | 70D.112 [gathers dust] | M.202 [gathers dust] | waiting for M5II



toms

750D:

Magic Lantern Rescue
----------------------------
- Model ID: 0x393 750D
- Camera model: Canon EOS K393
- Firmware version: 1.0.0 / 8.5.1 B4(52)
- IMG naming: 100CANON/IMG_2722.JPG
- Boot flag: FIR=0 BOOT=-1 RAM=-1 UPD=-1
- ROMBASEADDR: 0xFE0A0000
- F0000000-F7FFFFFF: byte 0x0 x 0x8000000
- F8000000-FBFFFFFF: byte 0x0 x 0x4000000
- FCE00000-FCFFFFFF: byte 0xFF x 0x200000
- FD400000-FD4FFFFF: byte 0xFF x 0x100000
- FCA00000-FDBFFFFF: byte 0xFF x 0x200000
- FDF00000-FDFFFFFF: byte 0xFF x 0x100000
- FC000000-FFFFFFFF: uniq 0x2000000 x 0x2
- DONE!

You may now remove the battery.

critix

For Canon 1300D can you give me FIR file?
Thanks a lot.
Canon 1300D, 500D, EOS M, EOS M2


OneCameraDude

 @a1ex i recently got a 5dmkii from a friend and it's bricked. i was wondering if i can just run the autoexec.bin file or do i have to do something? idk im new to this lol

Walter Schulz

If it is bricked you can't run standard installation procedure.
Portable Display Test autoexec.bin is able to run on a cam that has been enabled for ML (part of the installation process) with a bootable card (enabled by installation process or using PC and some software).
So: Is cam just dead in the water?

tor

Hello,

Just ran this test, here's the picture :

I've an issue with my 5D2, It doesn't read any CF card. I don't know how to fix it. I already open a topic a few weeks ago but didn't get any answer, and tried to investigate a little further.

How can i make it work again ? I just need to make it boot on the right ML again !