EOS M100 porting - page 9 - DryOS Development - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 ... 4 5 6 7 8 [9] 10   Go Down

EOS M100 porting

  • 96 Replies
  • 11315 Views
*

Offline Caefix

  • ****
  • 428
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #80 on: 11 / November / 2020, 15:18:43 »
Advertisements
Quote from: Caefix on 04 / November / 2020, 12:46:00
A lovely lens is 7artisans 35 1:1.2. Looks nostalgic, boots fine.
Could we have focus magnifier with manual lenses?
  :( Well, now I have another nice magnifier, but due to missing contacts it isn´t recognized as an attached lens.
Is there a CHDK-way to make cam shooting without any lens?
Logged
All lifetime is a loan from eternity.
*

Offline srsa_4c

  • ******
  • 4396
Re: EOS M100 porting
« Reply #81 on: 11 / November / 2020, 16:44:23 »
Quote from: Caefix on 11 / November / 2020, 15:18:43
Is there a CHDK-way to make cam shooting without any lens?
No and there is no need. Check out the C.Fn section of the Canon menu (only available in rec mode).
Logged
*

Offline c_joerg

  • *****
  • 1066
Re: EOS M100 porting
« Reply #82 on: 12 / November / 2020, 11:54:01 »
Quote from: srsa_4c on 11 / November / 2020, 13:47:11
0xE03E644F for firmware 100a.
Thanks, power down works…
But the script didn’t shoot after power down.
I have to set
Code: [Select]
set_record(true)before I shoot. On my M3, it is not necessary.
Is this something with the port or is the M3 different in the way to shoot?

Is there any reason, why cam comes back in playback mode?
Code: [Select]
-- schedule power-on event, '2' is for playback mode
 call_func_ptr(func,2,delay*1000)
Logged
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd
*

Offline srsa_4c

  • ******
  • 4396
Re: EOS M100 porting
« Reply #83 on: 12 / November / 2020, 12:04:01 »
Quote from: c_joerg on 12 / November / 2020, 11:54:01
Is there any reason, why cam comes back in playback mode?
Code: [Select]
-- schedule power-on event, '2' is for playback mode
 call_func_ptr(func,2,delay*1000)
The answer is in the comment. If you replace 2 with 1, the cam should restart in rec mode. Those constants are the same for M100 and M3 (and probably the rest).
Logged
*

Offline Caefix

  • ****
  • 428
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #84 on: 12 / November / 2020, 12:23:03 »
Quote from: c_joerg on 04 / November / 2020, 13:30:44
Quote from: Caefix on 04 / November / 2020, 12:46:00
??? Seen in other EOS-M topics,too: some lenses avoid to write their dist_values at the expected addresses,
even Canon EF28-90 &EF70-210.

Older lenses probably do not offer this interface...

EF35-80(II) & EF35-80-Ultrasonic, EF28-80(IV)-Ultrasonic & Cosina AF 100-400 same,
fine dist_values from EF70-300-IS-USM.
Seems, that we need Canon EF not without STM or USM.  :-[
Don´t know the most important letter here, but Tamron 18-270 Di2 VC PZD is all fine, too.
Edit:
Can EFS18-55: Don´t know, AF Hardware faulty,random&blocking, always fdl=25 and fdu=25.

Edit2: Canon´s EFS 18-55 (II), EFS 18-55 IS (II)  & EFS 18-200 IS have fine returns.  ::)
Now it seems, that lens needs image stabilizer...
« Last Edit: 22 / April / 2021, 12:02:54 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline c_joerg

  • *****
  • 1066
Re: EOS M100 porting
« Reply #85 on: 12 / November / 2020, 13:31:09 »
Quote from: Caefix on 12 / November / 2020, 12:23:03
but Tamron 18-270 Di2 VC PZD is all fine,
My friend has the lens. Image quality is really bad…

Quote from: srsa_4c on 12 / November / 2020, 12:04:01
The answer is in the comment. If you replace 2 with 1, the cam should restart in rec mode. Those constants are the same for M100 and M3 (and probably the rest).
Yes of course. So far, I have never paid attention to this parameter and asked myself why it is set to playback mode.
With the M3 the shoot seems to work from playback mode. If that wasn't the case, then I would have thought about the parameter more.

I changed now PowerDown.lua record mode. It looks like, that I have now less time jitter.
Logged
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd
*

Offline Caefix

  • ****
  • 428
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #86 on: 25 / November / 2020, 11:01:19 »
 :DHere I used the NPP++ Compare plugin to get M100.100a compiled with r5637.
Edit : Removed, probably as outdated as conf.c in the last 'testzip'.
All gccs seem to work, if this files are deleted before dropping into trunk.

&& Don´t touch thjs switch here, no, don´t!!!    [ ]>:haha
// CHDK Compiler GUI switch, doesn´t match all cams.
#ifdef OPT_EXMEM_MALLOC
« Last Edit: 25 / December / 2020, 14:17:44 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline c_joerg

  • *****
  • 1066
Re: EOS M100 porting
« Reply #87 on: 29 / November / 2020, 06:22:15 »
Not that important to me, but maybe this information is interesting.
Bracketing (TV) and Custom Timer:
If TV is > 1s, then it doesn’t work all the time. Sometimes it’s start’s only once after restart.
I didn’t see the problem with TV < 1s.

Logged
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd
*

Offline Caefix

  • ****
  • 428
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #88 on: 19 / February / 2021, 15:16:13 »
Quote from: hokage on 19 / February / 2021, 05:04:02
Quote from: srsa_4c on 18 / February / 2021, 16:12:44
Quote from: hokage on 18 / February / 2021, 06:33:58
Also EOS M100 with Firmware 1.2.1
If there's no typo here, I'd like to see a dump of that firmware. The latest official upgrade is 1.1.0 (110b), from October last year.

I'm (slowly) working on a 110b port, but I don't know when it will be ready. The published source only works on the original 100a firmware (downgrading to that is not possible).

I have another M100 camera with V.1.0.0 also, I will give it a go.
:)  The latest diskboot.bin I got working today is 5670.
(My next reserve 5678 failed,
(since then one green LED left, after any power on ~ every ~15secs, 32Gb Sandisk ultra).

But everything seems to work fine as usual with my latest modules (5779)
(Latest Romlog: Occured Time  2020:11:17 18:18:46 : Exception!! [data abort] (5628))
No time need to look deeper in code next days, so for first pictures before official solution ...
Edit: (M100_100a)
Just to have a full setup available for some extended fun with the cam.
« Last Edit: 01 / April / 2021, 14:47:17 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline Caefix

  • ****
  • 428
  • Sorry, busy deleting test shots...
Re: EOS M100 porting
« Reply #89 on: 02 / March / 2021, 14:24:26 »
 :-[ How to avoid...
Quote
d:/hostluaportable/chdk-shell/trunk/gcc1021_host920/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/bin/ld.exe: ../../../../platform/m100/libplatform.a(wrappers.o): in function `GetFreeCardSpaceKb':
wrappers.c:(.text+0x308): undefined reference to `live_free_cluster_count'
collect2.exe: error: ld returned 1 exit status
?
Logged
All lifetime is a loan from eternity.
Pages: 1 ... 4 5 6 7 8 [9] 10   Go Up
« previous next »
 

Related Topics