EOS M3 porting - page 69 - DryOS Development - CHDK Forum  
« previous next »
Pages: 1 ... 64 65 66 67 68 [69]   Go Down

EOS M3 porting

  • 689 Replies
  • 268344 Views
*

Offline reyalp

  • ******
  • 13230
Re: EOS M3 porting
« Reply #680 on: 29 / April / 2021, 19:33:25 »
Advertisements
Quote from: Ant on 29 / April / 2021, 18:09:43
Quote from: reyalp on 29 / April / 2021, 17:33:12
Does starting spytask (CHDK is started regardless) cause some problem in these cases?

Yes. The spytask causes "ASSERT!! KerSem.c Line 312"
Thanks. That's definitely worth avoiding. Interesting M10 doesn't have similar code, but it does have some other special stuff related to spytask start.

I've added a comment and put the romlog stuff under #ifdef BOOT_ROMLOG_SHORTCUT
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • ****
  • 471
  • Sorry, busy deleting test shots...
Re: EOS M3 porting
« Reply #681 on: 11 / May / 2021, 13:37:01 »
(mod edit: please try to make your posts easily readable)

Ahje,  my 1st hour with M3_121a.
Tried todays version & homebuilt #5879,5891, lenses 15-45 & 18-55.
Always "sd-card locked" only...  :-[
« Last Edit: 11 / May / 2021, 15:13:58 by reyalp »
Logged
All lifetime is a loan from eternity.
*

Offline Ant

  • ****
  • 485
Re: EOS M3 porting
« Reply #682 on: 12 / May / 2021, 05:46:28 »
@Caefix

Probably there is something wrong with your SD card.

Try to start CHDK using the firmware update method.(see attachment)

Add:
PS.FI2 updated
« Last Edit: 12 / May / 2021, 06:05:11 by Ant »
Logged
*

Offline Ant

  • ****
  • 485
Re: EOS M3 porting
« Reply #683 on: 12 / May / 2021, 07:18:42 »
@reyalp
How to check inside boot.c, was the OPT_FI2 option activated?
Logged
*

Offline Caefix

  • ****
  • 471
  • Sorry, busy deleting test shots...
Re: EOS M3 porting
« Reply #684 on: 12 / May / 2021, 10:45:00 »
 ::) SD-card was not bootable. Now it starts at once.
But there is no WF-update enrty in the <play>menues 1..4.
Logged
All lifetime is a loan from eternity.
*

Offline Ant

  • ****
  • 485
Re: EOS M3 porting
« Reply #685 on: 12 / May / 2021, 10:58:01 »
Quote from: Caefix on 12 / May / 2021, 10:45:00
But there is no WF-update enrty in the <play>menues 1..4.
FW update entry is not allowed in playback mode. Switch to rec mode.
Logged
*

Offline Caefix

  • ****
  • 471
  • Sorry, busy deleting test shots...
Re: EOS M3 porting
« Reply #686 on: 12 / May / 2021, 11:21:18 »
 :xmas Thanks, found it & it works.
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 13230
Re: EOS M3 porting
« Reply #687 on: 12 / May / 2021, 16:44:59 »
Quote from: Ant on 12 / May / 2021, 07:18:42
@reyalp
How to check inside boot.c, was the OPT_FI2 option activated?
If you mean whether the camera was booted from FI2, I'm not aware of anything really simple, though there's very likely lots of memory values that are different. The MMIO from the FI2 might be an option https://chdk.setepontos.com/index.php?topic=11316.msg136622#msg136622 (this doesn't appear to be implemented on M3, but is on M10)

Logged
Don't forget what the H stands for.
*

Offline Ant

  • ****
  • 485
Re: EOS M3 porting
« Reply #688 on: 12 / May / 2021, 18:12:27 »
Quote from: reyalp on 12 / May / 2021, 16:44:59
If you mean whether the camera was booted from FI2

I mean something like #ifdef OPT_FI2 inside boot.c for marking the code which used for building FI2 only.

It looks like the compiler options can't be accessed from boot.c

But anyway, there is a bigger problem with FI2: the firmware update can't start when the battery is low.
« Last Edit: 12 / May / 2021, 18:16:04 by Ant »
Logged
*

Offline reyalp

  • ******
  • 13230
Re: EOS M3 porting
« Reply #689 on: 12 / May / 2021, 19:42:49 »
Quote from: Ant on 12 / May / 2021, 18:12:27
I mean something like #ifdef OPT_FI2 inside boot.c for marking the code which used for building FI2 only.
It looks like the compiler options can't be accessed from boot.c
Defines can be accessed in boot.c like any other file, you just need to make sure -Dwhatever gets in the right CFLAGS. But that won't help you because DISKBOOT.BIN and PS.FI2 are the same binary, encoded differently after compile. I guess we could theoretically edit some magic bytes in the unencoded main.bin before encoding each one.

Quote
But anyway, there is a bigger problem with FI2: the firmware update can't start when the battery is low.
That does make sense for an actual firmware update ;)
Logged
Don't forget what the H stands for.
Pages: 1 ... 64 65 66 67 68 [69]   Go Up
« previous next »
 

Related Topics