Is there a developer mailing list ?
> 1) The ARM processor core has a JTAG port built into it. Has anyone investigated if the processor (or board !) had a JTAG port on it ?Nope. The whole CHDK is developed without taking a screwdriver. If you so brave you can try to find.
> 2) Most ARM processors have a provision for encrypting the contents of the ROM. Apparently the ROMs on the cameras are not encrypted, thus the firmware can be dumped ? Do I have this right ?[/i]I did not know that the ROM can be encrypted. But lucky, Canon's DIGIC do not use this feature.
> 3) What tools are developers using to debug the code they write?No tools. At all. The most hardware dependent part was implemented a long ago, so the camera hangs very rarely. If we need an indicator that the code reach some point, we use any LED (switching it ON).
> I saw a routine for blinking the camera LED. It's just for firmware dumping.
> What sort of baud rate can be accomplished doing that and has anyone written/run a monitor to help with debugging?Someone dumped a firmware on ~10000 bits per second.
> 4) What hardware specs are we working with ? Typical processor speed, exact processor model, ROM/RAM/(e)Eprom sizes ?No specs. It's a fun.
Processor - Digic II or Digic III (with ARM9 core integrated). 32M RAM. Eprom - we do not use it.
> 5) I assume that all of the code stored in the current repository is for the VxWorks OS. Yes.> How is the code going to be organized when we start working on the DryOS OS ? Total fork ? Integrated into the current structure ?Who knows. We return to this question when such porting will be done.
> 6) What tools are being used for disassembly?Mostly - IDA Pro.
> How are various routines discovered for a camera? One of the Camon's firmware updates had more than 5000 function names. And there is a lot of text strings in the firmware.
> I assume the disassembler can find the function pre and post setup code and functions can be found, but how are the developers determining what they do ?Why you do not read For Developers, especially this?
> 6) Has the DryOS firmware been dumped by anyone yet? This!
> Is there a functioning "blink the LED" program for a DryOS camera?This! And this!
(I know of a moderator that is getting an itchy "smiting finger". )
> Its one thing to find functions in code, another to figure out what those functions do.Disassembled code and imagination. We do not have a debugger, emulator and something similar to trace a code.
> HAS ANYONE DUMPED THE DRYOS FIRMWARE ?Again. Do you have eyes? I provided you with the link to the page, which has only two external links, and one of them is the link to the firmware dump.
> I also recommend that the G9 and 40D be moved to under the Digic III list.They are already there. Not under the DryOS, because it is not proved yet.
Started by dvornik
« 1 2 »
Started by RyeBrye
Started by Parham
General Help and Assistance on using CHDK stable releases
Started by gdharmraj
Started by geocrasher
Creative Uses of CHDK