This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

enet_s2e DK-TM4C129X --- BUILDING ERROR

Expert 1255 points
Other Parts Discussed in Thread: EK-TM4C1294XL, TM4C1294NCPDT, TM4C129XNCZAD

Hi ,

I have made the suggested changes in the Files as suggested in the forum(https://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/522950/1923558#1923558. I was able to build successfully for EK-TM4C1294XL.

BUT....Since i am working with DK-TM4C129X

I made the following changes:

(a) Replace the labels PART_TM4C1294NCPDT and TARGET_IS_TM4C129_RA1 with
PART_TM4C129XNCZAD and TARGET_IS_TM4C129_RA0 in the project settings.
(b) Uncomment the line that defines the label DK_TM4C129X in the enet_s2e.c file.

(c) In properties -->ccs general-->Changed the variant and connection to tm4c129xnczad and stellaris icdi---since it dint get updated automatically

(d)still showed error during build regarding pinoutset() function. The pinout.c file in the driver was still linked to the ek-tm4c129xl. So in pinout.c properties --> resources I changed the location as SW_ROOT\examples\boards\dk-tm4c129x\drivers\pinout.c .

(e)During build am facing the following errors

(f) Made the following changes in enet_s2e.c

#ifndef DK_TM4C129X
    PinoutSet();
#else
    //PinoutSet(true, false);
#endif

(g)  Made the following changes in tm4c129xnczad.cmd

MEMORY
{
//FLASH (RX) : origin = 0x00000000, length = 0x00100000
// SRAM (RWX) : origin = 0x20000000, length = 0x00040000
}

and

//__STACK_TOP = __stack + 512;

(h) Deleted the file startup_ccs.c as there were issues regarding multiple declarations in startup_ccs.c and tm4c129xnczad_startup_ccs.c

(i) changed __STACK_TOP = __stack + 4096; to __STACK_TOP = __stack + 512;  I am not sure if that was needed.

Now I don't have errors, but i am doubful if this the right thing to do in terms of the utility of the application.


Could you help me regarding this

Thanks a lot 

av