FourG

Try downloading this copy of Testmode_2.3.rar. Some of the ones linked elsewhere seem to be corrupt (bad CRC errors for a few of the files).

Europe. US F-series has no 3.x updates yet.

Pioneer recommends you run HW100-SW330 RC3 as long as you don't have a Sony Ericson W300i or Samsung SGH-U900. If you do, you want to stick with HW100-SW290. Follow this link to the F90/F900BT firmware updates, look under "Bluetooth Software Updates".

Unless you have purchased and installed the 3.0 update (with the CNSD-100FM update in the Pioneer store), the 3.x firmware upgrade on that site won't install.

The schematic for the AV board in the F900/90BT repair manual has the speed sensor signal going through a margining network and then over to the Navi board into a Xilinx CPLD used for timing control. The schematic doesn't call out how the CPLD connects to the Titan CPU, it may be a GPIO/interrupt pin or a two-wire interface. Might still be trial-and-error territory.

Heh, not necessarily. Thanks to the service manual, we know that the Wired Remote goes to the uCom chip on the AV board, which I'm willing to wager notifies the Navi about the button press (or press and hold) via the UART (COM2). This is probably done by one of the programs in APL (MainMenu, AV or NEventWatcher, perhaps) which sends a message to the application that is currently running in the foreground. We'd probably need to do some hacking on the event dispatcher to do the remapping, the knowledge required is held by a few members here (carver most likely, I'm still working on getting my

lucaspeedy, You need to copy some files from Testmode 2.3's testmode folder into LeetLauncher 3.0's testmode folder for it to wok with the latest releases of the AVIC firmware. Copy all the 0-length files without an extension (they are named like "45487613469745412354668745684665", etc) from Testmode 2.3's "testmode" folder into the LeetLauncher 3.0's "testmode" folder and it should boot. These files are like keys the firmware looks for before it will let you enter testmode.

Huh, so it is. Luckily my copy is still OK, I'll attach it to this reply. If it's a more recent version, perhaps. What firmware version do you have (I think it can be found under Settings->System Settings->Service Information). Mine's 3.020100 (UC) and Testmode 2.3 works fine for it. Testmode_v2.3.rar

Sounds like the AU testmode was based upon an old Testmode release. Make sure you use Testmode_2.3.rar (download/file.php?id=8932). It has a single folder called "testmode" that you put in the root of the SD card. That folder has some 0-length files with names like "164C549550B84211BA8C4B84AC5C0081". These files are the "keys" the firmware looks for to know you're allowed to boot into test mode. When a new version of the firmware comes out, one usually needs to determine what the new key file's name is an add it to the test mode folder. EDIT 2010-01-18: Uploaded my copy of Testmode 2.3

Any luck getting this going? I've been trying to reverse-engineer carver's instructions on how to carve up the WINCEIMG.BIN into toc.bin, eboot.nb0, chain.bin and wince.nb0 files so I can use 3.0 in the emulator. I think I've got the four files created right but the emulator doesn't like wince.nb0. Also tried the same process on a 2.06 WINCEIMG.BIN (following carver's instructions in viewtopic.php?f=34&t=25385) but the emulator didn't like that one either. Has anyone successfully extracted nk.bin out of a WINCEIMG.BIN?

Sounds like you might have used an old Testmode release. Make sure you use Testmode_2.3.rar (download/file.php?id=8932). It has a single folder called "testmode" that you put in the root of the SD card.

Not yet, but in Alex's defense: I just put the F90BT on my desk back to stock versions (data.zip, sys.txt, etc) and deleted all user save data. Rebooted, and the AV.exe clock went an hour ahead even with my timezone set manually in iGo's (didn't do this w/ 2.006). Looks like it's a bug w/ the way iGo 8.3 sets the date/timezone when it gets a GPS lock to me... Especially since I can go do this: [*:1reesinh]Start in Settings->Navi Settings->GPS & Time Settings [*:1reesinh]Set to Auto timezone (and swear under breath that the damn thing thinks I'm in Idaho now) [*:1reesinh]Bac

Just a note that I've got the same behavior, and I already tried setting the OS timezone through a different process (this is w/ Diaftia's 10/10 release). I used a mod I made to Diaftia's Settings->Navi Settings->Run menu to launch Explorer without needing to boot into test mode. Brought up the Date/Time control panel, there was no time zone selected (drop-down was blank) and the time was an hour ahead of what it should be. Fixed the timezone to Pacific time which automatically set the clock correctly in the taskbar and in the APL\ apps (AV.exe, etc) when I hit Apply. I have to manua

On my Blackjack II, I think I had to pair the phone first and make sure the Serial Port service was selected under the Windows Mobile Bluetooth connection settings for the Pioneer Navi. So first go through the process of adding the Pioneer Navi to your phone. Under the Advanced settings, make sure the "Serial Port" service has been checked too. Steps to transfer the phonebook: 1) Select "Phone Book Transfer" from the Phone menu 2) Select OK on the first dialog box (some info or warning, I forget) 3) Select OK on the "Send Business Card" dialog box, don't bother sending a business card

More than likely the AV UI is in the APL\AV.exe and APL\AVRes.Res files and Main Menu UI is in APL\MainMenu.exe and APL\MainRes.Res, with both pulling image data from APL\Image.Res. Both are independent executables from APL2\iGo\ezrider.exe and APL2\iGo\data.zip. ezrider just posts messages to both via commands in the scripts like this one: ;send message to mainmenu EXEC "other.pioneer.postmessage" "MainMenu" "WM_APP_AV_IGOMAP" 0 If that command wasn't captured right by MainMenu, then that's when you end up with the "System Startup In Progress" message stuck on the screen (I think

Haven't tested it yet but I'm pretty sure we can use their driver. The "install" process has to be redone every time we reboot the system though. This is due to the fact that the DLL, .ini and registry entries are not part of Pioneer's WINCE.BIN image, so it's not in \Windows after the reboot and must be copied off the flash drive as part of a scripted startup process. For now, anyway. Hmmm, not aware of any virtual machine monitors designed for CE since the ARM/OMAP cores CE runs on might be a tad underpowered for the task. Now if VAG-COM was a .Net app, maybe using the .Net mi

You'll likely need to use MortScript to help copy the FTDI driver DLL and .ini to \Windows and install the registry entries they outline in the "INF Files/registry settings.txt" file inside the driver. You should be able to call this script when the system starts up each time so driver.exe knows how to bind the driver to the USB device when detected. Once that's done and the FTDI chip's virtual COM port is available, it's a matter of getting the VAG-COM software working in the WinCE environment. I'm not sure if Ross-Tech ported the software to WinCE or not, I've only ever seen it on a Windo

He mentioned it at the end of his last post: WinHex

At this point no one has found a way to change major features/layout of the "skins" of any of the Pioneer applications (tel.exe, av.exe, mainmenu.exe or settings.exe, i.e. the ones in the APL folder). Only a few hex edits to the .exe/.dlls to disable messages or enable features and modifying the contents of image.res to change icons/colors have worked so far.

I'd be shocked if they didn't have some way to inject the GPS coordinate data into iGo via emulation, maybe they can collect some location and hysteresis data from one of our units and replay on a development unit or emulator... Interesting thing to note is that running TomTom and Garmin under Testmode, I had no trouble with the unit setting its timezone correctly. Still think this is pointing at problems with their iGo implementation (either a bug in ezrider.exe, the data.zip's multi-timezone support or the map data they used).

Still in waiting mode. Pioneer knows no one in Oregon has working Auto timezone yet either, and you're not the only one with the screwed up time in the non Navi screens.

Yep, Windows CE 5.0. Uses Platform Builder 5.0 to make the system images and Visual Studio 2003 or eVC 4 for app development.

azux's answer: R3 (iGo 8.3) maps will only work with 3.0 firmware + hacked ezrider.exe + license. 2.009 only has iGo 8.0 (R1) support, there is no way to use R3 maps with 2.x series firmware.

These files should be 0-length, the file names act as a "key" for your version of firmware to OK entry into testmode (usually one key per release version, but they're all here so the release works with multiple firmware releases). When Pioneer releases a new version of the firmware, usually a new one of these files is required before we can enter test mode again: 164C549550B84211BA8C4B84AC5C0081 45487613469745412354668745684665 63D21BEFE088433dBE3CF942347464C7 66543C4BA1ED45d0AF57DB70682069AA 70560201322534565929232100000201 738AE337FD024201A799B90250D6335A BAC66FE457CF4b43B9751BD370C0

What might be happening is without the .exe that initializes communication with the uCOM on the AV board (due to empty flash disk) the reset watchdog's timer expires and it resets the Navi because it thinks it's stuck. If you don't have enough time to copy the APL folder from your My Flash Disk backup back over to the flash drive before reset, there might be another option. If you've got Testmode 2.3, there is a file in the "testmode" folder called CopyTool.mscr. It's a script that gets executed by the CopyTool.exe (really Mortscript.exe that's been renamed so the AVIC executes it to ent