unbrick gopro hero2

just note to everyone who is trying to debrick old gpro hero2

I really do not make notes, so it's just from memory, but it can help:

I try to folow this instructions, but as cammera is not responding to anything it didn't work: https://gopro.com/support/articles/fix-for-hd-hero2-stuck-in-v198-update-mode

after hours on google here is solution:

place HD2-firmware.bin and autoexec.ash on your sdcard, put "cd d:\" on first line of autoexec.ash

donwload this 2 github repos:


git clone https://github.com/evilwombat/gopro-fw-tools.git
cd  gopro-fw-tools
make
cp ~/Downloads/HD2-firmware.bin .
./fwparser HD2-firmware.bin > unpack.sh
chmod +x unpack.sh
./unpack.sh HD2-firmware.bin
it is bunch of "dd" commands, output is 14 files names section_1,section_2,section_3, etc

then we need usb tool:
cd ..
git clone https://github.com/evilwombat/gopro-usb-tools.git
cd gopro-usb-tools/
sudo apt-get install libusb-1.0.0-dev
make
 then, place gopro in usb command mode:

- remove battery, disconnect usb cable
- press and hold shutter button
- put battery in camera
- connect usb cable
- front red led should start blinking
- press power button
- release power button, led should stop blinking
- release shutter button,

lsus shout give as device gopro:
Bus 001 Device 090: ID 4255:0001 GoPro

we are goot to go:
sudo ./gpboot --rtos ../gopro-fw-tools/section_3

camera will boot to rtos:
Initializing libusb
Initializing DDR................................... done
Testing DDR....................... passed
Okay, loading and booting RTOS image ../gopro-fw-tools/section_9 on a Hero2 camera
Loading v312-bld.bin to address c0000000
 ... done                   
Loading relocate.bin to address c7000000
 ... done                   
Loading v312-hal-reloc.bin to address c8000000
 ... done                   
Loading ../gopro-fw-tools/section_9 to address c9000000
 ... done                   
Patching in a jump to our relocator..
Okay, here goes nothing...
Exec c0000000: 12 (ok)

on display will be icon with arrow pointing to camera icon, and information about firmware version (v312 in my case)

this time it will not flash any led, so give it few minutes, take a coffe or go for lunch. after while, I came back to camera, disconnected it removed baterry, and try lot of strange thing like make it again and again put autoexec.ash on sdcard without luck.

after same time, i just for hack of it, I removed version.txt from MISC folder and put camera to usb command mode, and boot rtos:
sudo ./gpboot --rtos ../gopro-fw-tools/section_3

it show exact same icon about falshing firmware but, this time, flashing led! \o/

I wait antil flashing stoped, then removed battery and usb cable, press power button and it continue to upgrade !

gopro saved!

again, it's just from memory, so if you try it and make it works, give me comment down below

inside Car Door Logo Light

have same crazy plane to change logo from audi to AUDI B5 Familia

jut for fun, so I ordered one set: from ebay

here is what is inside :

 

OVC3860 how to change name

EDIT:

Arduino library for this module with support of change module name even if AT commands did not works.

recently MBT28 contact me on github about OVC3860 based BT modules [1], we have some chat about configuration of this modules, and mbt pointed to microcontroller.net where someone put link to pdf with instruction how to configure OVC3860 based modules (I put it on my github [2] including executable you need).

I personally tested it, and it works. I try to change baud-rate, name, reconfigure module class, sound settings ....

tested on winXP,win7 and wine on ubuntu

so, how to change name? start software, then connect  serial port to module and start module, it should connect to module automaticaly if you connect your module before starting SW, simply restart module by connecting reset pin to ground. Then push "Read All" button, next find key named  "localname" and change his "value" to  new name of you module, hit "Write selected" Button and you are done.  For other keys take a look at documentation pdf at github [2].


I try to sniff communication, to make it configurable from arduino, to be able set BT name by user on final product ....

[1] https://github.com/tomaskovacik/hw/issues/1
[2] https://github.com/tomaskovacik/kicad-library/tree/master/library/datasheet

vwcdpic v2 firmware for v3 boards

I do not know why it take me so long o realize that i can change pins in v2 firmware to make it works on v3 boards. But better later then never, here it is.

audi chorus - concert: how to recover password

what you need:

motorola cracker :

for serial connection I used cp2102 based adapter from ebay, it has wired RTS signal:

Software part is motorola cracker version 6.x (7 didn't work!!!). It has support for com port from 1 to 4, so change this in advance settings for your usb2UART adapter, then just boot MCU and read eeprom, here is a actual eeprom dump, with code 1790, you can see its on 3 places:

number in eeprom, directly after code (from my observation) can be:

06 - SAFE2 mode, you need to wait 1hour(info from here) to be able to enter pin
08 - SAFE1 mode, you can enter pin code to unlock
A0 - no code required

locked for 1 hour

no code required

standard SAFE mode

UPDATE: I have Motorola MCU with fixed volume problem, so I dump eeprom of this MCU as it has fixed problem, it didn't store volume value in eeprom and so this dump is "clean" of garbage. I try to load this dump to one of affected MCU, just to test how long it take to have volume issue back. For now it's looks ok.

EDIT: it didn't fix it radio volume is garbage at low temperatures, of corse. But I have to try :)

any data are on my github including eeprom dumps.

UPDATE: based on this blogpost: http://www.realitytech.co.uk/rich/?p=192

I try it, it's works kind of. communication was really unstable, but it works for reading eeprom directly after booting CPU, or write simple byte of data, in my case It take 3times to boot CPU and each time write simple byte (0xA0) on positions 3,33 and 63, to disable code protection.

!!1important note!!!  you must connect only 12V and ground on main connector of radio. In my first attempts I have illumination connected to 12V and this makes pin 22 go Low so my additional pull-up did not work.

here are some pictures:

RESET LINE (18)

RX/TX/+12V/pullups on 22,9,11

only 12V and ground is connected in main connector of radio

RX,TX,RTS and ground on UART2USB

openbox x-810 won't boot

another bad caps story with PSU, this time openbox x-810, won't boot, stoped with double dot ":" on display. Measuring on 3.3V rail showed 2V with load. Changing 1000uf and 470uf caps on this rail fix problem, just to be on safe side, I changed all caps on secondary side of psu.

audi FIS 3-line protocol update

   Finaly got time to grab on working configuration, so now I know how cluster tell radio its there and have 2nd display capability.

   Each 5s cluster make 3ms 5V pulse on enable line. after while radio respond with update.

cluster enable signal delay/timing

cluster enable signal

cluster enable signal