Messages

Wow, you bricked your 1000d camera ?

I just wanted to post that I want to check out setting the bootflag this weekend, but now I'm scared
Anything here:
http://www.magiclantern.fm/forum/index.php?board=45.0

@shmadul
You're right.
Normally to run ML you don't need the fir file.
Once you enabled the bootflag, ML runs with autoexec bin file and the ML files in the ML directory on your SD card

Good work by the way, Syscall.
You now a lot more about the technical side then I do.

So you set the bootflag, can you share the FIR file you did it with?
This way we could just run autoexec.bin at startup, no more firmware updates.
I'm just new to the magic lantern source files and finding my way to find addresses in firmware.
So I hope I can help when you're a little further in finding your way in magic lantern.

Now I see. But why you are playing with LEDs and don't modifying VxWorks branch

We're gonna use our 1000D as christmass decoration this year, hanging in a tree with blinking leds

Just wondering, is there a moderator who can change the title of this topic?
Since it's no longer about compiling, but more about, porting ML to 1000d ?
Or at least, small steps in trying to port ML to the 1000d 

Great to see Alex arrive in this post 

Indeed the 1000d and 450d have a lot in common, but I'm not sure if that helps a lot with porting ML.
Since we know that even different firmwares need different ports, like in the 5d3.

It seems that most of the work is in finding the right addresses in the firmware.
But for that we need to have a firmware dump.

Which, as far as I know, isn't available for the 1000d ?
So is the first thing to do now, get a firmware dump ?
And how, can we write a program to make the 1000d do a firmware dump on the SD card.
Or can we just use the FIR file from the 1000d 1.0.7 update from the Canon site ?

And Alex, are there advantages to make it run in QEMU, or can we just try our stuff out on our real alive and kicking 1000d's, how big is the risk of bricking them ?

With and without raw_twk enabled, live view freezes during 10bit recording on 6d.
But as far as I know, you need to configure config_raw_edmac_slurp to fix this.
At the moment this only done for 4 cams, 5d3, eosm, 60d and 600d

With 14 bit, live view works like it should be.

I've recorded in 10bit, many times, on the 6d and there are no corrupted frames, both in raw_rec and mlv_rec modules.
Only problem is that liveview freezes (no config_edmac_raw_slurp).
I'm stuck with figuring out how to find the address for the 6d to configure config_edmac_raw_slurp(see few post back in this topic).
http://www.magiclantern.fm/forum/index.php?topic=5601.msg175682#msg175682

But I can assure, that there are no corrupted frames on the 6d with 10bit recording.
Although 12bit has sometimes the purple banding issues on every frame.

@shmadul and @Syscall,

Meanwhile I checked the topic of the 450d progress.
http://www.magiclantern.fm/forum/index.php?topic=8119.msg174078#msg174078

Seems to be a vxworks branch for this type of camera's
https://bitbucket.org/hudson/magic-lantern/src/18ac6b0f992918c7ba6dd282c3e74ca42574561c/?at=vxworks

In the platform folder, you can find the 450d folder and it's source files.

@Alex

Look, both leds are blinking, even made them alternate blinking, just like you asked for 

http://drive.google.com/open?id=0B1BxGc3dfMDaRUZweUJ5NWZUTTQ

What's next ?

Thanks Syscall, and sorry for the bad reading on my part  , the working files were already there in you earlier post.

So now we've got a 1000d with flashing LED's. Perfect decoration for under the tree this christmass season 

So I've downloaded your zip file and compiled it myself, there where some files missing to do that, which I took from Coutts files.
I want to start with a clean directory of files, I've downloaded your zipfile and added these files, are they all necessary ?

assemble.wf
crc16.c
crc16.h
e6kr5107.fir_0_header.bin
e6kr5107.fir_1_flasher.bin
entry.S
link.script
entry_subs.S
header.bi
main.h


Something went wrong here, all files are in the zip

Ok, now that I compiled the autoexec.bin and the 1000d.fir myself.
I only get a blue burning led on the 1000d, no more blinking...

I do get a lot of error messages during autoexec.bin compiling:
Command make:
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc    -c -o entry.o entry.S
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc    -c -o entry_subs.o entry_subs.S
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc -nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99   -c -o main.o main.c
main.c: In function 'dumpmemo':
main.c:19:3: warning: implicit declaration of function 'FIO_CloseFile' [-Wimplicit-function-declaration]
   FIO_CloseFile(f);
   ^
main.c:22:2: warning: implicit declaration of function 'FIO_OpenFile' [-Wimplicit-function-declaration]
  f = FIO_OpenFile("B:/ROMDUMP.BIN", 0, 0644);
  ^
main.c: In function 'MyTask2':
main.c:34:2: warning: implicit declaration of function 'msleep' [-Wimplicit-function-declaration]
  msleep(5000);
  ^
main.c:37:5: warning: implicit declaration of function 'prop_request_change' [-Wimplicit-function-declaration]
     prop_request_change(0x80040007, &x, 4);
     ^
main.c: In function 'CreateMyTask':
main.c:94:2: warning: ISO C forbids passing argument 4 of 'CreateTask' between function pointer and 'void *' [-Wpedantic]
  CreateTask("MyTask2", 0x1A, 0x2000, MyTask2, 0);
  ^
In file included from main.c:1:0:
main.h:2:12: note: expected 'void *' but argument is of type 'void (*)()'
extern int CreateTask (const char *name, int prio, int stack_size /*?*/, void *entry, long parm /*?*/);
            ^
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc -nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99 -Wl,-T,link.script -oAUTOEXEC.arm.elf entry.o entry_subs.o main.o link.script
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-objcopy -O binary AUTOEXEC.arm.elf AUTOEXEC.BIN

Great work you guys 

Will try it this stuff out today, start clean, make the autoexec.bin, and after that the FIR file.

I do get a lot of warnings during compiling, don't know if it means anything?

in terminal I do the command 'make' and this shows up:
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc    -c -o entry.o entry.S
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc    -c -o entry_subs.o entry_subs.S
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc -nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99   -c -o main.o main.c
main.c: In function 'dumpmemo':
main.c:19:3: warning: implicit declaration of function 'FIO_CloseFile' [-Wimplicit-function-declaration]
   FIO_CloseFile(f);
   ^
main.c:22:2: warning: implicit declaration of function 'FIO_OpenFile' [-Wimplicit-function-declaration]
  f = FIO_OpenFile("B:/ROMDUMP.BIN", 0, 0644);
  ^
main.c: In function 'MyTask2':
main.c:34:2: warning: implicit declaration of function 'msleep' [-Wimplicit-function-declaration]
  msleep(5000);
  ^
main.c:37:5: warning: implicit declaration of function 'prop_request_change' [-Wimplicit-function-declaration]
     prop_request_change(0x80040007, &x, 4);
     ^
main.c: In function 'CreateMyTask':
main.c:94:2: warning: ISO C forbids passing argument 4 of 'CreateTask' between function pointer and 'void *' [-Wpedantic]
  CreateTask("MyTask2", 0x1A, 0x2000, MyTask2, 0);
  ^
In file included from main.c:1:0:
main.h:2:12: note: expected 'void *' but argument is of type 'void (*)()'
extern int CreateTask (const char *name, int prio, int stack_size /*?*/, void *entry, long parm /*?*/);
            ^
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-gcc -nostdlib -march=armv5te -fno-builtin -Wall -pedantic -std=gnu99 -Wl,-T,link.script -oAUTOEXEC.arm.elf entry.o entry_subs.o main.o link.script
~/gcc-arm-none-eabi-4_8-2013q4/bin/arm-none-eabi-objcopy -O binary AUTOEXEC.arm.elf AUTOEXEC.BIN

I tried your piece of code, put it in the main.c
Compiled and only the blue led blinks 

Are you sure nothing needs to be changed in the entry.s file ?

For best results, downscale at the end, so like you're saying in option 1, the render settings.
However, with the video quality of Facebook, I don't expect to see differences in quality if you use the route you mention in 4.

@Syscal and @shmadul
Great, so we got three people who are willing to put some effort in the 1000d.

Alex is willing to help us if we can get some stuff done
http://www.magiclantern.fm/forum/index.php?topic=14732.msg172723#msg172723
I've send him a message a few weeks ago that I got the blue led blinking, now he asks for making the blue and the red led to blink
Probably to prove some sort of understanding of the written code.
But I got stuck letting the blue and red blink, here's where you guys probably could help.

As far as I understand, the program that runs on 1000d exists from these files.
main.c
main.h
Entry.s
Entry_subs.s

All these files can be viewed in a normal text editor and edited and compiled for testing.
Most stuff is done in the main.c
The entry.s contains arm code, see this link:
http://magiclantern.wikia.com/wiki/ASM_introduction
The entry_subs.s contains addresses where commands are called in the 1000 firmware I think.

So does one of you know how to change the above files to get both the red and blue led blinking ?

Ah, so you can't use 3200 crop recording with good live view preview ?
(crop_rec.mo isn't working on the 6d, so no experience with it.)

In that case you need to use the grayscale preview.
It's in the raw menu, where you also set resolution.
Preview options -> ML grayscale

On 6d(and probably all other models too) sound recorded with mlv_rec is perfectly in sync.

About the wide shots

baccinoluigi's shares how  he did it:

Sequence shot with 5dMK III
Canon 16-35 f/4 is
Image Resolution 3200x 1200
FPS override 23
Card spanning on
magiclantern-Nightly.2015Dec20.5D3113
Graded in DaVinci Resolve
Edited in Premire Pro CC

Like MitchLally says, 3200 pixels is 1.8 crop (so ignore the 5x/10x zoom names, the recording is far wider then the display shows)
With your 8mm, you could get 8 x 1,8 crop = 14mm wide recordings with 3200 pixels wide settings.

Forget the gray scale preview, recently they discovered how to get accurate live view in crop mode.

In this post there is a build for the 5d3 with the crop mode module(select 1x1 in crop mode menu).
http://www.magiclantern.fm/forum/index.php?topic=5601.msg175774#msg175774

As a bonus it has also options for the experimentally 10 and 12 bit recording options (but if I read all the posts in this topic, I'm not sure if it works for 5d3)
Furthermore it's better not to enable the 'raw_twk.mo' module, because this one messes with the crop recording.

I have a 6d myself, so I don't have any experience with this build for the 5d3, but I think it's worth a try and remember if stuff looks weird, pull out the battery

Unfortunately there is not much to compile, the files which were made by Coutts are only capable of letting the blue led on the camera burn.
So these files are only a very small beginning for porting the 1000d and no where near a working magic lantern build.

I'm not sure what the next step would be, probably a firmware dump with the use of the blue led?
After that, all sorts of addresses need to be found in the rom dump for use in the magic lantern software.

Use the zoom button while in videomode and seeing liveview on your camera display.
The liveview should zoom by every push of the zoom button, 1x zoom, 5x zoom, 10 times zoom.
When in 5x zoom or 10x zoom, enter magic lantern raw video menu and you can select higher resolutions.
The 5x and 10x zoom don't give correct framing, the grayscale low resolution liveview does give proper framing

@DeafEyeJedi
Just tried the build you made for 6d, and noticed it doesn't have 10/12 bit options in mlv_rec and raw_rec.
Just saying(Already have a build for 6d with 10/12bit options)

Just wondering, is it possible to disassemble a RAM dump from the camera with 'disassemble.pl' ?
Ans if so, at which address does it start, the ROM loads at 0xFF000000, but what value to use for the RAM dump ?