can't find the led GPIO or on/off control values to put debugging blinking in - these seem to have changed again.Any ideas or pointers on how I can track these down would be greatly appreciated.
Quote from: philmoz on 06 / May / 2019, 00:36:42can't find the led GPIO or on/off control values to put debugging blinking in - these seem to have changed again.Any ideas or pointers on how I can track these down would be greatly appreciated.From this post, GPIO base address is 0xd2080000, led on 0x20d0002, off 0x20c0003.By following what I did in finsig, the LED table element init function is sub_E045D84A, the GPIO offset is either in r1 or r2. The led_on function used by task_LEDCon is sub_E003BF00, led_off is sub_E003BF16. Addresses are for firmware 101b.You can do various experiments from Canon Basic, you can find examples in this thread.And I keep mentioning that the D7 ARM cores don't support integer division, you'll need to adjust the makefile.
Any thoughts on what setting to use in arm_rules.inc for -march?
Quote from: philmoz on 06 / May / 2019, 18:04:43Any thoughts on what setting to use in arm_rules.inc for -march?-march=armv7-aThat might just work for the DIGIC 6 Cortex R too, but if it comes to integrating D7 support, it would be great if D6 could still keep this small piece of performance (integer division) somehow.
the Digic7 needs a different ARM architecture from Digic6 the files that are compiled as 'camera independent' are not compatible between D6 and D7.
- Setting the build directory to .o3 if DIGIC7 is set.
D7 may bring a different set of troubles (I'm thinking about threading problems) which may then require specific fixes. That would then go against keeping D6 D7 compatibility.
Started by photonoob « 1 2 » General Discussion and Assistance
Started by lireboy CHDK Releases
Started by Skumgummifabriken « 1 2 3 » General Help and Assistance on using CHDK stable releases
Started by pigeonhill General Help and Assistance on using CHDK stable releases
Started by oPryzeLP General Discussion and Assistance