-
Notifications
You must be signed in to change notification settings - Fork 72
1300d port take 2 #199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
1300d port take 2 #199
Conversation
Thanks - I will look at this but it's not going to happen until after the 2025 release for old and new cams. You've labelled it as a draft, and obviously I can't do much with "WTF" comments - it doesn't tell me what you're unsure about. This kind of discussion is probably better on Discord, although it can happen here if you prefer. I don't have a 1300D so can't test this code on phys cam. What testing has been done? How much confidence do you have, and why? We had multiple reports of potentially permanent damage to 1300D using mlv_lite.mo. Have you tested this, or not? It is now possible to control what modules are packaged with the zip file for cam build, with modules.included and modules.hidden. I'm surprised your changes build without these present. Either way, I recommend using these files to only include those modules that you've personally tested on phys cam. We can extend these as more modules are tested. |
Hi, I get this error when I try to build your fork:
P.S. Is there some new place to discuss Magic Lantern development now? The 1300D forum post hasn't been posted to since 2023 and I wanna talk about porting ML to my camera :( |
It's not finished yet. CONFIG_1300D has to be added to some of the ifdef chains in fps-engio and raw.c among others. @Zi7ar21 check the 1300d topic on ML discord and you'll see all the work we've done so far |
All of these values were taken from the critix 1300d 1.1.0 port. The values in raw.c appear to be placeholder data copypasted from the 600D: > `// PLACEHOLDER DATA FROM 600D TO BUILD HELLOWORLD` Yet these weren't ever changed, and ended up being shipped in builds. raw.c: https://bitbucket.org/ccritix/magic-lantern-git/src/234e117aba5a0b0147e9327656dc359d54e9ed04/src/raw.c edmac-memcpy.c: https://bitbucket.org/ccritix/magic-lantern-git/src/234e117aba5a0b0147e9327656dc359d54e9ed04/src/edmac-memcpy.c fps-engio.c: https://bitbucket.org/ccritix/magic-lantern-git/src/234e117aba5a0b0147e9327656dc359d54e9ed04/src/fps-engio.c#lines-309
Otherwise, cam would crash at boot because it places BSS outside the space available for ML (ml_reserved_mem). BSS is placed next to autoexec.bin, and (last time I checked) it assumed the space would be available with no checks. My memory isn't that great from this, and I think I misread a lot. So check this for the full story: https://discord.com/channels/671072748985909258/807566022424789022/1279547942989987997
This port is crashing at boot, but the crash appears to be similar enough on qemu/hardware that it could be debugged in qemu.
|
Around 2-3 years ago I got the 1300d 1.2.0 port working against this repo with a few tweaks. Now that the build system rewrite has stabilized some, maybe now is a good time to try again.
Anything copy-pasted or I'm not sure about has been labeled with a 'WTF' comment.