Attached tarball of my platform/sx530hs fw:100c :
I enabled filewrite, exp_drv_task and movie_rec tasks.I disabled jogdial and liveview.
I also removed 'fix_writable_media_flag', as well as 'init_required_fw_features'. It was not clear from reading the port thread that those mods were actually required for the cam to run.. In basic tests, I saw no problems with power-On in play mode, using either button; and I had no problems with my (correctly prepared) bootable SD card.
I wasn't sure how to test exp_drv_task, so beware, it may have bugs.
Movie_rec was tested from CHDK scripts using cam/gui/buttons. Two small mp4's were made on the cam's SD card; ffplay identifies and plays them.
@blackhole, @reyalpThanks for the comments. I will try to re-enable what I had commented out, one element at a time. And will post 'svn diff' of changes instead of a tarball next time. It may take a few days..
I really encourage you to do one thing at a time. Start with a clean working copy, do just the filewrite stuff, post that as a standalone patch. Then do expdrv, post a patch for that, and so on.
I was just about to test the JogDial stuff using some chdkptp devutils "dpget" etc to see if it was working. I would read props, move the dial, compare props, etc. I thought this function was commented out in the orginal build, so I guess it's untested?
Umm.. I could take it all apart and submit one func at a time. I don't know svn that well (only enough to pull CHDK & chdkptp, otherwise a git user), so I will read about svn and see what's up.
You're right, it appears to be commented out in SVN. I had assumed it was previously enabled since you said you had disabled it, and missed that hook was commented out. I see comments I left when the port was added that there was conflict between the code-gen file and the provided boot.cI'm not clear what you expect to test with propcases. The jogdial hook in CHDK has two main purposes:1) Allow the use of the dial to navigate CHDK menus2) Prevent use of the dial in alt mode from being seen by the Canon firmware
As far as I can tell from the manual, this camera does not have a traditional jogdial (wheel combined with the directional keys) but does have a separate control dial. Treating the control dial as a jogdial in CHDK is probably worthwhile. This approach was used for the sx60 port.
Anything else I could test re: exp_drv_task or capt_seq generally, let me know.
After 15 consecutive exposures of 64 seconds, the battery temperature increases by 5 degrees and stays at that level the next 5 exposures.
Can you please test extra long (and extra short) exposures, using vanilla, unaltered svn? I had the impression that at least extra long ones are already working.
If exposure times outside the range available from the Canon UI are working, implementing exp_drv_task is rather pointless.
Started by gvandyk
Started by Jez
General Help and Assistance on using CHDK stable releases
Started by ProfHankD
« 1 2 »
Started by eaglesong
Started by duenyas
General Discussion and Assistance