Hot![Solved] BM71 command 0x39 always fail

Author
Post
Essentials Only Full Version
Jonathan Chau
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2018/10/12 03:11:46
  • Location: 0
  • Status: offline
2018/10/12 20:30:23 (permalink)
0

[Solved] BM71 command 0x39 always fail

Using BM71 for custom service application (i.e. working directly with GATT instead of using transparent UART), it seems that unless handle value is 0x0003 (pointing to Device Name in build in DIS) issuing command 0x39 for all other GATT chars to update char value will always fail with error 0x0C Command Invalid, i tried one by one for all handles, from 0001 up to custom GATT services 8004, and the result is the same, is it normal situation and if so, what does that error mean and what is the prerequisites for issuing 0x39 command?
post edited by Jonathan Chau - 2018/10/13 02:58:09
#1

2 Replies Related Threads
    Jonathan Chau
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2018/10/12 03:11:46
    • Location: 0
    • Status: offline
    Re: BM71 command 0x39 always fail 2018/10/13 02:04:35 (permalink)
    0
    A follow up to this problem: command 0x38, which is Send Characteristic Value, works perfectly when connection established and client turn on notification on that characteristic, but such method only works when client turn on notification and the underlying value of the characteristic is not updated, this is not a solution to me as client may instead choose to poll the value by using read instead.
     
    Also looking at the source code of the example at http://microchipdeveloper.com/ble:bm71-app-example-stopwatch-demo I can see that in the BM70.c library the action for command 0x39 is, out of my guesses, goes to ReadLocalAllPrimaryService! So if I had to guess, 0x39 is a NOT IMPLEMENTED operation but somehow existed in the user guide?
     
    Also a bit out of topic, but yesterday I submitted a case to the microchip support and today I got somehow banned saying "account is temporarily deactivated because of inactivity" and cannot login to look at my case anymore, what can I say except how good services Microchip provides me?
    #2
    Jonathan Chau
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2018/10/12 03:11:46
    • Location: 0
    • Status: offline
    Re: BM71 command 0x39 always fail 2018/10/13 02:57:11 (permalink)
    0
    Update: Finally solved this problem, the solution is, one have to check the "attribute updated" check box when creating Characteristics in configuration tool to allow 0x39 operates! Now only if someone can point to me, in which document do this behavior well documented, so that next time I (or somebody else) will not again make such mistake anymore?
    #3
    Jump to:
    © 2019 APG vNext Commercial Version 4.5