CC256x Production Line Testing

Hi Skip,

Yes, I had reviewed the logs and my previous comment was related to that.
- The rx_f0f0.lgr does not have any delay between the HCI_VS_DRPb_BER_Meter_Result and the corresponding HCI_VS_DRPb_Read_BER_Meter_Result.
- The rx.lgr does and it had multiple HCI_VS_DEPb_Read_BER_Meter_Result calls.
After the confirmation, looks like this is not the case. So moving on in the debug.

The PLT test documentation was originally written to do the PLT test with a Bluetooth tester like the liteview IQ2010 or similar. Another CC256x device is not typically used as TX for this kind of test.

That being said, it is not impossible to use a CC256x as TX and most likely we have a mismatch in the packet configuration. I will check this in the Lab and post my result here tomorrow.

Best regards,
Vihang

Hi Skip,

Necromancing this thread to post the solution for your setup:

* You will need 2 CC256xB boards.

1. Load the initscript (cc256xb-bt-sp) to both TX and RX boards.

2. Start the BER Meter on the DUT (RX) with the following commands.

$l10
count = 0
#DH5 
Send_HCI_VS_DRPb_BER_Meter_Start 0xFD8B, 3, 0, 0x341278563412, 1, 0x5, 339, 500, 0x1FF, 0x1
Wait_HCI_Command_Complete_VS_DRPb_BER_Meter_Start_Event 5000, any, HCI_VS_DRPb_BER_Meter_Start, 0x00

#
$l11
Sleep 100
count++

Send_HCI_VS_DRP_Read_BER_Meter_Status 0xFE2A
Wait_HCI_Command_Complete_VS_DRP_Read_BER_Meter_Status_Event 5000, any, HCI_VS_DRP_Read_BER_Meter_Status, 0x00, &synched, &finished, any, &total_bits, &bit_errors, &packets
if finished== 0 then
	if synched == 0 then
		log"not synced yet %d count",count
		#Fail "no SYNC"
	else
		log"not finished yet %d packets, count %d",packets,count
	endif
	goto $l11
else
	BER = 1000000*bit_errors/total_bits
	log"BER is %d e-6 (%d bits out of %d)",1000000*bit_errors/total_bits,bit_errors,total_bits
	if BER > 100 then
		Fail "BER is too high"
	else
		pause "Finished"
	endif
	
endif

#pause""
goto $l10

3. Start the packet TX on the TX board with the following commands.

# Set BD address
BD_ADDR="123456781234"
Send_HCI_VS_Write_BD_ADDR 0xFC06, BD_ADDR
Wait_HCI_Command_Complete_VS_Write_BD_ADDR_Event 5000, any, HCI_VS_Write_BD_ADDR, 0x00

Send_HCI_Write_Scan_Enable 0x00
sleep 1000
Send_HCI_VS_DRPb_Enable_RF_Calibration 0xFD80, 0x01, 0x00000000, 0x01
Wait_HCI_Command_Complete_VS_DRPb_Enable_RF_Calibration_Event 5000, any, HCI_VS_DRPb_Enable_RF_Calibration, 0x00
Sleep 1000

# Sent Tx Packets
Send_HCI_VS_DRPb_Tester_Packet_TX_RX 0xFDCC, 0x03, 3, 0xFF, 0x5, 0x5, 0, 339, 7, 1, 0x01FF
Wait_HCI_Command_Complete_VS_DRPb_Tester_Packet_TX_RX_Event 5000, any, HCI_VS_DRPb_Tester_Packet_TX_RX, 0x00

When the TX is transmitting the packets with specified modulation and length parameters, every callback of the HCI_Command_Complete_VS_DRP_Read_BER_Meter_Status_Event (0xFE2A) will show you the current count of the packets received. When the count reaches the specified "Number of Packets" value in the HCI_VS_DRPb_BER_Meter_Start command, the last HCI_Command_Complete_VS_DRP_Read_BER_Meter_Status_Event will show you the number of packets received, number of total bits received and number of bit errors.

I have attached the HCITester scripts that I used in this test for your reference.

8424.HCITester_BER_Example.zip

Best regards.

Vihang

Hi Vihang,

I'm confused by "Send_HCI_VS_DRP_Read_BER_Meter_Status 0xFD5B" (line 161 in the script).  According to processors.wiki.ti.com/.../CC256x_VS_HCI_Commands  the 0xfd5b command is HCI_VS_LE_Enable. 

Are the commands prior to the comment "## Set up DUT RX for BER test" in the attached script part of the "service pack", i.e. all of the Send_HCI_VS_Write_Memory_Block commands?

Skip