Region 3 looks to possibly be the DIGIC Register area, since anything in the 0xC range maps to digic registers (from what we know). I know the flag area is at 0xF8000000 so maybe related to that. Region 1 could represent 1gb of RAM area, in the bootloader it references the RAM area as 0x0-0x40000000. Region 0 is the total addressable space of the 32-bit ARM (0x0-0xFFFFFFFF). It kind of makes sense! Some regions overlap, but the permissions for all are the same so overlapping doesn't mean much. This is one of the early functions called when the bootloader starts: Here is where the different memory regions are setup. The interesting stuff can be found here regarding the Control Coprocessor CP15's registers: We're pretty lucky to have this documentation available to us. The ARM documentation is actually quite helpful now that I am reading it and not skimming it for key words.
The ones that don't are halting on the bootcode I have written), we call the camera's normal boot procedure directly and hardly have to do a thing So instead of re-writing all of the boot code (which appears to be the problem with the 5dc, some cameras work some don't. ML initializes and at the end of the ML startup task it calls the Canon startup task to continue booting like normal. Replace the pointer to canon's startup task with a pointer to ML startup task (so canon starts ML startup task instead of its own). So, we can modify this cache to essentially re-write parts of the firmware. I don't know many details yet, but essentially when VxWorks reads or writes to/from say address 0x123, the ARM uses 0x123 and applies an index to it, to know where in the cache to look for this value. The ARM (processor) doesn't read instructions and data directly from the ROM/RAM rather, it reads them from a cache (to provide a lower latency read method). I've been working with him trying to make it work, and also studying the ARM documentation for how it all works.
I think that if we use g3gg0's cache hack to boot ML, we may be able to make ML work on all 5dc cameras
0 kommentar(er)
