Is it possible to open the .dis file generated with capdis with ida or some visual tool?
regarding the disasm of the RAM with./capdis.exe ../../dumps/sx720/sub/100e/PRIMARY.BIN 0xfc000000 -stubs=../platform/sx720/sub/100e -s=0x010e1001 -e=0x010fce10 -f=objdump -d-const -d-addr -d-bin > ../../dumps/sx720/sub/100e/RAMCODE1.DISI think it is missing some RAM areas , the start and end seems to be right// RAM code 0x010e1000 - 0x010fce10 copied from 0xfcd3b79c ( 114192 bytes)// RAM code 0xbfe10800 - 0xbfe1751d copied from 0xfcd575ac ( 27933 bytes)But dosnt seems to start correctly , the g7x has much more at the begining looking for example for the surrunding areas for CreateBinarySemaphoreStrictly
Thanks reyalp,No great problems so far, just time to double check, able to find most of them, CreateBinarySemaphoreStrictly is still missing but looking for cluesAny cams with 2 rams ported so far?
No great problems so far, just time to double check, able to find most of them, CreateBinarySemaphoreStrictly is still missing but looking for clues
If any other is wrong like the close, it should be replaced then in stubs_min.S to avoid using the wrong one?
Also Close_FW was wrong too, the right one is lowecase close0xfc33303f,Close0xbfe155f5,close0xfc33303f,Close_FW
Yes replaced them at stubs_entry_2 withNHSTUB(CreateBinarySemaphoreStrictly,0xfc33303e) NHSTUB(Close,0xbfe155f5) NHSTUB(Close_FW,0xbfe155f5)
Almost have a ready to compile version, based fully on gx7 , some questions:How do I find LED_PR for lib.c ? need to poke with canonbasic or there is another way?
FI2KEY & FI2IV & dancing bits will be needed to any guess on the firmware location?
$ ./discam.sh sx720hs 100e -s=0xfc000001 -c=10 cmp r0, r3; fc00 mov ip, r0; fc00 movw r0, #0x3fcc movt r0, #0xfc00 bx lr
Also is possible with capdis to look for at the end of rom for levent tables for example?
EDIT: Also not sure about the validity of (0x4ffc)=0x12345678; from g7x since it does not not appear in sx720 fw
" bl sub_fc0781f4\n" // power-on mode handling & startupchecks here, no override needed with 0x12345678 set
Started by waterwingz « 1 2 ... 54 55 » DryOS Development
Started by Qanthelas « 1 2 ... 27 28 » DryOS Development
Started by reyalp « 1 2 ... 16 17 » DryOS Development
Started by tim dif « 1 2 » CHDK Releases
Started by sekx17 CHDK Releases