Quote from: frk203 on 21 / March / 2016, 16:26:01i know that first i must create a dump file (there is one already listed on the forums but its for sx520 firmware v.1.00b so im assuming i need to create a new one for v.1.00c)If you are sure your cam has the 1.00c firmware, you don't need to upload a new dump. If you're not sure, make a new dump and search for the "GM1." string in it with a hex editor - there are other methods for determining the fw version of course.The sx530 port (the official source) can't currently be compiled, but his situation will likely change shortly. The port also has an unsolved problem: many SD cards seem to give trouble when CHDK is running - we don't currently have an idea how to solve this.If you also have the 100c firmware making the port will consist of:- making a new row in camera_list.csv for the sx520hs- copying loader/sx530hs to loader/sx520hs (with all its files)- copying platform/sx530hs to platform/sx520hs (with all files)under platform/sx520hs- fixing platform_camera.h (CAM_DNG_LENS_INFO), focus_len_table stuff in main.c (it's wrong for sx530 too)under platform/sx520hs/sub/100c- fixing PLATFORMID in makefile.incHope I didn't forget something.If it turns out that you have a fw version other than 100c, making a port will require some research (for files in platform/sx520hs/sub/{version})
i know that first i must create a dump file (there is one already listed on the forums but its for sx520 firmware v.1.00b so im assuming i need to create a new one for v.1.00c)
Thanks for all the help,i have done all the steps specified and the ones in the last reply, i booted the camera using bootable SD Card method, it loaded CHDK but right after it gave and error that stated that its "missing modules"?! (the camera still works and chdk is loaded and i can access it, just the missing module error stays on top)do i have to do any changes to the modules folder/files?
also I am getting the memory card error when trying to capture pictures, i know that was an unsolved issue previously, but i was wondering could having the card in lock mode be causing that issue? is there a way to start chdk without having the SD card in lock mode?
Thanks for all the help,i have done all the steps specified and the ones in the last reply, i booted the camera using bootable SD Card method, it loaded CHDK but right after it gave and error that stated that its "missing modules"?! (the camera still works and chdk is loaded and i can access it, just the missing module error stays on top)
here is the link to google drive with all the files that i have on the sx520hs:https://drive.google.com/folderview?id=0BzbV7TkC9ia4TjJfMTQtdmtDYUU&usp=sharing
is there a way to start chdk without having the SD card in lock mode?
all sd cards work over firmware update(thanks to blackhole)
Are you saying you do not have problems with your SD cards when you boot with firmware update? Do the same cards have problems when booting with diskboot.bin and locked card?
QuoteAre you saying you do not have problems with your SD cards when you boot with firmware update? Do the same cards have problems when booting with diskboot.bin and locked card?Yes it happens, I do not know whether it is the case, with all the cards that have a problem with diskboot.bin file, but the cards we've tried so far work well with ps.fi2 file.
I'm wiped patch from my reply # 68, with the changes in boot.c, cameras starting with firmware update method in wireless AP mode.
I'd like to note that several other hw (and other?) flags are ignored by the simplified method above, some of which might be important (might influence the card issue for example)?See sub_ff02bbc0 and sub_ff073c68 for details (fw 100c).
I see, I was under the impression (see reply #72) that the cards also fail with firmware update boot.
I might have asked this earlier, but: when you get card error in diskboot mode, do file operations fail afterwards? For example, can you launch stuff like the file browser?It might be possible that one of the boot flags (that go in (0x2cf4+0x8) ) is related to the card issue. Other guess is that the camera's card protect sense switch is influencing more than one firmware variable, and only one of those is masked in kbd.c
Quote from: srsa_4c on 18 / March / 2016, 01:03:06I'd like to note that several other hw (and other?) flags are ignored by the simplified method above, some of which might be important (might influence the card issue for example)?See sub_ff02bbc0 and sub_ff073c68 for details (fw 100c).If you need help with this, I can come up with more concrete suggestions.
Started by gvandyk CHDK Releases
Started by Jez General Help and Assistance on using CHDK stable releases
Started by ProfHankD « 1 2 » Feature Requests
Started by eaglesong General Chat
Started by duenyas General Discussion and Assistance
