OSBDM and TBDMLのトピックRe: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Thu, 16 Feb 2012 14:04:01 GMT

Dear All,

USBDM has been updated to V4.9.

Please post any queries on this version in this thread,

Information available at: SourceForge

bye

Note

Please note that these design are different from the Freescale OSBDM-JM60 design which was proceeding independently while I was doing the above designs.

BDM History

V4.9 (February 2012) -
- Extensive changes to HCS12 programmer
- Added programming algorithms for several HCS12 devices (HY,HA,XE,XS).
- Autoselection of firmware image for update.
- Tested with Codewarrior 10.2
V4.8 (December 2011) -
- General update of how the programming algorithms are controlled.
  They are much more configurable by the external XML and TCL files. This allows for some customisation of the memory map on HCS12 devices or custom startup operations.
- Added Coldfire+ devices & algorithms.
- Erase options extended (on some targets).
- Re-testing of all devices (see programmer help file) with complete memory images including paging were used.
- Bug fixes on HCS08 programming. Unsure were these were introduced but (hopefully) now squashed.
- Paging of Flash and EEPROM has been updated for HCS12 and HCS08 devices.
- The memory image descriptions are now more detailed and are more carefully enforced when programming. Attempting to program non-existent memory is now reported before programming is attempted. This should result in more meaningful error messages.
- msi install updated for Codewarrior 10.2
- Testing with Codewarrior 10.2 Beta
V4.7 (October 2011) -
- Improved support for devices in low power modes (Eclipse).
- Improved support for secured devices (Eclipse).
- BDM interface speed control implemented for CFVx devices
- Windows Installer
- Updates for Eclipse Kinetis device name changes
- BDM firmware (including bootloader) will now auto-detect 4, 8 or 12 MHz crystals. (JS16/JMxx)
- Added progress dialogues for programmers.
- Programmer erase options are more consistent.
- Bug fixes
  - Devices incorrectly identified as secured
  - Failure to connect to device in low power modes
  - Corrections to CFVx connection sequences
  - Corrections to USB CDC Driver installation
  - Bootloader reliability improved
  - Corrections to USB CDC driver installation file.
V4.6 (June 2011) -
- Support for Kinetis Targets in Codewarrior V10.1 (Eclipse, USBDM/CF only)
- Improvements to USB error checking (JMxx/JS16 only)
- TCL scripting
V4.5 (February 2011) -
- Support for Codesourcery Lite - Coldfire Vx
- Support for Coldfire Flasher (CFFlasher) Coldfire V2,3,4 only
- Support for Codewarrior Eclipse 10.1
- Flash buffer is now dynamically sized in Flash programmers
- Added fix for Legacy Codewarrior tools missing TBDML/OSBDM targets

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

MarkK — Fri, 17 Feb 2012 06:18:59 GMT

Hi,

Can you tell me if version 4.9 of USBDM will work with S9S12P32JOMQK processors?

Thank you,

Mark

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Fri, 17 Feb 2012 09:04:12 GMT

Dear Mark,

It has been tested with a S9S12P128J0MQK which is the same die I believe so it should. I have not however tested it as I don't have that chip.

By tested I mean with the HCS12 programmer provided and as a TBDML device with Codewarrior 5.1.

It would work with codewarrior in previous versions in any case I believe.

bye

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

MartinKupec — Fri, 17 Feb 2012 17:21:18 GMT

Hi,

I was looking for linux version of USBDM and I have found linux instalation only for V4.6, but not for any newer.

Is something different on the new releases, or was just linux support droped?

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Fri, 17 Feb 2012 18:45:42 GMT

Hi Martin,

No - not dropped just neglected.

I built the V4.8 on linux but couldn't get the eclipse plug-in to load for some reason. I've been distracted since then.

I'll do the current version and see if I can work out what the problem is.

bye

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

MarkK — Fri, 17 Feb 2012 18:48:22 GMT

Thank you; I'll give it a try.

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

MartinKupec — Fri, 17 Feb 2012 19:29:57 GMT

pgo wrote:
Hi Martin,

No - not dropped just neglected.

I built the V4.8 on linux but couldn't get the eclipse plug-in to load for some reason. I've been distracted since then.

I'll do the current version and see if I can work out what the problem is.

Ok. Thank you a lot. If I can be of any help, let me know. I don't know much about eclipse and eclipse base codewarrior, but I can did some developement on linux platform.

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

joncas — Wed, 22 Feb 2012 21:17:31 GMT

Hello PGO,

many thanks for all this!

A totally minor and cosmetic bug: the 4.9 installer seems not to put a shortcut to the Bootloder.exe in the Startmenu with all the other USBDM utilities.

In case it is of any use to anyone else who has the Rx and Tx pins brought out so they can connect to the target, I recompiled the USBDM_JMxxCLD version with the serial port enabled: http://flashgenie.net/Firmware-Update.html

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Thu, 23 Feb 2012 09:24:04 GMT

Dear joncas,

I've confused you by changing the name The program is still bootloader.exe but the Menu item is

USBDM Firmware Updater which is a better description.

bye

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

joncas — Thu, 23 Feb 2012 15:08:59 GMT

pgo wrote:

... The program is still bootloader.exe but the Menu item is USBDM Firmware Updater which is a better description.

Of course ! I should have looked more closely ...

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

MarkK — Fri, 24 Feb 2012 03:34:20 GMT

Hi,

I tried version 4.9 with a S9S12P128J0MQK chip, and got the following error message:

Programming of target flash failed!

Reason: Program data not within target flash memory

Can you give me any idea what might cause this?

Thank you,

Mark

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Fri, 24 Feb 2012 08:21:58 GMT

Dear Mark,

The programmer checks the S-record file against the description in the USBDM XML device files. The error you are getting indicates that the programmer thinks the range you are trying to program is outside of the memory map for the Flash in the chip.

The device entry for the MC9S12P128 is as follows:

      <device family="HCS12" name="MC9S12P128">         <clock type="External" />         <memory type="ram">            <memoryRange end="0x3FFF" start="0x2800" />         </memory>         <memory registerAddress="0x0100" type="eeprom" sectorSize="256">            <memoryRange end="0x0013FF" start="0x000400" />         </memory>         <memory pageAddress="0x0015" registerAddress="0x0100" type="flash" securityAddress="0xFF00" sectorSize="512">            <securityInfoRef ref="HCS12-default-security-off" />            <securityInfoRef ref="HCS12-default-security-on" />            <memoryRange end=  "0x27FF" start=  "0x1400" />            <memoryRange end=  "0x7FFF" start=  "0x4000" />            <memoryRange end="0x00BFFF" start="0x008000" pageNo="0x0E" />            <memoryRange end="0x08BFFF" start="0x088000" />            <memoryRange end="0x09BFFF" start="0x098000" />            <memoryRange end="0x0ABFFF" start="0x0A8000" />            <memoryRange end="0x0BBFFF" start="0x0B8000" />            <memoryRange end="0x0CBFFF" start="0x0C8000" />            <memoryRange end="0x0DBFFF" start="0x0D8000" />            <memoryRange end="0x0EBFFF" start="0x0E8000" />            <memoryRange end="0x0FBFFF" start="0x0F8000" />            <memoryRange end=  "0xFFFF" start=  "0xC000" />         </memory>         <sdid value="0x3980" />         <flashScripts>            <tclScriptRef ref="HCS12-FTMRCK-flash-scripts" />         </flashScripts>         <flashProgramRef ref="HCS12-PMMC-FTMRCK-flash-program" />      </device>

This is for a paged memory map.

Could you compare your s-record file? I might have made a mistake in the above or possibly the s-record file is using linear addresses which would require a different entry.

How are you producing the file?

If it's not confidential and not too large you could post a Zip and I will look at it.

bye

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

marco8 — Sat, 25 Feb 2012 07:14:51 GMT

Hi PGO,

I am attaching the file that won't load into the 9s12P. I have tried deleting the S0 record and also all the RAM address records which gets past the addr range error. After that it seems to finish programming but is rejected when verifying. I have tried all the different erase options. The board is working and I can program it with another programmer but am trying to use the USBDM-1 board with ver 4.9.

Thanks for your help,

MarkK

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Sat, 25 Feb 2012 07:44:26 GMT

Dear mark

Yes I can confirm that it is a bug in USBDM. The chip has a minimum program element of 8 bytes (a phrase). Your image has two disjoint regions with in the same phrase. This is triggering the bug.

I will fix this shortly!

If you are in a hurry you can modify your program to close the gap at 0xFFE9-0xFFEE but there may be other spots.

Sorry.

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Mon, 27 Feb 2012 07:13:42 GMT

Dear Mark,

This bug has been fixed in V4.9.2 uploaded to sourceforge.

Test at you convenience.

PS. You will still need to remove the reference to the RAM areas.

bye

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

marco8 — Tue, 28 Feb 2012 05:37:17 GMT

Hello pgo,

I downloaded the updated V4.9.2 to USBDM-1 and now file loads and works great - THANKS!

Mark

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

Cdn_aye — Tue, 28 Feb 2012 12:24:20 GMT

Sorry if this is obvious but I just got my usbdmlt from Technological Arts, I ran the updater and allowed it to find its own load file, which it seemed to do ok. I ran the check and it failed. Now the USbDM firmware updater fails on "USB device failed to open" when I tell it to read from the device, although it is displaying a serial number of USBDM-J16-SER-CF-0001.

I then tried to flash to USBDM_CF_SER_JS16CWJ_V4.sx, but it says that the "Image file does not appear to be for this hardware."

Then I allowed the updater to find the flash update on its own (auto update bdm firmware), and it successfully updated to 4.9. But the target would not load. It kept saying to power cycle hardware, but the usbdm was supplying the 3.3v power. I reran the Updater with the auto update and it said it failed on the 2nd reboot attempt.

I am running Windows 7 x64, Codewarrior 10.2 & MQX 3.8. The project is a 51jm129 (CF V1).

I ran the zadig program, and added the launch configuration to CW10.2. The debugger launchs but gets stuck in assembler code.

1) Is there a special firmware file I need to load other than the one I tried to load?

2) Will this device support JTAG, and if so what do we need to do to connect it to a K20?

Thanks

Robert

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

pgo — Tue, 28 Feb 2012 13:54:44 GMT

Dear Robert,

I'm very surprised with the result you got when updating the BDM.

I believe the usbdmlt is a JS16 based HCS08/12 BDM so the auto-update should display

USBDM-JS16-0001 as the serial number and

USBDM - (JS16CWJ) as the Hardware version

I don't have a USBDMLT to check this with however. I upgraded a similar bdm just to check and this appeared to go OK.

The correct file should be USBDM_JS16CWJ_V4.sx.

Testing was done on windows-7 64-bit.

The BDM only supports HCS08, HCS12 and CFv1 devices. It does not support JTAG (K20 etc).

I'm unclear if some of the errors you mentioned were with the stand-alone programmers. If you haven't tried these please try the CFV1 Programmer.

Also the Cycle Power message is something of a generic error message that is produced whenever the BDM can't connect. Some of the HCS08/CFV1 devices may required a power cycle to connect in debug mode. The BDM can't differentiate this situation from the many other reasons that a connection may fail. The BDM can't do the power cycle itself and so prompts for manual cycling of the power (with the BDM connected). I'm unsure how to do this with the USBDMLT - does it have a power connection jumper that can be temporarily removed? In any case, as mentioned this may be irrelevent to the problem. You would probably get the same error without a target connected.

I suggest you try the following:

Connect the BDM directly to the PC (no hubs).
Run the Firmware Updater and check the auto option box. Confirm that the File information is as described above. If not it can't be updated properly using the firmware updater.
If it indicates the correct details, select the Verify option to verify the BDM flash against the image. If you get a reboot error - repeat! If it succeeds even once it indicates that the Flash is correctly updated. Some PCs seem to object to the 'suprise removal' event used to reboot the BDM the second time - I haven't been able to find a reason for this but it only occurs very rarely on one of the machines I've tested. If it appears to spend a long time at the Doing normal re-boot... dialogue you can even try quickly removing and re-plugging the BDM to get the reboot to work.
Try the stand-alone CFV1 Programmer. If you get errors please advise. It may be necessary to cycle the power if the chip is entirely blank due to COP timeout problems (one of the occasions that require the power cycle reboot to guarantee successful connection).

bye

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

brunolalb — Wed, 29 Feb 2012 03:32:23 GMT

Hi pgo,

I'm trying to make a USBDM to program DSCs (MC56F8006 specifically) that provides power to the target. Is it possible to use all USBDM_CF_JS16CWJ v1.2 schematics and add a LDO to provide 3V3 to the target, using the same firmware? or the firmware would have to be modified? Could you suggest something for this project?

I already have a prototype that uses a LDO which uses USB power (5V) and turns it to 3V3. The power is selected through a jumper between 3V3 (from LDO), 5V (directly from USB) or nothing, but I'm getting several errors and software hangings.

Regards,

Bruno

Re: USBDM - Version 4.9 (JS16/JMxx Hardware Versions)

marco8 — Thu, 01 Mar 2012 06:12:13 GMT

Hello pgo,

To get the file to load thru USBDM-1 I changed the DFlash location in the mc9S12P128.inc codewarrior file from 10400 to 0400. But then the DFlash doesn't show up on the codewarrior memory map (using 10400 it shows up at 0400). I don't need to use the global memory map. Is there a DFlash address that will work for both codewarrior and USBDM?

Thanks

Mark