"Do you work with E1 firmware too?"

Not really as I don't have the cam but I'm looking for a chance to get one used. I've got some experience with other Amba A7/A9/A12/H22 devices.

"I need real address in RAM because I work with memory map."

I can be wrong but it seems like the adj settings are loaded into memory before ambashell script. Anyway you can locate the memory offset for this byte by searching for the surrounding bytes as it is loaded as binary.

@nutsey, yes. But it's difficult because I can't get ambash log (it does not write terminal history to file - reconstructing debug routines that were not compiled is very difficult).

(">" symbol does not work too - example: {command} > c:\1.txt)

@storyboardcreativity '>' and '>>' should work but not every shell command gives output.

Linux to RTOS communication is possible with dbus which seems to be disabled here.

Perhaps @vitaliy_kiselev can get the source code from his friends at z-cam

@zcream

I can try to talk about any small help.

@zcream and @Vitaliy_Kiselev, I already have sources for another camera with Ambarella SoC (full SDK without DSP microcode sources). It helps me to reverse-engineer API calls (obviously, prototypes are the same). E1 sources can be very interesting because of some things I can't understand now:

• We can't set h264 bitrate higher than 65535999 (Real bitrate = our value % 65536000)
• For some reason ambash logging system to file does not work (but code exists and is executed for each command)
• Camera freezes after some time of recording when we increase VBR percent and overall bitrate is higher than 100 Mb/s (no messages, just freeze). Because of no any logging we can't understand the reason. But we know, that 100 Mb/s is NOT a highest bitrate possible (MJPEG works on ~200 Mb/s)

Bitrate problems are not in RTOS code. It's in DSP microcode. But I don't know, how to reverse it :c

Vitali .. or Zcam give the linux code Open Source

@Vitaliy_Kiselev, any info about SDK?

@Vitaliy_Kiselev, you said:

_ Yet I can try to talk about any small help._

Well, they made a lot of promises and released a camera with a lot of issues (sync sound being one of them). Then release a new product and only support the E1 when resources allow. They never officially out up FW 0.31 on the E1 support page and make you download it through google drive. It's all a little suspect in my humble opinion. Keep up the good work @storyboardcreativity!

@CFreak, I've made first version of RTOS logging firmware version and... I bricked my camera :DDD

Camera still starts up without sd-card (when it can't find sd-card, it does not try to write log) - I can reupload old firmware. But it's funny :)

Z-Cam supported the crappy E1 (that most people bought for $200 and then whined about how it wasn't as good as more expensive cameras) (I was on the kickstarter and it was a $700 camera for me - which I hated, sold, and never have to worry about again) with new firmware updates for longer than other companies supported much more expensive cameras. I wouldn't expect much more in the way of updates for the E1.

It also seems like a number of the problems with that camera came from their choice to use a third-party chipset which, itself, had a number of problems.