supplierdeeply

GoPro HD HERO 1080 Firmware

  • 102 Replies
  • 107557 Views
Re: GoPro HD HERO Firmware
« Reply #20 on: 01 / February / 2011, 04:24:33 »
Advertisements
Just to let you know that a new firmware for the GoPro LCD BacPac became available for download:

http://gopro.com/support/hd-hero-firmware-update/

So now there are two firmware versions out to compare.

Jan
DIY-streetview.org - Do It Yourself streetview!

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: GoPro HD HERO Firmware
« Reply #21 on: 01 / February / 2011, 13:06:14 »
Just to let you know that a new firmware for the GoPro LCD BacPac became available for download:

http://gopro.com/support/hd-hero-firmware-update/

So now there are two firmware versions out to compare.
Hehe, thats timing...
I was right about new firmware.

Firmware Version: v01.01.46
Firmware File Date: 30.01.2011
Firmware Size: 8.001.536 Bytes

Kind of strange, last Firmware Update was v02.05.11, File Date: 31.08.2010, Size: 6.967.296 Bytes

I will take a closer look at it soon.

LCD BacPac doesn't look bad. Not shure if i need one for regular use but hacking ;-)
« Last Edit: 01 / February / 2011, 15:37:24 by pixeldoc2000 »

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: GoPro HD HERO 1080 Firmware
« Reply #22 on: 01 / February / 2011, 15:32:27 »
I did firmware update from v02.05.11 to v01.01.46.

UART Log reveals some more details...

firmware.bin consists of different part of cause:
- kernel
- rom / romfs
- DSP

Code: [Select]
firmware program pre-process
nvd-pref object 0 load
nvd-pref backup success
nvd-calib object 0 load
nvd-calib object 1 load
nvd-calib object 2 load
application receives user command 0xFFFEA00A
nvd-calib object 3 load
nvd-calib backup success
firmware program pre-process success
could also mean:
- kernel
- rom
- DSP
- romfs

Looks like ROM is first object in firmware.bin .

Next interessting output:
Code: [Select]
kernel image found in firmware!
romfs found in firmware!
DSP microcode found in firmware!
        length:         4300020
        crc32:          0xb921db2a
        ver_num:        0.1
        ver_date:       2011/1/27
        img_len:        4299764
        mem_addr:       0xc0100000
        flag:           0x00000000
        magic:          0xa324eb90
verifying image crc ... done
program pri to NAND flash ...

program ok

        length:         2027776
        crc32:          0xeb472f27
        ver_num:        2.0
        ver_date:       2011/1/27
        img_len:        2027520
        mem_addr:       0x00000000
        flag:           0x00000001
        magic:          0xa324eb90
verifying image crc ... done
program rom to NAND flash ...

program ok

        length:         1668828
        crc32:          0xfaa2070d
        ver_num:        1.0
        ver_date:       2011/1/27
        img_len:        1668572
        mem_addr:       0xc34fffb0
        flag:           0x00000000
        magic:          0xa324eb90
verifying image crc ... done
program dsp to NAND flash ...

program ok


------ Report ------
Program to kernel success
Program to romfs success
Program to DSP success
firmware program post-process
firmware program post-process success

ROM Memory Address: 0x00000000 , length: 2027776
pri (Kernel / Loader ?): 0xc0100000 , length: 4300020
DSP Memory Address: 0xc34fffb0 , length: 1668828
Memory Address probably refere to NAND Address.

Of cause its still possible some relocation takes place on startup.

Looks like Firmware downgrade is also possible without any tricks. I was able to flash back to v02.05.11 after v01.01.46.

Compiler Config Dump shown 3D Stereo support is also included:
Code: [Select]
ENABLE_3D_MASTER_SLAVE_FUNC=y
Also v01.01.46 permanently output this to UART:
Code: [Select]
Initialize USB BITSTREAM Class
Finalize USB BITSTREAM Class
Maybe we have some Webcam / PTP stuff going on...

In romfs only bitmaps.bin and strings.bin files changed.
« Last Edit: 01 / February / 2011, 16:03:55 by pixeldoc2000 »

Re: GoPro HD HERO 1080 Firmware
« Reply #23 on: 02 / February / 2011, 06:23:41 »
Compiler Config Dump shown 3D Stereo support is also included:
Code: [Select]
ENABLE_3D_MASTER_SLAVE_FUNC=y

That is EXTREMELY interesting and the first time that such information has been discovered.

I would be very interested if you find-out any more about this.


David


*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: GoPro HD HERO 1080 Firmware
« Reply #24 on: 04 / February / 2011, 13:02:04 »
I would be very interested if you find-out any more about this.
GoPro anounced GoPro Hero 3D. Basicly it two GoPro with 3D Hero link cable in a special case: http://ces.cnet.com/8301-32254_1-20027589-283.html .
ENABLE_3D_MASTER_SLAVE_FUNC=y probably means Firmware v01.01.46 already has 3D (camera sync) support.
If you are interested in something else you have to be more specific.

I didn't have much time to look at the firmware yet.

Also i still not shure about how to identfy the differens part in firmware files like rom, romfs, kernel, dsp...

Re: GoPro HD HERO 1080 Firmware
« Reply #25 on: 05 / February / 2011, 07:24:16 »
I am curious if anyone has any insight into the HD HERO 960 version. As far as I have been able to gather, it is identical in hardware (minus the extension port) and limited in the firmware only.

Has anyone tried to "unlock" it (adding the higher resolution and framerate modes) by modifying the 1080 firmware? Does anyone here know if it is even possible?

Any pointers in the right direction are greatly appreciated!

Re: GoPro HD HERO 1080 Firmware
« Reply #26 on: 08 / February / 2011, 09:40:42 »
Hi, some now commands to record take snapshot with the GoPro over the terminal ?

Re: GoPro HD HERO 1080 Firmware
« Reply #27 on: 08 / February / 2011, 10:01:25 »
Hey hey I found the command to start/stop recording:

t gpio 43 sw out0
t gpio 43 sw out1

this command simulate the button press !!! It work's well.

I found it dump all gpio's with

t gpio dump

Press the record button and dump again.

Now i search for the other functions....


Re: GoPro HD HERO 1080 Firmware
« Reply #28 on: 08 / February / 2011, 10:09:32 »
Here is the dump:

--- Start of recording: 08.02.2011 16:02:46 ---
                                                                                
a:\>                                                                            
a:\>  t gpio 43 sw out0                                                        
a:\>  application receives user command 0xFFFE000C                              
app_rc_qmode_selector ==> mres:28 CBR 12.0 Mbps                                
No EXT was registered.                                                          
No EXT was registered.                                                          
audio frame size: 1536                                                          
Video bitstream buffer Reserved time (100ms) = 81                              
Video descriptor buffer Reserved time (100ms) = 409                            
Audio bitstream buffer Reserved time (100ms) = 81                              
Audio descriptor buffer Reserved time (100ms) = 600                            
[yqx]rec_dsc_sensor.c no 3d                                                    
bits buffer addr = 0xC24BD3E0                                                  
desc buffer addr = 0xC34F88E0                                                  
bits buffer addr = 0xC2429DC0                                                  
desc buffer addr = 0xC34ED4A0                                                  
tlv320aic3101_sfreq_conf()                                                      
audio_enc_info->encoder_type=32                                                
start_enc_time = 2745396                                                        
dsp encoded frame reset, time = 2745522                                        
fmt_isomux_open(): sizeof p_movie 1104, sizeof ctx_fmt_isomux_t 528            
ISO muxer[0] takes 2 ms to open the index file (size=2314556 duration=2949) 3840
000 73725 storage_freespace= 22183616 vdelta 3600.000000                        
fmt_isomux_open done                                                            
G_storagemon.reservspace 9580                                                  
FRMON_VDSP: 3040ms past validating Vdsp monitor.                                
                                                                                
a:\>  t gpio 43 sw out1                                                    

a:\>  application receives user command 0xFFFEA00C                              
                                                                                
a:\> t gpio 43 sw out0                                                        

a:\>  application receives user command 0xFFFE000C                              
AMBA_FRMON_AVSYNC: Stop recording. encoding frate: 25.000000frm/sec            
total encoded frm: 704frm, expected encoded frm: 703.988265frm                  
dropped audio smp: 0, upsampled audio smp: 0, audio smp freq: 48000smp/sec      
[AIN] FadeOut done                                                              
tlv320aic3101_sfreq_conf()                                                      
 Isomux met EOS 4 ffffff 0 stream_id=0                                          
closing mp4..                                                                  
Before insert, p_movie->end_pos=45347870                                        
ISO muxer takes 143 ms to close the ISO file                                    
isomux close done                                                              
No produce thumbnail picture                                                    
[app_check_special]sys_status.mvrecover=0                                      
                                                                                
a:\>  FRMON_VDSP: 3040ms past validating Vdsp monitor.                          

a:\> t gpio 43 sw out1
                                                          
a:\>  application receives user command 0xFFFEA00C                              
                                                                                
a:\>                                                                            
--- End of recording: 08.02.2011 16:04:24 ---


I need a connector for jtag/uart connection or a good idea to connect my wire to the GoPro board you need clam hands and eagle eyes by solder the wires.
 :blink:


« Last Edit: 08 / February / 2011, 11:00:01 by Stefan »

Re: GoPro HD HERO 1080 Firmware
« Reply #29 on: 08 / February / 2011, 11:31:40 »
Stefan,

well done!

Just to remember that there is another thread regarding the GoPro HD and it's BUS socket over at goprouser.freeforums.org.

Wiring info starts at page 6 and goes on for a few pages:
http://goprouser.freeforums.org/the-gopro-hero-hd-bus-interface-t797-50.html

I took the liberty to re-post your findings:
http://goprouser.freeforums.org/post13030.html#p13030

Regarding the plug for the BUS socket, its the
DD1P030MA1 from JAE Electronics.

read this and the next few postings for it:
http://goprouser.freeforums.org/the-gopro-hero-hd-bus-interface-t797-80.html#p12428

I assume your camera was in video mode when you send the command?
Can you please set camera to still image mode, and test if it works too?

Me personally I need to release 5 GoPro HD for still images synchronized. So far I am wiring cables to the release buttons. But the cameras seem not to release 100% synchronized.

Do you think one can send the terminal commands using the BUS socket to 5 cameras at once somehow?
I am OK with an embedded board or Arduino or something like that for this.

Thanks,
Jan
« Last Edit: 08 / February / 2011, 12:32:58 by janmartin »
DIY-streetview.org - Do It Yourself streetview!

 

Related Topics