Topics

Hi all.

I have'nt been programming for a while, progres on the 40D is equal to none. The open beta ML version is 70% done, the reason being the camera is old, different from the newer camera, and last but not least, the camera model is really old. I have learned alot about ML firmware, and I think it's time to utilize this and move on to a newer unsupported camera.

I would like to hear from other people which camera would be interessing to get into the ML "program". I'm not in a rush, as I need to sell some old HAM gear inorder to get additional cash, but I would estimate I can spend around 800€ on a camera body. Timeline for getting a new body is approx 31th of December 2022.

Which camera's are interessing for this budget, and why ?

[How about this setup]

Hi all, I need a debugger setup for debugging QEMU.

I never liked gdb text interface, it's rubbish! I'm used to work with Microsoft debugger for windows programs and Segger's Ozone debugger with the J-Trace PRO debugger for arm development, and nothing compares to this combo, tried many others, but the last combo for embedded is really power full. Here's an long list of visual frontends for GDB is long https://sourceware.org/gdb/wiki/GDB%20Front%20Ends but if you are used to working with said tools, you end up not debugging at all on QEMU, and qprintf becomes you best friend. But in 2020 (at work) we're started to use Visual GDB, a good alternative. It ain't free, but there's and 30 day free trail, and after that you'll need to pay 79€, that's cheap. It can be used with Microsofts free VS Community Edition.

How about this setup
* Microsofts free VS Community Edition.
* Visual GDB
* Ghidra (or IDA)
* QEMU (ML version)

Work flow

Ghidra (or IDA for that matter)
* Disassemble/analyze the camera ROM with Ghidra and let Ghdira auto name all function stubs & data
* Create a Ghidra script to perform advanced function renaming, auto rename function that has a DebugMsg(x,y,"[??] ...")
* Do you own renaming ...
* Use Ghidra2Dwarf to export symbol file


Scripts
* convert Ghidra text file into dwarf debugging file
* convert the camera ROM into a camera elf file
* inject the newly created dwarf file into camera elf file

QEMU
* run the camera elf file in QEMU

Visual GDB
* Connect to remote target
* Debug ...

Anyone tried this combo ? suggestion, ideas are welcome ..   

Wikipedia just deleted the best overview of canon eos products    Accordingly to wikipedia, it's a fan page. former url : https://en.wikipedia.org/wiki/Comparison_of_Canon_EOS_digital_cameras.

Any other alternatives (other than wayback mashine ?)

https://web.archive.org/web/20200411023301/https://en.wikipedia.org/wiki/Comparison_of_Canon_EOS_digital_cameras

I wish to share a homepage I recently found which is pretty cool. Its a complete online arm simulator, from a man called Henry Wong in Canada, I'm really impressed and the interface is really good. Those who want to learn armv7 assembly language (gnu-as) without setting up anything at all, or just for quick tryouts, tricks, hacks and similar, this is indded a good place to start.

https://cpulator.01xz.net/
https://cpulator.01xz.net/?sys=arm
https://www.01xz.net/wiki/Project:About