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

CC256x fails HCI VS commands...

TB at WHY6
Intellectual 290 points
Other Parts Discussed in Thread: BL6450, MSP430F5438

Hello,

I suspect that the post that I left at http://e2e.ti.com/support/low_power_rf/f/660/t/260129.aspx was both too long and failed to get to the point quickly enough.

The problem is that HCI VS commands sent to the Controller fail, typically returning a Command_Complete event packet indicating that the commands are not recognized. This is  consistent with a note regarding HCI_VS_Start_VS_Lock that was found in an HCI VS guide for the BL6450.

This problem means [it seems] that I am not able to load an initialization script into the Controller. More details regarding why I want to do this are included in my other post (link included above).

Aside from the Panasonic wrapper (a PAN1323) for the TI Controller, this is a TI-centric application using CCS v5 for development and MSP430F5438 for the Host. The Host is running a non-preemptive task manager (no OS), and the Controller is responsive to other HCI commands. However, the BT radio cannot currently be made discoverable, which is the reason for running an initialization script (a service pack).

Help with this would be greatly appreciated!

  • 0
    TI__Mastermind 23565 points

    Hello Tim,

    This topic will be followed in this post: http://e2e.ti.com/support/low_power_rf/f/660/t/260379.aspx 

    Thank you,

    Miguel

  • 0
    Intellectual 290 points

    Hello Miguel,

    You have answered my questions regarding those things which are "on the other side of the fence" from my development work, which helps me to partition the problem more decisively.

    It didn't make sense to me that there would be any special HCI VS command unlocking sequence, but I wanted to confirm this before focusing more time on the application-specific code, which is where the problem is most likely to exist. As mentioned, the HCI commands work fine and it is just the processing of the VS commands that fails. As a result, I will look into what, if any, differences there are in handling these different types of commands.

    Thanks for your help.

    Regards,

    Tim

  • 0 in reply to TB at WHY6
    TI__Mastermind 23565 points

    Tim,

    Most likely there is something wrong with the format of the HCI cmds that you are sending. From the BHET, you could check the HEX dump for each command.

    Regards,

    Miguel

  • 0 in reply to Miguel
    Intellectual 290 points

    Miguel,

    I agree and am looking into the actual bytes being transmitted. I suspect that a "face palm" moment is on the horizon: the most plausible cause of this problem is programmer error.

    Aside from this bump in the road, the MSP430F5438 and the PAN1323 are both nice packages to work with and CCS v5 is doing all that I ask of it. The 5438 is very responsive and is just sipping power.

    Thanks again for your help.

    Regards,

    Tim