1
Camera-specific Development / Re: Canon EOS R / RP
« on: January 19, 2023, 11:09:45 PM »
No posts = no progress.
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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.
1 EEKO_TX
2 EEKO_RX
3 ?? (3v3), trying to transmit resets ICU
4 ICU_TX
5 ICU_RX
6 GND
7 ?? (3v3)
8 MPU_TX
9 MPU_RX
10 ?? (3v3)
Dry> vers
DRYOS version 2.3, release #0051
Dry-MK 2.60
Dry-DM 1.20
Dry-stdlib 1.52
Dry-NET6 0.33 111125+4796
Dry-ECI6 0.20+110927
Dry-DNS 1.23pre 120130-4845
Dry-DHCPC 2.23
Dry-PX 1.09
Dry-drylib 1.21
Dry-shell 1.17
Dry-command alpha 058
Dry> help
[Debug]
xd xm task PCMcheck PCMclear
[EekoLog]
GetEekoLog PutEekoLog
Interesting though if resetting the count in menu resets the total count via this method?
10806: 36140.093 [SHTD] ERROR SemTimeOut SetJpegDispEncodePathForRawJpeg
10807: 36140.144 [STARTUP] ERROR ASSERT : Warp::ShtDevCommon.c
10808: 36140.323 [STARTUP] ASSERT : Task = ShootEncodeSub
10809: 36140.330 [STARTUP] ASSERT : Core 0
10810: 36140.334 [STARTUP] ASSERT : Line 125
10811: 36140.338 [STARTUP] ASSERT : bFlag
10812: 36140.346 [STARTUP] < StackDump >
EXIFTOOL shows 71mm.Windows shows 7mm, see my screenshot / "Długość ogniskowej" = Focal Length. Though other parameters doesn't make any sense, like 60s expo... yes, for sure.
On the other notes I have a lot of Digic 8 ML code working on SX740, but also have a nasty crash that I can't trace yet. Thus for now it lives on branch in my fork.
We can run code on these but not as much work has been done, no active devs happen to have D6.
- Canon Raw recording through USB port for USB SSDs (Jus a routing from CFexpress to USb or even a dual recording).Impossible. CFExpress is just DMA over PCI Express, USB - even if camera had USB host functionality (and to my knowledge it doesn't) handling overhead and lack of implementation would be most likely too much to achieve it without a significant effort - if possible at all.
Not sure what your point is, but OP (and others) have problems with ML documentation. OP came to the forum to find an answer to a problem caused by incomplete ML documentation, and instead of getting straightforward help, it was suggested that the problem was his fault.
Yes, it should -- because of the problem with the instructions that is the cause of this thread.
because most folks go to YouTube videos by @Zeek and others that show them how to do so -- they don't use the vague/incomplete ML instructions.
Those instructions should probably add:
"Go to the 'firmware' selection in the menus (usually in the gold 'tools' section of the menus), and update the firmware."
It's not the "opposite" -- it just doesn't give any clue on how to "Launch the Firmware Update process..."