This page collects resources and techniques for testing a CHDK build or port. See also Debugging
this is a work in progress, please expand!
The CHDK User Manual gives an good overview of many features. Working through this list and verifying that your port matches the documented behavior.
Note that many CHDK features are poorly documented or poorly defined. When in doubt, consult the source.
When testing overrides from script or the override menu, it is important to know Canon firmware displays and EXIF information may not reflect the actual value used. The functionality of the override should be determined from the image.
Testing with scripts
There are some scripts which exercise various CHDK capabilities
Tests the lua standard libraries. This also exercises many C library functions.
- run the script, with all of the 'skip' options set to zero.
- If all test succeeded, it will print "end ... OK" for each item.
- If any tests failed, examine A/llibtst.log
Tests the capture mode switching functions and mode map.
- start the camera in play mode
- run the script with all options set to zero
- the camera should switch to record, and switch rapidly between each known shooting mode
- If everything was OK, it will print pass
- If something failed, examine A/setmode.log
General purpose ubasic test.
- Download: ubtest.bas (also included in "full" install)
- Documentation: http://chdk.setepontos.com/index.php?topic=6592.0
- Start the camera in play mode
- Start the script with interactive = 1 and sleep between tests = 5
- The "message key test - set to end" will appear
- If you press up/down/left/right the corresponding key name should be printed.
- Press set to go to the next test
- The canon menu should open and selection change a couple times
- The camera will switch to record mode, and switch to P mode
- The camera will take shots as follows:
- auto exposure, using get_shooting, press shoot_half, press shoot_full etc
- auto exposure + or - 2 stops Tv, using shoot
- auto exposure + or - 2 stops Sv, using shoot
- If ND filter is present, one shot each with ND forced in and out, using shoot
- If no failures were identified, prints "ok", otherwise failed.
- Output is logged to CHDK/LOGS/LOG_0001.TXT. The log will indicate whether the shots above were + or -, with the corresponding exposure number. Compare the jpegs to ensure the images show the expected variation in exposure.