gopro-usb-tools
gopro-usb-tools copied to clipboard
evilwombat
GoPro hero 3 silver
Hero 3 SILVER does not work. I would need DDR init sequence and HAL patch.
I do not have support for Hero3 Silver in gpboot, but you may be able to add support yourself. The CPU in the Hero3 Silver (A5L) is similar to what is in the Hero2, so you may be able to re-use the Hero2 boot code. I do not know if the DDR init would be the same, since I do not know what memory part is being used...
Why the hero3 silver does not work if the silver uses the same processor as the hero2?
yes processor is same (A5S). I tried to init DDR Hero 2 and also ddr init alternative for Hero 2 but without result. I always showed failed. camera is in command mode driver works the same as the Hero 2.
The hero2 and hero3 silver may use the same processor, but the DDR chip is probably different. Different DDR chips need different timing settings to work properly.
That is a pain in the neck. I had to reverse engineer them from the BST bootloader (section 0 in the firmware file) by dissembling the code and following through it...
Section_0 of hero 2 and section_0 of hero 3 silver is very little different (only in 7 bytes).
good news. I have two GoPro Hero 3 silver. The second H3S carried DDR test correctly. So DDR init should also be applicable to H3S. you know to help me make a patch for HAL and create relocate.bin file?
Hmmm. I wonder what the 7 bytes are. Are they at the start of the file? Maybe you can find the same bytes in the hero2 DDR sequence and replace them with the ones from the hero3silver file. Changing relocate.bin should not be necessary - that file is independent of the camera version. As far as the HAL patching goes, hmmm. In theory you need the original HAL section from the firmware, as well as a copy of the HAL from a running camera (saved using the savebin command with the right addresses). But, I only do the HAL patching to avoid giving out a copy of the HAL with my software - who knows, it's probably gopro-copyrighted, so I only have the 'differences' in my code. If you can save a working HAL from a working H3S camera, you should just be able to use THAT as your 'patched HAL' file, directly. I am incredibly sleepy right now, but I want to say the HAL lives at address 0xc00a0000 and is (at most) 64k in size.
Thank you for information. Differences in section 0 are: position 0x000c = 0xe5 position 0x000d = 0xb2 position 0x0021 = 0x36 position 0x0022 = 0xb8 position 0x0024 = 0x7a position 0x080c = 0x87 position 0x080d = 0xac
I do not have working H3S. I have only two broken H3S. One broken H3B (boot Linux using your software) and one working H3B.
Sorry for my english.
Hello. If I had to take a wild guess, based on this information, I would try modifying the hero2_alt_ddr_init_seq sequence as follows: Replace "{SEQ_WRITE, 0x60004008, 0x48B7B6A3}," with "{SEQ_WRITE, 0x60004008, 0x48B836A3}," Replace "{SEQ_WRITE, 0x6000400C, 0x01FF3472}," with "{SEQ_WRITE, 0x6000400C, 0x01FF347A}," I am not sure if that will help, but if you are able to recompile the code, that may be something you could try...
I tried but it does not work. H3S is about useless anymore. I use for parts. But I still H3B which is hard bricked (booting linux on it). Is there any way to transfer the system from the functional H3B on hard bricked H3B?
You could try to gpboot the H3Black, and then use an autoexec.ash file containing "firmfl prog d:\HD3.03-firmware.bin" to force the camera to reflash itself. Sometimes the camera has a bit of an identity crisis and refuses to accept new firmware (thinking the header is bad because the camera model won't match, or something silly like that), but this can be overcome with an autoexec.ash command to patch away the silliness. See http://goprouser.freeforums.org/post105043.html#p105043 for an ongoing discussion on this topic.
Thank you for your help. I've found the problem. The camera froze because of damage to the sensor image. When I changed it so the camera works without a problem. Dňa 13.8.2014 13:52 používateľ "evilwombat" [email protected] napísal:
You could try to gpboot the H3Black, and then use an autoexec.ash file containing "firmfl prog d:\HD3.03-firmware.bin" to force the camera to reflash itself. Sometimes the camera has a bit of an identity crisis and refuses to accept new firmware (thinking the header is bad because the camera model won't match, or something silly like that), but this can be overcome with an autoexec.ash command to patch away the silliness. See http://goprouser.freeforums.org/post105043.html#p105043 for an ongoing discussion on this topic.
— Reply to this email directly or view it on GitHub https://github.com/evilwombat/gopro-usb-tools/issues/1#issuecomment-52038500 .
Hi,
evilwombat, can You help me with Hero3 Silver ? It is hard bricked.... I tried stuff that You recommended to marek786, but also without success. But i do have also a working H3 Silver. With Your method I "debricked" at least ten h2, but i do not have solution for h3s. How can a working one (h3s) help me with bricked one ? In details, if You will.... I would be very greatfull....
Or how much work, trouble is for You, to add support to gpboot ? I know, it`s a big ask, but i got to ask....
P.S. Sorry for my bad English
Dear, evilwombat if you add support H3S ans H3S+ to your loader it will be great!
Hi friend Will you please explain how can a working h3s can save a bricked one,is this possible to reverse all? Is there any luck to have DDR timing sequence of h3s and Hal patch.
Thanks
I bought an h3s a while back, but I'm out of the country for another two weeks. I can look when I get back. On Jul 19, 2015 11:18 AM, "nikko20" [email protected] wrote:
Hi friend Will you please explain how can a working h3s can save a bricked one,is this possible to reverse all? Is there any luck to have DDR timing sequence of h3s and Hal patch.
Thanks
— Reply to this email directly or view it on GitHub https://github.com/evilwombat/gopro-usb-tools/issues/1#issuecomment-122638229 .
Hi
i found some time to make a few photos of the problem on Hero 3 silver.
.
.
.
.
after nothing,no reaction like dead with working display.
when i reinstall the battery dead again
I'm sorry, did you say you had a H3 Silver, or a H3 PLUS Silver?
I have a H3 Plus Silver at home, but I have never owned a "standard" H3 Silver (without the "Plus"), so I am not sure what to do with H3 Silver models (instead of H3+ Silver, which are quite different).
It almost looks like you are booting Hero2 firmware on the H3 Silver. Though it may be working initially, I would recommend trying to run with the H3 Silver firmware, instead. I am not sure what the section structure of H3 Silver firmware looks like, but I imagine you can try to boot the H3 RTOS section on your camera in this way.
Sorry I don't have more info - I have never played with H3 "plain" Silver.
On Wed, Jul 29, 2015 at 7:48 PM, nikko20 [email protected] wrote:
Hi i found some time to make a few photos of the problem on Hero 3 silver. [image: image1] https://cloud.githubusercontent.com/assets/13392894/8963711/5b4e23cc-35d6-11e5-8b4a-06c1053e5c7d.JPG.
[image: image2] https://cloud.githubusercontent.com/assets/13392894/8963728/74c9a33a-35d6-11e5-98ec-b3fe87a8588b.JPG . [image: image1 1] https://cloud.githubusercontent.com/assets/13392894/8963745/846e9f48-35d6-11e5-8381-6c215c36678a.JPG . [image: image2 1] https://cloud.githubusercontent.com/assets/13392894/8963756/99fd4c4c-35d6-11e5-9d10-0174acf1fabd.JPG . after nothing,no reaction like dead with working display. when i reinstall the battery dead again
— Reply to this email directly or view it on GitHub https://github.com/evilwombat/gopro-usb-tools/issues/1#issuecomment-126015143 .
I have a Second one that works,is there any way to get a running Hal or else from it? Is this possible?
hi again will you tell me please any possible way to take image from a working HD3S with out mess up my working one? Regards
hi is it possible to load linux on h3s, or not, is zImage only for H3B? can i back up nand dump from my working h3s some help will be nice Thank you
hi friend is there any command or ash file that can make image on sd card,i found this ,is this possible?
d:> savebin d:\memdump.bin 0xC0000000
have a nice day