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.

CCS/TMS320F28388D: Where I can get the description of the macros define in the error code file; errno.h? How to test errno.c?

Part Number: TMS320F28388D


Tool/software: Code Composer Studio

Hi,

I am not able to find the description in the following code file, errno.h, which is located in the following pat:; C:\ti\ccs920\ccs\tools\compiler\ti-cgt-c2000_18.1.3.LTS\lib\src\errno.h

Could you guys please check and tell me where to find? is there any document provided?

Also, how test these macros, is there any use case?

Regards

Gurusha

  • TI does not provide documentation for parts of C and C++ which are standard.  For details, please search the C28x compiler manual for the sub-chapter titled Related Documentation.

    gurusha nahar said:
    how test these macros, is there any use case?

    Unfortunately, TI has published nothing on this topic.

    Thanks and regards,

    -George

  • George,

    Since the header file contains so many macros but didn't mention the description of many of them, then how do we supposedly check on this part?

    -Gurusha

  • Use the same web sites, training courses, tutorials, books etc. you use to learn C.  

    Another method to consider ... The function strerror returns a string that corresponds to an error code from errno.h.  The source code to all of the RTS, including strerror, is in a directory with a path similar to ...

    C:\ti\ccs1011\ccs\tools\compiler\ti-cgt-c2000_18.1.3.LTS\lib\src

    Here are the key lines in strerror.c ...

    _CODE_ACCESS char *strerror(int errnum)
    {
       switch(errnum)
       {
          case 0      :  return ("No error");
          case EDOM   :  return ("Domain error");
          case ERANGE :  return ("Range error");
          case ENOENT :  return ("No such file or directory");
          case EFPOS  :  return ("File positioning error");
       }
    
       return ("Unknown error");
    }

    Thanks and regards,

    -George