FourG

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: NPuComRcvSelectorChangeEvent NPuComSelectorChg NPuComRcvSourceEnableEvent 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.

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

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.

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

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.

I can confirm my Spectec SDW-821 works with the AVIC-F90BT.

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

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.

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

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.

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.

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): run(SystemPath("ScriptPath")\"..\\LeetLauncher\\LeetLauncher.exe")

Actually, you *want* guidance strip and you don't want guidance arrow. Use this in your sys.txt: [3d] show_guidance_arrows=0 show_guidance_strip=1

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

Still Windows CE 5.0.

That's been described by a few others on the forum, not sure if it's been 100% solved or not. Another alternative might be tethering via USB, if there's a WinCE driver for your phone to act as a serial modem.

download/file.php?id=8932).

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

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 Mio

Not likely, unless someone got a USB based Bluetooth dongle working (carver was working on that but ran into a problem with the software portion of the BT stack). The Bluetooth device that the AVIC-Fs have does not support the Bluetooth PAN profile, which is what you need to tether. It just does Handsfree and Serial Port profiles.

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 und

Whoops, the Wiki entry was stale as far as the description of the archive contents and what you see when you get a successful boot into Testmode when using it. I've updated the Wiki entry.

It has one, it's the Wiki link you see at the top of the page. It's just that no one looks there, they just post "How do I?" questions in the forum instead.

Sounds like yopu're using an older release of Testmode... Try this copy of Testmode_2.3.rar, I don't think it pops the green copy box up.

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.