Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by FourG

  1. OK, fair enough. Next question: Does anyone know, and have a few minutes to tell me, how switching audio sources is done? Is there a (known) command already on the system to do it, as I suspect, or is it done at a lower level by the programs themselves?

    Aside from av.exe being the prime suspect where you'd find the use of the API calls, I would investigate the code inside NDeviceLib.DLL, where you'll see such tasty strings as:






    I'm not sure if those are structure names or API functions, but either way I'd say it's worth going at it with WinHex or IdaPro.

  2. Short answer: No documentation yet.


    Long answer: That's only because no one's had the time to do so. EEGeek's been working with carver on the WINCE.BIN modifying aspect (update the registry and files to add drivers/programs, like the FTDI driver you referenced or the SpecTec 802.11 SD card as an example). See the Wiki. I started working on porting HaRET to our AVICs for the purpose of watching the COM port that controls the uCOM to do the source switching/volume control/etc, but the J-O-B has my undivided attention (well, OK, the large majority of my attention) until the end of April at the earliest. Shouldn't be too difficult, it's a matter of setting up HaRET to observe the memory region the COM port resides in and capturing the writes and reads to the control registers, then executing the command of interest.

  3. It connects via USB. So far this only works for Standback units since I wrote the standback software, I had to code to modify to make it work for these WinCE units. If we had a USB to CAN cable for which we could find WinCE drivers, I could probably modify my software to use it instead of the Standback hardware.

    I know the ElmScan.Net software I use with my OBDLink scan tool has their source on their website. Since it's basically a glorified FTDI 232 (I forget if it's a 232R or 2232H) you can probably use their ARM driver (see http://www.ftdichip.com/Drivers/D2XX.htm) to add support to some of these scan tools.


    Just a thought. :)

  4. I did notice that booting "normally" launches a process called av.exe. If it's responsible for the audio output to the backplate, maybe we could just launch it by itself.


    Very likely since on the in-dash units it's the AV board that has the uCOM ASIC that controls the audio source. It sends commands to the E-Volume chip over I2C that will select which source to output (Navi, AV1, AV2, IPBus, DVD, FM Tuner, etc).

  5. Yeah, and when I said "phone" what I really meant was the Handsfree profile. No A2DP, no Dial Up Networking, no LAN Access Profile, etc, etc. Hoping to use your CE image cooking guide from the Wiki to put a CSR Bluetooth radio driver and the BlueSoliel Bluetooth stack from my iPaq 310 onto the AVIC and see what happens when I put one of the USB Bluetooth adapters into the USB cable. :D


    Thanks, that's actually helpful!


    Will be following your progress, good luck. I suggest reading this thread if you haven't already:




    The OP got the internet working using a SD WiFi card and tethering it to a phone. The Droid can act as a hotspot, but you would still need a way for the unit to connect to the Droid.


    Also, I don't really know what this means, but this is a quote from that thread about the bluetooth capability of the AVIC unit:


    Sadly the Bluetooth in our AVICs isn't a full-featured one, it's a phone and serial port only device made by Parrot. It looks like the Navi board communicates with the Bluetooth module over a serial or USB connection and uses Parrot's DLL/driver to run the board, rather than a full Bluetooth stack that can talk to HID devices.
  6. Could someone elaborate on how to acquire this key so that we can gain access via Testmode with this version of the firmware? Is it something that a very experienced layman could do or more that I want to bite off and chew at this time?

    Well, you could write a script that generates every possible combination of the 0-byte file names. The file names are 32 characters long with every position as a digit (0-9) or an upper case letter (A-Z). Only 6.3340286662973277706162286946812e+49 possible combinations... Well, that minus the known good keys for previous versions that obviously don't work on 2.0080. ;) Then you copy all the files (or the number that the file system can support in a directory minus the number of pre-existing files) to your SD card, put it in and see if it boots. If not, delete and copy the next set over, retry, yada yada yada... You get the idea. Once you find the set that works, you start chopping the set in half and retrying, each time you get success you cut that set in half.


    As you can see, the brute force method can be very labor intensive. I'm willing to wager someone with IdaPro can disassemble the .exe that launches the MortScript to find the key in less time. Carver usually finds the latest keys on the Russian GPS enthusiast sites, you could try PM'ing him to see if he's come across it yet.


    I'm running 3.0, so no way for me to test out this on my deck.

  7. Sounds like you'll need to determine what "key file" (the files in the Testmode archive without an extension that are a mix of numbers and letters) 2.0080 is looking for in order to let you enter test mode. We usually have to get new ones after a firmware release.


    Reason number 1 not to upgrade your firmware until after someone posts the ones for the new release. :(

  8. Holy Shit my friend, I thought this was uncharted territory? I didn't think you could change the radio side. This is an awesome upgrade to your theme. You always impress me, bro.

    Sadly Alex is correct, you can't create new features in the APL\* apps yet. You can only change the way the radio controls look by editing the pictures inside APL\image.res. You can't create new buttons or change the way the existing buttons behave without changing the code inside the programs themselves (no event handlers).

  9. I am confused.

    Where on Pioneer's site, or elsewhere, can I find a free firmware upgrade for download for my U.S. version F700bt?


    Thanks everyone for being kind to the nOOb! :)

    If you're running a 2.x version of the firmware, this has the update to 2.008: http://www.pioneerelectronics.com/PUSA/ ... port?tab=B


    If you have 3.x firmware, there haven't been any updates released for the US 3.x firmware yet. If you mean a free 2.x to 3.x upgrade, it doesn't legally exist (need to buy the SD cards from Pioneer) but search the forum for the morally flexible method if you're opposed to paying.

  10. ===================================================

    After reading 55 pages I believe that the radio is not working it is "normal" :(:(:(

    But how can I put maps in the TT file?


    Have nobody a solution?? PLEASE :roll::roll::?: (not only for my I have read :) )


    Thanks for the answers


    Sorry Ron, but until we get the APL DLLs figured out we can't tell the uCOM device on the AV board to change the audio source from the Navi sources (SD & USB) to other sources like the Radio, IPBus, iPod or AV1/2. I'm not sure if Leet got around to that, and none of us have his source to make modifications ourselves.

  11. In most programming languages a single '\' in between two double quotes in a string declaration usually means you're using a control character (like being "\t", for example). Try escaping the "\"s in the command string (notice I left the first "\" that's outside the double quotes alone):


  12. right.. had my unit for a week or so and had a look at afew bits and I'm thinking is it worth having ago to write my own frontend.


    I am looking at coding it using visual studio 2008.. vb.net. here's a few questions.. It .net installed already in the WinCE image ? Is it even worth me having a play ?


    I'm assuming the Menu / Nav and other buttons are just keypress but how is the volume controlled etc ? Is the GPS just linked to a com port ?


    Lots of questions.. but first steps and all.





    If you look at the Service Manual (search this forum, I think carver's got a link in one of his posts) you'll get a schematic of the AV board and a block diagram of the Navi (no schematic) that will answer a lot of your hardware questions. I've got a build of HaRET going that recognizes the ARM1136 core and the iPaq 310/Pioneer AVIC F-series, but haven't gotten very far in the GPIO and IRQ mapping to figure out the button press setup. Pretty sure the GPS is COM7, and COM0 talks to the uCOM ASIC on the AV board to control volume, source, IP Bus, etc. COM1 would be your serial console, if you populate the header (don't think it's stuffed by default).

  13. I can't seem to unzip the testmode file. Can someone send a new link for this file? It keeps giving me the corrupt error on winzip and winrar. I am unable to get into Windows CE on my AVIC F90BT. Does anyone have any suggestion? I have downloaded the testmode multiple times and have been trying all day. THe windows screen comes on and then the navigation goes blank. Please Help. Nothing works now.


  14. VirtualPC won't work as an AVIC emulator because the AVIC uses an ARM based processor, while your PC uses an x86 based one. You need to follow the instructions in the Wiki under the "OS Emulation" article to install the Device Emulator and WinCE images. Also search under the Hacks & Mods forum for Emulator (this link is probably the most relevant).


    "Any sufficiently advanced technology is indistinguishable from magic." - Arthur C. Clarke

  15. FourG


    Thanks, that got it working. No sound yet though


    In order to get sound, you have to play a media file from USB or SD card using avic's software, pause it then go back to miopocket.

    Yep. Reason for this is the Navi board has to tell the AV board to switch the e-Volume source input from the AV1/AV2/Tuner/IP-Bus source you left it on to the one output by the Navi, the USB and SD sources are the only 2 that correspond to a Navi source. This is one more TODO item in a long list: to figure out all the DLLs in the APL folder and how to call the software that does this.


    You should be able to launch "My Flash Disk\APL\AV.EXE" from inside MioPocket to try to switch sources. I'd make sure you've used the control panel to unhide the taskbar before you do so you can switch back to MioPocket after (though I think MioPocket puts that big red X in the upper corner to close the current app, might give that a try first).

  16. I have downloaded MioPocket 3.0 and it looks like a great program but I have no idea how to install it. All the posts seem to be for older versions of AVIC(2.X) and Mio (2.0). Is there a thread that describes how to install MioPocket 3.0 onto AVIC 3.X(X910bt)?


    I'm pretty sure this will work but I'm not going to test it out on my AVIC since MioPocket will alter the WinCE Registry slightly (lots of entries under HKLM\SOFTWARE\MioPocket and HKCR\MortScript), on my iPAQ I have to reset the registry via the uBoot engineering menu to completely remove MioPocket. No warranties implied or offered and if you brick, it's your problem. Be aware that your radio, phone, iPod and Navi apps may not work with this environment, but you can still try to launch them from Explorer.


    Suggested process:

    • [*:r66xkfxk]Obtain Testmode 2.3, there is a link to it under the Wiki's backup topic
      [*:r66xkfxk]Obtain MioPocket 3.0 (I'm using Release 57 as a reference)
      [*:r66xkfxk]Extract MioPocket to a temporary directory on your computer
      [*:r66xkfxk]If you don't want to alter the contents of the flash drive and just run MioPocket from the SD card, delete the SDFree folder from inside the extracted archive's "MioPocket 3.0 Release <#>" folder
      [*:r66xkfxk]Open MioAutoRun\MioPocket.ini, change the value of OrigNavApp to "\My Flash Disk\APL2\iGo\EZRIDER.EXE". Save.
      [*:r66xkfxk]Copy the contents of the "MioPocket 3.0 Release <#>" folder to the root of your SD card
      [*:r66xkfxk]Rename the file "MioAutoRun.exe" to "CopyTool.exe"
      [*:r66xkfxk]Rename the file "MioAutoRun.mscr" to "CopyTool.mscr"
      [*:r66xkfxk]Inside the Testmode 2.3 archive, there are several 0-length files whose names are a mix of letters and numbers. Copy any file matching this description over to the SD card's root. Example name: 164C549550B84211BA8C4B84AC5C0081
      [*:r66xkfxk]At this point, you should have an SD card that will boot into MioPocket. If at any time you get a GAPI configuration GUI asking you to select the type of PDA you have, select "HP iPAQ 310" (they use the same SiRF Titan processor).


    There you go. Try not to brick yourself, eh?

  17. I'm a noobie, so please go easy if I missing something basic here. I've copied the Testmode & MiTACAP folders on the SD card. I've also placed the Data.zip file on the SD card (for software bypass to watch video while in motion). I erased all other files from the SD card. I tried repeatedly to boot it up, but nothing is happening. I did the upgrade to 2.006 previously, so I know the system should be reading the SD card. Help! :x

    If you have a MiTACAP folder you're using an older release of Testmode that doesn't work with 2.006 or 3.x versions of the firmware. Try this copy of Testmode_2.3.rar.

  • Create New...