utorok 10. apríla 2018

full fis over 3lb

extended lib(work in progress, we can say) from https://github.com/arildlangseid/vw_t4_tcu_temp_to_fis

with support for fullscreen, everything is on github as always :)

please push any updates, patches to github



piatok 2. februára 2018

analysis of volume fix adapter from ebay by tomsad

so friend has problem with volume on his audi concert, I know what is problem, and also that there are at least 2 adapters on ebay which should fix this [1], [2] (second one is also here: [3])

second one is smaller and cheaper so I go for this one.

.... adapter arrived at postbox, so I was curious how it's works. So i take closer look at traces on PCB and realize that mcu is STM32, and is only grabbing SPI from display and send I2C to audio controller (TDA7342), so they recreate complete audio control stack, nice, lets check it how well it works ;).

 I made simple arduino sketch to get i2c data on this radio [4], and here is my observations:

input selector is not working,

changing bass/trebble/fade/ballance can by set diferent from what is showned on display, check my github for output from arduino i2c sniffer links to files [5],[6],[7] are from "modul from ebay/programatory.com" and file in link [8] is output of reprogramed Motorola MCU which I buy like 3-4years back.

so, what to do? return it and try first one(from ebay) or impelemented volume rewrite in my code??

so after while I write few lines of code to fix this, code is on my github [9]
schematics will be there in few days

[1] https://www.ebay.com/itm/152875338212

[2] https://www.ebay.com/itm/142651501685

[3] https://www.programatory.com/index.php?p1106

[4] https://github.com/tomaskovacik/arduino/tree/master/audi_volume_fix

[5] https://github.com/tomaskovacik/arduino/blob/master/audi_volume_fix/fix_module_by_tomcad.txt

[6] https://github.com/tomaskovacik/arduino/blob/master/audi_volume_fix/fix_module_by_tomcad2.txt

[7] https://github.com/tomaskovacik/arduino/blob/master/audi_volume_fix/fix_module_by_tomcad3.txt

[8] https://github.com/tomaskovacik/arduino/blob/master/audi_volume_fix/newchip.txt

[9]  https://github.com/tomaskovacik/arduino/tree/master/audi_volume_fix_stm32

streda 17. januára 2018


if you want to support my work, here are few of my wallet addresses:

ETH: 0x17c0e8c2a312908ee4e6aacd20563422dff9622e

BTC: 1F82BPbnZ5nZVWa89bNKPPikSq2XE7wVcD

LTC: LMHUz6UniJp2xZcuzScJwZ313q2VtHCgpG


utorok 7. novembra 2017

BK8000L change name

- unsolder flash chip on module(in my case it was FT25H04 by Fremont Micro Devices, datasheet: [1])
- connect it to programmer supported by flashrom [2]
- download flashrom source code [3]*
- extract, compile
- download flash content, or download dump from my github repository [4]

./flashrom --programmer serprog:dev=/dev/ttyUSB0 --read BK8000L.flash

edit with favorite hex editor:

search for asci string BK8000L, change it, save and flash:

./flashrom --programmer serprog:dev=/dev/ttyUSB0 --read BK8000L.flash
flashrom v0.9.9-r1955 on Linux 4.4.10-040410-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Calibrating delay loop... OK.
serprog: Programmer name is "frser-duino"
serprog: requested mapping AT45CS1282 is incompatible: 0x1080000 bytes at 0x00000000fef80000.
Found FMD flash chip "FT25H04" (512 kB, SPI) on serprog.
This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to flashrom@flashrom.org if any of the above operations
work correctly for you with this flash chip. Please include the flashrom log
file for all operations you tested (see the man page for details), and mention
which mainboard or programmer you tested in the subject line.
Thanks for your help!
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

 solder flashchip back on module, power it and enjoy ;)

*originaly I use flashrom 0.9.9 + apply my patch [5]

[1] http://famousconnections.eu/wp-content/uploads/2017/10/FT25H04.pdf
[2] https://www.flashrom.org/Supported_programmers
[3] https://github.com/tomaskovacik/flashrom
[4] https://github.com/tomaskovacik/kicad-library/raw/master/library/datasheet/F-6188_BK8000L/BK8000L.flash
[5] https://github.com/tomaskovacik/kicad-library/blob/master/library/datasheet/F-6188_BK8000L/flashrom_patch_for_FT25H04_support.patch

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:

 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
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
 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