Hi all, and particularly PGO,
I'm experimenting issues with CodeWarrior10.6 and the USBDM with DSC MC56F8345 or MC56F84789 device. I have created a project and keep all default options. However, it is not possible to load and debug the application. I get the following error when launching the debugging:
In the console:
Executing Initialization File: E:\Codewarrior\84789_BDM/Project_Settings/Debugger/MC56F84789.tcl
radix x
cmdwin::eclipse::config hexprefix 0x
cmdwin::eclipse::config MemWidth 16
cmdwin::eclipse::config MemAccess 16
cmdwin::eclipse::config MemSwap off
Starting 3rd party flash programming...
DiMemoryDownload() - DI_DNLD_TERMINATE - Programming memory image...
===========================================================
Programming target
Device = 'MC56F84585'
Trim, F=0, NVA@0000, clock@0000
Ram[0000...3FFF]
Erase=EraseMass
Security=intelligent
Total bytes=35556
doRamWrites=T
Erase Time = 3.48 s, Speed = 9.97 kBytes/s, rc = 0
DiMemoryDownload() - DI_DNLD_TERMINATE - Programming complete, rc = 7
Thanks for your attention,
Best Regards,
yongsheng
Hi yonhsheng,
The DSC support is rather patchy - The support for MC56F84789 was based upon testing with a similar device MC56F84763 so it is quite possible that I have made a mistakes in the configuration.
You can check the configuration for the device in the dsc_devices.xml device and see if it looks correct.
Could I get you to test the stand-alone programmer first. If this doesn't work please try the debug version of the programmer and provide the usbdm.log and dsc programmer log in %APPDATA%\usbdm directory.
bye
Dear PGO,
Firstly, thank you for your help!
I try to test the stand-alone programmer,and it seem to be right. No errors occur during the programing.Here are the information in the console:
fl::target -lc "test2"
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::device -d -append "MC56F84789_X_FLASH" -o "152kx16x1" -a 0x8000 0x3ffff
cmdwin::fl::protect all off
Beginning Operation ...
Hi yongsheng,
Could you change the options in Codewarrior to use the debug build of the GDI interface:
This will produce a more verbose log in the Codewarrior Console as well as separate USBDM log files
Please look in %APPADATA%/usbdm for the usbdm.log and another DSC or MC56F log file and post here.
bye
Hi pgo,
Thanks for your careful guidance,I follow your advice and find two files:GDI_DSC.log and usbdm.log.Because of the file including too much infomation,I upload the files so that you can convenient to read it.
Thanks for your kind help!
Bye
Hi yongsheng,
The GDI_DSC.log file is indicating that it is finding the device secured.
This may be due to a detection problem in the software but could you do the following to check please:
You can also change the erase option in Codewarrior to "Mass Erase". to see if it makes any difference.
bye