LCF functionality in CodeWarrior Eclipse for DSC56F8300/E QuickStart v2.5 project

[matejpacha_Ineltech]

Hi,

I'm migrating old Classic CW v8.3 project for 56F8300 and QuickStart v2.5 to the new CW Eclipse v11.1. I'm able to use the GCT, compile the code, debug and run the program, but there are certain issues:

1) the Classic CW uses LCF files to configure memory. Here in the Eclipse, I have found only the "prefix" file option, so I'm using the "version.h" from the QuickStart. I have copied settings from the original linker command file header to the prefix file, but it seems it is not enough to initialize variables in startup automatically.

2) FreeMASTER Recorder requires the buffer is placed in fardata section. I'm using the same cmd file as in the classic CW and I have included the section definition in the prefix file. However, if I enable the FreeMASTER Recorder in its _cfg file, I'm getting an error "Description Location Resource Path Type
Accessing Fpcm_pOwnRecBuffer symbol [freemaster_rec_c.obj] in section fardata.bss located in X data memory address above 0x007FFF, with small data model, can result in wrong memory access. Rebuild [freemaster_rec_c.obj] with -largeAddrInSdm to resolve possible wrong memory access. Project C/C++ Problem"

If anyone has some experience with migration of QuickStart v2.5 projects, I will be very happy to hear about it.

[xiangjun_rong]

Hi,

I suppose that the part number is MC56F83xx for example MC56F8346 instead of MC56F83xxx for example MC56F83789, am I right?

As you know that the CodeWarrior Eclipse tools supports both MC56F83xx and MC56F83xxx, I suppose that you can create a project with the correct part number and use the default link file the tools generates, it is okay

BR

XiangJun Rong

[matejpacha_Ineltech]

Hi,

thank you for following up.

Yes, I mean i.e. 56F8346 or 56F8367 (those two specifically), in more general: the "E-core" family (Core V2).

CW Eclipse does "support" those parts, however, the QuickStart v2.5 is using different linker command file (different in content), also containing some definitions for LCF processing (like a prefix). I'm pretty sure about this, because when I use old-style cmd file with those LCF definitions, they are not considered. If I put those definitions into a separate prefix header file, they are (pre-)processed correctly.

In case I would start a brand new project, I would probably go with the MCUXpresso and its configuration tools. This is different - I have a project with the QuickStart v2.5 GCT @codewarrior Classic IDE working & validated and it would mean another round of development + complete V&V process. This is why I would highly appreciate to have it running with the original QS GCT v2.5.

Thanky you in advance!

Best regards,

Matej