Search results

@0dan0 it's worth mentioning that this is the module list on the Firmware D model. Note the awbOs04D10--that looks very sensor dependent. Was there an equiv for the older sensor in the A, B, and C models? module list: dma Engine DMA status drvdump Dump driver...

@0dan0 here's the latest console output to your firmware D. I'm calling this test build 003: Hello, World! > TestProtection begin EDesEn_Crypt pass SC CRC PowerOnCheck: OK! Enter DSC bind - begin! bind - end! event loop - begin! ERR:ramdsk_setParam() No Implement! uiEvt 1 Init...

ok, thanks for another build to test. here's the section with your highlights, @0dan0 : a1-3:2564 1444 1244 a1-3:466 84 8 a1-3:1452 1076 8 Full output from Hello World to the kernel crash: Hello, World! > TestProtection begin EDesEn_Crypt pass SC CRC PowerOnCheck: OK! Enter DSC bind -...

As I'm about to dive into research on the new image sensor, Claude.ai put together this comparison table for me: OmniVision OS04D vs Aptina AR0330 - Sensor Research Summary Key Specification Differences Feature AR0330 (Types A/B/C) OS04D10 (Type D) Resolution 3.15 MP (2304×1536) 4 MP...

Where should I add prints to the code? As I don't know what you've added or where, I'd need some guidance from you on that, @0dan0. I did re-test the new BIN and even made a new BIN from the RBN file in your ZIP, but I got the same result.

As I'm new to the community, I'm not sure if there's a documented process for doing a full overscan, but I re-installed stock firmware D and zoomed out all the way and centered the film in the frame. Is this what you want, @0dan0 ?

I’ll test again, but that’s where the process froze. We’ll get this solved! Did you determine all four type 4 variables for your host.c?

Here’s the sensor on my D unit.

Thanks for the effort, @0dan0 ! No hard crash, but the buttons are unresponsive on the unit. Here's the complete output from the "Hello World!" string: Hello, World! > TestProtection begin EDesEn_Crypt pass SC CRC PowerOnCheck: OK! Enter DSC bind - begin! bind - end! event loop - begin...

In my hunt for the auto exposure function/hook in Ghidra in Firmware D, I found this function. The most interesting bit is at the end where there's a jal instruction (not shown in this copy of the function) to printf calls: void FUN_802b6a08(void) { uint uVar1; int iVar2; undefined4...

Ok, thanks for providing the source code for the RBN utilities, @0dan0. Indeed, the new command works and stops the motor! mem w 80ddc670 30 As an aside, I'm seeing this error continuously during capture. Is it normal? ERR:UIFlowWndMovie_OnTimer() Record400MinTimeOut 0 I've attached...

Thanks 0dan0! I ran that mem command, and the motor did not stop. To be clear, the BIN you provided is your code update for the motor shutdown hack and should be inserted at whatever address we find in Firmware D that stops the motor? Also, should we have a dedicated thread for code development?

As I continue work to find the AE hook to run 0dan0's custom code, I wanted to share my current bash script to update 0dan0's freed up space version of the Stock D firmware. I typically like to use Ubuntu (or wsl on Windows 11) to run Linux commands, and compile there too. Are there Linux equivs...

I've done a lot of video compression with my professional work, and I use ffmpeg regularly. YouTube is going to recompress anything you upload, so as a mezzanine format, high-bitrate H.264 is the way to go. For archiving locally, or for my own players/streaming setups, I use ffmpeg and libx264...

Thanks, @0dan0! I confirmed that the button address is correct at 0xA0E8b7d0 by seeing 01 for up arrow and 02 for down arrow. The ISO address doesn't seem to be correct, but I'll keep looking around that range. I haven't been able to successfully tie into an auto exposure hook yet---I found...

@0dan0 , were you able to see the reelType value in the D.BIN dump I provided? I've finally got a hook calling into your hist.c code, but I'm getting a crash in the unit. I probably don't have the frame number pointer correct, or it's not finding reelType where it thinks it should be.

Thanks for your patience with me, @0dan0 ! I've attached the compressed D.BIN file that I grabbed from my D unit. I used your "freed up space" version of the D RBN (shows "Type D - WIP" on boot screen). As far as I can tell, the LCD address is still the same. When I ran the mem commands you...

I've ported (what I believe are) the core improvements from 0dan0's Type C firmware to Type D hardware. The device now runs 1600x1200 @ 18fps with improved auto exposure, stable with no motor issues. The following summary was created by Claude.ai with some notes of my own. What's Working ✅...

Device: Kodak Reels Type D (H-series, Serial: H2825148BK...) Achievement: 1600x1200 output resolution working on D variant hardware! Background The Type D variant has been unsupported by existing firmware mods due to significant differences from A/B/C variants. After extensive reverse...

@0dan0 - Perfect timing! I've been working on D variant analysis. What I have: Stock D firmware (H2825... serial) NVM base address: 0x80E0D600 (found via Ghidra analysis) Device type should be 4 (as you predicted) Successfully injected manual WB code already (device boots and captures, and...