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 2 3 [4] 5 6 7
76
Camera-specific Development / Re: Canon 80D
« on: January 28, 2019, 07:54:34 PM »
- emulation is able to reach GuiMainTask (after updating the MPU messages and some trivial GDB patches - not yet committed)
- it gets stuck trying to communicate with Zico/MZRM (as expected)
Have you tried to apply modified EOS M3 patches? (0xFC3F1110, 0xFC3F1114, 0xFC3F1178)

77
General Development / Re: How to run Magic Lantern into QEMU?!...
« on: January 28, 2019, 06:39:38 PM »
Some progress with Zico core emulation:


But direct font taken from ML doesn't look beautiful...
But I found these fonts in M3 rom:
Code: [Select]
0xfd8a9640, 0x00021704
0xfd8eb030, 0x00024060
0xfd90f090, 0x00012e60
0xfd921ef0, 0x00056d70
0xfd978c60, 0x0009fe10
0xfda18a70, 0x0001f18c
0xfda37bfc, 0x00024cf4
0xfda5c8f0, 0x0000b9a0
0xfda682a0, 0x00000cc4
0xfda68f64, 0x00000f40
0xfda6aa8c, 0x00000cb8
0xfda6b744, 0x00000854
0xfda6bf98, 0x00000b88
0xfda6dc10, 0x00000cb0
0xfda6e8c0, 0x00000ad4
0xfda6f394, 0x0000113c

16 of them can be opened with FontForge

Also there need to decode images from ROM used to draw icons and some texts in Viewfinder mode.
These are vector graphic objects. They can be found by signature "99 99 0C 00" in DSLR's ROMs too. The next 32bit word is a size of drawing object.
Probably there need to use OpenVG to render it.



78
General Development / Re: How to run Magic Lantern into QEMU?!...
« on: January 20, 2019, 02:17:13 PM »
If you receive these strings from MMIO hooks, or from breakpoints into certain drawing functions, you will need to store them somewhere in a data structure, until the next display event comes up.

I recieve these strings from eos_handle_digic6: mzrm_send function writes 1 into register 0xD20F0840 to inform Zico core about new message.

I was trying this code, but it doesn't work:
Code: [Select]

DisplaySurface *surface = qemu_console_surface(s->disp.con);
printfxy(surface, (pos_x >> 16), (pos_y >> 16), "%s", MZRM_str);
Do I need to update the display somehow?

Even calling printfxy from eos_update_display doesn't work.

79
General Development / Re: How to run Magic Lantern into QEMU?!...
« on: January 19, 2019, 10:12:45 PM »
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.

Got Canon menu navigation working on M3:
Code: [Select]
CtrlSrv -> SflwWrpDrawStringWithinRect [0000,0222]: No Image.
CtrlSrv -> SflwWrpDrawStringWithinRect [-6962,0434]: Memory card locked
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: SETUP4
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: Certification Logo Display
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0219]: Copyright Info
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0271]: Clear all camera settings
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Wi-Fi Settings
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: PLAY1
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Transition Effect
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0115]: Fade
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: Index Effect
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0167]: On
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0219]: Scroll Display
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0219]: On
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0271]: Auto Rotate
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0271]: On
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0323]: Resume
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0323]: Last seen
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: PLAY2
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: Magnify (approx.)
CtrlSrv -> SflwWrpDrawStringWithinRect [0410,0167]: 2x
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Playback information display
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: SETUP1
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0219]: Format
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0271]: Video system
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0271]: PAL
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0323]: Electronic Level
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Create Folder
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0115]: Monthly
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: File Numbering
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0167]: Continuous
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: SETUP2
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: Power Saving
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0271]: Time Zone
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0323]: Date/Time
CtrlSrv -> SflwWrpDrawStringWithinRect [0410,0323]: '19.01.13 20:00
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0219]: LCD Brightness
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Eco Mode
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0115]: Off
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0375]: Language
CtrlSrv -> SflwWrpDrawStringWithinRect [0410,0375]: English
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: SETUP3
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: Hints & Tips
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0167]: Off
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Beep
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0115]: On
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0219]: Touch Operation
CtrlSrv -> SflwWrpDrawStringWithinRect [0412,0219]: Standard
CtrlSrv -> SflwWrpDrawStringWithinRect [0544,0060]: SETUP4
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0167]: Certification Logo Display
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0219]: Copyright Info
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0271]: Clear all camera settings
CtrlSrv -> SflwWrpDrawStringWithinRect [0036,0115]: Wi-Fi Settings
CtrlSrv -> SflwWrpDrawStringWithinRect [0000,0222]: No Image.

Any idea how to render these strings on QEMU VGA screen?

80
There is another solution without additional hardware. But you need to slow down your projector.

81
SX70HS

82
Canon released firmware update for EOS M50.

83
Camera-specific Development / Re: Canon 80D
« on: July 05, 2018, 08:46:26 PM »
According to this page
Quote
AD80334BBCZ
4 CHANNEL, 14 bit , 50MSPS AFETG+PPP

80D sensor has no ADC onboard?

84
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: June 03, 2018, 05:05:26 PM »
I am interested in the idea of using this camera as a 4K video camera.

slow image sensor * slow processor * slow storage device = bad idea  :)

85
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: May 10, 2018, 09:22:03 AM »
if you could PM me you rom files form a download link somewhere  ?
I interesting in decompiling it to do some investigations in the Jpeg routines .

If you don't want to wait you can download and decompile 1000D fw right now.
Or do you need exactly 450D?

86
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: May 09, 2018, 09:36:57 AM »
I don't have any code.
But AFAIK this program captures MJPEG frames via USB. I posted the resolution and framerate from video file recorded using this program. The average bitrate was ~30-35 Mbit/s. Maybe it's limited by USB.

87
Camera-specific Development / Re: Porting ML to XSi (450D)
« on: May 08, 2018, 10:14:16 PM »
Is there any other version which I can record video with?

EOS 450D has no video recording function out of the box. It's only theoretically possible to implement Motion JPEG(848x568px, ~22fps) recording without sound, but I abandoned the porting process in 2016 because of problems with the compiller...

89
I'm not sure what to explain. Any specific question?

You prepared M50_DUMP.FIR for M50 but today you "expect it to be PowerShot, too"
Why?

Sorry. I forgot to look at the date of your post.

90
Can you explain?

91
Unsure about M50, but I'd expect it to be PowerShot, too.

Has something changed since that post ?

92
General Development / Re: How to run Magic Lantern into QEMU?!...
« on: May 02, 2018, 10:40:12 AM »
- Twitter -> sticky post -> video
Should I go on?

Please recommend the exact version of linux you are using(have used) for it.

93
Reverse Engineering / Re: battery grip pins
« on: April 29, 2018, 05:49:09 PM »
Make sure you are using proper speed and signal levels.
FYI, diagnostic uart has 1.8v levels on Digic 6 Powershots.

94
EOS 450D



The background is black.

95
Reverse Engineering / Re: UHS-I / SD cards investigation
« on: April 11, 2018, 04:30:18 PM »
I did not found significant changes in the standard.
Look at the paragraph 3.9.3 of "Physical Layer Simplified Specification" (from v3.01 to v6.00). There are three host types.

96
Reverse Engineering / Re: UHS-I / SD cards investigation
« on: April 11, 2018, 02:06:19 PM »
good luck configuring Canon controller to use that. Brute-forcing the "known" registers didn't help.

Why do you think that camera controller has support of DDR mode?
In accordance with debugging messages inside D6 & D7 firmwares the fastest mode is SDR104 and there are no signs of DDR...

97
Camera-specific Development / Re: Canon 750D
« on: April 05, 2018, 11:44:08 PM »
did you have any luck with the new finsig_thumb2?
No. There was no luck with finsig_thumb2 & DSLR's firmware. But it found more than hundred functions in M3 firmware.

To find bitmap, raw, video buffers in RAM dump I recommend this tool.

98
Reverse Engineering / Re: UHS-I / SD cards investigation
« on: April 02, 2018, 12:18:17 PM »
Yay tricky one.
Ant123 states to switch power off if already in UHS mode. Maybe he can comment on it.

What can I comment? Just read CHDK forum from here.
On powershots the card is already in UHS mode while loading CHDK. So most cards can't be switched to UHS mode two times.
Maybe on DSLRs the card is not in UHS mode while loading autoexec.bin and you don't need to turn off SD power.

99
Camera-specific Development / Re: Canon 750D
« on: March 12, 2018, 09:30:33 PM »
We don't have a GUI at the moment as, as far as I understand it, as the memory address of the frame buffer is unknown.
Even if you will know this address you will not get Canon GUI emulation because it's rendered by graphical core GV550.

100
Camera-specific Development / Re: Canon EOS M3
« on: March 11, 2018, 09:09:48 AM »
Does Magic Lantern have a function to bypass this limit? If so, is it a good idea for my camera?

 :)

https://chdk.setepontos.com/index.php?topic=11316.msg136285#msg136285

Pages: 1 2 3 [4] 5 6 7