EOS M3 porting - page 52 - DryOS Development - CHDK Forum

EOS M3 porting

  • 615 Replies
  • 208997 Views
*

Offline srsa_4c

  • ******
  • 4054
Re: EOS M3 porting
« Reply #510 on: 27 / March / 2019, 18:09:27 »
Advertisements
Can anyone confirm that GRIDS works with the current build for the M3? Particularly in conjunction with an evf?
As far as I know, the m3 port has no support for the evf. That means, when evf or hdmi is in use, the CHDK overlay becomes unusable/unreadable.
Even if evf was supported, CHDK grids need to be adapted to the resolution of the output device, which work has obviously not been done either (the EVF has higher res than the LCD).

Re: EOS M3 porting
« Reply #511 on: 27 / March / 2019, 19:50:44 »
Thanks for the clarification

Re: EOS M3 porting
« Reply #512 on: 20 / May / 2019, 02:48:50 »
I don't have EVF-DC1 and this feature was not tested,
Yes I know that… I have one now  ;)

Even if evf was supported,

I did not expect the EVF to be supported by CHDK. However, CHDK seems to disturb the EVF. After loading, the top lines and one line in the middle are destroyed. If I open a CHDK menu, then almost half of the EVF is disturbed. Presumably some buffer will somehow be overwritten…

M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 2*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 Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #513 on: 20 / May / 2019, 11:50:48 »
@c_joerg

You can try modify display resolutions for EVF inside this function
Current display type can be found here


Re: EOS M3 porting
« Reply #514 on: 20 / May / 2019, 14:26:43 »
I think I got it so far...
Current display type can be found here
I first had to find the display type. Of course, it is difficult to find with debug if the display does not work. Well, I have to write a script which logs this value all the time.

You can try modify display resolutions for EVF inside this function
Then I have to put the right resolution (XGA, 1024x768) in update_screen_dimensions
After that I have to rebuild CHDK. I've never done that before, but it's time do it…
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 2*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 Ant

  • ****
  • 431
Re: EOS M3 porting
« Reply #515 on: 20 / May / 2019, 15:35:09 »
Of course, it is difficult to find with debug if the display does not work.

Use CHDKPTP.

Another way is creating RAM dump with delay to attach EVF. This also could be helpfull to find addresses and resolution of display buffers...

*

Offline reyalp

  • ******
  • 12208
Re: EOS M3 porting
« Reply #516 on: 20 / May / 2019, 16:13:33 »
FWIW, if you use
Code: [Select]
set gui_verbose=2
chdkptp will report the various buffer dimensions used in the console when they change.
Don't forget what the H stands for.

Re: EOS M3 porting
« Reply #517 on: 21 / May / 2019, 12:22:59 »
FWIW, if you use
Code: [Select]
set gui_verbose=2chdkptp will report the various buffer dimensions used in the console when they change.

Thanks for the hint.

For the size I get the following information.
Code: [Select]
vp.buffer_width:736->736
vp.visible_width:720->1024
vp.visible_height:480->684
 

However, I also get some errors. I attached the list.

Is “fb_type” the  “display type” which changes from 2 to 4?
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), 2*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

  • ******
  • 4054
Re: EOS M3 porting
« Reply #518 on: 21 / May / 2019, 13:12:40 »
Is “fb_type” the  “display type” which changes from 2 to 4?
I don't think so, but reyalp can correct me if I'm wrong.
You can get the displaytype by executing the following in chdkptp.
firmware 101a:
Code: [Select]
=return peek(0x9974)firmware 120f:
Code: [Select]
=return peek(0x9990)In other words, you peek the displaytype variable's address that you can find in stubs_min.S.

Can you get the displaytype in following cases (you can try rec & play mode, but they might be the same):
- LCD mode
- EVF mode
- HDMI mode

The framebuffer dimensions should be in sub_FC177FCA for 101a, but I see 640px widths there for types 0,3,4,5, which I find confusing.

*

Offline reyalp

  • ******
  • 12208
Re: EOS M3 porting
« Reply #519 on: 21 / May / 2019, 13:18:11 »
However, I also get some errors. I attached the list.
vp.buffer_width:736->736
vp.visible_width:720->1024

So the visible width updates correctly to 1024 (based on _GetVRAMHPixelsSize), but the buffer width (which would be set in update_screen_dimensions) does not.

Quote
Is “fb_type” the  “display type” which changes from 2 to 4?
No, that just indicates the format of the buffer. The vp is viewfinder, bm is bitmap / ui, bmo is the opacity channel for the bitmap. The types of a given buffer don't change at runtime.
Don't forget what the H stands for.

 

Related Topics