Menu

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.

Show posts Menu

Messages - nikfreak

#1126
Sigma 18-35mm 1.8. Top for APS-C. Know you don't want zoom but it's wort it..
#1127
cool i will try and report once i get home later
#1128
    Yes, back again! I tried to follow your tutorial. What steps did I do?


    • hg clone dm-spy-experiments branch
    • edited makefile.user and enabled "CONFIG_DEBUG_INTERCEPT_STARTUP = y"
    • edited dm-spy.c according to your instructions + plus ofc I set RAM_OFFSET of 6D not like in your code where you used 5D3 RAM_OFFSET
    • needed to verify and enable GetTaskname stub for 6d or compilation would fail
    • compiled and tested but nothing happens. No log on scard available after startup.
    • get back in makefile user and enabled "CONFIG_DEBUG_INTERCEPT = y" too although no instruction to do so. Got afterwards some "gdb_setup" error in dm-spy-extra. Deleted that line and could compile. Afterwards debugmsg Log menu is available  but all messages saved by menu have 0 bytes.

    What step am I mising or doing wrong? any hint?
#1129
Modules Development / Re: DotTune AFMA (dot_tune.mo)
August 01, 2014, 12:00:59 AM
Seems to be spot on for -16 at 70mm and -1 at 200mm using "all lenses".
I have no clue why I get -6 at 70mm at this lens and werent able to get a beep between 71-200mm using "this lens" setting
#1130
Bug confirmed on 6D:
"This lens" option doesn't work correct for some lenses. e.g. if I use this option on my 70-200 then only at 70mm it will do AFMA. With that option it will do at 200mm too but won't beep so won't find any focus beep.

If I set to "all lenses" then it will work fine at 70mm and also on 200mm and in between. Value for 70mm differs heavily compared to the value I git from "this lens" where as stated above 200mm wouldn't beep at all...
#1131
No problem
#1132
Archived porting threads / Re: Canon 70D
July 31, 2014, 09:15:47 PM
if someone can message me (PM) a ROM dump then I might look into missing stubs. You miss some, right? Or where is 70D builds stuck? Hello World?
#1133
Understood i am just at the dmspy branch with your hints from toay so I will recompile fullres-silent-pics tomorrow. got it!
#1134
Same game. Fullres-silent-pics branch needs to be compiled and retested. we do this tomorrow ok?
#1135
Still the skip offsets were worth it plus I learned to correct some mistakes
#1136
Thx for your response. Merging gets me headache. i am still uncomfortable with hg mercurial compared to using git / github. I tried copying raw_diag into unified and tried compiling as you suggested but that gave me compile errors. Dunno at least me and Levas tried. Hopefully this is honored and 6D won't be thrown out. Maybe ayshih you can instuct me or upload a raw_diag.mo for us so we can use my built zip from "fullres-silent-pics" branch from today which I compiled for 6D??
#1137
I have really no clue. I compiled "fullres-silent-pics" branch and what's that about v5.0 / 6.0 I don't know cause I didn't try myself. If a1ex tells what to do I will do and we can do the requested test for 6D. Sorry still freshman over here....
Btw that raw_diag module from 1st page is prebuilt. I have no idea where the sources are so that I could increase a version number in source and compile myself

@a1ex: This is what I did: http://magiclantern.fm/forum/index.php?topic=12523.msg124160#msg124160

Where did I wrong? Can you teach plz?
#1138
Done! had to fix my docutils:

Here you go http://www59.zippyshare.com/v/38767089/file.html

Sorry again.
#1139
Yeah I did it like Audionut instructed. But you are right about missing modules. They don't get added cause of some missing rst2html:


Building module silent...
REBUILDING
[ README   ]   module_strings.h
cat README.rst | grep -v -E "^:([^:])+:.+$" | rst2html --no-xml-declaration | python ../html2text.py -b 700



/bin/sh: 1: rst2html: not found

(<type 'exceptions.SystemExit'>, SystemExit(1,), <traceback object at 0x2ad947187368>)
make[4]: *** [module_strings.h] Error 1
#1140
Walter Schulz: I would like to help you but can you lead me to which edmac I shall use when compiling branch "fullres-silent-pic" for 7D? Old value which got thrown out (was 0xc0f04A08)? it needs to be put here before I can compile for 7D. Can you find correct value of 7D? I assume it can be 0xc0f04208 but I am unsure about that. Older cameras seem to use that. Newer cameras seem to use 0xc0f04008:

#if defined(CONFIG_5D2) || defined(CONFIG_50D) || defined(CONFIG_60D) || defined(CONFIG_550D) || defined(CONFIG_500D) || defined(CONFIG_600D)
#define RAW_PHOTO_EDMAC 0xc0f04208
#endif

#if defined(CONFIG_5D3) || defined(CONFIG_700D)
#define RAW_PHOTO_EDMAC 0xc0f04008
#endif
#1141
@Levas:

For 6D I compiled for you "fullres-silent-pic" branch but before compiling I made changes to "raw.c" as a1ex and 1% have been discussing on bitbucket:

First I defined edmac like discussed above:


#if defined(CONFIG_5D3) || defined(CONFIG_700D) || defined(CONFIG_6D)
#define RAW_PHOTO_EDMAC 0xc0f04008
#endif


and also changed height + skip-values according to a1ex's suggestion on bitbucket discussion linked above:
#ifdef CONFIG_6D  //Needs check from Raw dump but looks aligned.
width = 5568;
height = 3722;
skip_left = 72; //Meta Data
skip_right = 0;
skip_top = 52; // Meta Data
#endif


Here's the zip to try for you @Levas:

http://www59.zippyshare.com/v/38767089/file.html

Please lemme know if you have no time to do the necessary test before a1ex will drop 6D out of this


Before anyone gets the idea to use thos for anything othe rthan 6D: I had to use fake stubs and defines for some cameras to get this compiled. So this will only work with 6D.


Edit: fixed link with correct zip containing modules
#1142
Fullres-silent-pic branch is almost ready for you @Levas. I will PM you the download link soon
#1143
Thanx for this a1ex. Will try and see what I get from my 6D but my initial thoughts according to your card initiliazation messages on 5D3 should be true:

6D / 5D3 (and maybe other UHS-I capable cams) use at least SDR50 or DDR50 bus speed with 1.8V signal voltage and a possible max. power of 1.44W. 5D3 is set at 48Mhz. card initialization messages give no details about max. power or stuff like Buswidth (UHS-I can only use 1bit or 4bit).
#1144
Actually I guess Host type for 6D according to the above table is SDR50. If we are lucky then it also could be SDR104. Dunno the technical details of my cam  :o
And yes I get 40MB max, too. This could be influenced by some of those variables / commands stated above. Good thing is it's a standardized spec which Canon has to follow as long as they state that a cam is UHS capable. They do so I found lots of stuff in ARMu. It's not only squeezing out the max performance for 6D I am looking for but also for 650D, 700D, 70D and future cams. Investigating all the threads on the forum I realized there's simply no other chance actually to get more write performance. I tried setting higher buffer size, reducing fps and or resolution for raw recording. I don't know if it is possible but I simply think and hope that Canon crippled max. performance by commands / software.
#1145
Spend some hours now to read through standarized specifications. Found a really interesting document here https://www.sdcard.org/downloads/pls/simplified_specs/part1_410.pdf.

To sum it up UHS-I modes and speeds are controlled by different commands for e.g. cmd6, cmd11, cmd55 and so on. Those control and set block lengths, speed modes, bus widths, voltages and much more. As canon specifies cams like 6D as UHS-I capable I was able to verify in 6D ROm with ARMu that we use "1.8V signaling" and there' also command for "voltageswitch" and blocklength control or set"buswidth" stuff and also that earlier stated commands cmd6, cmd11, cmd55 etc. I also found out that the default voltage is 0.72w for UHS-I and it's stated in the linked document above that for maximum performance standardized 1.44W should be used and as I understood can be used riskfree as it is standardized for UHS-I spec. But i have no clue how to use earlier stated "voltage" sw.
Document above also states that somehow in idle mode of a card when it's powered on again the bus width i 1bit and needs first to be set to 4bit again via commands. This could explain while we need some kind of warm up for our cards before we reach max performance in benchmarking? If anyone has some more ideas please help. i am free to try experiments with my 6D. in ARmu for eg I think I found some stubs for voltageswitch, transfer commands and so on. But for e.g. I have also no clue how to disassemble "./card/STGinitialsetting.c " which i see in ARMu comments.





#1146
Any idea how to identify which hi-speed mode gets used in e.g. photo mode or while raw recording. I attached an image of ARMu so you can see what I mean.

#1147
General Development / Re: FIO_SeekSkipFile testing
July 30, 2014, 08:17:44 AM
All [PASS] on 6D!!!
#1148
General Development / [Q] Diet libc ???
July 26, 2014, 10:19:11 PM
Hi,

just wanted to ask why ML switched to diet libc in early 2013? Was it to be able to shrink file sizes as much as possible and being able to use TCC, too??
Another question: Last weeks I have heard lots about  "musl libc" as it seems to become more and more used in community / opensource projects (e.g. openWRT). Please have a look at the following comparison http://www.etalabs.net/compare_libcs.html

Could this or parts of it (cherry picking code) be useful for us? What do you think?
#1149
Ok just wanted to add this info for 650D / 700D / probably 70D and 6D. Found some benches done in photo mode for taking RAWs in burst. Looks like the sandisk extreme Plus 80MB/s is best performer for these cams having crippled sd controller. Ofc results need to be compared in camera with ML. Maybe I will buy one and test some days later.



Sources:
Picture source
Another Review with some nice audio pulse benchmarking
#1150
Quote from: Audionut on July 21, 2014, 03:00:18 AM
Thanks for the results.
Would be nice to have some more 5D2, 7D, 50D, and UHS SD bodies (6D, 700D, 650D, EOSM).

@nitfreak, can you confirm the mode used and the FPS.

Movie Mode: 1920x1080 24fps
Global Draw: Off