Здравствуйте, уважаемые!
Имею ГУ Columbus для а/м Skoda Octavia A7.
Хочу подключиться к аппарату посредством терминала. Идея навеяна вот этим руководством http://ru.scribd.com/doc/225614389/How- ... lus#scribd
Но таких коннекторов, подобных указанному в этом мануале, на материнской плате моего аппарата два. Непонятно, где и как искать TX, RX.
Кто что может подсказать, буду признателен за помощь.
ниже перевод на английский
here translated into English
Hello, dear!
I have the Columbus (mib 1) for Skoda Octavia A7.
I want to connect to the device through the terminal. The idea here is inspired by this guide http://ru.scribd.com/doc/225614389/How- ... lus#scribd
However, such connectors on the motherboard of my device - two, as opposed to one, as in this manual. It is not clear where and how to look for TX, RX.
Anybody can help, I will be grateful for your help.
Подключение терминала на Columbus (Skoda A7) / Connecting the terminal to Columbus A7
Hey my friend! The MIB you unit of The have, is a the complete the Hardware Different as with the MMI3G in the bricked the discription.
You CAN use nothing from the this thread for the you have the MIB. Of The the Serial the Port is reacheable from the Quadlock connector on the REAR! You don'nt have a need to open the unit! ;-)
By the way: The port is locked by a root password!
You CAN use nothing from the this thread for the you have the MIB. Of The the Serial the Port is reacheable from the Quadlock connector on the REAR! You don'nt have a need to open the unit! ;-)
By the way: The port is locked by a root password!
Tschako,Tschako писал(а):
By the way: The port is locked by a root password!
Thanks.
What we have now. Yes, the system asks a root password. Somebody knows it? Is it any way to determine it, may be extract "shadow" file/hash ?
The second thing, we can enter to the IPL mode. In this mode, we can some set of commands.
eraseit & flashit are that supported (info from "help command")
There is a question. What possible to do with all this ? Is it possible to download the current firmware?
If not, how to modify it (some parts? )
The Harman developers do a fine job to secure the MIB. All access and flashing activities in the actual MIB release firmware versíons were secured by special procedures and certificates means signatures and hashes. Not the old and simple usage of checksums. The developer password for root are not known in the community right now, as far I know...
The main SW system is build on QNX, thats true. But they use two corresponding envirements named "MMX" and "RCC" for different job level in the unit.
It´s not possible to direct boot from the IPL to the EMG Image like the MMI platform. You have to path via the transaction image as an example...
The main SW system is build on QNX, thats true. But they use two corresponding envirements named "MMX" and "RCC" for different job level in the unit.
It´s not possible to direct boot from the IPL to the EMG Image like the MMI platform. You have to path via the transaction image as an example...
Yes you are right.The developers have done a good job security MIB-1.
But, nevertheless, MIB1, and even MIB2 has been hacked.
Firmware of my device is 0202, this firmware is buggy and now she has a problem - the constant rebooting.
The device inoperable.
How can reflash it to the latest firmware?
I don't have access to green menu...currently, my device is a brick 99%.
But, nevertheless, MIB1, and even MIB2 has been hacked.
Firmware of my device is 0202, this firmware is buggy and now she has a problem - the constant rebooting.
The device inoperable.
How can reflash it to the latest firmware?
I don't have access to green menu...currently, my device is a brick 99%.
After command "boot" it loading an emergency IFS. But some errors occur during the loading process. If you know a solution how to fix it - explain,It´s not possible to direct boot from the IPL to the EMG Image like the MMI platform. You have to path via the transaction image as an example...
please.
Also, in the IPL mode, I have constant rebooting occur - do not understand why, how to fix it?
The reboot is part of the build in trouble shooting routine. The mmx ramdisk image in the flash is missing and the internal routine tries to fix the problem with rebooting...
Try to initiate an Emergency FW update with the command "dd if=/dev/zero of=/dev/fs0 seek=59 bs=131072 count=1 > /dev/null 2>&1"
if possible. Make sure to have a valid FW Version in the SD slot.
Last chance could be to erase the transaction image with command "flashit -a 540000 -e 1000".
Following this, the emergency app should try to start the emg app with an emg update from SD.
Make sure to have a valid FW Version in the SD slot too.
Try to initiate an Emergency FW update with the command "dd if=/dev/zero of=/dev/fs0 seek=59 bs=131072 count=1 > /dev/null 2>&1"
if possible. Make sure to have a valid FW Version in the SD slot.
Last chance could be to erase the transaction image with command "flashit -a 540000 -e 1000".
Following this, the emergency app should try to start the emg app with an emg update from SD.
Make sure to have a valid FW Version in the SD slot too.
Tschako
"mmx ramdisk is missing" - this is the operation system bug/error?
It is happened a few days ago, I turned on the trace in the engineering menu.
At first everything was fine, but then the device was continuously reboot.
Now it is impossible to turn off tracing, and my device became a brick.
(Perhaps it's just a coincidence, and to blame the 0202 firmware ...I do not know much about the address.
They are correct for my device? In what format should I write the firmware to SD-card? I have the firmware file in * .zip from the Discovery (0200 version) and the firmware file from Columbus (native), 0390 version.
Thanks for your help.
"mmx ramdisk is missing" - this is the operation system bug/error?
It is happened a few days ago, I turned on the trace in the engineering menu.
At first everything was fine, but then the device was continuously reboot.
Now it is impossible to turn off tracing, and my device became a brick.
(Perhaps it's just a coincidence, and to blame the 0202 firmware ...I do not know much about the address.
They are correct for my device? In what format should I write the firmware to SD-card? I have the firmware file in * .zip from the Discovery (0200 version) and the firmware file from Columbus (native), 0390 version.
Thanks for your help.
Bad idea to activate the trace function w/o any need... sorry to say! The problem would be, that the trace writes and writes and fullfill the flash ramdisk til it crashes.
I´m sorry, but for the Columbus FW versions I don´t have any information.
For the Audi MIB the version 0337 is quite old and 1531 is the actual one...
You have to use the exactly the same region and variant of the FW on a FAT32 formatted SD Card for an emergency update.
Wrong variant or region doesn´t work.
I´m sorry, but for the Columbus FW versions I don´t have any information.
For the Audi MIB the version 0337 is quite old and 1531 is the actual one...
You have to use the exactly the same region and variant of the FW on a FAT32 formatted SD Card for an emergency update.
Wrong variant or region doesn´t work.
I have EU version, so everything ok with this.You have to use the exactly the same region and variant of the FW on a FAT32 formatted SD Card for an emergency update.
Wrong variant or region doesn´t work.
Yes...Tschako писал(а):Bad idea to activate the trace function w/o any need... sorry to say! The problem would be, that the trace writes and writes and fullfill the flash ramdisk til it crashes.
It was my fault. Now I can not turn off this trace, after deactivation option, reboot the device - option is active again.
It is necessary to disable this option, but it is unknown how.
There is any way to clean/restore the virtual ramdisk?
Complete firmware changing will lead to the activation the component protection, also navigation will not work. Not a best way.
"Complete firmware changing will lead to the activation the component protection, also navigation will not work."
The CP signature is not part of the Firmware or software. The CP Signature is part of the specific EEProm of the Unit.
Means, if you do a emergency recovery, normally the CP signature was protected and there was no changes in it. I´m not shure for the Map autorization?!
The CP signature is not part of the Firmware or software. The CP Signature is part of the specific EEProm of the Unit.
Means, if you do a emergency recovery, normally the CP signature was protected and there was no changes in it. I´m not shure for the Map autorization?!