Ixus180_elph190 porting thread - page 3 - DryOS Development - CHDK Forum supplierdeeply

Ixus180_elph190 porting thread

  • 34 Replies
  • 1702 Views
*

Online blackhole

  • *****
  • 928
  • A590IS 101b
    • Planetary astrophotography
Re: Ixus180_elph190 porting thread
« Reply #20 on: 10 / May / 2023, 02:33:17 »
Advertisements
@reyalp
What's wrong with this syntax:
Code: [Select]
path\to\tools>make-fw-crc.py ixus180_elph190 100a -o ixus180_elph190100a.crcAs far as I remember, I was able to create crc on that  way before. After reinstalling Python311 I keep getting the error: the following arguments are required: platform, sub
PRIMARY.BIN is usually in the platform/sub/100a folder.
You should be able to use the make command
Code: [Select]
make PLATFORM=ixus180_elph190 PLATFORMSUB=100a rebuild-firmware-crc
You can find the command that ends up being used for that in the top level Makefile
It looks like a similar problem: - Cannot openmake: *** [rebuild-firmware-crc] Error 1
I looked at Environment Variables and everything is fine there now, but the problem still exists.

*

Offline reyalp

  • ******
  • 14039
Re: Ixus180_elph190 porting thread
« Reply #21 on: 10 / May / 2023, 13:42:34 »
It looks like a similar problem: - Cannot openmake: *** [rebuild-firmware-crc] Error 1
I looked at Environment Variables and everything is fine there now, but the problem still exists.
This is strange, the "the following arguments are required: platform, sub" should mean argparse didn't see the platform and sub args somehow  ???

You are on windows, correct? If so, what python distribution are you using (conda, msys2...) ?

Both the command line and the makefile versions work for me with msys2 python 3.10.8 (not saying you should change, just a data point). I don't see anything obvious on the argparser manual page that's changed in 3.11
Don't forget what the H stands for.

*

Online blackhole

  • *****
  • 928
  • A590IS 101b
    • Planetary astrophotography
Re: Ixus180_elph190 porting thread
« Reply #22 on: 10 / May / 2023, 15:57:59 »

This is strange, the "the following arguments are required: platform, sub" should mean argparse didn't see the platform and sub args somehow  ???

You are on windows, correct? If so, what python distribution are you using (conda, msys2...) ?

Both the command line and the makefile versions work for me with msys2 python 3.10.8 (not saying you should change, just a data point). I don't see anything obvious on the argparser manual page that's changed in 3.11
Yes, Windows 10 22h2.
The distribution is standard CPython, downloaded from python.org
I just tried version 3.10.8 and the same problem persists. :(

*

Online blackhole

  • *****
  • 928
  • A590IS 101b
    • Planetary astrophotography
Re: Ixus180_elph190 porting thread
« Reply #23 on: 10 / May / 2023, 16:50:38 »
I can't find a solution for this problem with python script on windows, but I can create crc using linux under VM. :D
The output file is attached.


*

Online blackhole

  • *****
  • 928
  • A590IS 101b
    • Planetary astrophotography
Re: Ixus180_elph190 porting thread
« Reply #24 on: 10 / May / 2023, 17:47:00 »
@Caefix
A test version with crc verification is attached.
You can check if it works by going to Miscellaneous stuff>>Tools>>Checksum ROM

*

Offline reyalp

  • ******
  • 14039
Re: Ixus180_elph190 porting thread
« Reply #25 on: 10 / May / 2023, 18:01:09 »
I can't find a solution for this problem with python script on windows, but I can create crc using linux under VM. :D
The output file is attached.
Matches what I get.

FWIW, it's totally fine to submit the patch without, I only mentioned in the sx600 post to be clear about how my commit differed from the posted patch, not a complaint.

That said, if you can enable the CRC check in your test build, it would get tested before we add the port, which is good.

I'll try to figure out what's going on with argparse later, good chance I've made some silly python mistake.
Don't forget what the H stands for.

*

Online blackhole

  • *****
  • 928
  • A590IS 101b
    • Planetary astrophotography
Re: Ixus180_elph190 porting thread
« Reply #26 on: 10 / May / 2023, 18:28:59 »
FWIW, it's totally fine to submit the patch without, I only mentioned in the sx600 post to be clear about how my commit differed from the posted patch, not a complaint.

I'll try to figure out what's going on with argparse later, good chance I've made some silly python mistake.
No problem, I didn't take it as a complaint, I just tackled it because I wanted to figure out why it wasn't working for me anymore.
Last year on Windows 10 21h1 everything worked fine, but I had some older distribution of Python. Otherwise, I noticed that the python installer does not set user variables properly and does not add .py to PATHEXT.

*

Offline Caefix

  • *****
  • 943
  • Sorry, busy deleting test shots...
Re: Ixus180_elph190 porting thread
« Reply #27 on: 11 / May / 2023, 11:38:26 »
@Caefix
A test version with crc verification is attached.
You can check if it works by going to Miscellaneous stuff>>Tools>>Checksum ROM
:xmas YES!
All lifetime is a loan from eternity.


*

Offline reyalp

  • ******
  • 14039
Re: Ixus180_elph190 porting thread
« Reply #28 on: 12 / May / 2023, 01:33:01 »
Adding this port, I noticed stubs_entry has
Code: [Select]
// Current modemap entry not found in firmware - MODE_SMART_SHUTTER       33333
// Current modemap entry not found in firmware - MODE_HIGHSPEED_BURST     32778
If those don't exist in the canon UI (which I suspect they don't) they should be removed from shooting.c

Other questions:
- Has startup behavior been checked?  That is powering on with either play or power (or wifi if it can power on the cam) starts in play mode, while holding power starts in rec?
- Has PTP live view been checked?
- have viewport framebuffer counts been checked with a OPT_VIEWPORT_DEBUG build? (background https://chdk.setepontos.com/index.php?topic=14022.msg143092#msg143092, patch is not needed in current trunk)
Don't forget what the H stands for.

*

Offline Caefix

  • *****
  • 943
  • Sorry, busy deleting test shots...
Re: Ixus180_elph190 porting thread
« Reply #29 on: 12 / May / 2023, 09:42:18 »
...  8)
- have viewport framebuffer counts been checked with a OPT_VIEWPORT_DEBUG build? (background https://chdk.setepontos.com/index.php?topic=14022.msg143092#msg143092, patch is not needed in current trunk)
:) Seems no need for debug-build.

Edit: But done, always 0..3 buffers.  :-*
« Last Edit: 12 / May / 2023, 10:29:28 by Caefix »
All lifetime is a loan from eternity.

 

Related Topics