streda, 16. novembra 2016

how-to unpin miniiso connector

 You neet paper click with diamer around 0,8mm , cut two around 2cm long peaces





Insert them and push with pliers as far as they go







then wire should came out easily.


On balck 20pin connector do not forget to unlock it first:

this is how its looks locked:

 unlocking:
 other side unlocked:

HOW-TO connect VWCDPIC adapter

Black 20pin miniiso connector 

this connector has pin lock which need to be unlocked befor inserting pins, this is how it's look from booth sides:


Use screwdriver os something flat to push lock on side which is on previous picture, lock will slide inside few milimeters:


On the other side it will popout:


This is how its looks inside of connector:


and after unlock:


CD changer ground pin in mini iso connector


If your radio has ground pin(CD-GND) as this one has (in this case audi concert2) connect emulator like is on next pictures (but insert pins all way down). Take attention to power pin, red one, it must go to switched output pit, in case you put it on constant +12V emulator will probable not works, maybe for first time.



audio cable goes here:



CD changer ground in 10pin tel/nav connector


if your radio is for example audi chorus/concert1, ground pin for CD changer is on 10pin connector on this picture, upper right, but body for this connector is to expensive for low budget project like this emu, so ground connection is made by cable fastened to metal chassis of radio. Screw has torx T-9 head.


Audio pre-ampifier


In case you have  pre-ampifier, this one is powered from constant +12V pin, righr audio channel is also red, but goes from shielded cable pare, I marked it with pinkish color:


grounding goes to chassis:


Units with 12pin connectors

If your radio has this type of connector, you are lucky you need just insert connector like on next picture and connect ground like on previous picture.



streda, 30. marca 2016

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






štvrtok, 10. marca 2016

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 :




 

utorok, 26. januára 2016

OVC3860 how to change name

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