Compiler/TM4C129XNCZAD: Compiler/TM4C129XNCZAD

Hello Marco,

Can you post some of the code so we can better understand this?

Do you have optimizations on, and if so, at what level?

Also, if you do have optimizations on, can you turn them off and see if the issue still persists? That could indicate if optimizations are a possible issue.

Lastly, CCS is free now and TM4C is well supported on newer versions, can you try the same with CCS v9.1 and the latest LTS compiler and see how that works? Even if just to help give us another data point here as this is a very obscure issue as it stands right now.

Hi Ralph,

thank you for your reply.

As a matter of fact I've already tried to compile with CCs9.1 and last arm-ti compiler v.18 but the problem is always the same.

I think you are right when you talk about optimization, and for that reason I'll do same try with these parameters.

I'll let you know the result of this tuning and meanwhile I'll post you the piece of code where the system stuck.

 //***************************************

    uint8_t *pData = (0x10000000 + offset);
    int32_t iRead = 0;
    int32_t iSizeAlloc = getSize( filename );
    int8_t buff = 0;
    
    fp = fopen( filename );
    iRead = iSizeAlloc;
    while( iRead > 0 )
    {
        buff = fgetc( fp );
        EPIWorkaroundByteWrite( pData, buff );
        pData++;
        iRead--;
    }
    fclose(fp);