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.


Messages - Ant123

Pages: 1 ... 3 4 [5] 6 7
101
Reverse Engineering / Re: Interrupt IDs
« on: January 23, 2018, 08:27:41 PM »
0x145: MZRM

102
Camera-specific Development / Re: Canon 80D
« on: January 17, 2018, 09:42:27 PM »
I'm not sure that this is useful until emulation reaches the mzrm initialization.

103
Camera-specific Development / Re: Canon 80D
« on: January 17, 2018, 05:45:48 PM »
found in RAM dump provided by sombree:
two uyvy buffers at 0x41785B00, 0x41901800
one RGBA buffer at 0x043ED100

bitmap buffers are 960*540 pixels with black bars:


104
General Development / Re: How to run Magic Lantern into QEMU?!...
« on: December 21, 2017, 08:19:47 AM »
The emulation doesn't seem to initialize Zico on 80D yet - does reach this stage on M3?

Code: [Select]
Set default DRAM parameter
#
DRYOS version 2.3, release #0055+p6
Copyright (C) 1997-2013 by CANON Inc.
[SDIO] Error
[SDIO] Error
[SDIO] Error
[SDIO] Error

StartDiskboot
Diskboot file not found
2.1.1
3.1.1
4.1.1
3.1.2:11,0,0,4,0
3.1.3:1
3.1.3:0
3.1.2:11,0,0,4,0
3.1.3:1
3.2.1:2
3.2.3:2
3.2.7:2
3.2.9:2
3.2.11:2
3.2.13:2
3.2.15:2
3.2.17:2
3.2.19:2
3.4.4.1:0,128,128,1
== PnlSync =========
  vwidth  : 494
  hwidth  : 909
  h_pre   : 723
  h_blank : 719
  vb_lt   : 490
  vb_st   : 11
  vp_lt   : 490
  vp_st   : 11
  vb_l    : 490
  vb_s    : 11
  vp_l    : 490
  vp_s    : 11
====================
3.4.1.1:720,480,1,10,1
3.3.2:fc5f95cc(32,32,32),1
3.3.3:fc5f95d0(0),1
3.3.4:fc5f95ec,(0,1),1
3.3.5:fc5f962c,1
3.3.7:fc5f965c,1
3.3.9:fc5f9664,1
3.3.10:fc5f9668,1
3.3.1:fc5f95cc,1
3.1.6:1,2,9,0
3.10.1:124,128,134,0,0,0,1
3.3.12:1,1
3.2.19:0
3.2.17:0
3.2.15:0
3.2.13:0
3.2.11:0
3.2.9:0
3.2.7:0
3.3.14:0,0,1
InitializeGraphicLog Addr:0x4112b000 Size:0x5000
DlphLog:Addr:0x4112b000, Size:0x1400
_FreeMsg   : ------ req:0 stt:32
_CreateMsg : 0xbff00500 size:12
_FreeMsg   : ------ req:0 stt:32
SendMsg   : 1
ZicoLog:Addr:0, Size:0x2800
InitializeGraphicLog SUCCESS
_FreeMsg   : ------ req:1 stt:33
_FreeMsg   : 0xbff00500 free:1
_CreateMsg : 0xbff00500 size:4
_FreeMsg   : ------ req:1 stt:33
SendMsg   : 2
_FreeMsg   : ------ req:2 stt:33
_CreateMsg : 0xbff00528 size:76
_FreeMsg   : ------ req:2 stt:33
SendMsg   : 3
_FreeMsg   : ------ req:3 stt:33
_CreateMsg : 0xbff00598 size:4
_FreeMsg   : ------ req:3 stt:33
SendMsg   : 4
_FreeMsg   : ------ req:4 stt:33
_CreateMsg : 0xbff005c0 size:0
_FreeMsg   : ------ req:4 stt:33
SendMsg   : 5
[GRYP]T: --- Initialize start ----------------
_FreeMsg   : ------ req:5 stt:37
_FreeMsg   : 0xbff00500 free:2
_FreeMsg   : 0xbff00528 free:3
_FreeMsg   : 0xbff00598 free:4
_FreeMsg   : 0xbff005c0 free:5
_CreateMsg : 0xbff00500 size:0
_FreeMsg   : ------ req:5 stt:37
SendMsg   : 6
[GRYP]T: InitializeGryp(Pri)    : Completed.
         Privilege Event handle : 0x02500050
_FreeMsg   : ------ req:6 stt:38
_FreeMsg   : 0xbff00500 free:6
_CreateMsg : 0xbff00500 size:0
_FreeMsg   : ------ req:6 stt:38
SendMsg   : 7
         GRYPHON revision       : 0x00000000
[GRYP]T: Initialize(Pri): Completed.
[GRYP]T: --- Initialize(Pri/Nml) Completed ---

_FreeMsg   : ------ req:7 stt:39
_FreeMsg   : 0xbff00500 free:7
_CreateMsg : 0xbff00500 size:12
_FreeMsg   : ------ req:7 stt:39
SendMsg   : 8
_FreeMsg   : ------ req:8 stt:40
_FreeMsg   : 0xbff00500 free:8
_CreateMsg : 0xbff00500 size:12
_FreeMsg   : ------ req:8 stt:40
SendMsg   : 9
_FreeMsg   : ------ req:9 stt:40
_CreateMsg : 0xbff00530 size:16

...



SendMsg   : 27
_FreeMsg   : ------ req:27 stt:59
_FreeMsg   : 0xbff00500 free:27
_CreateMsg : 0xbff00500 size:772
_FreeMsg   : ------ req:27 stt:59
SendMsg   : 28
3.4.1.4:5,00690f70,1,0,1e0
3.4.1.5:5,0,0,720,480,0,0,1
3.4.1.6:5,0,3,0,1
3.4.1.2:5,1,1
3.2.21:1,fc152451,00000000
3.2.22:1,1
3.2.3:0
3.3.15:1,1

At least it tries to draw something by sending JediDraw message (0xFC4BB8BA)
I've used this patch to display debug messages:
Code: [Select]
PatchDbgByte(0x00028698,0xFF);
PatchDbgByte(0x00028699,0xFF);
PatchDbgByte(0x0002869A,0xFF);
PatchDbgByte(0x0002869B,0xFF);

PatchDbgByte(0x000286A0,0x9D);
PatchDbgByte(0x000286A1,0xFD);
PatchDbgByte(0x000286A2,0x37);
PatchDbgByte(0x000286A3,0xFC);

PatchDbgByte(0x000286A8,0x9D);
PatchDbgByte(0x000286A9,0xFD);
PatchDbgByte(0x000286AA,0x37);
PatchDbgByte(0x000286AB,0xFC);

Quote
BTW, do you happen to have any notes on UTimer or Omar?
no

105
General Development / Re: How to run Magic Lantern into QEMU?!...
« on: December 20, 2017, 03:52:38 PM »
Some progress on emulating DIGIC 6:

I think it's possible to emulate simple drawing of text strings in case main CPU will send certain messages to MZRM core...
But on EOS M3  the camera controller still does not allow to start it normally and goes to shutdown.
What is the situation with DSLRs?

106
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: December 07, 2017, 06:31:11 PM »
BTW - address 0xFFD65490 doesn't seem valid for 450D - did you mean 0xFFD237F0 ?
Yes. There was wrong address 0xFFD65490.
But it doesn't help to create working binaries using modern GCC.
Only gcc-arm-none-eabi-4_7-2012q4 generates binary which doesn't stuck.

Quote
Does that mean not all these patches from disable_cache_clearing are actually required for booting?
I don't know. I just found the same opcodes based on 40D port.

107
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: September 24, 2017, 01:39:54 PM »
Does the "ETTR ETTR ETTR ETTR" message show up on actual hardware as in the above screenshot?
Yes, if you are talking about ML Prefs menu.

Quote
Compiling from latest changeset from Ant (c700f92) gives the same result (stuck on initial screen, with LED turned on).
Try this patch:
Code: [Select]
diff -r 18ac6b0f9929 platform/450D.110/init.c
--- a/platform/450D.110/init.c Sun Oct 30 14:43:33 2016 +0200
+++ b/platform/450D.110/init.c Sun Sep 24 14:27:14 2017 +0300
@@ -89,7 +89,9 @@
  // _mem_init();
  bmp_vram_idle_ptr = malloc(360*240);
  // _find_ml_card();
- msleep(550);
+ // msleep(550);
+ uint32_t size;
+    while((FIO_GetFileSize("AUTOEXEC.BIN", &size ) != 0) || (size == 0))  msleep(10);
  _load_fonts();
        // msleep(300);
  call("DisablePowerSave");
Note: I'm using gcc-arm-none-eabi-4_7-2012q4. With GCC 4.8 it stuks.

108
Camera-specific Development / Re: Canon 750D
« on: July 12, 2017, 06:33:45 PM »
Walter Schulz

Are not you tired of answering stupid questions from new members?
Maybe it's need to oblige them to read the FAQ before they can leave comments?

109
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: June 24, 2017, 10:12:29 PM »
I'm I missing something?
Read the FAQ first...

110
Reverse Engineering / Re: UHS-I / SD cards investigation
« on: June 19, 2017, 11:31:21 AM »
My hypothesis was that 5D3's SD controller is UHS-capable, but for some unknown reason (could be even problems during the initial tests), Canon decided not to include it in the firmware. As a result, some of the UHS initialization code (hopefully a small part) was optimized out.

If you can not enter UHS mode with ML but it works without, read this topic.
Conclusion:
Most SD cards need to be reinitialized by switching off SD power if they already were in UHS mode.

111
Camera-specific Development / Re: Canon 80D
« on: May 12, 2017, 10:15:02 PM »
http://chdk.wikia.com/wiki/Digic_6_Porting

Copying CHDK cache functions is probably enough to move forward.

What is "CHDK cache functions" ?

113
Camera-specific Development / Re: Canon 7D Mark II
« on: April 16, 2017, 11:52:07 PM »
and M5, M6, M10...
M3 and M10 already run CHDK  :P

114
Reverse Engineering / Re: Intercepting DebugMsg with cache hacks
« on: April 15, 2017, 12:09:09 AM »
Can anybody post here logs containing UHS-SD initialisation messages(like there)

115
Camera-specific Development / Re: Canon 80D
« on: February 26, 2017, 07:24:28 PM »
EnableBootDisk
Code: [Select]
0xFE5F150C(0xFC040004, -1);
DisableBootDisk
Code: [Select]
0xFE5F150C(0xFC040004, 0);
Try it on YOUR camera first.  ;D

116
Camera-specific Development / Re: Canon 80D
« on: February 26, 2017, 03:26:48 PM »

117
Camera-specific Development / Re: Canon 80D
« on: February 24, 2017, 07:17:20 PM »
When we will see exactly the same picture on the camera display?   :)

118
Camera-specific Development / Re: Canon 80D
« on: February 19, 2017, 02:23:11 PM »
There is a new firmware for the 80D available , maybe this will help developing an 80D ML Version ?
No. Only finding the developer with the camera would help...

119
General Help Q&A / Re: Battery drain
« on: February 16, 2017, 11:14:11 PM »
Image quality is not sufficient to read IC marking.
But it looks like one of those...

120
General Help Q&A / Re: Battery drain
« on: February 16, 2017, 10:52:53 PM »
Might work, but somebody has to reverse engineer it :D

First of all it's need to identify the RTC chip.
Where to find mainboard photos better than this?

121
General Help Q&A / Re: Battery drain
« on: February 16, 2017, 09:42:49 PM »
What about using the RTC chip for waking up the camera? Some chips have an alarm output signal, but I am not sure it's connected to cpu/mpu.

122
General Chat / Re: Eos M with Magic Lantern or Eos M3 without?
« on: February 04, 2017, 10:04:15 PM »
But currently CHDK still have no ML features implemented...

123
General Chat / Re: Eos M with Magic Lantern or Eos M3 without?
« on: February 04, 2017, 09:38:51 PM »
I bet you the M2 will get ported first!
Do you remember, where and when M2 was released?

is there still any possibility of a ML port to the M3?
The possibility is equal to the possibility of a ML port to Digic6-based Powershot cameras.  :)


124
Camera-specific Development / Re: EOS M5 - 80D in your "pocket"
« on: January 21, 2017, 07:34:01 PM »
There is no working port for M2, unlike M10
2 vs 1  :)

125
Camera-specific Development / Re: EOS M5 - 80D in your "pocket"
« on: January 21, 2017, 07:08:41 PM »
http://builds.magiclantern.fm/ -> under "Your camera is not listed?"
There should be writen: "most of Canon EOS M cameras (M3, M5, M10) are based on PowerShot firmware"  :)
There are two cameras with CHDK vs. one with ML.

EOS M5 internals - there is no ADTG chip

Pages: 1 ... 3 4 [5] 6 7