Mods for Garmin 55

lacibaci

Well-Known Member
Joined
Mar 5, 2015
Messages
1,617
Reaction score
818
Country
United States
Any mods to improve bit rate on Garmin 55?
CPU: Ambarella A12A55 SOC
Image sensor: OV4689
 
Unzip the script into the root of the card and start recording the video.
Then check if there are any changes in 1080 and 1080HDR modes.
Check for version 3.70...
 

Attachments

  • autoexec_55.zip
    265 bytes · Views: 13
  • Like
Reactions: gse
Unzip the script into the root of the card and start recording the video.
Then check if there are any changes in 1080 and 1080HDR modes.
Check for version 3.70...
No difference :( Both modes are about 9Mbps with and without autoexec.
 
Scripts may not be supported.
I can change the settings in the firmware, but I can not risk the failure of the
camera after reflashing. Ideally, you would have an ELF to restore the camera...

Try this script now:
Code:
GETINFO script by nutsey (GoPrawn.com).
This script is for getting detailed information about Ambarella A12 SoC based cams.

1. Put autoexec.ash to the root of your memory card.
2. Start your action cam with this card inserted.
3. Wait ~15 seconds and turn the camera off.
4. Check the memory card for the LOG.TXT file.
5. Remove/rename autoexec.ash to disable it from running.

Please share your LOG.TXT file and your camera details.
 

Attachments

  • Autoexec_A12_log.zip
    934 bytes · Views: 7
Here is the log I did some time ago.
 

Attachments

  • log.txt
    33.2 KB · Views: 10
This is strange, but the script in fact should have worked...
It is risky to reflash with a modified firmware without having an ELF on your hands.
Upload short video originals at various resolutions or give media information (MediaInfo).
 
Try again...
Code:
GARMIN DashCam 55 v3.70 - 36Mbit TEST
#=================================================
#2.5.6.0.x.1.4.4.0. .3.0.P
writew 0xA07E7379 0x4210
writew 0xA07E7389 0x4210
#=================================================
#2.5.6.0.x.1.4.4.0. .3.0.P.H.D.R
writew 0xA07E7481 0x4210
#=================================================
#1.9.2.0.x.1.0.8.0. .3.0.P
writew 0xA07E7B29 0x4210
#=================================================
#1.9.2.0.x.1.0.8.0. .3.0.P.H.D.R
writew 0xA07E7C21 0x4210
#=================================================
 

Attachments

  • autoexec_Garmin 55 v3.70.zip
    298 bytes · Views: 7
Try again...
Code:
GARMIN DashCam 55 v3.70 - 36Mbit TEST
#=================================================
#2.5.6.0.x.1.4.4.0. .3.0.P
writew 0xA07E7379 0x4210
writew 0xA07E7389 0x4210
#=================================================
#2.5.6.0.x.1.4.4.0. .3.0.P.H.D.R
writew 0xA07E7481 0x4210
#=================================================
#1.9.2.0.x.1.0.8.0. .3.0.P
writew 0xA07E7B29 0x4210
#=================================================
#1.9.2.0.x.1.0.8.0. .3.0.P.H.D.R
writew 0xA07E7C21 0x4210
#=================================================

:( no change. (no autoexec on the left)

g55.png
 
Ok, I just realized that the first line "GARMIN DashCam 55 v3.70 - 36Mbit TEST" was missing a comment char (#)...
No change still.
Bash:
#GARMIN DashCam 55 v3.70 - 36Mbit TEST
#=================================================
#2.5.6.0.x.1.4.4.0. .3.0.P
writew 0xA07E7559 0x4210
writew 0xA07E7651 0x4210
#=================================================
#2.5.6.0.x.1.4.4.0. .3.0.P.H.D.R
writew 0xA07E7749 0x4210
#=================================================
#1.9.2.0.x.1.0.8.0. .3.0.P
writew 0xA07E7841 0x4210
#=================================================
#1.9.2.0.x.1.0.8.0. .3.0.P.H.D.R
writew 0xA07E7939 0x4210
#=================================================
 
Last edited:
was missing a comment char (#)
Tigra_1.gif
 
I retested all without the first line (commented out) and still no go.
 
Having no idea regarding Ambarella A12 but it might be a good idea to read and store the values on the sdcard you are trying to modify for debugging purposes?
As far as I know ther should be a readw command?
Maybe try something like
readw 0xA07E7559 > c:\reads.txt
This should store the current bitrate in the file if the address is correct?
 
Having no idea regarding Ambarella A12 but it might be a good idea to read and store the values on the sdcard you are trying to modify for debugging purposes?
As far as I know ther should be a readw command?
Maybe try something like
readw 0xA07E7559 > c:\reads.txt
This should store the current bitrate in the file if the address is correct?
I can do that. But how do I know that what I'm getting is a bitrate?
 
You could post it here so we can verify it. Or you use a hex to dec converter and check it by yourself
 
Could not get anything out... Didn't even get anything with the original GETINFO script from nutsey. Maybe they disabled it in the latest firmware?
 
strange, seems like they've disabled it. That would explain why @Falsificator modifications didn't work. Gopro did this some time ago as well, simply disabling autoexec.ash support via firmware update.
 
Thread starter Similar threads Forum Replies Date
O Firmware Modifications 0
Back
Top