Author Topic: 5D2 dm-log files for R&D  (Read 489 times)

reddeercity

  • Hero Member
  • *****
  • Posts: 1437
5D2 dm-log files for R&D
« on: December 16, 2017, 11:55:52 PM »
Starting a new thread for the 5d2 dm-log and other log files for r&d , didn't what to clutter up the 12-bit (and 10-bit) RAW video development discussion thread
so I saw some interesting things in dm-0001.log file from my bitbucket downloads
Code: [Select]
1A2C2>    PropMgr:ff99bbdc:01:03: MovieParamData
1A31B>    PropMgr:ff99b5b4:01:03: #mode 0 size 0x0 , framerate 0x18 , type 0xc
Code: [Select]
       
6AC67>    Startup:ff8e5f88:98:03: GetImageTrimming X(2976)=0(2414, 2416), Y(1928)=0(1552, 1548)

Code: [Select]
3003C>    Startup:ff814378:8b:03: startupPrepareCapture
304F4>    Startup:ff8b89c4:80:03: MemMgr 0 2
30539>    Startup:ff8b89c4:80:03: MemMgr 0 0
3055C>    Startup:ff8b89c4:80:03: MemMgr 0 4
3057D>    Startup:ff8b89c4:80:03: MemMgr 0 0
306C5>    Startup:ff8b5ea4:80:03: RearrangeMemMgr 0 5
30712>    Startup:ff8b2d54:80:01: ###### AllocateMemoryFromShootMemoryObject 1
3073B>    Startup:ff8b2dfc:80:01: ###### 0 0x73CFE0 0x73CFE0
3076B>    Startup:ff8b2dfc:80:01: ###### 1 0x73CFE8 0x73CF2C
30797>    Startup:ff8b2e28:80:01: ###### 1 pMemoryUnit 0x73CF2C 0x73D3B0
307D2>    Startup:ff8b2e58:80:01: AllocatableSizeOfPackHeap 30408592, 16384, 16384
30809>    Startup:ff8b30e0:80:01: !!AllocateMemory 16384
30891>    Startup:ff8b2f28:80:01: AllocateMemoryFromShootMemoryObject 1 97517232 16384 0x0073d518
308D8>    Startup:ff8b2f44:80:01: ###### VirtualXXXFreeSize1 97517232 137296720
30920>    Startup:ff8b32d0:80:01: ###### VirtualXXXFreeSize2 97500836 137296720
30959>    Startup:ff8b32e4:80:01: ###### !! AllocateMemoryFromShootMemoryObject hMemSuite 0x73D518
30983>    Startup:ff8b5d40:80:05: Enter AllocateMEM3 0x4000 JOB

Bet you seen this before  ;D
Code: [Select]
3B836>     RscMgr:ff8af44c:80:03: SetBusy 0x50(0x50)(0x10)
Shoot Capture
Code: [Select]
4189C> ShootCaptu:ff881d04:93:03: scsProperty ID=0x0(0x0)
41988> ShootCaptu:ff87f820:93:03: scsInit
41A4B> ShootCaptu:00095f98:00:00: *** register_interrupt(0x0, 0x33, 0xff871c50, 0x0), from ff871db8
41CB9> ShootCaptu:00095f98:00:00: *** register_interrupt("CAPREADY", 0x51, 0xffa35980, 0x0), from ffa359f4
42060> ShootCaptu:ff9a77d0:00:01: [CLKSAVER] ��ClockSave Out��
423A9> ShootCaptu:00095f98:00:00: *** register_interrupt("JpCoreIntrHandler", 0x64, 0xff9a5954, 0x0), from ff9a5c80
42849> **INT-64h*:00095c38:00:00: >>> INT-64h JpCoreIntrHandler ff9a5954(0)
428A0> **INT-64h*:0000057c:00:00: <<< INT-64h done
42EEC> ShootCaptu:00095f98:00:00: *** register_interrupt("JpCore2IntrHandler", 0xa3, 0xff9a64bc, 0x0), from ff9a6774
42F82> ShootCaptu:00095f98:00:00: *** register_interrupt("CompleteReadOperation", 0x60, 0xffb273d8, 0x0), from ffb27454
4303D> ShootCaptu:00095f98:00:00: *** register_interrupt("AfComplete", 0x61, 0xff9a8c00, 0x0), from ff9a8df8
43092> ShootCaptu:00095f98:00:00: *** register_interrupt("AfOverRun", 0x62, 0xff9a8d84, 0x0), from ffb26df8
430E6> ShootCaptu:00095f98:00:00: *** register_interrupt("ADKIZ", 0x65, 0xffb27fac, 0x0), from ffb26dfc
43161> ShootCaptu:00095f98:00:00: *** register_interrupt("Obinteg", 0x63, 0xffb27744, 0x0), from ffb26e04
431B1> ShootCaptu:00095f98:00:00: *** register_interrupt("WbInteg", 0x66, 0xffb26754, 0x0), from ffb267d4
431FC> ShootCaptu:00095f98:00:00: *** register_interrupt("WbBlock", 0x67, 0xffb2677c, 0x0), from ffb26e08
4325E> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac0Interrupt", 0x58, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x0), from ff9a4438
432B3> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac1Interrupt", 0x59, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x1), from ff9a4438
43307> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac2Interrupt", 0x5a, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x2), from ff9a4438
4335C> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac3Interrupt", 0x5b, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x3), from ff9a4438
433B2> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac4Interrupt", 0x5c, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x4), from ff9a4438
43406> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac5Interrupt", 0x6d, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x5), from ff9a4438
4345C> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac6Interrupt", 0xc0, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x6), from ff9a4438
434B5> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac0Interrupt", 0x5d, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0x8), from ff9a4438
43509> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac1Interrupt", 0x5e, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0x9), from ff9a4438
4355E> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac2Interrupt", 0x5f, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0xa), from ff9a4438
435B2> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac3Interrupt", 0x6e, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0xb), from ff9a4438
43607> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac4Interrupt", 0xc1, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0xc), from ff9a4438
4365C> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac5Interrupt", 0xc8, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0xd), from ff9a4438
436B1> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac7Interrupt", 0xf9, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x10), from ff9a4438
43708> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac8Interrupt", 0x83, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x11), from ff9a4438
4375F> ShootCaptu:00095f98:00:00: *** register_interrupt("WEDmac9Interrupt", 0x8a, 0xff9a4038 "[ENG] WriteDMACInterrupt(%d)(%#lx)(%d)", 0x12), from ff9a4438
437B6> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac6Interrupt", 0x8b, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0x18), from ff9a4438
4380C> ShootCaptu:00095f98:00:00: *** register_interrupt("REDmac7Interrupt", 0x92, 0xff9a426c "[ENG] ReadDMACInterrupt(%d)(%#lx)(%d)", 0x19), from ff9a4438
4382C> **INT-0Ah*:00095c38:00:00: >>> INT-Ah Timer ff81027c(0)
4386D> **INT-0Ah*:0000057c:00:00: <<< INT-Ah done
4390D> ShootCaptu:00095f98:00:00: *** register_interrupt("CompleteOperation", 0x9a, 0xffb895c0, 0x0), from ffb26e18
43965> ShootCaptu:00095f98:00:00: *** register_interrupt("CompleteOperation", 0x93, 0xffb2a0c4, 0x0), from ffb26e1c
43EA7> ShootCaptu:ff87f908:93:03: BathtubAddress:0x5c714000, Size:65536
43F62>     RscMgr:ff8af184:80:03: ClearBusy 0x10(0x10)(0x40)

Still looking for liveview sync stuff .

reddeercity

  • Hero Member
  • *****
  • Posts: 1437
Re: 5D2 dm-log files for R&D
« Reply #1 on: December 17, 2017, 08:51:24 AM »
Some Liveview stuff , NTSC Sync  -- maybe ?
Code: [Select]
D7292>    Startup:ff867658:82:03: InitializeDisplayDeviceController (PUB)
D746C>    Startup:00095f98:00:00: *** register_interrupt("EngInt PBVD", 0x68, 0xff866fb4 "VdInterruptHandler img=%x bmp=%x", 0x0), from ff867688
D74D5>    Startup:00095f98:00:00: *** register_interrupt("EngInt PBVD", 0x69, 0xff86719c "!! PBERROR_InterruptHandler 0x%lX", 0x0), from ff86769c
D783D>    Startup:ff9ad254:82:02: Factory TFT Com Adjust Add  0x404c6fc4
D7886>    Startup:ff9ad268:82:02: Factory TFT Com Adjust Size 12
D78AC>    Startup:ff9ad284:82:02: Factory TFT Com Adjust R 80006 G 80540 B 81024
D7906>    Startup:ff9acee8:82:02: Factory Sync Burst Adjust Add    0x404c6f68
D7935>    Startup:ff9acefc:82:02: Factory Sync Burst Adjust Size   16
D7957>    Startup:ff9acf18:82:02: NTSC Bf   0xeb, 0xeb
D7977>    Startup:ff9acf34:82:02: NTSC Sync 0x9471, 0x94719471
D79A2>    Startup:ff9acf50:82:02: PAL  Bf   0xec, 0xec
D79C2>    Startup:ff9acf6c:82:02: PAL  Sync 0x946f, 0x946f946f
D79FE>    Startup:ff9acfb4:82:02: Factory YUV Adjust Add  0x404c6f80
D7A29>    Startup:ff9acfc8:82:02: Factory YUV Adjust Size 24
D7A49>    Startup:ff9acfe8:82:02: TFT  Y   0x80, 0x80
D7A69>    Startup:ff9ad004:82:02: TFT  UV  0x8080, 0x8080
D7A8E>    Startup:ff9ad020:82:02: NTSC Y   0x35, 0x35
D7AAE>    Startup:ff9ad03c:82:02: NTSC UV  0x2d42, 0x2d42
D7AD2>    Startup:ff9ad058:82:02: PAL  Y   0x34, 0x34
D7AF2>    Startup:ff9ad074:82:02: PAL  UV  0x3d59, 0x3d59

Lens info
Code: [Select]
F0639>    CtrlSrv:ff9caf08:83:03: CurrentLensName[EF24-70mm f/2.8L USM]
a little VSync stuff
Code: [Select]
1F6DD> GuiLockTas:ff868058:00:02: [DispCon] EnableTftIc
1F76D> GuiLockTas:00095f98:00:00: *** register_interrupt(0x0, 0x34, 0xff871c50, 0x1), from ff871db8
21AD2> **INT-0Ah*:00095c38:00:00: >>> INT-Ah Timer ff81027c(0)
21B0E> **INT-0Ah*:0000057c:00:00: <<< INT-Ah done
226AF> GuiLockTas:ff866168:82:01: WaitVSync (PRI)
226DC> GuiLockTas:ff863fb4:82:01:  RequestNotifyBlank (PRI)
22702> GuiLockTas:ff864078:82:03: RequestNotifyBlank img=0 bmp=ff864cec
23750> **INT-68h*:00095c38:00:00: >>> INT-68h EngInt PBVD ff866fb4(0)
23787> **INT-68h*:ff866ff8:82:03: VdInterruptHandler img=0 bmp=ff864cec
237B6> **INT-68h*:ff864cfc:82:01: WaitBmpCBR
237E3> **INT-68h*:0000057c:00:00: <<< INT-68h done
23809> GuiLockTas:ff8661c0:82:02: EnableTftCtrl CurrentBrightness=4
23896> GuiLockTas:00095f98:00:00: *** register_interrupt(0x0, 0x34, 0xff871c50, 0x1), from ff871db8
241E2> **INT-0Ah*:00095c38:00:00: >>> INT-Ah Timer ff81027c(0)
2421C> **INT-0Ah*:0000057c:00:00: <<< INT-Ah done
242D5> **INT-10h*:00095c38:00:00: >>> INT-10h HPTimer ff86ca8c(0)
24337> **INT-10h*:0000057c:00:00: <<< INT-10h done
268F1> **INT-0Ah*:00095c38:00:00: >>> INT-Ah Timer ff81027c(0)
26924> **INT-0Ah*:0000057c:00:00: <<< INT-Ah done
2747D> GuiLockTas:ff8658e8:82:02:   NotifyChangeTurnOnDisplay
2784C> GuiLockTas:ff864be8:82:02:  SelectParameterToBmp (PRI)
2787D> GuiLockTas:ff864a40:82:02:  SetParameterToBitmapDisplayDevice (PRI)

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 10716
  • 5D Mark Free
Re: 5D2 dm-log files for R&D
« Reply #2 on: December 17, 2017, 10:06:11 AM »
All of this is before Canon GUI even starts.

You'll see the same stuff (and be able to run it step by step or with additional debug infos) in QEMU, with:
Code: [Select]
./run_canon_fw.sh 5D2,firmware="boot=0" -d debugmsg ...

reddeercity

  • Hero Member
  • *****
  • Posts: 1437
Re: 5D2 dm-log files for R&D
« Reply #3 on: December 18, 2017, 05:27:16 AM »
Ok thanks  , I did try to run QEMU on my AMD desktop that runs the VM of Ubuntu but clashed/errors out , I'll try on my dell i5 intel laptop .
If I'm not mistaken QEMU has been update , I'll need to catch up -- last version I tried was 1.6 I think

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 10716
  • 5D Mark Free
Re: 5D2 dm-log files for R&D
« Reply #4 on: December 18, 2017, 04:47:06 PM »
If all else fails, check this sticky tweet and the QEMU guide. Works on Mac and Windows too.

reddeercity

  • Hero Member
  • *****
  • Posts: 1437
Re: 5D2 dm-log files for R&D
« Reply #5 on: December 20, 2017, 06:44:46 AM »
Ok thanks , will do  :D