Messages

Has anyone done a dump of the ROM and BL fir v 1.1.1.?

great job! Let's get the 40d port on its way
Next step: copy/paste boot code into entry.S like the 5dc one. copy enough of the boot code until you can hook a task.

For initial hacking you may want to refer to 5dplus:
https://bitbucket.org/coutts/5dplus

Many will read this and get to thinking that an easy task!

I really want to install the Magic Lantern in my camera and give my modest contribution to the community but,
without your precious help will not go away.

You have done an excellent job over the years.

Congratulations.

great job! Let's get the 40d port on its way
Next step: copy/paste boot code into entry.S like the 5dc one. copy enough of the boot code until you can hook a task.

For initial hacking you may want to refer to 5dplus:
https://bitbucket.org/coutts/5dplus

Coutts,

yes I am currently reading your posts in CHDK.
In 2008 there were major developments, but for some unknown reason you moved away from this project. Made great advances that have helped future ports to other cameras but 40D & 450D were forgotten! Why?! ...

Their progress in the port 1000D can give a great help! I think the cameras 1000D, 450D, 40D have many similarities. This can be an advantage.

Thank you for providing the code :

https://bitbucket.org/coutts/1000d_dev

the only thing i will open is the card slot to swap CF card and the battery slot if the camera locks up
both will be done a few hundred times i guess.

my SD card reader slot in my PC is already defective due to plugging/unplugging the card too often

The card reader of your camera is still working properly?

[~/magic-lantern/doc/mkdoc.py]

3. In files ~/magic-lantern/doc/mkdoc.py and ~/magic-lantern/doc/mkdoc-cam.py you need to replace rst2latex.py with rst2latex

4. Directory already exists, so ignore.

Thank you!

I used the information provided by Coutts to flash both LEDs.

See the examples:


1_1000D LED Finder

2_1000D LED-Dumper

These are the addresses of blue and red LEDs:

LED_RED     0xC02200E0
LED_BLUE    0xC02200E8

I have a 40D with version 1.1.1. After much reading and testing I was able to flash both LEDs.

I'm trying to get things to compile on a Debian system for the first time, but I have a few issues. I don't want to brick my camera, so I am asking out of an abundance of caution:

1. Are there any Debian/Ubuntu repositories for the arm toolchain that people are using with success? I think it would be helpful to include platform-specific instructions in the README files.

2. The toolchain/summon-arm script is looking for patch-gcc-4.6.2-config-arm-t-arm-elf.diff in the wrong place.

3. doc/menuindex.py is complaining about "Could not open menuindex.txt". What should I do about this? Is this safe to ignore, or is it a fatal error?

4. doc/menuindex.py is complaining about "mkdir: cannot create directory `cam': File exists". What should I do about this? Is this safe to ignore, or is it a fatal error?

5. ld is complaining about "stat: cannot stat `autoexec.bin': No such file or directory", but then I objcopy creates an autoexec.bin file. What should I do about this? Is this safe to ignore, or is it a fatal error?

Thanks

I have Ubuntu installed and also got errors 3) and 4).

Hi,

I still have nothing to work but I have spent many hours reading the forums CHDK / ML.
I'm learning, have some patience with me. This still seems very complicated. Sorry if the questions are basic.

I got the firmware version 40d1.1.1. With application dissect_fw3_2, I got the unencrypted header and body. I've compiled a small application to try to find the addresses of the red and blue LED, but I've got a problem. I do not know how to encrypt the new firmware to be able to use on my machine. I read a lot about it but I could not understand the steps that have to follow.

If I can correctly encrypt my firmware I can proceed with my tests.

Since I've been searching for some string in the firmware files and I could see some interesting things. I found the string EnableBootDisk.

After seeing the flashing LEDs, I'll try to do a DUMP the firmware.
When I succeed in the previous tests, I proceed to the discovery of the function EnableBootDisk addresses.

Someone can help me create my own firmware for the 40D?

I could not compile the project, the following error occurred:

Code Select Expand


make -C lua/; make -C testplug/;
make[2]: Entering directory `/mnt/canon/canon/magic-lantern/plugins/lua'
~/arm-toolchain462/bin/arm-elf-gcc-4.6.2 -E -Wp,-MMD,/mnt/canon/canon/magic-lantern/plugins/lua/../.plugin.lds.d -Wp,-MT,/mnt/canon/canon/magic-lantern/plugins/lua/../plugin.lds -nostdlib -fomit-frame-pointer -fno-strict-aliasing -DCONFIG_MAGICLANTERN=1 -DCONFIG_=1 -DRESTARTSTART= -DROMBASEADDR= -DVERSION=\"\" -DCONFIG_DEBUGMSG=0  -Os -Wall -W -r -mstructure-size-boundary=32 -Wno-unused-parameter -Wno-implicit-function-declaration -Wno-unused-function -Wno-format -std=gnu99 -D__ARM__ -I/mnt/canon/canon/magic-lantern/plugins/lua -I/mnt/canon/canon/magic-lantern/plugins/lua/.. -I/mnt/canon/canon/magic-lantern/plugins/lua/../../src -mlong-calls -fpic -nostartfiles -ffreestanding /mnt/canon/canon/magic-lantern/plugins/lua/../plugin.lds.S | grep -v ^# > /mnt/canon/canon/magic-lantern/plugins/lua/../plugin.lds
~/arm-toolchain462/bin/arm-elf-gcc-4.6.2  -c -o /mnt/canon/canon/magic-lantern/plugins/lua/../entry.o /mnt/canon/canon/magic-lantern/plugins/lua/../entry.S
/mnt/canon/canon/magic-lantern/plugins/lua/../loader_gen.rb
/bin/sh: /mnt/canon/canon/magic-lantern/plugins/lua/../loader_gen.rb: Permission denied
make[2]: *** [/mnt/canon/canon/magic-lantern/plugins/lua/../loader.c] Error 126
make[2]: Leaving directory `/mnt/canon/canon/magic-lantern/plugins/lua'
make[2]: Entering directory `/mnt/canon/canon/magic-lantern/plugins/testplug'
/mnt/canon/canon/magic-lantern/plugins/testplug/../loader_gen.rb
/bin/sh: /mnt/canon/canon/magic-lantern/plugins/testplug/../loader_gen.rb: Permission denied
make[2]: *** [/mnt/canon/canon/magic-lantern/plugins/testplug/../loader.c] Error 126
make[2]: Leaving directory `/mnt/canon/canon/magic-lantern/plugins/testplug'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/mnt/canon/canon/magic-lantern/plugins'
make: *** [all] Error 2



Someone can help me?
Thank you.

BR

I'm thinking start doing the first tests.
I know it's a bit risky. Certainly, I will need your help.
Firstly, I will begin by installing and configuring ubuntu to compile the project. When I can, I will test the tools specified by Coutts.

I understand your argument. Probably I would be the first to feel it.

I really enjoyed this thread, do not think it a priority to improve the graphical interface, but can make its use more attractive to many users.

I appreciate your answers.

Might be a good idea to have a dynamic menu which would be presented the last user-selected options.
This way we could have a menu that is automatically adjusted to each of us, without additional configuration.

It seems you an idea of implementing feasible and useful?

I think this makes sense even if you only have a camera.
I've often thought that functionality.
I never understood why Canon does not implement such basic things.
With the original firmware you can save multiple settings in C1, C2 and C3,
but the camera does not persist this information on the card.
Each one of us could keep a list of specific settings for each type of photography.
Save some information about the menus would also be interesting.
In the camera could save or read files available on the card.
And were it possible would be useful load in C1, C2, C3 settings read previously.

I think there are many users who have 350D, 400D, 450D and 40D.
This equipment has been discontinued but are still in the drawers of many millions of Canon customers.
Over time these became obsolete equipment. Many of its users would like to use them to make their first tests with ML. On the other hand, might serve to improve the potential of its old cameras. In many cases, they could use them to perform some types of photography that do not allow your new equipment. Thus they avoided damaging your most valuable equipment. Because they are equipment with a lower cost, it is normal that there are many. By supporting these models would benefit a greater number of users.
Developers to work on these models can also acquire useful knowledge to support the latest and most advanced models.

I do not know if it's possible but it would be very interesting to have a channel of communication with the camera. I think, can not use a serial console or even a JTAG is a major limitation in this project.

If it were possible to use the USB port as a Virtual Serial Port for debugging purposes, developers could save much time and simplify many of the tasks of the development process.

With a virtual serial port, you could send debug messages to a computer, allow interaction with the developer. The transfer of small files also not be excluded.

Maybe it was still possible to implement a payload with 'GDB Stubs' allowing use GDB to perform remote debugging.

If this were possible it would be an excellent tool in development.

Sorry if this makes no sense.
It was just one idea that I thought I'd share with you.

This was my first contribution.

Finally some good news! I am enjoying the ML. I thank all who have worked on this project. I hope one day to use the ML with a 40D. I hope to give my contribution to make this possible.

I think the work done by Coutts to 5DC will be useful for even the 40D and 400D.