Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - acasta

Pages: [1]
1
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: August 01, 2019, 04:20:50 PM »
...too many problems with Cygwin  :o
I switched to an Ubuntu VM and everything went smoother and much faster.

2
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: July 31, 2019, 11:28:44 AM »
Thank heder  :)
At the moment I'm struggling a bit to build QEMU on Cygwin.
I had to modify configure_eos.sh to make it use the right compiler and then some dependecies were missing.
Now I get some compiler errors that I still have to analyze...

Indeed, building this on Cygwin is apparently not so well supported and some problems could be because of that. But I can't use WSL at the moment.

3
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: July 28, 2019, 04:44:04 PM »
I checked out the vxworks branch (commit 18ac6b0, the last one on that branch) and tried to build ML for the 40D.
I am on Win7 + Cygwin at the moment and did:

Code: [Select]
cd platform/40D.111
make zip

Many modules were not built, other modules had comments such as "Will not load on 40D".
In the end I have a zip named magiclantern-Nightly.2019Jul28.40D111.zip containing, among the rest, the following modules:

Code: [Select]
$ ls -l
total 1028
-rwxr-xr-x 1 ...  33118 Jul 28 15:58 40D_111.sym
-rwxr-xr-x 1 ...  21828 Jul 28 16:03 adv_int.mo
-rwxr-xr-x 1 ...  11816 Jul 28 16:03 arkanoid.mo
-rwxr-xr-x 1 ...  17800 Jul 28 16:03 autoexpo.mo
-rwxr-xr-x 1 ...  18068 Jul 28 16:03 bench.mo
-rwxr-xr-x 1 ...   7632 Jul 28 16:03 deflick.mo
-rwxr-xr-x 1 ...  11636 Jul 28 16:03 dot_tune.mo
-rwxr-xr-x 1 ...  15488 Jul 28 16:03 dual_iso.mo
-rwxr-xr-x 1 ... 324544 Jul 28 16:03 edmac.mo
-rwxr-xr-x 1 ...  28240 Jul 28 16:03 ettr.mo
-rwxr-xr-x 1 ...  14600 Jul 28 16:03 file_man.mo
-rwxr-xr-x 1 ... 304104 Jul 28 16:03 lua.mo
-rwxr-xr-x 1 ...  42224 Jul 28 16:03 mlv_lite.mo
-rwxr-xr-x 1 ...  44372 Jul 28 16:03 mlv_play.mo
-rwxr-xr-x 1 ...  62596 Jul 28 16:03 mlv_rec.mo
-rwxr-xr-x 1 ...   5772 Jul 28 16:03 pic_view.mo
-rwxr-xr-x 1 ...  30576 Jul 28 16:03 raw_rec.mo
-rwxr-xr-x 1 ...  22028 Jul 28 16:03 silent.mo

This is my very first attempt to build ML: would you please let me know if I'm on the right track, or is there anything evidently broken?

I have disassembled my ROM dump, my next step would be trying to understand more about stubs...

4
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: July 26, 2019, 04:39:38 PM »
Ok, I see, I'll check that.
Thank you A1ex!

5
Camera-specific Development / Re: [UNMAINTAINED] Canon 40D
« on: July 25, 2019, 02:04:12 PM »
Hi, I recently got interested in ML and would like to make something of it on my old 40D...
I'm still looking around in the forum and trying to understand how code is organized, but I'm also stuck with the preliminary step of rom dump.
I tried the portable dumper (DUMP_40D.FIR) with 4 different CF cards, also old ones with 256 MB capacity, but it does not seem to work: the MD5 for ROM1.BIN is different each time (even if the check with PC always succeeds).
I was wondering if anyone had success with DUMP_40D.FIR and could suggest anything...
Otherwise I'll have to try what previously described in this thread, but that I'll need some more work to be ready with that...

6
General Development / Re: Portable ROM dumper
« on: July 22, 2019, 11:00:19 PM »
Hi,

I recently got interested in ML, but unfortunately both my Canon cameras are not supported yet.
One is the old 40D so I'd like to try and help make the port proceed a bit, hopefully.
A starting point could be what described here:
https://www.magiclantern.fm/forum/index.php?topic=1452.msg195051#msg195051
However, I'm stuck with the preliminary step of rom dump.
I tried DUMP_40D.FIR with 4 different CF cards, also old ones with 256 MB capacity, but it does not seem to work: the MD5 for ROM1.BIN is different each time (even if the check with PC always succeeds).
ROM0.MD5 is always the same though...

Here is a sample of my logs:
Code: [Select]
  Magic Lantern Rescue
 ----------------------------
 - Model ID: 0x190 40D
 - Camera model: Canon EOS 40D
 - Firmware version: 1.1.1 / 4.0.1 6C(3e)
 - IMG naming: 100CANON/IMG_2435.JPG
 - Boot flags: FIR=0 BOOT=0 RAM=-1 UPD=-1
 - ROMBASEADDR: 0xFF810000
 - card_bootflags 101f34
 - boot_read/write_sector 108350 108354
 - Patching 10281C from e3510001 to e3510000
 - 1027DC Card low-level init => F4240
 - 101E18 Card init => 0
 - Patching 101E28 from e3510001 to e3510000
 - 101E18 Card init #2 => 1
 - Dumping ROM0... 100%
 - MD5: 2c7ab85a893283e98c931e9511add182
 - Dumping ROM1... 100%
 - MD5: 68e2c7549d97b6394f10607b6718606f
 - No serial flash.
 - Saving RESCUE.LOG ...

Any idea about what's wrong? Has DUMP_40D.FIR ever been tested in a camera, or only in QEMU?
I could try to do the dump in another way, but I understand I'd need ML to have a bootable camera... Could someone please point me at alternative ways to do that?

Pages: [1]