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 - zloe

Pages: [1]
1
Camera-specific discussion / Re: Canon 80D
« on: June 21, 2016, 07:56:25 PM »
Ok, photo transistor connected to Audacity, ready to record.
Just need to attach it a bit better to the cam.

2
Camera-specific discussion / Re: Canon 80D
« on: June 20, 2016, 08:08:42 AM »
Volunteer found, but I need some assistance. It would take me some time to prepare the fir file myself.

- zlo

3
Camera-specific discussion / Re: Canon 80D
« on: June 19, 2016, 08:00:07 PM »
I also own a 80D and just ordered an external power supply. I have some HW as well as SW skills.
So I'm ready to help as well.

Btw. should/can we start an 80D thread?

- zlo

4
Archived porting threads / Canon 6D - someone dumps newest firmware?
« on: February 01, 2015, 03:15:06 PM »
Somebody out there who wants to have the 6d with latest firmware 1.1.6 to be supported by ML?
If so I would start working on finding the entry points. All I need is a volunteer to dump the rom.

-Klaus

5
Archived porting threads / Re: Canon 6D
« on: January 10, 2015, 11:49:09 AM »
Is there a way to get the BIN files from a 6D with newest firmware (1.1.6).
I could invest some time to work on finding the stubs.

6
Reverse Engineering / Re: Tutorial: finding stubs
« on: January 10, 2015, 11:11:54 AM »
Is there anyway to extract ROM1.BIN from vendors firmware update (FIR) file?
I have the same question.

Same for me.
I'd like to look into the new firmware of the 6D (1.1.6), but I don't want to install it yet on my camera.

7
General Development Discussion / Re: FIO_SeekSkipFile testing
« on: July 31, 2014, 11:19:07 PM »
Just ran the tests on 650D again, now all tests pass!

Edit: I ran the stubs api tests (just to be precise).

Thanks!
So now we need to find the CancelDateTime stub.

This might take some time.

8
General Development Discussion / Re: FIO_SeekSkipFile testing
« on: July 30, 2014, 10:58:52 PM »
All tests pass besides this one:
Code: [Select]
       t0 = *(uint32_t*)0xC0242014 => 0x20902
       msleep(250)
       t1 = *(uint32_t*)0xC0242014 => 0x70687
[FAIL] ABS(MOD(t1-t0, 1048576)/1000 - 250) => 0x4d
       LoadCalendarFromRTC( &now )
       s0 = now.tm_sec => 0x2f
       Date/time: 2014/07/30 22:55:47
       msleep(1500)
       LoadCalendarFromRTC( &now )
       s1 = now.tm_sec => 0x31

9
General Development Discussion / Re: FIO_SeekSkipFile testing
« on: July 30, 2014, 10:42:44 PM »
Just tested the nightly build from 25th of July for the 650D, also there the api stub tests do not complete and the Camera hangs.

10
General Development Discussion / Re: FIO_SeekSkipFile testing
« on: July 30, 2014, 10:35:04 PM »
The mentioned test passes but it is the last thing displayed. After that the Camera does not respond any longer.
The msleep(500) I added in the macro made it worse. Now the Camera shuts down after the 2gig file has been created.

11
General Development Discussion / Re: FIO_SeekSkipFile testing
« on: July 30, 2014, 10:07:04 PM »
Hm,
the last test that run was
Code: [Select]
            /* this one should not overrun */
            timer_func = 0;
            TEST_TRY_FUNC_CHECK(SetHPTimerAfterNow(100000, timer_cbr, overrun_cbr, 0), % 2 == 0);
The memory allocation takes place later in the test. still I reduced the value but it did not have any effect.

I also tried to skip the FIO tests and see if then the tests succeed. They do not. They crash at various points during the timer tests.
Anything I can try to narrow that down?

I created a pull request now for the FIO_SeekSkipFile.


12
General Development Discussion / Re: FIO_SeekSkipFile testing
« on: July 30, 2014, 08:42:25 PM »
I have run the tests on my 650D.
The FIO Tests run all OK but afterwords the test crashes and I did not get a logfile.
Now I simply skipped the rest of the tests.
Result is:
Code: [Select]
[Pass] f = FIO_CreateFile("test.dat") => 0x3
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
[Pass] FIO_WriteFile(f, (void*)ROMBASEADDR, 0x10000) => 0x10000
       FIO_CloseFile(f)
[Pass] FIO_GetFileSize("test.dat", &size) => 0x0
[Pass] size => 0x20000
[Pass] p = (void*)_alloc_dma_memory(0x20000) => 0x407f5c24
[Pass] f = FIO_OpenFile("test.dat", O_RDONLY | O_SYNC) => 0x3
[Pass] FIO_ReadFile(f, p, 0x20000) => 0x20000
       FIO_CloseFile(f)
       _free_dma_memory(p)
[Pass] count => 0x3a98
[Pass] buf = fio_malloc(0x1000000) => 0x4a104094
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000000
[Pass] f = FIO_OpenFile("test.dat", O_RDWR | O_SYNC) => 0x3
[Pass] FIO_SeekSkipFile(f, 0, SEEK_END) => 0x82000000
[Pass] FIO_WriteFile(f, buf, 0x10) => 0x10
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_END) => 0x81fffff0
[Pass] FIO_WriteFile(f, buf, 0x30) => 0x30
[Pass] FIO_SeekSkipFile(f, 0x20, SEEK_SET) => 0x20
[Pass] FIO_SeekSkipFile(f, 0x30, SEEK_CUR) => 0x50
[Pass] FIO_SeekSkipFile(f, -0x20, SEEK_CUR) => 0x30
[Pass] FIO_GetFileSize_direct("test.dat") => 0x82000020
[Pass] FIO_RemoveFile("test.dat") => 0x0

Now I have to find out how to create a pull request.
If someone else is faster in adding the change and creating a pull request here is the changed line in stubs.S
Code: [Select]
NSTUB(0xFF34276C,  FIO_SeekSkipFile) 

13
Ok, I have some new values in the lower and upper temperature range for the 6d:

Time    raw-before raw-after temp C
00:03   150     150   24
01:04   149     149   23
07:05   146     146   22
07:13   146     146   22
09:12   146     149   23

13:08   161     161   34
13:08   163     163   37
13:17   173     173   50
13:23   183     183   54
13:40   186     183   56
13:40   185     185   57
13:47   187     187   60
13:48   189     189   60
13:52   189     189   63

Anything else we need in this area?

- Klaus

14
...
One would need more data points in the lower and upper temp segments to be sure, though.
With more points, a better fit... a simpler equation?

/Oscar

I'll give it a try to come up with more data points in the lower and upper temp area.
Have to get up early to be able to measure temperatures below 26°C, but the upper part should be easy.

- Klaus

15
Just saw that scripting is not yet reactivated.

Here are the new values I measured today.
I wrote down the raw value before and after taking the image:

time    raw-before  raw-after  temp C
19:02   151        151   26
19:04   152         152   30
19:05   156        156   33
19:06   156        159   36
19:08   159        159   38
19:09   164        164   39
19:11   166        166   41
19:12   166        166   42
19:13   171        171   42
19:16   175        175   45
19:16   175        175   45
19:18   175        175   46
19:19   177        177   47
19:20   177        177   47
19:22   176        176   48
19:23   181        181   48
19:25   181        181   49
19:30   183        183   50
19:32   183        183   51

- Klaus

16
General Development Discussion / Wanted: temperatures from your cams
« on: July 17, 2014, 07:48:46 AM »
Wouldn't it be possible to use scripting to automate this tests and also reduce mistakes?
Is it possible to get the raw temperature reading from the script and write it to a file?
I would love to write such a test script.

- Klaus

17
General Development Discussion / Wanted: temperatures from your cams
« on: July 16, 2014, 10:14:50 PM »
I have some measurements for the 6D:
raw  temp in C
151   26
152   30
159   35
162   36
166   43
167   40
171   45
173   42
175   45
176   46
177   48
181   42
181   42
181   44
182   49

I hope this helps, does not really look like a linear relation.
I'll repeat these tests later this week.

- Klaus

Pages: [1]