Freescale DSC Flasher :: Digital Signal Controller Stand-Alone Flash Programmer

cancel
Showing results for 
Search instead for 
Did you mean: 

Freescale DSC Flasher :: Digital Signal Controller Stand-Alone Flash Programmer

2,070 Views
NXP Employee
NXP Employee

Access AN4824 at www.freescale.com

and AN4824SW for the executalbe.

 

The Freescale DSC Flasher is a stand-alone flash

 

programmer for the MC56F8xxx family of Digital Signal

 

Controller products. It is meant as an alternative to the

 

CodeWarrior Flash Programmer

that is integrated within the

 

DSC Flasher: Stand-Alone DSC Flash Programmer

 

application is provided under a command-line interface and

 

is intended to easily integrate with scripts.

Labels (1)
20 Replies

4 Views
Contributor II

Hello John ,

As you wrote it was a Font issue , I cleared the "Clear Font" and it worked thanks .:smileyhappy:

But Now when I Do a Program/Verify I get the following message :

================================

Performing PROGRAM operation on MC56F84789 through the UTAP . . .

Error 1: Unaligned srecord at C:/work/Bootloader/uC/Bootloader/MC56F84789_Internal_PFlash_LDM/56F84789_Bootloader.elf.S:271: "S30B0001F3FDCDAB3412FF0046" .

=============================================

But when I am using the Flash operation using the Codewarrior  I do not get any Error , please see the following :

pastedImage_1.png

Console output :

====================================

fl::target -lc "LC for Simple Flash"

fl::target -b 0x60400 0x1000

fl::target -v off -l off

cmdwin::fl::device -d "MC56F84789_P_FLASH" -o "144kx16x1" -a 0x0 0x6bfff

cmdwin::fl::image -f "C:\\work\\Bootloader\\uC\\Bootloader\\MC56F84789_Internal_PFlash_LDM\\56F84789_Bootloader.elf.S" -t "Auto Detect" -re on -r 0x0 0x6bfff -oe off

cmdwin::fl::erase image

Beginning Operation ...  

-------------------------

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Performing target initialization ...  

Erasing ......

Erase Command Succeeded. 

cmdwin::fl::write

Beginning Operation ...  

-------------------------

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Programming ...

Program Command Succeeded  

Flash Operation. done 

cmdwin::fl::device -d "MC56F84789_X_FLASH" -o "152kx16x1" -a 0x8000 0x3ffff

cmdwin::fl::image -f "C:\\work\\Bootloader\\uC\\Bootloader\\MC56F84789_Internal_PFlash_LDM\\56F84789_Bootloader.elf.S" -t "Auto Detect" -re on -r 0x8000 0x3ffff -oe off

cmdwin::fl::erase image

Beginning Operation ...  

-------------------------

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Nothing to erase.  No sectors selected

Erase Command Succeeded. 

cmdwin::fl::write

Beginning Operation ...  

-------------------------

Flash Operation.  ...

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Programming ...

Programming warning.  No data to be programmed in selected flash memory range.

Program Command Succeeded  

Flash Operation. done 

fl::target -lc "LC for Simple Flash"

fl::target -b 0x60400 0x1000

fl::target -v off -l off

cmdwin::fl::device -d "MC56F84789_P_FLASH" -o "144kx16x1" -a 0x0 0x6bfff

cmdwin::fl::erase all

Beginning Operation ...  

-------------------------

Performing target initialization ...  

Erasing ..........

Erase Command Succeeded. 

cmdwin::fl::device -d "MC56F84789_X_FLASH" -o "152kx16x1" -a 0x8000 0x3ffff

cmdwin::fl::erase all

-------------------------

Erasing ..........

Erase Command Succeeded. 

cmdwin::fl::device -d "MC56F84789_P_FLASH" -o "144kx16x1" -a 0x0 0x6bfff

cmdwin::fl::blankcheck all

Beginning Operation ...  

-------------------------

Flash Operation. 

Blank Checking ..........

BlankCheck Command Succeeded. 

cmdwin::fl::device -d "MC56F84789_X_FLASH" -o "152kx16x1" -a 0x8000 0x3ffff

cmdwin::fl::blankcheck all

Beginning Operation ...  

-------------------------

Flash Operation. 

Blank Checking ..........

BlankCheck Command Succeeded. 

fl::target -lc "LC for Simple Flash"

fl::target -b 0x60400 0x1000

fl::target -v off -l off

cmdwin::fl::device -d "MC56F84789_P_FLASH" -o "144kx16x1" -a 0x0 0x6bfff

cmdwin::fl::image -f "C:\\work\\Bootloader\\uC\\Bootloader\\MC56F84789_Internal_PFlash_LDM\\56F84789_Bootloader.elf.S" -t "Auto Detect" -re on -r 0x0 0x6bfff -oe off

cmdwin::fl::erase image

Beginning Operation ...  

-------------------------

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Performing target initialization ...  

Erasing ......

Erase Command Succeeded. 

cmdwin::fl::write

Beginning Operation ...  

-------------------------

Flash Operation.  ...

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Programming ...

Program Command Succeeded  

Flash Operation. done 

cmdwin::fl::device -d "MC56F84789_X_FLASH" -o "152kx16x1" -a 0x8000 0x3ffff

cmdwin::fl::image -f "C:\\work\\Bootloader\\uC\\Bootloader\\MC56F84789_Internal_PFlash_LDM\\56F84789_Bootloader.elf.S" -t "Auto Detect" -re on -r 0x8000 0x3ffff -oe off

cmdwin::fl::erase image

Beginning Operation ...  

-------------------------

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Nothing to erase.  No sectors selected

Erase Command Succeeded. 

cmdwin::fl::write

Beginning Operation ...  

-------------------------

Flash Operation.  ...

Auto-detection is successful. 

  File is of type Motorola S-Record Format. 

Programming ...

Programming warning.  No data to be programmed in selected flash memory range.

Program Command Succeeded  

Flash Operation. done 

================================

Please advise if you have a solution as I need to give our production line an easy tool for programming ( via command line ...batch ...)

Thanks in advance for your support

Ruvi

0 Kudos

8 Views
Contributor II

Hello ,

Please advise if the DSC Flasher can work on Windows 7 64bit ? as I am getting garbage on the GUI ..

DSC.JPG

Thanks Ruvi

0 Kudos

8 Views
NXP Employee
NXP Employee

It should work perfectly well.  It uses Java. Perhaps it is a font issue?

8 Views
NXP Employee
NXP Employee

Hi John,

I have used the standalone DSC Flasher, it needs longer time to download than 56800E Flash Programmer 1.2. Whether or not there is a way to improve the download speed?

0 Kudos

8 Views
NXP Employee
NXP Employee

Have you compared it to USB TAP? Or are you comparing two different programming hardwares?

Best Regards,

John L. Winters

Senior Applications Engineer

AMR/EU MCU & MPU AE Group

Freescale Inc.

2100 Elliot Road

This email and any associated attachments have been classified as:

Freescale Confidential and Proprietary

0 Kudos

8 Views
NXP Employee
NXP Employee

Hi John,

We used the stand alone DSC Flasher to download S-Record file through USB TAP, it needs longer time than old 56800E Flash Programmer 1.2. Whether or not it is ccs driver issue? if yes, is there any way to improve? thanks!

0 Kudos

8 Views
NXP Employee
NXP Employee

Please provide all data such as part number and customer.

Best Regards,

John L. Winters

Senior Applications Engineer

AMR/EU MCU & MPU AE Group

Freescale Inc.

2100 Elliot Road

This email and any associated attachments have been classified as:

Freescale Confidential and Proprietary

0 Kudos

8 Views
NXP Employee
NXP Employee

Customer: Little Swan

Part number: MC56F82723

The download time comparision:

Freescale DSC Flasher: 70s               56F82723

56800E Flash Programmer 1.2: 5s       56F8023

For Freescale DSC Flasher, after click "Run" button, the message box displays as follows, which last for 60s.

"Performing PROGRAM operation on MC56F82723 through the UTAP"

What operation is done in this status?

0 Kudos

8 Views
NXP Employee
NXP Employee

The source for this slow programmer can be given to a resource once one is identified. Then that resource can address issues with the programmer. Please escalate to your local management for this resource to be assigned.

Best Regards,

John L. Winters

Senior Applications Engineer

AMR/EU MCU & MPU AE Group

Freescale Inc.

2100 Elliot Road

This email and any associated attachments have been classified as:

Freescale Confidential and Proprietary

0 Kudos

8 Views
Contributor I

We just upgrade the controller from MC56F8367 to MC56F84789.

In the previous project, I able to dump some data into specific flash memory location by using 56800E Flash Programmer.

However this programmer cannot support MC56F84789.

I tried with DSC Flasher but it cannot support dumping method.

Can you please advise?

0 Kudos

8 Views
Contributor III

KS Chan -

I think that the only way you will get some assistance is if you submit a tech support request from the freescale.com web page.   It doesn't appear that this thread or this forum are monitored regularly by anyone at Freescale as my request/threads on the DSC Flasher haven't gotten any response from them in weeks.  So, I've submitted a support request, which does go into their tracking system.

Good luck - I am sorry that I cannot provide you with any info/clues.

0 Kudos

8 Views
Contributor I

Ok thanks.

0 Kudos

8 Views
NXP Employee
NXP Employee

One current limitation of the flasher is that it was not intended for programming the peripheral registers of the device.

If the s-records contain addresses in the peripheral memory map, those s-records containing such address should be removed.

The same applies to addresses in RAM.

The flashwer was intended only for programming flash.

On a powercycle, any updates to RAM or the peripheral register map would be lost anyway.

If you have other needs, please let us know.

0 Kudos

8 Views
Contributor III

I seem to be having issues trying to get this to work on the (2) Windows XP machines I have tried so far.

In both cases, I am using the same USBTAP Rev F, and trying to program some 56F8367 DSC devices.

In one case, I also have Codewarrior 8.3 installed on the machine and regularly use it for development.   The USBTAP works fine with it and I am using CCS Version 4.13 build 363p0.

But, without CW or an instance of CCS running and simply trying to use the DSC Flasher to erase and program some DSCs, it will fail to do so with the following appearing in the console window:

Performing PROGRAM operation on MC56F8367 through the UTAP...

Error 9: CC config string is invalid

Make Sure your Device is Plugged-In and No Other Devices are Configured to the Run Control Device. Close all CCS Applications Prior to Flashing Target Device.

Changing the JTAG clock speed to various values as low as 100KHz has no effect.  CCS Timeout is still at 10 seconds.

On the other XP machine (which I am trying to configure for actual production usage) there has never been any CodeWarrior software installed.   I downloaded and installed the DSC flasher and the CCS USBTAP drivers according to the documentation.  The CCS version actually appears to be the same revision and build that is on the other XP machine.

Attempts to program several different DSC 56F8367 devices all result in the same error messages and failure on this machine - the console log shows:

Performing PROGRAM operation on MC56F8367 through the UTAP...

Error 9: Core not responding

Check that the Target Device Model Number Matches "MC56F8367"

If Model Numbers Match, Then UnPlug and Replug the Device

It doesn't matter if I cycle power to the target device, unplug/replug the USBTAP connector, or unplug/replug the USBTAP itself - any other attempts result in the same outcome. It won't work.  It will (apparently) Mass erase the DSC OK, but always fails as soon as it starts to write to program flash.   The results are identical if I use the command line interface or the GUI interface.

I know that the S-record file is good, the target hardware is good, and the USBTAP is good because I can use my CodeWarrior 8.3 to debug, program, erase, etc. all of these target PCBs.   But, my intent is to use the DSC flasher for production programming use - and it appears to have problems.

Any assistance you can provide is much appreciated!

Mike F

0 Kudos

8 Views
Senior Contributor I

Mike, I gave-up trying to use this application, as using USB TAP ONCE, I can program the 56F8367 & 56F8257, but using the DSC flasher I am getting an error message: core not responding...

Ben

0 Kudos

8 Views
Contributor III

Hi Ben,

I guess misery likes company!   While I am glad that I am not alone in this, I wish I knew what was preventing it from working as it seems the utility would be very good for production usage - I need to get some automated scripts and procedures setup for production use, and using the old eval-version of CW to download with TCL scripts is clunky and not good/easy to describe to people who are as technically oriented, or English speaking.

0 Kudos

8 Views
Senior Contributor I

by the way: I posted a new question here, as you are using the same chip, maybe you have a solution for me. Please have a look

Ben

0 Kudos

8 Views
Contributor III

I will look!

0 Kudos

8 Views
Senior Contributor I

Hi Mike

I am sure that it is a problem of a script file for this chip, and I want to investigate it for several weeks, I wish there were more hours a day:smileyhappy:

Anyhow, why don't you download eclipse CW version? it has a good build-in programmer for this chip.

It will take you some time to move from the old version to this one, it has it's learning curve,but I think you'll like it.

0 Kudos

8 Views
Contributor III

We did get the new eclipse version early in 2013 and tried it out.   Frankly, we weren't too pleased with it.  Debugging with the USBTAP was no faster, and often slower than with the 8.3 version.  Also, code image size expanded by a significant amount, and we were already hard pressed to keep things working using the small memory model for faster performance.  Additionally, I've also written a bootloader for the chip which we use in a distributed system for performing firmware updates among the processors, and that was also getting closer to its 32K limit.

We will eventually jump to Eclipse, but it caused too much difficulty and made too many changes to already heavily tested and qualified code to make the change at this time.

I am primarily concerned right now on getting a production programming solution implemented so that people in Mexican factories can easily program these chips with the least amount of oversight/handholding or the need to have reconfigure and use CodeWarrior just for programming the chips.  And, do it cheaply..

0 Kudos