• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 636 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/TM4C123GH6PM: SCPI library for suing the UART at TM4C123GH6PM ?

Green Power
Intellectual 835 points
Part Number: TM4C123GH6PM

Tool/software: Code Composer Studio

Hi everyone, 

I am developing an instrument with the TM4C123GH6PM, I am using an UART to access to it for configuring and retrieving data from an external device (e.g. the serial port in a PC).  Now that I am developing the communication protocol, I was wondering if there exits any library for implementing the SPCI comunication protocol and make my instrument SPCI compatible :) 

SPCI is en.wikipedia.org/.../Standard_Commands_for_Programmable_Instruments

Any idea or comment?

Thanks in advance. 

Best regards 

  • 0
    TI__Guru*** 135355 points
    Hello Green Power,

    We don't have any library for SPCI with TM4C, and I searched the forums but it doesn't look like any community members tried to do that or shared anything related either unfortunately.

    Not sure it would work well with UART from what the wiki page stated though, USB might be a better option for that. But in any case, we don't have any collateral or resources to offer.

    You may want to look through source sharing sites like github and see if there is a general library for Cortex M4F processors which you could then import into TM4C. That'd likely be your quickest path forward.

    Best of luck if you move forward with implementing that, sorry we can't help more.
  • 0
    Guru 117855 points

    While the use of a, "Tech Standard" proves usually desirable - one wonders if this, "1990 era standard" proves best (today) - 28 years later?

    Much can be learned (especially command inclusion & format) yet before investing substantial, "blood/sweat/treasure" - might the "Search for a NEWER such "Instrument Standard" prove worth-while?"

    Should a "newer standard" exist - possibly even building upon & enhancing one past - that would appear a superior approach...

    (and ... rather than "Suing the UART" - "Arbitration" usually proves more collegial - and faster ...)     (Subject lines "Suing" - CAN be edited!)