Documentation error in CC256x Testing Guide?

Joe Black

Hi all,

This page (http://processors.wiki.ti.com/index.php/CC256x_Testing_Guide#UART_Communication) in CC256x Testing Guide says the following:

Outgoing Hex dump: 0x01 0x01 0x10 0x00
where the first number indicates a command sent (0x01), the second number (0x01) indicates command length and third and fourth is the command

I think this is a documentation error. If the third and fourth number are the command, the second number indicating command length should be 0x02 instead of 0x01.

Is this example actually correct at all? The Bluetooth specification clearly indicates an Op_code always has a length of 2 octets (16 bits), followed by Parameter_Total_Length of 1 octet (8 bits), followed by the actual parameters with a length defined in Parameter_Total_Length.

Thanks in advance for your insights on this.

over 11 years ago

0 Sundeep Javvaji over 11 years ago

TI__Mastermind 32615 points

Hi,

It is a command packet.

Please see the E2E post http://e2e.ti.com/support/wireless_connectivity/f/660/p/321214/1149375.aspx for better understanding

0 Joe Black over 11 years ago in reply to Sundeep Javvaji

Intellectual 440 points

Thanks for your reply.

I understand it is a command packet, because it starts with 0x01 and I understand the command itself is composed of an OCF and an OGF part.

To make it more clear:

0x01: This octet defines it is a command
0x01 0x10: These 2 octets are the command itself (as described in the Bluetooth specification)
0x00: This octet defines the argument length (which is 0, because no arguments are given)

In the Bluetooth specification is defined that an Op_code (0x01 0x10 in this case) is always 2 octets in size, so why does the TI wiki say you have to provide the length of the command if the length of the command has a fixed length per definition?

0 Joe Black over 10 years ago in reply to Joe Black

Intellectual 440 points

Hi, any news on this?

0 Sundeep Javvaji over 10 years ago in reply to Joe Black

TI__Mastermind 32615 points

Hi,

I did not get you question.

Anyway let me answer, we give "Length of parameters in bytes" . It is generic for all the Command Packet this command does not have any parameters. But other commands does have.

0 Joe Black over 10 years ago in reply to Joe Black

Intellectual 440 points

Did some testing and can confirm for sure this is faulty documentation in the wiki. The description in my previous post is the correct explanation of the code.

This is what the text in the wiki (http://processors.wiki.ti.com/index.php/CC256x_Testing_Guide#UART_Communication) should be:

Outgoing command: HCI_Read_Local_Version_Information
Outgoing Hex dump: 0x01 0x01 0x10 0x00
where the first number indicates a command sent (0x01), the second number (0x01) and third number (0x10) is the command and the fourth number (0x00) is the total parameter count.

I hope someone can update the wiki with this info.

0 Sundeep Javvaji over 10 years ago in reply to Joe Black

TI__Mastermind 32615 points

Hi,

Thanks for pointing out. we will update it ASAP.

Bluetooth®︎

Bluetooth forum

Documentation error in CC256x Testing Guide?