EOS M3 porting - page 16 - DryOS Development - CHDK Forum supplierdeeply

EOS M3 porting

  • 746 Replies
  • 391140 Views
*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #150 on: 16 / September / 2016, 11:06:58 »
Advertisements
But this function does not return focal length. It prints value as a string to somewhere like EventShell buffer(0x00051520).

UPD. The mistake was found in the first call. There should be "bl   sub_fc43cd97\n"
You don't need to set the thumb bit for BL instruction labels when you write asm code.

Due to the calling convention, a function call destroys the content of registers r0..r3.

I'd try this:
Code: [Select]
movs  r0, #0
push  {r4, r5, lr}  // modified
bl    loc_fc43cd96
mov   r4, r0
ldr   r0, [r0, #0x24]
movs  r1, #0xa0
strb  r1, [r0, #0]
movs  r1, #0
ldr   r0, [r4, #0x24]
strb  r1, [r0, #1]
ldr   r0, [r4, #0x24]
strb  r1, [r0, #2]
movs  r1, #3
ldr   r0, [r4, #0x20]
str   r1, [r0, #0]
mov   r0, r4
bl    loc_fc2f2c0e
ldr   r0, [r4, #0x28]
ldrb  r1, [r0, #1]
ldrb  r0, [r0, #2]
add.w r0, r0, r1, lsl #8
uxth  r5, r0                                           // modified
// ldr   r0, =0xfc43e274   ; *".Focal Length = %ld mm" // -
// bl    loc_fc37fd9c                                  // -
mov   r0, r4
bl    loc_fc43cdf4
// movs  r0, #0                                        // -
mov   r0, r5                                           // +
pop   {r4, r5, pc}  // modified

*

Offline a1ex

  • *****
  • 671
  • ML dev
Re: EOS M3 porting
« Reply #151 on: 25 / September / 2016, 18:09:33 »
QEMU is now able to load DISKBOOT.BIN on the M3 from the SD card image :)

Excerpt from the startup log with Ant's test binary.
Code: [Select]
StartDiskboot
Start Program on RAM

DRYOS version 2.3, release #0055+p6
Copyright (C) 1997-2013 by CANON Inc.

Hello world

Assert: File Battery.c Line 1468

TODO:
- find out how to run Canon Basic scripts
- figure out how to show the GUI

Ant, do you still have the voltmeter example you posted on ML forum a while ago?

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #152 on: 25 / September / 2016, 18:52:31 »
To run Canon Basic scripts you need to press SET from playback mode.
How to do it without Canon's GUI?
« Last Edit: 25 / September / 2016, 18:55:05 by Ant »

Re: EOS M3 porting
« Reply #153 on: 26 / September / 2016, 15:53:23 »
The address of 'movie_status' seems to be incorrect, does anyone know the correct value ?
 
Also, how can I disassemble the movie task without using ADA ?




Thanks.
Zweistein
« Last Edit: 26 / September / 2016, 16:12:39 by zweistein68 »


*

Offline reyalp

  • ******
  • 14079
Re: EOS M3 porting
« Reply #154 on: 26 / September / 2016, 16:30:17 »
The address of 'movie_status' seems to be incorrect, does anyone know the correct value ?
So far, an equivalent of the movie_status on previous digic has not been found for digic 6. In this case simple_move_status should be used instead. See https://chdk.setepontos.com/index.php?topic=11316.60

Quote
Also, how can I disassemble the movie task without using ADA ?
You can use the capdis tool in the CHDK trunk tools directory. See https://chdk.setepontos.com/index.php?topic=11316.60 for some examples. You can use it to either disassemble the whole ROM (as shown there) or individual functions.

There is also a perl+objdump based script: http://chdk.wikia.com/wiki/User:Srsa_4c/GPL:disassemblev7.pl

Neither of these has the features of something like IDA, but it is possible to make a port using them.
Don't forget what the H stands for.

Re: EOS M3 porting
« Reply #155 on: 29 / September / 2016, 13:48:31 »
Thanks for that.
For now I will use a FAKEDEF for movie_status.


Zweistein

Re: EOS M3 porting
« Reply #156 on: 29 / September / 2016, 13:49:33 »
another question: Does focus override work on this camera ?


thanks
Zweistein

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #157 on: 29 / September / 2016, 14:31:59 »
Not yet...


Re: EOS M3 porting
« Reply #158 on: 30 / October / 2016, 18:47:09 »
I would love if the "video quality control" would work.
Not working for me at the moment.

Re: EOS M3 porting
« Reply #159 on: 11 / November / 2016, 15:45:43 »
Hello folks, recent M3 owner here interested in CHDK. I've not really messed around with this stuff before, but STICK is reading my firmware at 110a. Am I out of luck?

To clarify, I am most interested in the GRIDS feature. I'd like to upload custom framelines if possible.

Thanks for your time and patience. I've tried to do as much homework as possible but clearly I have a lot of work to do.
« Last Edit: 11 / November / 2016, 15:51:00 by ness0013 »

 

Related Topics