• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 699 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.

GATT_WriteNoRsp documentation --- a contradiction?

Happy Dawg
Intellectual 300 points
Other Parts Discussed in Thread: CC2640

In the SWRU993_CC2640 BLE Software Developer's Guide, the description for GATT_WriteNoRsp() says: "Used to request the server to write or cancel the write of all the prepared values currently held in the prepare queue from this client."

The description in the code (gatt.h) says something very different.  It says it performs a write and does not ask for a response from the server back to the client.  Furthermore, it says the write is by definition a short write of just a few octets... which seems fine if that's all we need to do and don't need a write response back from the server.

The first description sounds more like a "write with full flush" function --- which is not suggested by the second description.

Is either one accurate?  Or is the actual function something that blends both of those contradictory descriptions?

  • 0
    TI__Mastermind 34660 points
    Hello. I'm looking at the 2.2 SDG and I see:

    "This sub-procedure is used to write a Characteristic Value to a server when the
    client knows the Characteristic Value Handle, and the client does not need an
    acknowledgment that the write was successfully performed. This sub-procedure
    only writes the first (ATT_MTU – 3) octets of a Characteristic Value. This subprocedure
    can not be used to write a long characteristic; instead, the Write Long
    Characteristic Values sub-procedure should be used. The ATT Write Command is
    used for this sub-procedure. The Attribute Handle parameter shall be set to the
    Characteristic Value Handle. The Attribute Value parameter shall be set to the new
    Characteristic Value."

    I'm not sure what you're referring to.
  • 0 in reply to Tim C
    Intellectual 300 points
    Ah, it appears I am looking at the 2.0 and the 2.1 SWRU993 SDGs.

    Sounds promising --- although I don't relish converting to 2.2 this soon after it is released.
    Glad they got this small part of the documentation fixed.