USBDM has been updated to V4.6. This version adds support for Kinetis devices but please be aware that this has had minimal testing due to lack of devices to test with .
Please post any queries on this version in this thread,
Information available at: http://usbdm.sourceforge.net/
Please note that these design are different from the Freescale OSBDM-JM60 design which was proceeding independently while I was doing the above designs
I do'nt have seen any change by remplacing the libusb dll with the new version one (on my Win 7 AMD computer, CFV1_programmer with the 4.5 version is OK, and the 4.6 version fails ).
For wath concerns the new firmware (4.6b), I programmed it with the JS16 GUI Bootloader (BLMS grounded during power-on) and with a P&E multilink.
Unfortunately, after being reprogrammed, the USBDM is recognized by the comptuter as "JS16 device" and not as USBDM. (I have the simplest JS16 version of USBDM - I have tried on my XP and on my Win7 computer with 2 differents USBDM).
Best regards and thanks for your work
I downloaded and tried programming the Posted USBDM_JS16CWJ_V4.abs.s19 file using the Freescale JS16 Bootloader. I believe this would be the file you are using.
I found the Freescale Bootloader unreliable on some machines especially if using a USB hub. It would give a programming error at a particular address.
Can you confirm that you get (only) the following messages for the Load, Mass Erase followed by Program sequence?
File Selected: [C:\Peter\Development\USBDM\USBDM_JMxx_Distribution_V4.6\1. Installation\USBDM_Flash_Images\USBDM_Flash_Images_4_6b\USBDM_JS16CWJ_V4.abs.s19] Erasing ... 0x0 Done Programming ... 0xFFFA Done Doing CRC ... CRC Checksum Error Error while doing CRC
The CRC Checksum error is to be expected. In particular could you note the adress of the last block programmed (0xFFFA in the above example).
Thanks for the time spent debugging.
I am trying to test your USBDM_JM60_CF with Codewarrior 7.2.2 — is that still possible?
I see that in the install script batch file, you check for “tblcf.dll” which is not present in the version 4.6 dll directory, so the script skips the section for Codewarrior 7.2
Does version 4.6 still work with Codewarrior 7.2, and where could I find the missing
That is an error in the installation script. tblcf.dll is no longer used. It has been replaced with usbdm-cfvx-gdi-legacy.dll.
I had intended including a copy of tblcf.dll for capatibility but it was missed. You can modify the installation script accordingly or manually install the preferred files.
Another thing to be fixed in V4.7 I guess
I was about to build a new prototype to test on Kinetis processors -- since you mentioned there were changes in version 4.7, would it be possible to get a sneek preview of your version 4.7 schematic and would it be of any help if I build and test a pcb?
I've uploladed some documentation for the V4.7 if you want to look at changes. Not much significant apar from an different PCB layout for the "deluxe" version.
Hopefully other files will follow in a few days after I fix some installer bugs.
I've a same problem with your new version 4.7 of usbdm firmware and tools software. I'm working on windows 7 64bit edition and I'm using codeworrior 6.3 and 7.2 under Windows XP mode in Windows 7. Usbdm device id shared to winxp via usb virtualization technology and it works fine with previous version of USBDM pack (4.6). But now under windws 7 for ex. cf_programmer tool view my usbdm device, but when I attach it to my windows xp mode this same software does not detect my usbdm device. I check device istallation in device manager and every thinks looks good. Also I try to connect with usbdm with new firmware (4.7) via old (4.6) software, and it works fine. Finally I don't know why the new version of your software don't detect my device.
Sorry I missed your post.
I've run Codewarrior for Microcontrollers V6.3 OK without using any virtualization 'stuff' under windows-7-64bit. The installation method has been posted earlier in this thread. I would suggest that this would be a easier approach.
In particular I think the problems you are seeing are due to changes in the libusb version being used. As a test please try the following:
Please advise if the above works.
If the above does work try re-installing the libusb driver files using zadig. This is provided in the USBDM installtion.
Report a problem:
This file does not meet the actual burning address.
Should be started from 0x3C00.
Lead to not run bootloader.
Flash Programmer to burn shows great progress.
In addition, when using MCF51AC series, select the environment in CW10 RESET button nothing happens.
One of the (unintended) changes was a movement from 16K to 32K flash images. The version 4 bootloaders should cope with any size image. It is possible that earlier bootloaders have a bug in this respect. Can you tell me what version bootloader is in the BDM or if its actually a JM16 chip?
I will post reduced files shortly as there was no real reason for the change apart from reducing the number of different linker files and juggling the amount of RAM available.
However, note that the combined versions require larger RAM & ROM.
thank you for all your answers !
Now the Coldfire V2 works both in CW10.1 and CW 7.2
Next I wanted to use the DSC in CW 8.3 on a MC56F8013 target.
I configured the remote debugging connection as you explained in the usage pages, and selected usbdm-dsc-gdi-legacy-debug.dll (the non-debug version had the same error)
When the debugger is launched the USBDM configuration dialog comes up, but when one okays the dialog, it fails saying "Illegal BDM command"
In the usbdm_DSC_gdi.log it says it's loading settings from "USBDM__HCS08.cfg", could that be the cause? The two log files are attached, in case you have a moment to look at them...
P.S.: If I can't get the USBDM to work with Codewarrior 7.2, do I have to fill in correct data in the "cfvx_devices.xml" for the CFVx_Flashprogrammer.exe to work with a Coldfire V2 target?
I wanted to flash a MC52254 which is not in the cfvx_devices.xml.
I can find the memory values in the "MCF52254.mem" file in the Codewarrior installation, but I don't know the sdid value ...
Many thanks again!
if by VMware you mean running this on a Macintosh in a virtual environment, I had the same problem using XP inside Parallels Desktop. My guess is, that the emulation messes up the USB timing.
I tried VirtualBox, but it had the same problem.
In Parallels, I can get it to work one shot at a time, meaning I have to unplug and replug the USBDM every time the connection gets lost.
In practise, once per debug session: launch the debugger without the USBDM plugged, when the USBDM dialog comes up and the device is not detected, plug it in, then rescan, it finds the device and succeeds to run, but when you close the debugger, this has to be repeated on the next launch.
I found that reverting to the old version 3.2 this problem doesn't occur, so it must be due to the new usb lib being used in version 4.
First of all I'd like to thank you for the great work on USBDM.
I managed to get USBDM 4.5 working on an ubuntu 8.04 (32-bit) by remanimg a few of the dlls.
The same 4.5 failed to install on a debian stable 64-bit.
I was not able to install V4.6 in either of the system mentioned above.
Both ubuntu 32-bit and debian 64-bit are missing several libraries (or have an incompatible version),
I believe most of the problem can be easily solved by recompiling the software on the target machine.
I downloaded the source distribution but I cannot figure out how to build it.
Do you have any documentation?
The source code for the libraries etc are an export of the projects from Eclipse. It's not set up for a stand-alone make mainly because I have no idea how to do it.
You should be able to import them into an Eclipse installation to re-create the projects. The build targets and settings are part of the Eclipse projects.
thanks for your reply.
I tried to import the project using the archive importer and a few other ways without success.
Regardless of how I try to do the import I can't find a way to create a native build (i.e. not a microcontroller)
I am sure it's my fault (I really don't understand how eclipse projects work).
Are you using CW eclipse or a different flavor?
Could you give me a few more hints?
Wot Jim said!
Sorry I was unclear. The Libraries etc are built using a standard Eclipse CDT (C development) version of Eclipse downloaded from http://www.eclipse.org/cdt/.
You may also need: