Original question:
CC1310: Linux collector hangs with ERROR: **ERROR** Set/Operation failed with status code: 0x19
Replies: 22
Views: 176
Part Number: CC1310
I have a simple set up with 1 coprocessor running on my Linux desktop + 3 temperature sensors that keeps sending temperature reading every 10 seconds. Frequency Hopping is enabled in this start network set up.
Observations:
1, Got quite a few of these:
14262.492: reset-indication msg(672d) nbytes=11 len=6 [ 0xfe 0x06 0x41 0x80 0x04 0x03 0x01 0x02]
Looks like the CC1310 device just restart once in a while.
2. After running for a day or two, the coprocessor just hangs. As a result, all sensors also hang. When I type "o"When I type "o" to permit join on/off, I get:
Hi Dzuy,
Can you post the SDK number for the CC13x0 SDK and Linux SDK? (For Linux SDK the latest version that is compatible with CC1310 is 3.30.)
Cheers, Marie H.
In reply to Marie H:
The linux ti_collector is from one of ti154stack_linux_x64_4_30_00_06 example.
The coprocessor is from the simplelink_cc13x0_sdk_4_10_02_04.
In reply to Dzuy Nguyen:
Can you download the 3.30 linux SDK and retry? (Scroll down for previous versions.)
This is the exact version I currently have.
This is the same exact version I have now.
You wrote that you are using ti154stack_linux_x64_4_30_00_06.
I would recommend you to use TI-15-4-STACK-GATEWAY-LINUX-SDK_3.30.00.12
Sorry, ti154stack_linux_x64_3_30_00_12 proves to be worse off than ti154stack_linux_x64_4_30_00_06.
With ti154stack_linux_x64_4_30_00_06, my test can run for days.
With ti154stack_linux_x64_3_30_00_12, it freezes up with 378.524: ERROR: **ERROR** Set/Operation failed with status code: 0x19 within minutes.
I think the problem is with the coprocessor code, not the linux SDK.
It sounds to me like the issue could be either with the linux side or the coprosessor side, or if the two are not working together as expected.
Were you able to debug what's going on n the CC1310 side when it's hanging? E.g. you can disconnect the linux and attach a debug session.
Marie,
We've debugged the linux side and we don't think the problem is with ịt The collector simply sends a command to the coprocessor and keeps waiting for a reply that never comes from the coprocessor, and it ceases to do anything else.
We tried to debug the coprocessor through CCS and it won't attach via XDDS110. I was hoping that since you're the expert, you can help us figure out how to use this thing.