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

I'd tried an ls on A: and Z: but no files found - just doing some work and will have another play in a bit :)
 
It looks like there is something funny with this one mate - I can't see any files on any drive letters other than the memory card D:

I'm guessing the user the executes the autoexec.ash doesn't have any permissions - on Z: all it can see is one 0 byte file:

Code: 
f---- Nul  0 1980 00:00:00            0

I've done a dig around and see the following reference in the file:

E:\A7L_c6000a_g90_sdk

I looks like szdome are responsible for this one so I've asked them if they can help with a firmware file.
 
Code: 
logo.jpg    44534
C6000A_ON.jpg    89091
C6000A_OFF.jpg    57127
CASKA.jpg    54972
BLACKVIEW.jpg    24028
LINGDU_OFF.jpg    12797
LINGDU_ON.jpg    12835
start10.jpg    44534
invalid.jpg    14281
plist_effect_cut.jpg    2624
plist_effect_fade_black.jpg    1622
plist_effect_fade_gray.jpg    1625
poweron_12k.pcm    45600
poweroff_12k.pcm    28800
shutter_12k.pcm    6176
short_shutter_12k.pcm    1086
optone_12k.pcm    9300
error_12k.pcm    13920
poweron_11k.pcm    41896
poweroff_11k.pcm    26460
shutter_11k.pcm    5676
short_shutter_11k.pcm    1000
optone_11k.pcm    8546
error_11k.pcm    12790
poweron_8k.pcm    30402
poweroff_8k.pcm    19200
shutter_8k.pcm    4120
short_shutter_8k.pcm    724
optone_8k.pcm    6202
error_8k.pcm    9282
1_48k.aac    171
1_44k.aac    185
1_32k.aac    256
2_48k.aac    342
2_44k.aac    372
2_32k.aac    512
2_48k.ac3    768
2_44k.ac3    768
2_32k.ac3    768
6_48k.ac3    1536
6_44k.ac3    1536
6_32k.ac3    1536
dec_cc_3D    16384
dec_cc_in    2304
cour.ttf    4595228
bitmaps.bin    7961752
strings.bin    348736
A7L_CC_reg_1_1.bin    18752
calib6.bin    65536
calib16.bin    65536
A5S_CC_reg_ver_1_1.bin    18752
A5S_default_cc_3d_video.bin    17536
A5S_default_cc_3d_still.bin    17536
A5S_default_cc_3d_hiiso.bin    17536
param_image_param_release.bin    0
param_aaa_param_release.bin    0
param_adj_photo_preview_param_release.bin    0
param_adj_video_tv_param_release.bin    0
param_adj_video_pc_param_release.bin    0
param_de_still_param_release.bin    0
param_de_video_param_release.bin    0
param_de_still_multi_param_release.bin    0
param_de_video_multi_param_release.bin    0
param_adj_still_fast_param_release.bin    0
param_adj_still_low_iso_param_release.bin    0
param_adj_still_high_iso_param_release.bin    0
param_adj_still_mf_hiso_param_release.bin    0
param_adj_piv_low_iso_param_release.bin    0
param_adj_still_mid_iso_param_release.bin    0
param_adj_still_hdr_hiso_param_release.bin    0
param_adj_still_hdr_miso_param_release.bin    0
param_adj_still_sr_param_release.bin    0
param_set01_param_release.bin    0
param_set02_param_release.bin    0
param_set03_param_release.bin    0
param_set04_param_release.bin    0
param_set05_param_release.bin    0
A5S_CC_3d_color_0_video_0.bin    17536
A5S_CC_3d_color_0_video_1.bin    17536
A5S_CC_3d_color_0_video_2.bin    17536
A5S_CC_3d_color_0_video_3.bin    17536
A5S_CC_3d_color_0_video_4.bin    17536
A5S_CC_3d_color_0_still_0.bin    17536
A5S_CC_3d_color_0_still_1.bin    17536
A5S_CC_3d_color_0_still_2.bin    17536
A5S_CC_3d_color_0_still_3.bin    17536
A5S_CC_3d_color_0_still_4.bin    17536
A5S_CC_3d_color_1_video_0.bin    17536
A5S_CC_3d_color_1_video_1.bin    17536
A5S_CC_3d_color_1_video_2.bin    17536
A5S_CC_3d_color_1_video_3.bin    17536
A5S_CC_3d_color_1_video_4.bin    17536
A5S_CC_3d_color_1_still_0.bin    17536
A5S_CC_3d_color_1_still_1.bin    17536
A5S_CC_3d_color_1_still_2.bin    17536
A5S_CC_3d_color_1_still_3.bin    17536
A5S_CC_3d_color_1_still_4.bin    17536
A7L_high_iso/08_cc_reg_l4c_edge.bin    2304
A7L_high_iso/09_cc_3d_l4c_edge.bin    16384
A7L_high_iso/17_fir1_mix_4x.bin    256
A7L_high_iso/18_fir1_mix_2x.bin    256
A7L_high_iso/31_fir1_l4c_edge.bin    256
A7L_high_iso/32_coring_l4c_edge.bin    256
A7L_high_iso/35_alpha_unity.bin    512
file count    104
There must be files (they are "available" using romfs command) :P
Otherwise the cam wont boot. RFS contains strings, font and ui gfx.

Only those "param_xxx" files are Zero-files. Don't know whats the matter with them.
 
I was trying to use romfs save to get them off the camera but it looks like that command may be to save to the camera (and not the SD?)

Just playing :)

romfs usage is
Code: 
Usage: ls - list ROMFS files
       inodes - list ROMFS inode tree
       load [name] [addr] - load data to memory
       save [slot] [name|all] [fpos]- save file to storage
       log_init [slot] - log the statistics of ROMFS initialized flag
 
I'd recommend to solder an uart converter to your pcb :P Otherwise you have to mess around with the ash script all the time :D

I forgot to mention this in the post before: There are no "users" available in the os. you can say you are always root and autoexec.ash gets executed as root as well.
 
Ah I got it!

Code: 
romfs save logo.jpg d:/romfs

That saves the file into the romfs folder on the card :)
 
then do this with all files :D
If you don't get the fw from Dome we could assemble one xD
 
That confused me - I had that many commands I picked the wrong one!!

It should be:

Code: 
romfs save d:/ start10.jpg

Got 95% of the files - just missing the A7L_high_iso folder now :)
 
I'm unsure what they do and why they are needed... But we can create thos 0kb files manually. Will look into it after lunch :D
 
Oops I didn't realise that was the time - I'm headed up to see the other half so that's a 2 hour drive!

Thanks for the help today as it looks like we've made some good progress with this one :)

Sounds like there is another firmware version out there which spytec has too - who knows we may get a full file from szdome too which we can compare :)
 
Well, I assembled errr...... something. Maybe we can call it G90 20140425 firmware. Maybe.
I had to guess a lot of values - I think they are the same for all A7 based devices.

Red marked values (date and length are from g90) have been taken from 0803 :D
g909dc1xklg2b.png


Also those exported files had a lot of extra data. I tried to realign them and to remove the unneeded leading and trailing junk. Now the structure looks like A7 partitions from other A7 dashcams. Then I created a flashable Firmware binary. It will Flash but I'm not sure if it will work. I reccomend to wait till I can compare it to a real G90 Firmware.
DL: dc.p-mc.eu/a7tool/tests/20140425-maybe-g90.bin
 
I don't have any knowledge about firmware customization. I hope someone will place here helpful information regarding G90.
A month ago there was also avilable (I think, by uploader mistake) .elf file for this device. If you find this file interesting I can share it. Full file name is: amboot_hal_kernel_romfs_dsp_release.elf
 
That's absolutely brilliant thank-you - after all that you make it look so easy :D

Not sure how the firmware numbering works on these - like you I have r93MP and the version on the website is r4396.

I've not flashed it yet but had a look in the file and this r4396 is a few days newer:

r4396: Administrator@haitaobi Wed Apr 30 10:03:25 2014
r93MP: ykhe@ykhen Fri Apr 25 10:49:42 2014
 
If you could share the elf file that would be great please - I've managed to get the device into Ambarella dev mode - just hold the right button as you connect the device to your PC and then it will talk to DirectUSB which you can use with the elf file in case it gets corrupted :)

SZDome got back to me as well and they're going to share the latest file that they have so as soon as I have anything I'll put it up here :)

This r4396 firmware works great with A7Tool too - can't believe I just got that date from a hex editor and could just have loaded it into A7Tool - user error :D
 
OK that has flashed fine - the language is reset to Chinese on startup which is easy to change, the options appear the same - just grabbing a frame off now.

Startup logos change to the Blackview ones from the car otherwise everything else appears very similar but thank-you :)
 
reverend said:
If you could share the elf file that would be great please - I've managed to get the device into Ambarella dev mode - just hold the right button as you connect the device to your PC and then it will talk to DirectUSB which you can use with the elf file in case it gets corrupted :)

SZDome got back to me as well and they're going to share the latest file that they have so as soon as I have anything I'll put it up here :)

This r4396 firmware works great with A7Tool too - can't believe I just got that date from a hex editor and could just have loaded it into A7Tool - user error :D
Click to expand...

Here you go: https://mega.co.nz/#!PRBRxD7C!xPFPKrk3yHQP4g9MA7gzCgylH-rJqTckDw7C8tG72ns
.zip file contains both .bin and .elf file. I think it is r4396 version (date 30.04.2014).

PS Thank you for checking the version r4396. I have to be careful, the G90 is the only dashcam I own right now and I don't think it will change any time soon :)
 
I'll get some footage posted - maybe they are the same but different logo as they are so close but we will see over the next few days :)
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top