kw45 hci_black box_RX test got wrong response

[Annie_he]

Hi NXP team,

    Now we are developing a bluetooth board with KW45B41Z83 for smart keyless entry application.

    And we flashed kw45b41zevk_hci_bb_bm.bin to our board. 

   TX cmd works OK and we got corret response cmd.

[10:33:04.322]发→◇01 1E 20 03 00 25 00 
[10:33:04.326]收←◆04 0E 04 01 1E 20 00

   But RX cmd did not work properly, it seems the dut response timeout or uncorretly.

the test log as Below:

9.RX_LE 2402 1LE ____________________________________________________________
ENABLE_RSSI : 1
FREQ_MHZ : 2402 MHz
CABLE_LOSS_DB : 0.00 dB
RX_PACKET_NUMBER : 50
RX_POWER_LEVEL : -70 dBm
OPTION_STRING :
PACKET_TYPE : 1LE
WAVEFORM_NAME : 1LE.iqvsg
>>>
Sending: 01 1d 20 01 00

<<<
>>>
Received: 04 0e 04 01 1d 20 00

<<<
>>>
Sending: 01 1f 20 00

<<<
>>>
Sending: 01 1f 20 00

<<<
>>>
Received: 04 0e 06 01 1f 20 00 00 00

<<<
Test Time = 8.213 s
ERROR_MESSAGE : com connection error
--- [Failed] : test function error

10.RX_LE 2442 1LE ___________________________________________________________
ENABLE_RSSI : 1
FREQ_MHZ : 2442 MHz
CABLE_LOSS_DB : 0.00 dB
RX_PACKET_NUMBER : 50
RX_POWER_LEVEL : -70 dBm
OPTION_STRING :
PACKET_TYPE : 1LE
WAVEFORM_NAME : 1LE.iqvsg
>>>
Sending: 01 1d 20 01 14

<<<
Test Time = 8.049 s
ERROR_MESSAGE : com connection error
--- [Failed] : test function error

   Therefore we wonder to ask you which pin is import to RF Hci RX test? Or the current/voltage of any pin is import to RF Hci RX test and what the value should be? Please help us to review and confirm. Thanks

    Best,

    Annie

[Christine_Li]

Hi, @Annie_he 

Can you please share your test steps?

So that I can have a try with our KW45-EVK. 

And then check our KW45-EVK design difference with our board.

Best regards,

Christine.

[Annie_he]

Hi Christine,

     Thanks for your response. Here is my steps:

     1. I asked my SW workmate to flash fulse in the board, it seems the key of blutooth.

     2. Then I flash kw45b41zevk_hci_bb_bm.bin to my board, and it reminded me of flashing OK.

     3. I try to use HCI TX cmd to control DUT, like 01 1e 20 03 00 25 00, and it response >>04 0e 04 01 1e 20 00.

     4. I started to use IQxel-80 to test the RF performce of the DUT, it went very well in TX test and I got the data which I wanted.

    5. When it stsrted to RX test, Iqfact reminded me "com connetion error".

    6. I used Uart to send RX cmd, and DUT can not response correct news, like below:

   So I can not test RX item, Sometime dut gave me wrong response.

   Would you please to help me to figure out the problem? Thanks

   Best Regards,

   Annie

[Christine_Li]

Hi, @Annie_he 

Thanks for your reply.

May I know your SDK version? I will download a same version with you to have a try on my side.

Are you using MCUXpresso? May I know your IDE version?

Best regards,

Christine.

[Christine_Li]

Hi, @Annie_he 

Can you please let me know what tool are you using to send these commands?

Are you using our Test Tool 12?

If not, can you please share me your tool by sending me a private email(christine.li@nxp.com)? Because here is a public community, you might not want to share it in public.

I am testing our KW45-EVK board with Test Tool 12.

Best regards,

Christine.

[Annie_he]

Hi Christine,

     Thanks for your help and sorry I am late.

     And SDK we are using: SDK_2_12_5_KW45B41Z-EVK. And We use MCUXpress generate  hci_bb.bin file to location and use J-link to flash.  IDE version is: STM32Cube IDE 1.13.2.

    The tool we uesd for sending command is a general UART tool, it Maybe not so important. And Our Developing Board can not connect to Test tool 12 but EVK can do that. I will send the tool for you by mail later if you need it.

    One thing is important is that, we are developing two kinds of boards by KW45, one named ECU, and the other one named Anchor.

    When we flashed hci_bb FW into ECU & KW45-EVK, It work successfully on TX and RX test, But Anchor is working the same as I mentioned---RX test fail.

    The only different is the different pin definication and working Voltage between the two kinds of boards.  But pins 39&40 of both of the two kinds of boards are BLE_KW45_MCU_UART1_RX [4,7]BLE_KW45_MCU_UART1_TX, it is same.

    Therefore, Maybe we need konw which pin is important for RF test, we think maybe the different pin definication may caused test failing.  Thank you very much!

    Best Regards,

    Annie

[Christine_Li]

Hi, @Annie_he 

Thanks for your info and sorry for my reply because I took 2 days PTO.

1.Yes, please share your tool to me so that I can have a try on my side. To protect it, please send it to my private email(christine.li@nxp.com) and not post it on this public community.

2. If ok, please send me your schematics for both ECU(OK) and Anchor(NOK), so that I can compare it for you. From your given info, it seems like a hardware side issue. And also, to protect your company's right, please do not post it on the public community, but send to my private email.

Best regards,

Christine.

[Christine_Li]

Hi, @Annie_he 

I checked our KW45-EVK schematics, the  VCC_TGMCU is connected to 3.3V power in default.

On your NOK board Anchor, what is your VCC_TGMCU voltage?

And how about your OK board ECU?

Best regards,

Christine.

[Annie_he]

Hi Christine,

     Thanks for your kind help for us.

     Rencently, We desided to stop the design of Anchor and we are not sure when it will start again. But if we have more time, I will check the VCC-TGMCU(3.3V supply) for ECU and Anchor.

     Thanks for your imformation providing for us. And I will sent you the UART tool by mail.

     Best Regards,

     Annie

[Christine_Li · Accepted solution]

Hi, @Annie_he 

Thanks for your reply.

Then would you mind help to close this ticket?

When you re-start  the Anchor project, and if still have problem, please feel free to create a new one.

Have a nice day~

Best regards,

Christine.