I have completed my SD970 boot sequence, led, spytask and can connect by CHDKPTP which is not bad. I plan to implement the keymap next so that I can enter ALT mode etc. but guess I need a pointer. If I can get that OSD for experimentally finding the kbd.c values by pressing the buttons onto the camera by CHDKPTP that would be great, any alternative method by CHDKPTP would be as great.Originally I thought I'd get the OSD that shows the values when you press a key by uncommenting Code: [Select]gui_draw_debug_vals_osd(); from core/gui.c. The porting wikia page instructs "you can force it to be always visible by uncommenting the commented call to gui_draw_debug_vals_osd() in core/gui.c and removing the if at the beginning of that function." I did not figure out what if that would be - is that hint deprecated? I did not get it to work.Thanks :-)
gui_draw_debug_vals_osd();
Quote from: koshy on 10 / January / 2020, 12:44:35I have completed my SD970 boot sequence, led, spytask and can connect by CHDKPTP which is not bad. Nice work.QuoteI plan to implement the keymap next so that I can enter ALT mode etc. but guess I need a pointer […]My preferred method to do this is with chdkptp rmem, like I described in https://chdk.setepontos.com/index.php?topic=13355.msg142207#msg142207The camera ignores keys when USB is connected (except power/play) and you can read the text on your PC instead of the camera screen.QuoteThe porting wikia page instructs […] and removing the if at the beginning of that function." I did not figure out what if that would be - is that hint deprecated? I did not get it to work.It refers to "if (conf.debug_misc_vals_show)" which isn't quite at the beginning any more. This hint is just so you can turn it on the display if your keyboard is so messed up you can't navigate to the debug menu. For dryos cameras, the key definitions in stubs_entry.S from the sig finder should normally get most of the basics right.srsa_4c also made a phys bit display that's really nice: https://chdk.setepontos.com/index.php?topic=13426.msg142287#msg142287
I have completed my SD970 boot sequence, led, spytask and can connect by CHDKPTP which is not bad.
I plan to implement the keymap next so that I can enter ALT mode etc. but guess I need a pointer […]
The porting wikia page instructs […] and removing the if at the beginning of that function." I did not figure out what if that would be - is that hint deprecated? I did not get it to work.
Thank you so much, that is plenty to work with.
I guess I made ample progress with my first actual port. Keybord is now implemented, custom palette, too. Raw shooting is implemented, ActiveArea set, ColorMatrix determined, Exposures longer 60 seconds tested so it is all getting to a point where I'm wrestling with the smaller things.I'm sort of puzzled by the Jogdial stuff. Here is where I'm at:Code: [Select]// ##TODO## SD970// 0x874 and 0x875 values may be camera model dependent, search them in firmware (in pair with RotateJogDialRight(Left)) strings.// sd970: table "PrintMenu" @ ffb8060e, fw 1.00Avoid JogDial_CW(void){ _PostLogicalEventForNotPowerType(0x874, 1); // sd970: RotateJogDialRight (in table "PrintMenu" @ ffb81b5a, fw 1.00A)}void JogDial_CCW(void){ _PostLogicalEventForNotPowerType(0x875, 1); // sd970: RotateJogDialLeft (in table "PrintMenu" @ ffb81ad3, fw 1.00A)}Other ports mentioned the entries in the table so I looked them up but I find no references to those hex addresses in Ghidra and looking through all functions that are listed to use the table "PrintMenu" did not give any clues. 0x874 and 0x875 values don't seem to work, can you think of what needs to be done to find the correct values?The other thing I thought I'd better ask about is the today preferred way to fill the tables in shooting.c with data. These tables:Code: [Select]aperture_sizes_tableshutter_speeds_tableiso_tablemodemapAfter that I'll look at the CHDKPTP things which don't seem to be working fully in the reference port and zebra which also does not work if comments are correct. I guess for Zebra it's just getting the sizes right, by now I get a zebra but expanded in height. I'll figure it out I hope...
// ##TODO## SD970// 0x874 and 0x875 values may be camera model dependent, search them in firmware (in pair with RotateJogDialRight(Left)) strings.// sd970: table "PrintMenu" @ ffb8060e, fw 1.00Avoid JogDial_CW(void){ _PostLogicalEventForNotPowerType(0x874, 1); // sd970: RotateJogDialRight (in table "PrintMenu" @ ffb81b5a, fw 1.00A)}void JogDial_CCW(void){ _PostLogicalEventForNotPowerType(0x875, 1); // sd970: RotateJogDialLeft (in table "PrintMenu" @ ffb81ad3, fw 1.00A)}
aperture_sizes_tableshutter_speeds_tableiso_tablemodemap
Quote from: koshy on 11 / January / 2020, 19:09:01I guess I made ample progress with my first actual port. Keybord is now implemented, custom palette, too. Raw shooting is implemented, ActiveArea set, ColorMatrix and ForwardMatrix determined by calibration using actual RAW imagery,If you can post how you did the calibration, that could be quite helpful.QuoteI'm sort of puzzled by the Jogdial stuff. You can dump the levent table with find_levent in the tools directoryCode: [Select]make find_levent.exe./find_levent.exe -full ../../dumps/ixus990_sd970/sub/100a/PRIMARY.BIN 0xff810000 > ixus990_sd970-levent.txtThe IDs appear to be correct:Code: [Select]0x0874, 2164, RotateJogDialRight, 20x0875, 2165, RotateJogDialLeft, 2It's possible the parameter needs to be 2 rather than one, some existing ports are that way.Note that these functions are for sending jogdial inputs from script with wheel_left and wheel_right. Using the jogdial in CHDK menus is separate code, usually in kbd.cQuotepreferred way to fill the tables in shooting.c with data So, this is a kind of broken neglected area that still needs to have something in it. Assuming this cam ND filter only (looks like it from the manual) and CAM_DRAW_EXPOSITION isn't defined, I don't think it's really used at all, although it still needs to exist and probably have at least one entry.On cameras that don't have ton of zoom steps, I've used the PROPCASE_AV value at each zoom step, with string from the canon UI, repeated with ND in (forced by a bright light source). But I think you could get away with just putting in the first value.shutter_speeds_table can just be copied from another port with the same shutter speed range. ixus100 looks like it should do.iso_table can be copied from another camera with the same iso range, probably ixus100 again. If there isn't a "high" auto setting, you can remove that. modemap This one is actually good to get right. Watch the PROPCASE_SHOOTING_MODE value and go through all the available shooting modes. For a camera of that vintage, there should already be an appropriate MODE_ enum value. If you can find some that are listed in stubs_entry, they are usually a setting within another mode, or somewhere else in the menu. E.g. "face self timer" and "wink self timer" might both be under one mode setting, but have different propcas values.QuoteI guess for Zebra it's just getting the sizes right Screenshots might be helpful. It looks like ixus100 didn't have the live view functions fully implemented. We can probably fix that.
I guess I made ample progress with my first actual port. Keybord is now implemented, custom palette, too. Raw shooting is implemented, ActiveArea set, ColorMatrix and ForwardMatrix determined by calibration using actual RAW imagery,
I'm sort of puzzled by the Jogdial stuff.
make find_levent.exe./find_levent.exe -full ../../dumps/ixus990_sd970/sub/100a/PRIMARY.BIN 0xff810000 > ixus990_sd970-levent.txt
0x0874, 2164, RotateJogDialRight, 20x0875, 2165, RotateJogDialLeft, 2
preferred way to fill the tables in shooting.c with data
I guess for Zebra it's just getting the sizes right
- most importantly to me at this time: I do not get the Debug entry on the Misc. CHDK menu
but again no debug menu no ROMLOG...
!require'extras/devutil'.init_cli()dromlog
Nice work. Doing your first original port is fun isn't it?
Quote from: koshy on 12 / January / 2020, 19:12:12- most importantly to me at this time: I do not get the Debug entry on the Misc. CHDK menuDo you have OPT_DEBUGGING turned off in buildconf.inc / localbuildconf.inc?
Quote but again no debug menu no ROMLOG...You can get a romlog using chdkptp devutilCode: [Select]!require'extras/devutil'.init_cli()dromlog
Any help with reading what the ROMLOG points to would be quite welcome.
Exception!! Vector 0x0AOccured Time 2009:02:01 23:13:37Task ID: -1Task name: <ISR>
Exc Registers:0x0034DFC00x000000000x000000000x000000000x002F27380x000000B00x19A147800x000000010x3B9ACA000x00001A340x199802180x199802180xFF815C400x0000D9740xFF817AB0 < LR0xFF817AB0 < PC 0xA0000033
PC should be where the exception happened, so you can look at that address and Ghidra and see if anything jumps out. LR being the same seems suspect.
Started by mas000 Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by BTGeekboy Firmware Dumping
Started by suffer1989 Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by tamjim « 1 2 ... 16 17 » General Discussion and Assistance
Started by reyalp DryOS Development
