G7 X porting thread - page 17 - DryOS Development - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 12 13 14 15 16 [17]   Go Down

G7 X porting thread

  • 167 Replies
  • 136811 Views
*

Offline pigeonhill

  • *****
  • 1131
Re: G7 X porting thread
« Reply #160 on: 25 / January / 2020, 02:44:41 »
Advertisements
@reyalp

Great, I'll give it a go today. Luckily I don't like people in my images  :D

First I need to get my new G5X up and running.

At the moment, the bootable card approach doesn't seem to work for me, ie I use firmware update everytime.

4Gb Fat32 card: have tried EOSCard, But not STICK as no option to just switch on boot (that I can find).



Logged
*

Offline c_joerg

  • *****
  • 1240
Re: G7 X porting thread
« Reply #161 on: 25 / January / 2020, 03:38:24 »
Quote from: pigeonhill on 25 / January / 2020, 02:44:41
At the moment, the bootable card approach doesn't seem to work for me, ie I use firmware update everytime.

4Gb Fat32 card: have tried EOSCard, But not STICK as no option to just switch on boot (that I can find).

Maybe that problem...
https://chdk.setepontos.com/index.php?topic=13704.msg139579#msg139579
Logged
M100 100a, M3 121a, 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 pigeonhill

  • *****
  • 1131
Re: G7 X porting thread
« Reply #162 on: 25 / January / 2020, 04:18:32 »
@c_joerg

Joerg thanks for that, used HxD to write BOOTDISK to the correct location  ;)

But still G5X doesn't boot CHDK, just says card locked.

Strange, but I'll carry on investigating ???
Logged
*

Offline c_joerg

  • *****
  • 1240
Re: G7 X porting thread
« Reply #163 on: 25 / January / 2020, 05:00:05 »
Quote from: pigeonhill on 25 / January / 2020, 04:18:32
But still G5X doesn't boot CHDK, just says card locked.

Strange, but I'll carry on investigating ???

But same Card works with G7x?
Logged
M100 100a, M3 121a, 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 pigeonhill

  • *****
  • 1131
Re: G7 X porting thread
« Reply #164 on: 25 / January / 2020, 07:59:26 »
@reyalp

Quote
OK, here's a test build with philmoz flicker workaround. I tried it on mine but I'm not sure it helped much.

No discernible difference as far as I can tell. I don't have face mode on.

Cheers

Garry
Logged
*

Offline reyalp

  • ******
  • 13882
Re: G7 X porting thread
« Reply #165 on: 25 / January / 2020, 16:35:03 »
Quote from: pigeonhill on 25 / January / 2020, 07:59:26
No discernible difference as far as I can tell. I don't have face mode on.
Does the level of flickering seem similar to what you see on g5x?

Another thing on g7x that causes a lot of flickering is the electronic level (edit: if the level is changing).
Logged
Don't forget what the H stands for.
*

Offline pigeonhill

  • *****
  • 1131
Re: G7 X porting thread
« Reply #166 on: 25 / January / 2020, 17:04:52 »
@reyalp


I have to say they look similar.


My DOFIC script is constantly updating the console, but I’m in the process of changing it so it only prints to the console if something changes.


But I don’t think that will help, as with the script off, the CHDK DoF area also flashes.


At the moment the ‘flashing’ seems about 2 per sec. but that’s a guess.
Logged
*

Offline reyalp

  • ******
  • 13882
Re: G7 X porting thread
« Reply #167 on: 06 / March / 2023, 22:20:42 »
In trunk r6225, I added multipartition support, requested by Mlapse in  https://chdk.setepontos.com/index.php?topic=14717.0

This allows FAT16 boot partition with exFAT for data, which is reported to give better performance with large cards.

Note
* The boot partition must be FAT16, not FAT32
* You cannot use CHDK (or the Canon MakeBootDisk eventproc) to make it bootable, you must use an external tool like stick, chimp or dd to write the BOOTDISK string

I tested 100d, but 100b and 100c are not tested. They should be fine since the relevant code is identical in 100c and only differs by function addresses in 100b, but if anyone owners of those subs want to confirm r6225 still works, that would be appreciated.
Logged
Don't forget what the H stands for.
Pages: 1 ... 12 13 14 15 16 [17]   Go Up
« previous next »
 

Related Topics