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

Pages: [1] 2 3 4
Camera-specific Development / Re: Canon EOS R / RP
« on: November 21, 2019, 04:21:00 PM »
Hi, I really only need one single feature from ML for the EOS R, and that's the ability to auto-restart video when it reaches the file size/time limit (30 mins, as I understand it.) Can ML currently allow this on the EOS R? My 5DMkII can do this with ML, and I'd love to upgrade but I need continuous video without having to return to the camera. Multiple files is A-OK. Any insight appreciated!

With an external recorder like the Atoms Ninja V, you can do 10-bit continues recording through the HDMI output port.

Camera-specific Development / Re: Canon 90D
« on: August 20, 2019, 01:08:26 AM »
There are the specifications from the video:

32.5mp APS-C Sensor
45AF points (all cross-type)
10fps shooting
4K at 30p/25p
FullHD at 120p/100p
Optical viewfinder & face detection
100% viewfinder coverage
220K dot RGB + IR metering
Touchscreen Vari-Angle LCD
Dust & water-resistant
Battery grip BG-E14

Camera-specific Development / Canon 90D
« on: August 19, 2019, 10:36:42 PM »

Can confirm that 6D2_DUMP.FIR is still working on 6D2 1.0.4.

Did 3 runs, MD5 of ROM0 is inconsistent, ROM1 is even.

Did run: ./ 6D2 -d debugmsg
FileMerge detected 69 differences between 6D2.103 and 6D2.104, all memory address related.

Tried: ./ 6D2 -d debugmsg -s -S & arm-none-eabi-gdb -x 6D2/debugmsg.gdb
but the iMac terminal complained: -bash: arm-none-eabi-gdb: command not found.

There seems to be a Homebrew problem not installing arm-none-eabi-gdb.
Found a script to fix that, but that didn't work!

Installed arm-none-eabi-gdb with Homebrew, now I get the following error.

Python Exception <type 'exceptions.ImportError'> No module named gdb:
Could not load the Python gdb module from `/Users/ibush/bin/arm-none-eabi/share/gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.

How can I fix this? Start all over again?   :o

Firmware update 6D200104.FIR is released.

Duplicate Questions / Re: Canon 6D mark ii
« on: July 12, 2018, 11:41:06 AM »
Firmware update 6D200104.FIR is released.

Camera-specific Development / Re: Canon 80D
« on: May 31, 2018, 11:38:43 PM »

Did the full install of the Mac sticky tweet.
Got the same result as with the
If I press 'C' to "open" the card door => also clean shutdown within Magic Lantern Rescue,
or type 'system_powerdown' there is no response at all.

When I close the Qemu window:
Code: [Select]
iMac-27:qemu-eos $ c
-bash: c: command not found
And I'm able to use the same Terminal window as usual.

Camera-specific Development / Re: Canon 80D
« on: May 31, 2018, 08:59:16 PM »

I suspect the problem lies within Qemu.
If I press C to "open" the card door => also clean shutdown within Magic Lantern Rescue
the terminal locks up.

system_powerdown --> No response!


Maybe someone here can confirm that your problems with ML could be related with the older MacOSX El Capitan.

Camera-specific Development / Re: Canon 80D
« on: May 31, 2018, 05:01:34 PM »
On my iMac: version 9.1.0

Code: [Select]
gcc --version
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin17.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Installed bash 4
Code: [Select]
$ bash --version
brew install bash
sudo chsh -s /usr/local/bin/bash

bash --version
GNU bash, versie 4.4.19(1)-release (x86_64-apple-darwin17.3.0)
Copyright (C) 2016 Free Software Foundation, Inc.

Still getting:
Code: [Select]
-bash: syntax error near unexpected token `&'
Danne suggested to skip the '&' altogether and now I do get a complete list of debug messages.
Code: [Select]
./ 80D,firmware="boot=0" -d debugmsg | grep -E --text Notify.*Cur
[DM] FROM Write Complete!!!
[      DbgMgr:fe5336b5 ] (00:01) [PM] Enable (ID = 18, cnt = 0/2)

But the terminal locks up again!

Camera-specific Development / Re: Canon 80D
« on: May 31, 2018, 01:01:28 PM »
Still learning, trying examples etc.
After this command line and (partially?) output the Terminal locks up.
Code: [Select]
./ 80D,firmware="boot=0" -d debugmsg 2>&1 | grep -E --text Notify.*Cur
[        init:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 0, 0x2018000, Flag = 0x10000)
[      SFRead:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 0, 0x2008000, Flag = 0x8000)
[     RomRead:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 0, 0x2000000, Flag = 0x2000000)
[    PowerMgr:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 1, 0x2, Flag = 0x2)
[     Startup:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 2, 0x20420010, Flag = 0x20000000)
[     FileMgr:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 2, 0x420010, Flag = 0x10)
[     FileMgr:fe0dc20d ] (00:03) [SEQ] NotifyComplete (Cur = 2, 0x420000, Flag = 0x400000)

Learned from Danne that '|&' should be altered into the older '2>&1 |'. Otherwise you get an error.
Code: [Select]
-bash: syntax error near unexpected token `&'

Camera-specific Development / Re: Canon 80D
« on: May 31, 2018, 08:38:26 AM »
I'm wondering which MacOSX version you're using.
In message #351 your screen dump still has the aqua graphical user interface which Apple flattened in 2014 (MacOS Yosemite)!

Camera-specific Development / Re: Canon 80D
« on: May 30, 2018, 11:17:22 PM »
Trying some older stuff:
Code: [Select]
>   sleep 3; echo "akashimorino";
>   sleep 1; echo "dumpf";
> ) | (
>   ./ 80D -serial stdio -s -S &
>    arm-none-eabi-gdb -x 80D/patches.gdb
> )
-bash: arm-none-eabi-gdb: command not found
iMac-27:qemu-eos $ qemu-system-arm 25643   12u   REG   1,10 259522560 8133999 sd.img

Error: please unmount the SD image.

Camera-specific Development / Re: Canon 80D
« on: May 30, 2018, 08:24:36 PM »
Many thanks Danne!   ;)

Camera-specific Development / Re: Canon 80D
« on: May 30, 2018, 06:34:38 PM »
Solved it myself.   :D

Running /Users/xxxx/qemu-eos/qemu-2.5.0/.git/
asked me this time for my email address and name.
The never did, and therefore the installation was incomplete and kept saying:"No such file or directory".

So I am up and running now.

Yes, I had seen the sticky tweet for Mac. I even loaded the animated GIF in PhotoShop to examine it frame by frame.

Camera-specific Development / Re: Canon 80D
« on: May 30, 2018, 12:23:56 PM »
Yep, even a few times. But all the simple testing (or install) command lines like

Code: [Select]
# all EOS models should run this without any trickery
/path/to/qemu-eos$  ./ 60D,firmware="boot=1"

are giving me:
Code: [Select]
No such file or directory

Camera-specific Development / Re: Canon 80D
« on: May 30, 2018, 11:16:36 AM »
Where do I put the ROM1.BIN and SFDATA.BIN and how to start emulation?
Can I still use Danne's Danne thought that a1ex or dfort were the ones who could help.

Where to put or make a SD-card image?
magic-lantern -> contrib -> qemu -> scripts -> 80D?
magic-lantern -> platform -> 80D.102?

Camera-specific Development / Re: Canon 80D
« on: May 29, 2018, 10:00:46 PM »
I can confirm that the latest autoexec.bin is writing data to the SFDATA.BIN file.
Compared SFDATA.BIN to the one I received from OlRivrRat (yesterday), there are 70 differences.

I used an old 2GB SD Card and didn't know how I used it before.
Nowadays I only use 128GB cards for video.
So this time I didn't format in the camera, but used SD Card Formatter.
Like you I used MacBoot to set the bootflag.

The rest I did was the same as I did in message #337.
Hope this helps.

Camera-specific Development / Re: Canon 80D
« on: May 29, 2018, 04:45:10 PM »
Interesting or not?
Code: [Select]
0fec9480 db "\n********** FACTORY ADJUSTMENT MENU **********\n", 0 ; DATA XREF=sub_fec9368+20
0fec94b0 db "0. Exit from Factory Adjustment\n", 0                  ; DATA XREF=sub_fec9368+28
0fec94d4 db "1. Leak Check\n", 0                                    ; DATA XREF=sub_fec9368+36
0fec94e4 db "2. ASV Display\n", 0                                   ; DATA XREF=sub_fec9368+44
0fec94f4 db "3. RAM Check\n", 0                                     ; DATA XREF=sub_fec9368+52
0fec9504 db "4. ROM Check\n", 0                                  ; DATA XREF=sub_fec9368+60
0fec9514 db "5. ICU Version Check\n", 0                          ; DATA XREF=sub_fec9368+68
0fec952c db "6. Serial Flash Check\n", 0                          ; DATA XREF=sub_fec9368+76
0fec9544 db "9. Input Device Unique\n", 0                        ; DATA XREF=sub_fec9368+84
0fec955c db "A. ALL Check\n", 0                                  ; DATA XREF=sub_fec9368+92
0fec956c db "B. Adjustment Data Display and Change\n", 0          ; DATA XREF=sub_fec9368+100
0fec9594 db "C. Check Flag Display and Initialization\n", 0        ; DATA XREF=sub_fec9368+108
0fec95d0 db "E. HDMI Check\n", 0                                  ; DATA XREF=sub_fec9368+124
0fec95e0 db "F. AUDIO Check\n", 0                                ; DATA XREF=sub_fec9368+132

Camera-specific Development / Re: Canon 80D
« on: May 29, 2018, 01:51:25 PM »
Just started all over again and now with success.
Incidentally, the SFDATA.BIN differs from the SFDATA.BIN that I received from OlRivrRat.

UPDATE: No wonder that my SFDATA.BIN is different. Just 8.4MB of 0x00's!

Camera-specific Development / Re: Canon 80D
« on: May 28, 2018, 01:46:29 PM »

Did send you a PM.

Camera-specific Development / Re: Canon 80D
« on: May 27, 2018, 06:50:48 PM »
Thanks to the more than excellent work of Danne on the I am able to compile ML on a Mac in a very short time. But the show must go on.

Have done the LED test with the 80D and it works.

As A1ex suggested I needed new ROM dumps with serial flash contents for emulation with the latest portable ROM dumper.

Didn't work with the 2GB SD card.
Made a 259.5MB SD partition, didn't work either!
There is some noise activity, but nothing read to the SD card, 80D works as usual.

Code: [Select]
iMac-27:~ $ diskutil list
/dev/disk0 (internal):
/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *2.0 GB     disk4
   1:                 DOS_FAT_16 EOS_DIGITAL             2.0 GB     disk4s1

iMac-27:~ $ diskutil unmountDisk /dev/disk4
Unmount of all volumes on disk4 was successful
iMac-27:~ $ sudo dd if=/Users/xxxx/Desktop/sd.img of=/dev/disk4
506880+0 records in
506880+0 records out
259522560 bytes transferred in 128.059448 secs (2026579 bytes/sec)
iMac-27:~ $ sudo diskutil eject /dev/rdisk4
Disk /dev/rdisk4 ejected
iMac-27:~ $ diskutil list

/dev/disk4 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *2.0 GB     disk4
   1:                 DOS_FAT_16 EOS_DIGITAL             259.5 MB   disk4s1

Camera-specific Development / Re: Canon 80D
« on: May 25, 2018, 03:23:29 PM »
Thanks for the directions. The last time I worked a lot in assembler was with a 6502 microprocessor together with the 6510 second processor on an Acorn computer (BBC +). I still have a lot to catch up and the tons of ML information are pretty much fragmented on the website.

Camera-specific Development / Re: Canon 80D
« on: May 24, 2018, 12:45:50 PM »
An old 2GB SD card did the trick.
Did get three ROM dumps:
ROM1A.BIN, ROM1B.BIN and ROM1C.BIN and their checksums.

Oddly enough ROM1A.BIN and ROM1B.BIN have the same checksum each dump. Even after trying 3 times.
Code: [Select]
Dump#1/ROM1A.BIN 0e103ef26d93d3ba7f03d5141a3f351c
Dump#1/ROM1B.BIN 0e103ef26d93d3ba7f03d5141a3f351c
iMac-27:~ $
Dump#2/ROM1A.BIN d9bfe2012acae3af0ad7cb77b751d067
Dump#2/ROM1B.BIN d9bfe2012acae3af0ad7cb77b751d067
iMac-27:~ $
Dump#3/ROM1A.BIN 59b7f7756bb6deb90e67c1e4bd0ec167
Dump#3/ROM1B.BIN 59b7f7756bb6deb90e67c1e4bd0ec167

I suppose I can ignore ROM1A or ROM1B?

Not on topic: On my 6D Mark II I got two ROM dumps: ROM0.BIN and ROM1.BIN!

Camera-specific Development / Re: Canon 80D
« on: May 22, 2018, 06:15:38 PM »
Trying to get a ROM dump of my 80D 1.0.2
No luck, blue or red background and nothing written to the SD card (Sony SDXC 64 GB).

The search example in the suggests 'croprec' not 'crop_rec'.

Pages: [1] 2 3 4