Hi all, I'm trying to install USBDM for use with a JS16 adapter (Ebay). If I install the USBDM V4.12 with the default settings it crashes badly during installation. So i have removed all unwanted features leaving only what i need (HCS08 & RS08 programmers). In this manner the installation work, but the programmers dont. No errors are shown, but, when i try to launch a programmer, the result is only a little flashing of the hd led. The task manager confirm that a process named HCS08_Flashprogrammer is started but a few seconds later the process is terminated. Same result with older releases of USBDM downloaded from sourceforge, and on three other PC all running WXP Professional.
The hardware seems to work properly, i can reprogram the chip and verify the result with no errors.
What i'm doing wrong?? any clues??
I have installed Win-XP 32-bit in a virtual machine on a Windows 8 machine.
I had trouble installing the drivers and have found the reason for that but I had no problems in installing or running the applications (except for being very slow).
I have been unable to locate a WINXP-64bit VM image. What version are you running *32/64-bit?
There might also be a problem with language version of windows but I have no real experience with this.
Attached the image of MergeXML. It says that 2 DLL's are missing. A message on
MS forum says that those DLL's are used on Vista and successive release.
I've tried to download the DLL's but there are so many variants, and i dont know
what is the correct one.
I'm using WXP 32bit on Intel & AMD x86.
I don't believe the problem is due to the DLLs you have mentioned. These are delay-loaded by DLLs within windows and not actually used by the USBDM DLLs.
It would appear that all the DLLs provided by USBDM are finding all their entry points in the supplied DLLs so that looks an unhelpful path.
Could you try the following:
The log files seem to confirm that the problem lies in Xerces-C DLL. I haven't had any luck coming up with ideas of why this would be occurring.
Could you try using the memory dump program which doesn't use Xerces to see if it operates correctly?
I have uploaded a new test version of USBDM to Sourceforge which uses (amongst other things) a different version of the Xerces DLL. This may have some impact on the problem. Could you try this please?
I was thinking that one of the PC on which I tried to install USBDM had WXPSp3
in USA language, on which I could install several language packs. So I think
that even the installation language is the wrong way. Can you send me the length
of the various files obtained after installation, to check that they are
Did you get my last message related to WIN-7 sp1 on 02/15/2017 ?
I can't find a posting with that date and I haven't received a PM, so I'm unsure which message you are referring to.
I am uploading a zip of the installation image for 4_12.1.150 to sourceforge which you can use to check sizes. I will delete it in a few days.
It is very unlikely the installer is changing files.
since it seems that you have not received my message (lost in space??) I am
The original msg was sent on 01/16/2017 00:32 GMT+1.
--> Sorry to have to inform you that the new release of USBDM not work either
under WXPsp3 nor under W7sp1.
The culprit is as always "mergexml". Since I have tried six PCs with different
operating systems and with Intel and AMD CPU and all have the same problem there
has to be a common cause: perhaps the language of my OS?
"Memory Dump", "Firmware Updater" & "JS1 ..." works properly. I enclose the
crash report generated from Win7 and WXP. <--
I provided 3 listings. Two were for the build directories and one for an actual installation. The build directories have extra folders as you have indicated.
I'm sorry but I can't see how I can make any progress on this. The problem may well be a language related error but since it is occurring in the Xerces DLL I can't see any way of debugging it since I can't repeat the error.
What language is your Windows installations? It is unlikely that I will be able to find a version to install but I can have a look.
The Stationery folder is part of the eclipse plugin and would not be created if that option was not installed.
One thing to try (to check another point) is to rename the DeviceData directory and see if the programmer still crashes.
If I rename the "DeviceData" dir, then run the "HCS08 Programmer" the "USBDM
installer" starts, reinstalls a fresh copy of "DeviceData" and then it crashes
with the usually message :smileysad: (Applicazione che ha provocato l'errore
usbdmflashprogrammer.exe, versione 188.8.131.52, modulo che ha provocato l'errore
libxerces-c-3-1.dll, versione 0.0.0.0, indirizzo errore 0x000072f8)
Unfortunately I no longer have access to WINXP machines for testing so the USBDM installer is no longer tested on that platform.
I am not aware of any changes that would prevent installation but that means little I'm afraid.
You can try running the installer with options for creating a log file which might indicate the problem. You may need to edit the attached file so that is references the correct installer name.
Please post the copious log file.
Can you be specific about which installation option is failing?
In the mean time I'll see which features are missing when Programmers are installed by themselves.
PS. It is unlikely that a eBay programmer will support RS08 devices. RS08 required a switched 12V supply which is a rarity in the commercial programmers.
I have tested installing with only the Programmer option selected. It appears to install correctly and function correctly, so it seems likely that there is some incompatibility with WINXP in general that is causing a problem rather than specifically an installer problem. It is possible that there is a problem with MinGW libraries or similar. Do you have MinGW installed?
Thank you for your kind reply.
To isolate the problem i've dedicated the fifth pc to USBDM.
This is a very old Acer 525TX laptop (PIII 800MHz, 512MB ram) with a "fresh &
clean" WXPsp3 OS installation. The only app. installed is Firefox. The other
PC's (4) on wich i've installed USBDM have al least CW6.3 plus oher non NXP mcu
The USBDM installation (184.108.40.206b), leaving only the programmers installed and
NO drivers installed, come flawlessy to the end without any error (NO CW6.3
installed so the installer disables the connection by default).
When i've tried to launch the HCS08 programmer the program crashes. Please see
USBDM#1 screenshot on attached file. The culprit seems to be the
"libxerces-c-3-1.dll" (USBDM#2, USBDM#3); this error appears on all my
installation. Then i've installed the drivers (USBDM_Drivers_4_12_1_WinXP_x32).
The installation failed with the message in USBDM#4.
I've found on NXP community a message (USBDM programmers problem; Dorin Horvath
il 6-gen-2014; https://community.nxp.com/thread/317629 ) that reports the same
problem i'm having.
In my system, two XML files are generated (HCS08_Testdevices &
HCS08_unsupported) that, while can be opened by a text editor, cannot be opened
by firefox or IE. Both reports an error in XML file.
Then i have installed 1.3.0 drivers. They have a strange behaviour: only the
com port e USBDM driver is installed (no JS16), and removing the harware from
USB and reconnecting it, the com port cannot be seen again in device manager.
With a new installation of 1.1.0 drivers, all things are installed ok (USBDM,
COM Port, JS16) but the programmer still not work.
The install log file attached has been obtained on another PC with CW6.3
installed, so the relative option is enabled by default.
The crash is reported in USBDM#5.
Hope it can help you to find a solution.
Do you have a release fully tested on XP machine?
Where can i find it?
Thank you so much,
il 12/02/2017 pgo ha scritto:
I suspect the problem is an incompatibility with MinGW libraries. There are some problems with different versions of the windows DLLs.
It is unlikely to be a problem with the XML files since they are unchanged on different OSs. The files you mention are not valid XML as they are only fragments that are used in other files.
Could you try dependency walker on the Xerces dll and see if indicates missing dependencies?
I will try to locate a Win-XP installation disk and see if I can run it in a virtual machine to see if there are similar errors.