you are not disturbing! which version did you use that caused the problem, and
which version worked? we need to make the build more resistant to this kind of
issue.
On March 12, 2018 7:46:24 PM PDT, "Sun Lifeng 孙立峰 (690)"
<sunlifeng...@haier.com> wrote:
>Hi, dev,
>
>About this issue, I found the root cause. This is because I used wrong
>version of tinyCbor.
>
>Sorry again for disturbing your work.
>
>Jason Sun
>
>发件人: Sun Lifeng 孙立峰 (690)
>发送时间: 2018年3月9日 17:35
>收件人: 'iotivity-dev@lists.iotivity.org'
>主题: 答复: Using CTT tool can't find device resource in SECURED mode
>
>Hi, dev,
>
>I compared the logs when doing finding resource and succeeded and
>failed, attached here.
>
>One key different is log 47:26.289 ERROR: OIC_RI_PAYLOADCONVERT: Failed
>closing link map with cbor error: 'unknown error'..
>
>Hope this is useful.
>
>Thanks
>
>Jason Sun
>
>发件人: Sun Lifeng 孙立峰 (690)
>发送时间: 2018年3月9日 15:29
>收件人: 'iotivity-dev@lists.iotivity.org'
>主题: Using CTT tool can't find device resource in SECURED mode
>
>Hi, dev,
>
>I did a test with CTT2.1.0 and IoT1.3.1. But unfortunately, CTT can’t
>find the resource I created. Then I run my project with those
>libs(libocbtstack.so, liboc.so) generated from IoT1.3.0, CTT does can
>find all.
>
>Then I compiles IoT1.3.1 again with following command.
>scons TARGET_ARCH=arm SECURED=1 LOGGING=1 LOG_LEVEL=DEBUG
>
>And run my project, I got 2 logs(attached here) for starting my project
>and running CTT to search resource respect.
>
>For log search.txt, we can see here are some ERROR and also one log as
>“47:26.269 INFO: OIC_RI_SERVERREQUEST: Server Request not found!!”.
>
>Could you help have a look at this because I am not familiar with the
>implementation.
>
>Thanks
>
>Jason Sun
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
