[App] AFT 1.3.2 - Ambarella firmware editor (development paused)

Can somebody explain me the exposure calculation with AE table?
I know that the values represent the sensitivity of the fields, but how is the exposure calculated with different modes (spot, center weighted, average, etc,)?
 
Uhm I don't get what you want to know, sorry
 
Okay I wil try a different way. What is the weighting between the values 1..5?
eg. I have a table with values of 1, 2 and 3.
1, Does it mean that the segment with 2 have the double sensitivity as the segmwents with 1?
2, And the 3 is only 1.5x more sensitive as the 2?
3, What if this is the measured light brightness in order of segment sensitivity: 2>3>1. How would be the exposre here calculated? Althoug the 3 is less bright tha 2, would it have more weight in the exposre calculation?
 
Can I change bitrate using this program on A12 chipset firmware?
 
Makabra said:
Can I change bitrate using this program on A12 chipset firmware?
Click to expand...
Hi, I have no idea about A12 but you could try to load the firmware with AFT and tell me if it is even able to parse it correctly.
 
Wow! It runs fine even on my MacOS X!
 
Tobi@s said:
Hi, I have no idea about A12 but you could try to load the firmware with AFT and tell me if it is even able to parse it correctly.
Click to expand...
Its not loading firmware file properly. But could I change it with any other softare? And another question. Is it possible to change in my firmware one option? I want my SOS button to protect longer files. Currently its only 1 minute and i want 3 minutes to be protected when i press SOS button on my camera.
 
Makabra said:
Its not loading firmware file properly. But could I change it with any other softare? And another question. Is it possible to change in my firmware one option? I want my SOS button to protect longer files. Currently its only 1 minute and i want 3 minutes to be protected when i press SOS button on my camera.
Click to expand...
I dont think that modifying the file protect duration is easily possible. I don't know any tools that are able to deal with that chipset, neither..
 
Hello, I have a drone DJI Phantom 2 vision +, I have the camera installed on a modified firmware by Falsificator in this thread July 2015, it works perfectly. I come to you to see if you can fix a small problem. Apart from the firmware was made (in other forum) a mod for improvements softening image outlines, works very well but has a bug that is accelerating the image, that is a real minute (60 seconds) the recording to 47 seconds. Could someone fix this?
Thank you. I attached the mod.
The chip is ambarella A5S and the sensor is Aptina MT9F002 (found while reading strings in PRI.bin and some debug output commands)

mod:
https://mega.nz/#!NUgRSQDT

Thanks to Güeria author mod.
 
I've tried this with AFT 1.3.2 and (because AFT said it was out of date) with AFT 1.3.3
I have a CDV300S. Firmware version from menus is listed as v0.4.8. I used the following to pull what I believe to be a good backup of the firmware:
Code: 
firmfl gen 6 bst bld hal pri rom dsp d:\backup.bin > output.txt
rm d:\autoexec.ash
drives > drives.txt
Opening the A7 firmware and choosing to extract all results in the following partitions:
Code: 
[~] adminx > ls ~/Desktop/partitions
BLD.a7h        BST.a7h        DSP.a7h        HAL.a7h        HEADER.a7s    PRI.a7s
BLD.a7s        BST.a7s        DSP.a7s        HAL.a7s        PRI.a7h        RFS.a7h
I can load bitrates from PRI.a7s, and I can edit bitrates, and I can apply the changes, reopen the file, and see that they've saved... but when I want to build the new ROM/firmware, I get an error (see screenshots) on both Mac and Windows.

I just got this dash cam, hoping it would be better than my trusty G1W. So far, I'm not at all impressed, so I was happy to see that there may be a solution. I do like the form factor though.

I might be doing something wrong, but it looks like AFT may not yet be compatible with the version of firmware. Can I help you, or can you help me? Thanks!

If this is covered in in a thread somewhere already, feel free to scold me appropriately. ;-)

Edit: I tried attaching the firmware binary, but that's a no-go. I'm sure I can get it to you if you want to PM me though.
 

Attachments

  • firmware-information.png
    firmware-information.png
    37.2 KB · Views: 25
  • build-error.png
    build-error.png
    30.3 KB · Views: 23
Last edited:
Gentlemen!
And under the android(Novatek) that anything exists?
 
Last edited:
silen7guardian said:
I've tried this with AFT 1.3.2 and (because AFT said it was out of date) with AFT 1.3.3
I have a CDV300S. Firmware version from menus is listed as v0.4.8. I used the following to pull what I believe to be a good backup of the firmware:
Code: 
firmfl gen 6 bst bld hal pri rom dsp d:\backup.bin > output.txt
rm d:\autoexec.ash
drives > drives.txt
Opening the A7 firmware and choosing to extract all results in the following partitions:
Code: 
[~] adminx > ls ~/Desktop/partitions
BLD.a7h        BST.a7h        DSP.a7h        HAL.a7h        HEADER.a7s    PRI.a7s
BLD.a7s        BST.a7s        DSP.a7s        HAL.a7s        PRI.a7h        RFS.a7h
I can load bitrates from PRI.a7s, and I can edit bitrates, and I can apply the changes, reopen the file, and see that they've saved... but when I want to build the new ROM/firmware, I get an error (see screenshots) on both Mac and Windows.

I just got this dash cam, hoping it would be better than my trusty G1W. So far, I'm not at all impressed, so I was happy to see that there may be a solution. I do like the form factor though.

I might be doing something wrong, but it looks like AFT may not yet be compatible with the version of firmware. Can I help you, or can you help me? Thanks!

If this is covered in in a thread somewhere already, feel free to scold me appropriately. ;-)

Edit: I tried attaching the firmware binary, but that's a no-go. I'm sure I can get it to you if you want to PM me though.
Click to expand...
So theres no RFS.a7s file? I guess the backup does not include the rom image. Maybe you could share the firmware backup so i can have a look at it?
 
Strange, it worked for me. Could you precisely describe what you are doing (step by step)?
 
Tobi@s said:
Strange, it worked for me. Could you precisely describe what you are doing (step by step)?
Click to expand...

I was following the steps in this video:
Except it turns out I'm an idiot and wasn't actually following all the steps. I didn't do the ROM/RFS -> Extract ROM to disk part.

Sorry for the trouble, and thank you for your help!
 
Can somebody explain which line in the bitrate editor should I change if I want to increase the bitrate for a specific resolution?
there are way too many lines in the editor, why?
 
You must log in or register to reply here.
Back
Top