Search results

With one hand impaired for typing (i got a xiaflex injection in my right pinky finger yesterday and it's wrapped to my ring finger), I can't type as fast so work today was slow. I tried a few different ways to compile your res.c into your latest RBN, but I keep getting stalls or crashes. Here's...

Hmmm... well, here's the code I compiled: #include <stdint.h> //extern void console(const char *ctx, int a, int b); extern void consoleD(const char *ctx, int a, int b); void res_mod(void) { register uintptr_t s1val asm("s1"); uint32_t *scanSize = (uint32_t *)s1val; char*...

@0dan0 , where do i inject the compiled res.c and crop.c ? i presume i should be using your RBN file for these updates?

@0dan0 , on test build 004, here's the boot output: ERR:AF_Open() #Register AF event table. Id=0 Mode=1 Id=0 Mode=1 Id=0 Mode=1 size :1452 1076 new sze:1452 1089 corner :466 84 new crn:466 78 But the GUI freezes and I can't go into capture mode.

whew! recovered!

@0dan0, is it possible to recover from a failed firmware update? it was in the middle of the erasing and the power plug was loose and power down.

@0dan0 not sure if this is where i should be putting effort, but I'm on the hunt for setting the default 656x480 capture to 1600x1200. so far, all of the memory reads and writes via UART that i'm trying don't change what i'm seeing here: ipl getimepath 0 P1: SW:0 Num:0 H:-559038737...

@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...