• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 490 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.

Original question:

CC1310: the sensor call ApiMac_mcpsDataReq to send out data but return error number 0xF1 sometimes

CC1350: How to increase collector data tx queue in linux sdk?

Pratik Bhagat
Intellectual 700 points
Part Number: CC1350
Other Parts Discussed in Thread: TIDEP0084,

Hello,

I am getting Tx overflow when i called some function to send data 15 times.

I am using BBB based collector application.

I am not able to find the file mac_cfg.c in my whole bbb sdk.

Any suggestion will be really helpful.

Thanks,

Pratik

  • 0
    TI__Mastermind 23636 points
    Hello Pratik,

    You can import the coprocessor image into ccs and go to mac_cfg.c and re compile the image changing the macro to a bigger number, usually when you get these type of errors is because you are sending data to the mac layer faster than it is being sent out through the radio/PHY. I would recommend reading the return value of send_msg and make sure it has successfully sent before attempting to send the next packet to the mac.

    Regards,
    AB
  • 0 in reply to AB
    Intellectual 700 points

    Hello AB,

    Thanks for your reply.

    For co-processor, currently i am using hex file directly from my linux sdk folder.

    So i don't have image to load and change that value.

    Secondly if i am sending data at faster rate than radio/PHY.

    For that reason i have given a delay of 500 ms in between two consecutive function calls.

    Than also i am getting same thing.

    Only first two times it is successfull, after that it is not giving success from sendmsg();

    Thanks,

    Pratik

  • 0 in reply to Pratik Bhagat
    Intellectual 700 points
    Hi AB,

    Furthermore i want to ask,
    My collector sdk is from :git.ti.com/.../tidep0084
    I dont know which ver of collector it is in tidep0084. How to check that ?
    So i was using hex file for co-processor.

    As u said i have imported co-processor image for sdk ver: sdk_2_20_00_38.
    But getting this error at starting of collector application.

    1.150: Collector_updateFwList: new oad file: ../../firmware/oad/sensor_oad_cc13x0lp_app.bin
    1.151: Collector_updateFwList: Added ../../firmware/oad/sensor_oad_cc13x0lp_app.bin, ID 0
    1.198: Found Mac Co-Processor Version info is:
    1.198: Transport: 3
    1.198: Product: 1
    1.198: Major: 2
    1.199: Minor: 0
    1.199: Maint: 1
    1.245: ERROR: **ERROR** Set/Operation failed with status code: 0x27
    1.261: ERROR: **ERROR** Set request failed code: 0x27
    1.277: ERROR: **ERROR** Set request failed code: 0x27

    is it mismatch of version?
    How to solve this.
    Do you have any version related mapping or something help, this is very confusing.
    For which sdk_xx_xx_xx_xx, which collector code and which co-processor code needs to be used?


    Thanks,
    Pratik
  • 0 in reply to Pratik Bhagat
    TI__Mastermind 23636 points
    Hello Pratik,

    Collector version is the one from that repo, the collector is the code that runs on the BBB. The co processor image is what runs on the CC1350, it was last updates in march 2018 for TI 15.4 Stack v2.4, this would mean that this matches CC13x0 SDK v1.60. Try this version of the SDK.

    Regadrs,
    AB
  • 0 in reply to AB
    Intellectual 700 points
    yes i did and it worked.
    But now the issue is after using this my co-processor is stopping after an hour.
    Means, It is running for an hour and than stops, again after some time it will run.
    This thing i noticed when i dump the co-processor image from code.
    But it was working perfectly fine when i used co-processor1310lp.hex from bbb sdk of TIDEP0084.
    Any other modification needed for this thing ?

    Thanks,
    Pratik