Announcements

Help us improve the Power & Sensing Selection Guide. Share feedback

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
edOfTheInfineon
Level 3
Level 3
First solution authored 10 replies posted 25 sign-ins

My goal is to delete bonding by reflashing.  The smp_delete_bond command is not working for anyone on my team.

 

What I Tried Using WICED_MOD_Programmer

I am using Windows 11.

  1. I downloaded ezserial_CYBT-483056-02.hex
  2. WICED_MOD_Programmer does not have an option to select CYBT-483056-02 so I selected CYBT-483039-02 instead
  3. Selected UART Adapter board
  4. Selected DUT #1, Configure, and selected WICED HCUI UART (COM12), 115200, CTS, then Connect button
  5. Set Firmware File Path to ezserial_CYBT-483056-02.hex
  6. Checked "program BD Address" and checked "Gen a random address"
  7. When I press Program button it quickly failed

 

29-09-2022 11:11:06.204: ProgramManager: Selecting_DUT 1/8
29-09-2022 11:11:07.575: Prog[0]COM12 : Reset (COM12) Timeout!
29-09-2022 11:11:07.580: Prog[0]COM12 : Soft-Reset Fail COM12
29-09-2022 11:11:07.581: Prog[0]COM12 : Failed to reset on baudrate = 115200
29-09-2022 11:11:07.582: Prog[0]COM12 : Failed to reset DUT
29-09-2022 11:11:07.582: ProgramManager: ---->SetResult [1,1] = TestFailed
29-09-2022 11:11:07.613: ProgramManager: Selecting_DUT 2/8
29-09-2022 11:11:07.735: ProgramManager: Selecting_DUT 8/8
29-09-2022 11:11:07.818: WICEDModuleProg: Test program stopped.
29-09-2022 11:22:47.505: PortSetDlg[42]COM12DUT: 4 serial ports found.
29-09-2022 11:23:37.285: PortSetDlg[42]COM12DUT: Connected to "COM12 - WICED HCI UART (COM12)" (115200, RequestToSend)

 

 

WICED Studio programming of a CYBT-483056-EVAL does not seem to be a supported platform?

Thanks in advance,

-Ed

 

edOfTheInfineon_0-1664469109847.png

 

References:

 

 

0 Likes
1 Solution
edOfTheInfineon
Level 3
Level 3
First solution authored 10 replies posted 25 sign-ins

Doing a recover procedure allowed me to program CYBT-483056-EVAL selected as CYBT-483039-02 using WICED_MOD_Programmer


1) Press and hold the 'Recover' button on the kit.
2) Press and hold the 'Reset' button on the kit.
3) Release the 'Reset' button.
4) After one second, release the 'Recover' button.

 

As expected, reprogramming clears the bond list displayed by /QB command

However, when I pair a new Windows or Android device to the CYBT-483056-EVAL,  the bond delete /BD command does not clear anything in bond list. 

Once four devices have been paired, there is no way for our customer's bonds to be deleted to add a new device.

Thank you,

-Ed

 

View solution in original post

0 Likes
6 Replies
edOfTheInfineon
Level 3
Level 3
First solution authored 10 replies posted 25 sign-ins

Doing a recover procedure allowed me to program CYBT-483056-EVAL selected as CYBT-483039-02 using WICED_MOD_Programmer


1) Press and hold the 'Recover' button on the kit.
2) Press and hold the 'Reset' button on the kit.
3) Release the 'Reset' button.
4) After one second, release the 'Recover' button.

 

As expected, reprogramming clears the bond list displayed by /QB command

However, when I pair a new Windows or Android device to the CYBT-483056-EVAL,  the bond delete /BD command does not clear anything in bond list. 

Once four devices have been paired, there is no way for our customer's bonds to be deleted to add a new device.

Thank you,

-Ed

 

0 Likes
Sven_Wang
Moderator
Moderator
Moderator
100 solutions authored 250 sign-ins 50 solutions authored

Hi ed,

 

Sorry for replaying so late.

Could you tell me what command did you send by uart?

Is that a classical BT did you bond?

 

Thanks

0 Likes
edOfTheInfineon
Level 3
Level 3
First solution authored 10 replies posted 25 sign-ins

Hi@Sven_Wang ,

Yes, this is a classic Bluetooth device bond that cannot de deleted.  It is only when query bond /QB command list bond as type FF that  bond cannot be deleted on this CYBT-483056-EVAL device.  Apparently there is a bug in EZ Serial 1.0.10 firmware that cannot handle deleting on a bond with type FF.

Other CYBT products device do not have problems deleting bonds.  Unfortunately, we need high-power extended-range for this application which limits us to CYBT-483056-02, which has a delete bond bug in the EZ Serial 1.0.10  firmware.

Multiple engineers have tried to delete EZ Serial 1.0.10 bonds using both binary and text mode commands.  It seems like this should be an easy fix of Infineon firmware since other CYBT EZ Serial firmware products do not have this problem.  We can find no work-arounds with our product using the CYBT-483056-02 devices.

 

# Reset
@E,0040,BOOT,E=01000A15,S=02072276,P=0100,H=E8,C=00,A=DBA0B965FA7B,T=01
@E,000E,ASC,S=03,R=01

# Bond list contains device with type FF
/QB
@R,000E,/QB,0000,C=01
@E,0020,B,C=00,A=58CB523B58FA,T=FF,D=01

# Text bond delete responds with 020C 
/BD,A=58CB523B58FA,T=FF
@R,000E,/BD,020C,C=00

# Binary bond delete responds with 020C 
C0 07 07 02 58 CB 52 3B 58 FA FF 6A 
C0 03 07 02 0C 02 00 73 

# Bond list unchanged
/QB
@R,000E,/QB,0000,C=01
@E,0020,B,C=00,A=58CB523B58FA,T=FF,D=01

 

Thank you,

-Ed

 

 

0 Likes

Hi Ed,

 

Is that correct? The address type just have pubilc(T=0) and random(T=1)from the spec.

WeChat Screenshot_20221018163344.pngI can't scan the type FF when I try to recur the issue.

So could you tell me how to recur this issue?

Thanks!

 

Sven

0 Likes

Hi @Sven_Wang,

The /BD command failure to delete a bond on a CYBT-383056-02 is easy to reproduce by initiating a Bluetooth RFCOMM pairing from an Android or Windows device.

 

 

I agree type FF is invalid and should not occur.  There seem to be multiple CYBT-483056-02 EZ Serial 1.0.10 bugs.  However, even when RFCOMM bond type is a valid 01, you still can NOT delete the bond on this module with EZ Serial 1.0.10, regardless of type.

 

The bond cannot be deleted when pairing is completed from a Bluetooth Classic RFCOMM device when pairing is initialed from Windows, Android, or other Bluetooth BR/EDR devices. 

The RFCOMM bond type seems to appear as FF (invalid type) when pairing from either Windows or Android.  The bond type may be 01 (a valid type) when pairing from a

nother BR/EDR embedded device.

 

This issue is a RFCOMM issue and not a BLE issue.   We understand this. 

 

If bond type is 01, then delete bond returns 0403.  If bond type is FF,  then delete bond returns 020c. In either case bond cannot be deleted.  Regardless on the RCOMM bond type the CYBT-383056-02 displays in response to /QB, the bond cannot be deleted.

Please see my other post focused on a bug in deleting bonds on the CYBT-383056-02

CYBT-483056-EVAL smp_delete_bond does not delete device address from bond query list ?

 

https://community.infineon.com/t5/Studio-Bluetooth/CYBT-483056-EVAL-smp-delete-bond-does-not-delete-...

Not being able to delete RFCOMM pairing  is a major problem.  We have multiple partners who have released multiple Android Bluetooth RFCOMM apps.  Once a customer has paired 4 devices to this CYBT module, they can no longer pair any new Android devices to the CYBT module because the delete bond command /BD has a bug and does NOT work.  This will result in products returned to factory and lost customers.

Thank you,

-Ed

 

0 Likes

Hi ED,

 

Thanks for your feedback. It seems like the same issue. This issue have reproduced by another one and escalated to FW team to fix it. We will solve it as soon as possible. I'll close this thread.

 

Thank you

Sven

0 Likes