Codewarrior 10.6 and 5F8335

cancel
Showing results for 
Search instead for 
Did you mean: 

Codewarrior 10.6 and 5F8335

440 Views
v_dave
Contributor IV

Hello All,

 

I am using Codewarrior 10.6 and a USB Tap for code development with a 56F8335 based project.  I am having troubles getting the USB Tap to connect with my target.  I keep getting "CCSProtocolPlugin : CCS: Core not responding" error when trying to enter debug.

 

I have seen some older posts about changing the config from a 56F8335 to a 56F8345 in order for the USB Tap to connect.  I have done this and now I can connect and load my debug app onto the target. What I want to know is if this is still the correct method to properly debug this type of project.  The posts I have seen are from 2007(Re: 56F8335 Debug Support - What CFG file should be used?) and it would seem with the new Eclipse based stuff this step should not be necessary.

 

So as I start working on a major project I would just like to know if this is the proper setup.

 

Thanks.

Labels (1)
0 Kudos
4 Replies

170 Views
TICS_Fiona
NXP Employee
NXP Employee

For 56F8335 programming and debugging, we should choose the configuration files for 56F8335, they are:

C:\Freescale\CW MCU v10.6\MCU\lib\wizard_data\DSC\DataBase\init_files\MC56F8335.tcl

C:\Freescale\CW MCU v10.6\MCU\lib\wizard_data\DSC\DataBase\mem_files\MC56F8335.mem

It is not the correct solution to use 56F8345’s configuration files.  Because 56F8345 has 128KB P flash, while 56F8335 only has 64KB.

I have no 56F8335 to test it, could you please send me the log file generated when programming with 56F8335’s configuration files? And which file (.tcl, or .mem) is replaced by 56F8345’s, then 56F8335 can programmed successfully by CW10.6? Thanks!

Fiona Kuang

Technical Information & Commercial Support

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

Note: If this post answers your question, please click the Correct Answer button. Thank you!

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

0 Kudos

170 Views
v_dave
Contributor IV

CW-10_6 56F8335 mem.JPG.jpgCW-10_6 56F8335 Init.JPG.jpg

Hello,

Above are two screen shots showing my configuration screens.  I simply change the Target Type to MC56F8345 and it will connect but if I leave the target type at MC56F8335 it will not connect to my target.

Is there a different .mem or .tcl files I need to reference?

0 Kudos

170 Views
TICS_Fiona
NXP Employee
NXP Employee

The difference in .mem file is: P flash address is from 0x00000000to 0x00007FFF in “MC56F8335.mem”, while it is from 0x00000000to 0x0000FFFF in MC56F8345.mem.

And the difference in .tcl file is that MC56F8335.tcl does not initialize FMCR, FMPROTB register.

Please only use “MC56F8345.tcl” to replace “MC56F8335.tcl”, and keep “MC56F8335.mem” does it work?

Fiona Kuang

Technical Information & Commercial Support

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

Note: If this post answers your question, please click the Correct Answer button. Thank you!

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

0 Kudos

170 Views
v_dave
Contributor IV

Hello,

I have finally gotten a chance to get back to this project.

I tried to make the changes as you suggest but I am not able to connect at all when I select the 56F8335 and point to the files you indicated.  I have opened an SR request on this issue  (1-3745451141)

I am pretty much unable to progress on my project until this is resolved.

0 Kudos