Database Users

ByteBlaster vs Xilink - JTAG

Hi I just killed my bootloader and just read http://xda-developers.com/jtag/
anyone else has succeed using this method?
please share more experiences before i open my Xda O2
also i search lil bit more deep on the net and found this doc on how to built the ByteBlaster
http://www10.brinkster.com/nsfreecore/Build%20your%20own%20ByteBlaster!.htm
which one is good? ByteBlaster or Xilink ? or both are the same?
TIA

other option
Hi,
Probably your best bet is: http://xda-developers.com/phpBB/viewtopic.php?t=2079
Only if this fails I would start to think about JTAG.

hmm my xda is really dead no bootloader at all,
i put on the cradle with power
Usb detected as USB Device not recognized
trying the bootloaderfix -> failed, nothing happened :|
I think its the JTAG way
is the simpliest JTAG cable download with only 5 resistors and db25 can help?
just like the one on http://openwince.sourceforge.net/jtag/iPAQ-3600/
this simpliest JTAG schematic:
http://openwince.sourceforge.net/jtag/iPAQ-3600/images/interface.png
or do we really need to build ByteBlaster/ Xilink board?
W4XY, please let me know
TIA

jtag
Ah my mistake. I confused the byteblaster with the bootblaster (another tool to write bootloaders).
About the interface I'm not sure. I would think that it should work with the simple one. Mostly because the iPAQ and XDA are similar enough. The more complex interfaces are a bit better because they do clean voltage level conversion. I suspect that the reason the simple interface works is because 3.3V is also seen as 1 for a 5V parallel port.
I've used a ByteBlaster cable. If you try the simple one let us know if it works.

I thought that I read somewhere that if the SD Card had the bootloader on it, the PocketPC would try and boot from the SD Card. Am I wrong?
I haven't tried it, but how else does the Manufacture restore a dead rom?
It seems that it should be able to use an alternate boot device if the first one fails.
??????
Wade

You can only boot from SD if a working OS is running. Now it is possible that PocketPC still works with a dead bootloader, and then you can reflash the bootloader in a number of ways. However if both are dead also the manufacturer will have to use jtag or other incircuit means to reflash the device. Normally this happens in the factory or with specific personalization hardware. The XDA has no backup boot ROM.

Hiya,
I just opened my XDA, wow looks like jungle for me! lil bit hard for newbie
well i read about a small patch for Jtag,
http://xda-developers.com/jtag/
"...I created a small patch to version 0.4 that takes care of flipping the bit just before erasing and writing of the flash. You can download the patch here"
download the patch where?
Thanks in advance
Brumie

Where can i download the patch for jtag 0.4
Hi,
Where can i download the patch for jtag 0.4?
or how can i access to the cvs version of jtag 0.4 with the poke command.
thanks

cvs version
Hi,
Sorry for not getting back to this, currently at CCC working on some other stuff.
The CVS version can be found at http://openwince.sf.net
or more precisely here: http://sourceforge.net/cvs/?group_id=52603
The patch will be there latest next week.

patch
thanks for your answer.
i finally got access to the cvs server and will try it monday with teh xilinx cable
have a nice time at the CCC ;-)

cvs version of jtag :-(
i tried to compile the jtag cvs version from yesterday
but i get error messages after make :-(
snip
###########
make[1]: Entering directory `/usr/local/src/cvsroot/jtag'
Making all in libbrux
make[2]: Entering directory `/usr/local/src/cvsroot/jtag/libbrux'
if gcc -DPACKAGE_NAME=\"libbrux\" -DPACKAGE_TARNAME=\"libbrux\" -DPACKAGE_VERSIO
N=\"0.1\" -DPACKAGE_STRING=\"libbrux\ 0.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\
"libbrux\" -DVERSION=\"0.1\" -D_GNU_SOURCE=1 -I. -I. -I/usr/local/include/ope
nwince -I/usr/local/include/openwince/device -I/usr/local/include/openwince/arm
-I./.. -I./../include -g -O2 -Wall -MT cmd.o -MD -MP -MF ".deps/cmd.Tpo" \
-c -o cmd.o `test -f 'cmd/cmd.c' || echo './'`cmd/cmd.c; \
then mv ".deps/cmd.Tpo" ".deps/cmd.Po"; \
else rm -f ".deps/cmd.Tpo"; exit 1; \
fi
cmd/cmd.c: In function `cmd_run':
cmd/cmd.c:40: error: `cmds' undeclared (first use in this function)
cmd/cmd.c:40: error: (Each undeclared identifier is reported only once
cmd/cmd.c:40: error: for each function it appears in.)
cmd/cmd.c: In function `cmd_get_number':
cmd/cmd.c:77: warning: comparison between signed and unsigned
cmd/cmd.c:82: warning: comparison between signed and unsigned
make[2]: *** [cmd.o] Error 1
make[2]: Leaving directory `/usr/local/src/cvsroot/jtag/libbrux'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/cvsroot/jtag'
make: *** [all] Error 2
snip
#############
It is possible to make a full working source version availiable for download ?
thanks
klaus

Create virtual CommPort for GPS emulation

Hi Folks!
I'm trying to add GPS emulation to my navigation system, that is based on CellTracking via GSM.
Does anybody know how to create a virtual CommPort in eVC++ :?:
I tried it with function like ActivateDevice or RegisterDevice, but i always receive a zero Handle:
Code:
#include "winbase.h"
bool virtPortOpen(HANDLE& HandleGiveAway)
{
//HandleGiveAway = ActivateDevice(L"HKEY_LOCAL_MACHINE\\Drivers\\GPSvirt", 0);
HandleGiveAway = RegisterDevice(L"COM", 7, L"serial.dll", 0);
if ((HandleGiveAway == INVALID_HANDLE_VALUE) || (HandleGiveAway == NULL))
return false;
else
return true;
}
int virtPortClose(HANDLE& GetHandle)
{
return DeactivateDevice(GetHandle);
}
Did i use the right .dll-File? Need i create a own .dll-DeviceDriver with the DDK?
Please give me a hint!
Greetings,
Florian

http://www.eltima.com/products/virtual_drivers/

ELTIMA Solution to expensive
cairo31male said:
http://www.eltima.com/products/virtual_drivers/
Click to expand...
Click to collapse
Thanks for the URL, but i think that this solution is much to expensive for a student!
Any other suggestions?
Greetings,
Florian

http://mamaich.kasone.com/rover/IrCOMM.rar
Archive contains a sample virtual COM-port driver. It is installed as a COM8 and after opening COM8 it redirects all data to COM1. You may modify the driver as you like.

Post of "mamaich"
mamaich said:
http://mamaich.kasone.com/rover/IrCOMM.rar
Archive contains a sample virtual COM-port driver. It is installed as a COM8 and after opening COM8 it redirects all data to COM1. You may modify the driver as you like.
Click to expand...
Click to collapse
In this Archive is a C++ project, which deals with infrared communication. I don't know what it has in common with creating a virtual CommPort. - Haven't you postet the right file?
When i try to compile this project, i found out, that it calls some functions not included in the header files, or anywhere else! Look here:
Code:
Compiling resources...
Compiling...
IrCOMM.cpp
C:\Dokumente und Einstellungen\Administrator.MCFLOWNNET\Eigene Dateien\Programmierung\eVC\IrCommEmu\IrCOMM.cpp(34) : warning C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning)
C:\Dokumente und Einstellungen\Administrator.MCFLOWNNET\Eigene Dateien\Programmierung\eVC\IrCommEmu\IrCOMM.cpp(47) : warning C4800: 'int' : forcing value to bool 'true' or 'false' (performance warning)
C:\Dokumente und Einstellungen\Administrator.MCFLOWNNET\Eigene Dateien\Programmierung\eVC\IrCommEmu\IrCOMM.cpp(77) : warning C4018: '<' : signed/unsigned mismatch
StdAfx.cpp
Linking...
IrCOMM.obj : error LNK2019: unresolved external symbol closesocket referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol recv referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol select referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol send referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol __WSAFDIsSet referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol accept referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol listen referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol bind referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol setsockopt referenced in function WinMain
IrCOMM.obj : error LNK2019: unresolved external symbol socket referenced in function WinMain
ARMRel/IrCommEmu.exe : fatal error LNK1120: 10 unresolved externals
Error executing link.exe.
Please give me further information! - Thanks in advance!
Florian

Re: Post of "mamaich"
oops. Wrong archive. Should be http://mamaich.kasone.com/rover/RIL_hook.rar
it contains 2 projects:
Serial - a wrapper around the standart COM1 driver
seRILal - a virtual COM8 driver that creates COM8 and redirects all its IO to the first driver.

Re: Post of "mamaich"
mamaich said:
oops. Wrong archive. Should be http://mamaich.kasone.com/rover/RIL_hook.rar
it contains 2 projects:
Serial - a wrapper around the standart COM1 driver
seRILal - a virtual COM8 driver that creates COM8 and redirects all its IO to the first driver.
Click to expand...
Click to collapse
Sounds good. - Thanks!
I'll give it a try in the evening! - Too good weather here in Germany!
Florian

How to install virtual ports?
This project seems to be exactly what I was searching for! - Much thanks!
But I still have a question: :arrow: How do I install the drivers? - Should I place a new Key in the registry, and in that case, which values do I need to add?
When I try to load one of the drivers with RegisterDevice, I always receive a NULL handle.
Is it a problem that I have deinstalled the standart serial COM1? - But the serial.dll is still existing!
Greetings,
Florian

Re: How to install virtual ports?
this project is coming from Anextek SP230. It had COM1 driver named xsc1_serial.Dll.
To install you should go to registry and modify COM1 driver to be serial.dll and add manualy COM8 driver to be seRILal.dll (you may choose any other COM-port number).
In case of Imate COM1 driver is com16550.Dll, so for this method to work you should recreate import library from com16550.Dll and overwrite Serial\serial.lib file with it. Otherwise your serial.dll would import functions from a nonexistent DLL and the system will crash.

Re: How to install virtual ports?
Well,
thanks very much for your explanations!
But I still have a problem: How do i edit the link to the "xsc1_serial.dll" in the .lib-file?
Need it to be rebuild? - My Problem is that i only have emVC++ without DDK or Platform Builder! - It isn't availibe for free, i think!
Why is the .lib-file needed? - Does it export the COM_Write etc. fuctions to the project?
Thanks in an advance!
Florian

Re: How to install virtual ports?
Probably you don't need this file.
My project is hooking COM1 and makes the real hardware accessible by both COM8 and COM1. As far as I understand you are trying to add a new COM-port to the system that would emulate a GPS receiver. You should take seRILal project, remove Redirected_COM_* functions, remove serial.lib from the project and write your own implementation of My_COM_* functions (they would be exported as COM_* functions, look into serial.def file).
Reed MSDN library for information on this, but remember that it is incorrect in most function prototypes .
You should implement COM_Init (typically driver reads its settings from registry), COM_Open (allocate buffers, return HANDLE for the opened port, that is typically a pointer to allocated buffer), COM_Read (read data), COM_Write (wite data), COM_Close (free the memory allocated in COM_Open). All other functions should be present, but they may do nothing (simply return "success"). You should later implement COM_IOControl function, so that your driver would correctly implement read/write timeouts. My code does not implements this. All timeouts are hard-coded.
My Problem is that i only have emVC++ without DDK or Platform Builder! - It isn't availibe for free, i think!
Click to expand...
Click to collapse
Everything is available for free (soft, beer, girls, etc ). At least in Russia.
Trial 120-day version of Platform Builder 4.20 is available for free from Microsoft.

http://franson.biz/gpsgate/index.asp
Maybe you could look here.

Sorry I can't be any help but...
I've been thinking about CellTracking via GSM for a while now.
Most folk I've talked to in the UK tell me that it's not possible for a GSM device to discover it's own position !?
Any links or pointers on tracking ?
Ideally i'd like to append coordinates of the device on every post to the backend db.
Cheers (and good luck with the comm port thingy!)

I need to creat on my ipaq 5550 a virtual comm port
Hi,
Have you solve your problem ?
I am working on a robotic project and I have the same problem but on a ipaq 5550 under ppc2003.
I need to creat on my pocket pc a virtual comm port.
Because I receive by WIFI, GPS NMEA sentences, so I want to redirect them to this virtual port, and finaly connect to this port my regular GPS navigation software.
Thanks
Laurent
FRANCE

http://ourworld.compuserve.com/homepages/richard_grier/CFSerial.htm

problems on adaptrom source code

Hey Guys
Im trying to update my Wallaby ( Gradiente Partner - Brazil) ROM with special edition ROM, but adaptrom trow a message "unsupperted language PTB". This because my ROM is a PPC 2002 in Portuguese Brasillian. So i picked up the source code of adaptrom to work on it. Installed pocket pc 2002 sdk, open the project and modified the includes and lib directories. But when i compile , i got these errors
rror LNK2019: unresolved external symbol [email protected] referenced in function _main
adaptrom.obj : error LNK2019: unresolved external symbol [email protected] referenced in function _main
Generaly they happen when utilizing a diferent libraries and/or target builds.
Someone could help-me on create a development enviroment to compile the source code?. im using Visual studio 2005 Express beta.

DllMain not run in windows mobile 5.0

It's seems DllMain won't run when a dll loaded by LoadLibrary in wm5.0.
The dll is very simple,complied by vs 2005 beta2,just a MessageBox in dllmain
I load this dll in another process,using the api loadlibrary,In windows mobile 5.0 ppc emulator,no dialog box appear,but you can see that dll.dll had been loaded with remote file viewer.In Pocket PC 2003 SE emulator,every thing is ok
anybody has any idea about it?
Thanks
dll.cpp
#include "stdafx.h"
#include <windows.h>
#include <commctrl.h>
BOOL APIENTRY DllMain( HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved
)
{
MessageBox(NULL,L"11",L"22",0);
return TRUE;
}

Hi,
There is no default entry point in a DLL. You are doing everything fine except you need to load the module (function) you want to call. I cant remember off hand the details but its LoadModule.
Look thought the documentation for calling a function in a dll some more.
Paul

psneddon said:
Hi,
There is no default entry point in a DLL. You are doing everything fine except you need to load the module (function) you want to call. I cant remember off hand the details but its LoadModule.
Look thought the documentation for calling a function in a dll some more.
Paul
Click to expand...
Click to collapse
Thanks for your reply.
I don't want to call any function,excep the default entry point DllMain when loading library.
There should be default entry point in the dll I complied,because in wm2003,everything is ok(Messagebox appears when loading or unloading library)

DllMain worked in my programs in 2K5. Maybe your messagebox appears behind today window? I never tried MessageBox in DLLs, but CreateFile worked fine.

oh right. Maybe I'm wrong - i always thought DLL's didnt have default entry points - I need to get reading the SDK's more
Paul

mamaich said:
DllMain worked in my programs in 2K5. Maybe your messagebox appears behind today window? I never tried MessageBox in DLLs, but CreateFile worked fine.
Click to expand...
Click to collapse
hi mamaich,what device are you using?Emulator?
I've tried in another way:return TRUE or FALSE in DllMain,then check whether the dll is loaded with remote process viewer.
In wm5.0 emulator,DllMain's return value is ingored,the dll is always loaded.And in wm2003 emulator,dll can be loaded only if DllMain's return value is TRUE

I've compiled the DLL with eVC4 and run it on XDA2 with WM5. That DLL was a part of a rather large project.
Maybe VS2005 produces incorrect DLLs?

mamaich said:
I've compiled the DLL with eVC4 and run it on XDA2 with WM5. That DLL was a part of a rather large project.
Maybe VS2005 produces incorrect DLLs?
Click to expand...
Click to collapse
The dll should be ok,it works well on ppc2003's emulator.I have also tried the dll produced by evc4.0.
Seems it's my fault,I got it work on wm emulator now
Thanks for all

I found it,dllmain not run just because the dll export no function.after add a not used fuction,MessageBox appear when loading

delcert - Sign strip tool

Hi,
here is a small tool that strips (removes) digital sign (Authenticode) from PE executable files like *.exe, *.dll, *.mui, etc. On error HRESULT is returned, i.e. 0x00000005 means that file is readonly.
Code:
C:\[snip]>delcert.exe OEM\OEMOpera\OperaWM.exe
Target file(s): OEM\OEMOpera\OperaWM.exe
Stripping file: C:\[snip]\OEM\OEMOpera\OperaWM.exe.
Succeeded.
C:\[snip]>delcert.exe OEM\OEM_Lang_0409\*.mui
Target file(s): OEM_Lang_0409\*.mui
Stripping file: C:\[snip]\OEM\OEM_Lang_0409\aboutprop.dll.0409.mui.
Succeeded.
Stripping file: C:\[snip]\OEM\OEM_Lang_0409\BKLBrightness.dll.0409.mui.
Succeeded.
Source is included. You may need to install Visual Studio 2008 C++ Runtime before running.

I can't believe no one posted thanks for this I just used it recently and it worked a charm! So, thanks! Appreciate your work.

deepred said:
Hi,
here is a small tool that strips (removes) digital sign (Authenticode) from PE executable files like *.exe, *.dll, *.mui, etc. On error HRESULT is returned, i.e. 0x00000005 means that file is readonly.
Code:
C:\[snip]>delcert.exe OEM\OEMOpera\OperaWM.exe
Target file(s): OEM\OEMOpera\OperaWM.exe
Stripping file: C:\[snip]\OEM\OEMOpera\OperaWM.exe.
Succeeded.
C:\[snip]>delcert.exe OEM\OEM_Lang_0409\*.mui
Target file(s): OEM_Lang_0409\*.mui
Stripping file: C:\[snip]\OEM\OEM_Lang_0409\aboutprop.dll.0409.mui.
Succeeded.
Stripping file: C:\[snip]\OEM\OEM_Lang_0409\BKLBrightness.dll.0409.mui.
Succeeded.
Source is included. You may need to install Visual Studio 2008 C++ Runtime before running.
Click to expand...
Click to collapse
Thanks for this...it fixed and issue I had when trying to remove a cert with another tool.

This sounds really interesting, however I was wondering what it can be used for? the certificates usully just provide authentication. Can this be used to bypass protection methods, or what are some real world examples of usage?

You're right, authenticode provides input data for Windows Mobile (originally Windows CE) policy mechanism which decides then if it is allowed to run the file or not. I used it to strip authenticode from OEM files taken from HTC devices before signing them with my own certificate (I usually sign files in my cooked ROMs). I.e. if file is already signed you can't sign it with another certificate until old one is removed.
Due to the fact that certificates are asymmetric you can sign files only with private certificates. That's why I use my own certificates.
To bypass the protection you need to get some how the private part and sign you file with it. Or you can just disable the security policy that enforces file origin check.

Thanks a lot for your work! Your neat little tool is just what I was looking for to be able to sign a Flash projector with my own certificate.

Thanks
Works beautifully when other tools didn't.

Works beautifully when other tools didn't ! Is Right !
Works beautifully when other tools didn't ! Is Right !
Worked Great Thanks - Just What I was Looking For !!!!!

Still working in Windows 8.1
Still working in Windows 8.1
It's great because I can remove the cert from bit torrent and any other group policy blocked programs on my school laptop

Great and awsome tool, this can be an asset for very good "hacks" :good:

Do you have any license requirements on your source or is it safe to assume this is public domain?

Thanks OP. Appriciste for your share
Sent from my DROID RAZR M using XDA Free mobile app

Useful for software publishers
We're using the delcert tool to avoid warnings with expired certificates. Our sign tool doesn't like exe files that already have a valid, but expired signature.