0% found this document useful (0 votes)
136 views42 pages

KT6368A Bluetooth Dual-Mode User Manual 7 - Added Status Query - V2.1

The KT6368A Chip User Manual provides comprehensive information on the KT6368A chip, which supports Bluetooth dual mode and is designed for ease of integration into products. Key features include low power consumption, a standard UART interface, and various AT command functionalities for configuration. The document outlines hardware specifications, communication protocols, and detailed instructions for testing and production considerations.

Uploaded by

junluantsui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
136 views42 pages

KT6368A Bluetooth Dual-Mode User Manual 7 - Added Status Query - V2.1

The KT6368A Chip User Manual provides comprehensive information on the KT6368A chip, which supports Bluetooth dual mode and is designed for ease of integration into products. Key features include low power consumption, a standard UART interface, and various AT command functionalities for configuration. The document outlines hardware specifications, communication protocols, and detailed instructions for testing and production considerations.

Uploaded by

junluantsui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 42

KT6368A Chip User Manual

Document Status: Document Identification: Publicly Available


[] Draft Current Version: V2.1
[√] Officially Released Author: Qingyue Electronics
[ ] Under Revision Completion Date: 2022-11-03

Page 1
V2.1

Version History

Version Date Reason


1. Added SPP password setting, see Section 5.4 for details.
2. Added functionality setting for Pin 2 of the chip, which can be set to blink when
unconnected and stay lit when connected, see Section 3.2 for details.
== 》 【 AT+CF01 represents blinking when unconnected and staying lit when
connected 】 【 AT+CF00 represents low when unconnected and high when
connected】
3. Added AT command setting for BLE UUID, see Section 4.7 for details.
4. Improved document details, and this version is backward compatible with
previous versions.
5. Added special notes and version description in Chapter 8.
6. Added an interface for adjusting Bluetooth transmission power, see Section
3.12 for details.
7. Added instructions for batch production testing, see Chapter 9 for details.
8. Added Chapter 10, hardware considerations, and added software
notes—important instructions for setting the Bluetooth name.
V2.1 2022/11/03 9. Fixed descriptive bugs in the document to improve clarity.

Page 2
『 Contact US 』for Technical Support and Sales Service
/*********************************************************************

EMail: [email protected]

WhatsApp: +86 159 0279 7635

WeChat: JAJB-Go

Tel: +86 159 0279 7635

*********************************************************************/

- Feel free to call for consultation at any time.

- Welcome to contact us anytime to obtain documentation or communicate.

Linkedin: https://www.linkedin.com/company/blevoice/
Blogger: https://blevoice.blogspot.com
Tumblr: https://www.tumblr.com/blog/blevoice
TikTok: https://www.tiktok.com/@blevoice
[BLE Voice Store]: https://www.aliexpress.com/store/1104656113

1. To request samples, please search for key words such as "KT6368A" directly on
AliExpress, enter our official store [BLE Voice Store] for solutions.
2. For each product, through rigorous development, debugging, and testing processes,
we provide comprehensive technical documentation including user manuals, FAQs,
schematics, Datasheet, Reference Code, debugging guides, critical notes and ect.
3. As our products expand into broader applications and industries, all related
technical resources are continuously updated to ensure relevance.
4. Full technical packages for every product are permanently hosted on Google Drive,
offering free lifetime access, and the corresponding download links are highlighted on
the detail pages of each product in our AliExpress store.
5. While our documentation may appear on third-party platforms, forums, or
websites (shared by enthusiasts, partners, or industry peers), the latest versions are
exclusively available on Google Drive.
V2.1
Contents

1. OVERVIEW .............................................................................................................................................................................. 5

1.1 I NTRODUCTION ..................................................................................................................................................................... 5


1.2 H ARDWARE DESCRIPTION ...................................................................................................................................................... 5
1.3 P RELIMINARY D ESCRIPTION OF CHIP P OWER CONSUMPTION .................................................................................................. 6
1.4 S IMPLE TESTING I NSTRUCTIONS FOR THE CHIP ....................................................................................................................... 6
1.5 H ARDWARE DESIGN —P IN D ESCRIPTION ................................................................................................................................ 7
1.6 H ARDWARE DESIGN —B LUETOOTH A NTENNA D ESCRIPTION .....................................................................................................8
1.7 H ARDWARE DESIGN —C RYSTAL O SCILLATOR FOR B LUETOOTH .................................................................................................. 8

3. SERIAL COMMUNICATION PROTOCOL ............................................................................................................................. 10

3.1 COMMUNICATION FORMAT ..................................................................................................................................................10


3.2 COMMUNICATION COMMAND EXAMPLES ............................................................................................................................. 11
3.3 S ETTING CHIP B AUD R ATE , R ESET, AND R ESTORE FACTORY S ETTINGS [CT][CZ][CW] ............................................................ 12
3.4 S ETTING BLE B LUETOOTH N AME AND A DDRESS [BM][BN][BD] ......................................................................................... 13
3.5 Q UERY BLE B LUETOOTH N AME AND A DDRESS [TM][TN][TD] ............................................................................................ 13
3.6 C HIP P OWER -O N I NFORMATION AND S ERIAL D EBUGGING A SSISTANT ....................................................................................14
3.7 C HIP LOW P OWER CONSUMPTION D ESCRIPTION .................................................................................................................. 15
3.8 C HIP BLE E NABLE AND SPP ENABLE [B4][B5][T4][T5] ......................................................................................................18
3.9 C HIP E RROR I NFORMATION DESCRIPTION 【ER】 ..............................................................................................................18
3.10 CHIP P OWER -O N F EEDBACK I NFORMATION D ISABLE COMMAND 【CR】 ........................................................................... 19
3.11 S ETTING THE BLE A DVERTISING I NTERVAL FOR THE C HIP 【UT】 ...................................................................................... 19
3.12 CHIP RF B LUETOOTH T RANSMISSION P OWER [BR] ............................................................................................................. 20

4. DETAILED DESCRIPTION OF BLUETOOTH PASSTHROUGH—BLE ................................................................................... 21

4.1 BLE PASSTHROUGH D ESCRIPTION ........................................................................................................................................ 21


4.2 BLE UUID D ESCRIPTION .................................................................................................................................................... 21
4.3 BLE TESTING I NSTRUCTIONS ............................................................................................................................................... 21
4.4 BLE M OBILE A PP T ESTING I NSTRUCTIONS —L IGHT B LUE T ESTING ......................................................................................... 22
4.5 BLE LARGE DATA VOLUME TESTING .................................................................................................................................... 23
4.6 BLE B ROADCAST PACKET DATA D ESCRIPTION — ADVERTIS DATA ..............................................................................................24
4.7 M ODIFYING BLE UUID VIA AT COMMANDS [U0][U1][U2][U3] ........................................................................................ 24

5. DETAILED DESCRIPTION OF BLUETOOTH PASSTHROUGH-- SPP ...................................................................................25

5.1 SPP PASSTHROUGH D ESCRIPTION ........................................................................................................................................ 25


5.2 SPP PASSTHROUGH D EMONSTRATION .................................................................................................................................. 25
1. SPP PASSTHROUGH DEMONSTRATION : HTTPS :// V.QQ .COM /X / PAGE /B 0766 JQW 0 P 5. HTML .......................................................25
5.3 SPP PASSTHROUGH T ESTING I NSTRUCTIONS .........................................................................................................................25
5.4 SPP CONNECTION PASSWORD DESCRIPTION [BE][B1] ..........................................................................................................25

Page 3
V2.1
6. DETAILED DESCRIPTION OF AT COMMANDS AND TRANSPARENT DATA TRANSMISSION ....................................... 27

7. FREQUENTLY ASKED QUESTIONS (FAQS) ......................................................................................................................... 28

8. ADDITIONAL NOTES ............................................................................................................................................................ 34

9. ADDITIONAL NOTES ON MASS PRODUCTION .................................................................................................................36

10. ADDITIONAL USAGE NOTES – VERY IMPORTANT!!! .................................................................................................... 38

10.1 LEVEL CONVERSION AND R ESISTOR P LACEMENT B ETWEEN KT6368A UART AND MCU ..................................................... 38
10.2 I MPORTANT N OTES ON KT6368A CRYSTAL O SCILLATOR .....................................................................................................39
10.3 I MPORTANT N OTES ON M ODIFYING B LUETOOTH N AME , BAUD R ATE , AND OTHER M EMORIZED PARAMETERS FOR KT6368A 39
10.4 P OWER S UPPLY CONSIDERATIONS FOR KT6368A ...............................................................................................................40

Page 4
V2.1

1. Overview

1.1 Introduction

The KT6368A chip is a pure data chip that supports Bluetooth dual mode and complies with Bluetooth 5.1. The
highlights of the chip are its ultra-small size, extremely competitive price, and straightforward passthrough and
UART AT control functionalities. These features significantly reduce the development difficulty and cost of
embedding Bluetooth into other products.

The chip supports both SPP (Serial Port Profile) and BLE (Bluetooth Low Energy), but only one protocol can be
used at a time.

Note: The most notable features of this chip are its low cost, ease of use, and simplicity in production —
nothing more. It also supports low power consumption; for details, refer to Section 3.7.

1.2 Hardware Description

Details Parameter Specifications


Standard UART interface with TTL level,Baud rate is configurable,A level converter
UART Interface
(e.g., CH340G—USB to TTL) is required when connecting to a PC.
Input Voltage Recommended voltage: 3.3V (operating range: 2.2V–3.4V).

Page 5
V2.1
Chip startup current: 20mA.Immediately after startup, the chip enters low-power
Rated Current mode, alternating between 20µA (broadcasting) and 4mA (wake-up).After a successful
connection, the current remains constant at 4mA.
Low Power The chip calculates average current because it continuously alternates between
Consumption Current low-power mode and wake-up mode internally.
Operating Range: -40°C to 80°C.
Temperature
Humidity Range: 5% to 95%.
Main Chip Model KT6368A [SOP8, shipped in tubes],KT6328A [SOP8, shipped in tubes]

1.3 Preliminary Description of Chip Power Consumption

1.3.1 We currently have two versions: KT6368A and KT6328A.


(1) The KT6368A version does not support low power consumption and is a dual-mode version. It consumes
15mA at startup and stabilizes at around 6mA afterward.
(2) The KT6328A version is a low-power version that supports only BLE. For detailed parameters, refer to
Section 3.7.
(3) The hardware of these two chip versions is identical. The purpose of the KT6328A version is to meet the
needs of customers who require low power consumption.

1.3.2 The features of the KT6368A version are as follows:


(1) Dual-mode (SPP + BLE), with all functionalities described in the manual supported. However, it does not
support low power consumption.
(2) This version is slightly more cost-effective.

1.3.3 The features of the KT6328A version are as follows:


(1) Lower power consumption. For detailed descriptions, refer to Section 3.7.
(2) Slightly higher cost.

==> Different versions can be identified by their Bluetooth names.

1.4 Simple Testing Instructions for the Chip

Step Instructions
Step 1 Set up the peripheral circuit for the chip and supply it with 3.3V power. For the Bluetooth
antenna, simply solder a wire in place.
Step 2 Check if Pin 2 of the chip outputs a high level for 1 second upon power-on. Connect an
indicator light to observe this.
Step 3 Connect to a computer using a serial port assistant tool. Verify if the chip’s TX pin returns
data at a baud rate of 115200.

Page 6
V2.1
Step 4 Create your actual board and debug it with the MCU.

1.5 Hardware Design—Pin Description

No. Layout Considerations


UART 1. The internal IO voltage of our chip is 3.3V. Pay special attention to the input voltage on
Considerations Pin 1.
2. When connecting to an external MCU, add series resistors (approximately 100 ohms) to
the RX and TX lines. If the MCU’s IO level exceeds 3.3V, increase the resistor value to 1K.
3. Pin 8 of the chip is the TX pin of the KT6368A, which connects to the RX pin of the MCU.
Pin 7 is the RX pin of the chip, which connects to the TX pin of the MCU.
Power Supply The maximum supply voltage for the chip is 3.4V. Do not exceed this voltage. It is
Considerations recommended to supply 3.3V.
Pin 2 Pin 2 is the connection status pin. It outputs a high level when connected successfully and
Considerations remains in a high-impedance state when disconnected. During debugging, it is
recommended to connect an indicator light or route it to an external MCU. Ensure a 10K
pull-down resistor is connected to ground.
Detailed 1. Strictly adhere to the recommended supply voltage. There are no significant
Descriptions requirements for the power supply design.
2. For the Bluetooth antenna, follow the provided footprint. The technology is mature, and
the communication distance typically exceeds 15 meters.
3. Test points must be reserved for Pins 7 and 8, as they serve as the upgrade interface. This
is crucial in case an upgrade is needed.
For upgrade test points, it is recommended to arrange Pins 1, 7, 8, and 3 in sequence.
Providing test points for these pins is very important

Page 7
V2.1
1.6 Hardware Design—Bluetooth Antenna Description

(1)Ensure a safe clearance distance around the Bluetooth antenna pin of the chip.
(2)Pay attention to grounding around the antenna.
( 3 ) Keep the area around the antenna clear. Do not apply solder mask (green oil) on the antenna area, and
avoid having any metal traces or components on both the front and back sides of the PCB near the antenna.

1.7 Hardware Design—Crystal Oscillator for Bluetooth

(1) Since Bluetooth has high requirements for frequency deviation, the quality of the crystal oscillator is crucial
for Bluetooth performance. During the selection process, it is essential to ensure the consistency and stability of
the crystal oscillator. The frequency deviation of the crystal oscillator must be ≤±10ppm, and the load
capacitance (CL) is recommended to be 12pF.
(2) If there are no size constraints, the crystal oscillator used on our demo board is recommended. It offers low
cost and good performance.
(3) If a smaller size is required, the 24M-3225 crystal oscillator is recommended. It has slightly higher cost but
excellent performance.
It is recommended to use the crystal oscillator provided by us, as it is more cost-effective and offers better
quality assurance compared to randomly purchased ones.
Cannot be used. Absolutely do not use.

Page 8
V2.1
Can be used.
1. For applications where cost is not a
concern and stability is prioritized, the
3225 package is recommended. It offers
extremely high quality.
The left image shows the 3225 package, and the right image shows 2. For cost-sensitive applications with
the M49-SMD-2PIN package. There is a cost difference between the no size constraints, the M49-SMD-2PIN
two. package is recommended.
No capacitors need to be placed next to the crystal oscillator. No capacitors are required. Capacitors can be
reserved on the PCB, but they do not need to be installed in mass production.

Page 9
V2.1

3. Serial Communication Protocol

The AT serial command, commonly used in control applications, has been optimized and customized by us,
significantly reducing the difficulty for users. Please strictly follow the command format we provide for
operation.

3.1 Communication Format

Supports asynchronous serial communication mode, receiving commands from the host computer via the
serial port.
Communication Standard: 115200 bps — Users can adjust this setting via serial commands. For details,
see Section 3.2.
Data Bits: 8 Stop Bits: 1 Parity Bit: None Flow Control: None
Note: All command designs follow a specific pattern and are not arbitrarily divided. You can refer to the
following to identify the pattern.
Control Command Format: AT+<CMD>[<param>]\r\n — All characters are in text format, not hexadecimal.

Data Feedback Format: <IND>[<param>]\r\n

Data Characteristics Detailed Explanation


AT+ This is the control command sent by the host to the BT201, starting with "AT+".

<CMD> Immediately followed by the <CMD> control, usually consisting of 2 characters.


[<param>] If there are parameters following the CMD, they are enclosed in [<param>].
The command ends with "\r\n", which represents a newline in character format
\r\n (equivalent to pressing the Enter key on Windows). In hexadecimal, it is represented as
0x0D, 0x0A.
1. Data feedback is the information (status and data) sent by the Bluetooth module
<IND> back to the host, starting with <IND>.
2. This is followed by the parameters returned by the chip.

Here is a detailed explanation of <CMD>.Since the chip runs an internal system, the main program is divided as
follows:
Function Category Command Remarks
General Command AT+C? General commands start with AT+C, and the "?" represents the specific
Characteristics detailed function command.
Music Command AT+A? Music commands start with AT+A, and the "?" represents the specific
Characteristics detailed function command.
Bluetooth Command AT+B? Bluetooth commands start with AT+B, and the "?" represents the specific
Characteristics detailed function command.

Page 10
V2.1

Here is a detailed explanation of <CMD>:


Example Command Remarks
Control Command 1 AT+CZ\r\n Represents a system reset.
Query Return Result 1 QA+01 For details, see Section 4.4.1. The returned query information always
follows the format Qn+xx, where n corresponds to the previous
command.
Query Return Result 2 QG+01 For details, see Section 4.2.12.

3.2 Communication Command Examples

Public Section—Control Commands — Description


CMD Function Detailed Description
AT+CT Set baud rate Followed by parameters. For details, see Section 3.3.
Example: AT+CT01\r\n
AT+UT Set BLE broadcast interval Followed by parameters. For details, see Section 3.11.
Example: AT+UT01\r\n
AT+CZ Chip reset Soft reset of the chip. For details, see Section 3.3.
Example: AT+CZ\r\n
AT+CW Restore factory settings Restores factory settings and clears all previously
stored parameters. For details, see Section 3.3.
Example: AT+CW\r\n
AT+CL Chip low-power setting For details, see Section 3.7. This command is no longer
available and is divided into two independent software
versions: KT6328A and KT6368A.
AT+CF Pin 2 connection status setting 【 AT+CF01 represents blinking when unconnected
and staying lit when connected】【AT+CF00 represents
low when unconnected and high when connected 】 .
Note: The AT+CF command is only supported in the
dual-mode version and not in the low-power version.
AT+CR Disable power-on information feedback For details, see Section 3.10.
Note: This feature is enabled by default.
AT+BM Set BLE Bluetooth name For details, see Section 3.4.
AT+BN Set BLE MAC address For details, see Section 3.4.
AT+BD Set SPP Bluetooth name For details, see Section 3.4.
AT+BS Set BLE connection password For details, see Section 3.4. Note: This feature is not
implemented due to poor compatibility with mobile
phones.

Page 11
V2.1
AT+BR Set Bluetooth transmission power For details, see Section 3.12. If Bluetooth
transmission power is not a concern, this command
can be ignored. The chip defaults to maximum power.
AT+QT Query system baud rate For details, see Section 3.3. The returned data format
is provided in the section.
AT+QL Query system low-power status For details, see Section 3.7. The returned data format
is QL+00.
AT+TM Query BLE Bluetooth name For details, see Section 3.5.
AT+TN Query BLE Bluetooth address For details, see Section 3.5.
AT+TD Query SPP Bluetooth name For details, see Section 3.5.
AT+TS Query BLE Bluetooth connection password Reserved, not supported.

Recommended Test Commands


AT+BM1234\r\n — Set the BLE name.
AT+BN112233445566\r\n — Set the BLE address.
AT+BD223344\r\n — Set the SPP name.
AT+CT01\r\n — Set the baud rate.
AT+CZ\r\n — Perform a chip reset.
AT+CW\r\n — Restore factory settings.
AT+QT\r\n — Query the system baud rate.
AT+TM\r\n — Query the BLE Bluetooth name.
AT+TN\r\n — Query the BLE Bluetooth address.
AT+TD\r\n — Query the SPP Bluetooth name.

3.3 Setting Chip Baud Rate, Reset, and Restore Factory Settings [CT][CZ][CW]

AT+CT01\r\n == 9600 AT+CT06\r\n == 256000 AT+CT11\r\n == 31250


AT+CT02\r\n == 19200 AT+CT07\r\n == 512000 AT+CT12\r\n == 2400
AT+CT03\r\n == 38400 AT+CT08\r\n == 230400 AT+CT13\r\n == 4800
AT+CT04\r\n == 57600 AT+CT09\r\n == 460800
AT+CT05\r\n == 115200 AT+CT10\r\n == 1000000
1. Once the baud rate is set, the chip will remember it. The next time it powers on, the baud rate will be the
one you set. You can also query the current baud rate using [AT+QT].
2. After setting the baud rate, wait for 1 second before sending the reset command [AT+CZ], or simply power
off and on the chip.

Page 12
V2.1
3. To restore the default baud rate, send the factory reset command. This will automatically erase all
configurations on the chip.

3.4 Setting BLE Bluetooth Name and Address [BM][BN][BD]

AT+BMBLE-1234\r\n Set the Bluetooth name to "BLE-1234".


Set the BLE address. The address displayed on the mobile phone will be: 66 55
AT+BN112233445566\r\n
44 33 22 11.
AT+BDSPP-1234\r\n Set the Bluetooth name to "SPP-1234".

1. After setting the Bluetooth name, you need to reset the chip by sending a command or powering it off and
on. This will display the new Bluetooth name. The default Bluetooth name is "KT6368A-BLE". The maximum
length for the Bluetooth name is 21 bytes. Please do not exceed this limit.
2. Normally, BLE names support up to 30 bytes. However, because our broadcast packet includes MAC address
information, exceeding 21 bytes will cause the broadcast packet data to overflow, resulting in BLE initialization
failure.
3. In summary, the BLE Bluetooth name should not exceed 21 bytes. If you need to exceed 21 bytes, please
contact us to modify the firmware.
4. If you modify the Bluetooth name using AT commands, note that your mobile device may not update
immediately and may still display the previous name.
(1) This is because you only changed the Bluetooth name, while the Bluetooth MAC address remains
unchanged. Therefore, the mobile device will not update the name.
(2) To resolve this, try searching with another mobile device, or delete the pairing information on the original
device and search again.
(3) Rest assured that once the Bluetooth name is set, it is definitely updated. The chip will also return the
Bluetooth name upon power-up for verification.

3.5 Query BLE Bluetooth Name and Address [TM][TN][TD]

AT+TM\r\n Returns TM+1234\r\n, indicating the Bluetooth name is "1234".


Returns TB+12345678AABB\r\n, indicating the BLE Bluetooth address: 0xBB, 0xAA, 0x78, 0x56,
AT+TN\r\n
0x34, 0x12.
AT+TD\r\n Returns TD+SPP1234\r\n, indicating the Bluetooth name is "SPP1234".

1. Here is a detailed description of the Bluetooth MAC address: The MAC addresses for BLE and SPP are
shared, so setting one is sufficient.
== 》 When the chip is powered on for the first time, it automatically generates a random Bluetooth MAC
address. This eliminates the need for manually setting the address. The algorithm used ensures that the
probability of duplication is one in a million. The Bluetooth MAC address follows the standard format and

Page 13
V2.1
consists of 6 bytes.
2. The SPP address is derived by incrementing the highest byte of the BLE address by 1. Therefore, only the BLE
address needs to be set. There is no specific query command for the SPP address, as it can be calculated
manually.

3.6 Chip Power-On Information and Serial Debugging Assistant

Test Environment: KT6368A test board


Serial Software: Serial Debugging Assistant_aithinker_serial_tool_v1.2.3
Receive Window: Data returned by the chip to the computer. This includes the firmware version and the last
modification date.
== 》 This returned data has no specific meaning. It is mainly provided for customers to conveniently test
whether the serial port connection is normal upon power-up and to check the chip's operating status.
== 》 The chip will always return this data upon power-up. If no data is returned, it indicates a hardware
connection error.
TM+KT6368A-BLE-1.7 Represents the current BLE name of the chip and the corresponding manual version
1.7.
Page 14
V2.1
TN+220CB1C8A22C Represents the current BLE address of the chip.
TD+KT6368A-SPP-1.7 Represents the current SPP name of the chip and the corresponding manual version
1.7.
TS+220CB1C8A22D Represents the current SPP address of the chip, which is calculated based on the BLE
address.
T4+01 Indicates that the BLE function is currently enabled. For details, see Section 3.8.
T5+01 Indicates that the SPP function is currently enabled. For details, see Section 3.8.
QL+00 Indicates that the chip is currently in normal working mode. For details, see Section
3.7.

Many of the returned pieces of information here do not need to be focused on by the user, as their purpose is
to assist customers during initial debugging.

3.7 Chip Low Power Consumption Description

1. Currently, our chips are divided into two versions: the low-power version [KT6328A] and the standard
dual-mode version [KT6368A]. Since the dual-mode version cannot reduce power consumption, this
requirement can only be met by separating the versions. These two versions must not be mixed.
2. In other words, the dual-mode version and the low-power version are the same chip but with different
software.
3. For usage, please refer to the additional document titled "10_About Low Power Consumption_Read Here
Read Here" in the folder
1. If entering low-power mode, all IO ports of the chip will be in a high-impedance state. This is very
important.
(1) If possible, connect pull-up resistors to pins 2, 7, and 8 of the chip to determine the IO state.
(2) Some customers have reported that after the chip enters low-power mode, their MCU continuously
receives FF data.
(3) For such applications, it is recommended to use pin 2 of the KT6328A to determine whether the chip is
connected. If not connected, no data should be received.
2. After setting to low-power mode, the chip can recognize AT commands within the first 5 seconds after
power-on in an unconnected state. After 5 seconds, AT commands will no longer be recognized.
(1) To achieve low power consumption, all peripherals of the chip are turned off, and SPP is no longer
supported. Only BLE is retained.
(2) However, many customer applications may require modifying some parameters in low-power mode.
Therefore, a 5-second timeout is set before entering low-power mode. During these 5 seconds, AT commands
can be recognized normally.
(3) If AT commands are needed to set parameters, try to send them in a connected state. After connection, the
chip automatically exits low-power mode.

Page 15
V2.1
Item Current Description
Low-Power Power-On 11mA 1. The chip initializes peripherals during power-on,
Version Moment resulting in a relatively high instantaneous current.
(KT6328A) 2. This state lasts for 300ms before entering low-power
Operating mode.
Mechanism Operating State - 20uA/4mA 3. In normal operation, the chip broadcasts periodically,
Unconnected (alternating) alternating between sleep and wake-up states to save
power.
4. The cycle is 500ms: 100ms for broadcasting and
400ms for sleep.
5. The current during broadcasting is 4mA, and during
sleep, it drops to 20uA.
Operating State - 4.3mA 6. Once connected, the chip no longer enters sleep
Connected mode and remains in the working state.
Dual-Mode Power-On 25mA 1. The chip initializes peripherals during power-on,
Version Moment resulting in a relatively high instantaneous current.
(KT6368A) 2. This state lasts for 300ms before entering the 5mA
Operating working state.
Mechanism Regardless of 5mA 3. The chip remains in the working state with minimal
Connection Status current fluctuations, which are negligible.

Page 16
V2.1

1. It can be observed that the current at the moment of power-on is 5mA, then drops to 4mA. After waiting a
few seconds, it enters the low-power broadcasting state.
2. In the low-power broadcasting state, the average current is 185.4uA.
3. The lowest current is 20uA. Due to the insufficient sampling rate of the uA meter software, this is not
reflected in the curve.
AT+VER2.0-20211111
TM+KT6328A-BLE-2.0 — The mobile device will search for this
name.
TN+3031E54D77D9
T4+01
T5+00
QL+01 — Entered low-power mode.

Page 17
V2.1
3.8 Chip BLE Enable and SPP Enable [B4][B5][T4][T5]

AT+B401\r\n Enable BLE functionality. Conversely, AT+B400\r\n disables it.


AT+B500\r\n Disable SPP functionality. Conversely, AT+B501\r\n enables it.
Query whether BLE functionality is enabled. The chip will return T4+01 (enabled) or T4+00
AT+T4\r\n
(disabled).
Query whether SPP functionality is enabled. The chip will return T5+01 (enabled) or T5+00
AT+T5\r\n
(disabled).

1. After disabling BLE functionality, the chip must be powered off and on again for the change to take effect.
The same applies when enabling it.
2. This setting only needs to be configured once. The chip automatically saves the parameters, so no further
configuration is required in the future.
3. After disabling BLE functionality, the BLE name will no longer be discoverable by mobile devices.
4. After disabling SPP functionality, the chip must be powered off and on again for the change to take effect.
The same applies when enabling it.
This setting only needs to be configured once. The chip automatically saves the parameters, so no further
configuration is required in the future.After disabling SPP functionality, the SPP name will no longer be
discoverable by mobile devices.

3.9 Chip Error Information Description 【ER】

ER+1\r\n The received data frame is incorrect. This means the data received by the 6368 chip's serial port
does not start with "AT".
ER+2\r\n The received command does not exist. For example, if you send a string like AT+KK, it cannot be
found.
ER+3\r\n The received AT command is missing the carriage return and line feed (\r\n).
ER+4\r\n The parameters provided in the sent command are out of range, or the command format is
incorrect. Please check your AT command.
ER+7\r\n The MCU is trying to send data to the mobile device, but the mobile device has not enabled
notify. This occurs when BLE is successfully connected.
ER+8\r\n Reserved—no specific meaning.
The chip provides real-time feedback for certain error states. Please refer to the table above for details.
Key Description of Notify [Listening]:When the mobile testing app connects to the Bluetooth chip, it must
enable notify. Only then can the Bluetooth chip send data to the mobile device. For sending data from the
mobile device to the Bluetooth chip, the write characteristic is sufficient.

Page 18
V2.1

3.10 Chip Power-On Feedback Information Disable Command【CR】

Disable power-on feedback information. After setting, the chip must be powered off and on
AT+CR00\r\n
again for the change to take effect.
Enable power-on feedback information. This will take effect on the next power cycle. After
AT+CR01\r\n
setting, the chip must be powered off and on again for the change to take effect.

1. Some customers have reported that the power-on feedback information from the chip is annoying.
Therefore, we have added this command to disable it.

2. Note that this feature is enabled by default when the chip leaves the factory. Once disabled, the setting is
saved and permanently disabled.
3. Additionally, this will also disable the chip's automatic feedback of OK or ER+X messages.

3.11 Setting the BLE Advertising Interval for the Chip【UT】

Currently, this feature is only available for the KT6328A version, which is the single-mode BLE low-power
version.
Command Meaning Reference Power Consumption

AT+UT00\r\n 0 — Corresponds to 250ms advertising interval Average power consumption: 300uA


AT+UT01\r\n 1 — Corresponds to 500ms advertising interval Average power consumption: 180uA —
Default factory setting
AT+UT02\r\n 2 — Corresponds to 750ms advertising interval Average power consumption: 140uA
AT+UT03\r\n 3 — Corresponds to 1000ms advertising interval Average power consumption: 100uA
AT+UT04\r\n 4 — Corresponds to 1500ms advertising interval Average power consumption: 70uA
AT+UT05\r\n 5 — Corresponds to 2000ms advertising interval Average power consumption: 62uA
AT+UT06\r\n 6 — Corresponds to 3000ms advertising interval Average power consumption: 40uA
AT+UT07\r\n 7 — Corresponds to 4000ms advertising interval Average power consumption: 30uA

Page 19
V2.1

1. Once the advertising interval parameter is set, the chip will remember it. The next time it powers on, the
advertising interval will be the one you set. This setting does not support querying.
2. However, the chip will actively return the current connection interval parameter each time it powers on.
Refer to the screenshot above for details.
3. To restore the default advertising interval, send the factory reset command. This will automatically erase all
configurations.
4. The specific interval time should be defined based on your product requirements. A longer advertising
interval means it will take longer for mobile devices to discover the chip.

3.12 Chip RF Bluetooth Transmission Power[BR]

AT+BR01\r\n Set the Bluetooth transmission power to level 1. The change takes effect immediately. The
valid range is [0---9].
AT+BR09\r\n Set the Bluetooth transmission power to level 9, which is the maximum.

1. The change takes effect immediately after sending the command. The valid range is [0---9].
2. After setting the RF power level, the chip automatically saves the setting upon power-off. The chip will
remember the setting, so there is no need to reconfigure it the next time it powers on.
3. The chip defaults to the maximum power level, which is level 9. Higher transmission power results in a
longer range but slightly higher power consumption, and vice versa.
4. If not necessary, there is no need to modify this parameter.

Page 20
V2.1

4. Detailed Description of Bluetooth passthrough—BLE

Currently, the chip supports BLE pure data transmission and can achieve passthrough. Both BLE and SPP can only
operate as slaves, i.e., the "SERVER" side.
Please note that once the Bluetooth is connected, the chip automatically enters passthrough mode. AT
commands can still be recognized during this mode. BLE must be searched for within the app.

4.1 BLE passthrough Description

1. The maximum single data throughput is 1024 bytes, supporting both 16-bit and 128-bit UUIDs. A 128-bit
UUID requires special customization.
2. If using BLE for data transmission, please connect to the Bluetooth name "KT6368A-BLE".
3. You can modify the BLE Bluetooth name and MAC address using AT commands.

4.2 BLE UUID Description

1. The main UUID is "FFF0".


2. The UUID for Characteristic 1 is "FFF1", with the characteristics "WRITE_WITHOUT_RESPONSE" and
"NOTIFY".
3. The UUID for Characteristic 2 is "FFF2", with the characteristics "READ" and "NOTIFY".
4. The UUID for Characteristic 3 is "FFF3", with the characteristic "WRITE_WITHOUT_RESPONSE".
Note: The UUID values can be modified using AT commands. For details, refer to Section 4.7.
==》If you need a specific UUID, please contact us for customization. — Please provide detailed requirements,
characteristics, UUIDs, and other relevant information.
The more detailed, the better.BLE passthrough Demo: https://v.qq.com/x/page/q07660m1bta.html

4.3 BLE Testing Instructions

1. For Android and iOS (Apple) phones, it is recommended to use the "LightBlue" software.
2. For Apple devices, you can search and download the app directly from the "App Store".
3. For Android devices, we will provide the installation program in the resource package.
4. Please note that Android phones can also test BLE. Testing BLE is not limited to Apple devices.
5. BLE on Android is not unusable, but it is less user-friendly. Android versions must be 4.3 or higher to
support BLE.
6. Due to the poor usability of BLE on Android, the dual-mode option is available: use SPP for Android and
BLE for Apple.
7. For Apple devices to use SPP, an MFI-certified chip is required, which is extremely expensive. Currently,
this is rarely used.

Page 21
V2.1
8. If the Bluetooth name has not been modified, connect to the Bluetooth name "KT6368A-BLE".
9. BLE testing demonstration video: https://v.qq.com/x/page/o0766ubm78n.html

4.4 BLE Mobile App Testing Instructions—LightBlue Testing

Step 1: Step 2: Step 3: Step 4:


1. Launch the LightBlue 1. Interface after 1. Find the required 1. Enable "Notify".
app. connecting to the chip. service. 2. This allows the
2. This is the Android 2. You can see the name 2. Specifically, "FFF1". KT6368A to send data
testing environment. and services. 3. Click on it. to the phone after
3. The iOS interface is 3. Click the "arrow". receiving it.
slightly different. 3. To send data from
4. Ensure location the phone, simply
permissions are enabled. transmit it. The
5. There are also many KT6368A will forward it
other testing apps directly via the serial
available, with slightly port.
different operations.

1. Notes:During testing, it is recommended to enable location permissions on the phone, as many apps require
this permission.
2. Whether developing your own app or using a WeChat mini-program, the steps are the same as shown in the
screenshots above.
3. It is recommended to use only the first characteristic, "FFF1", which supports write and notify operations
and is sufficient for most use cases.
4. For basic issues, please resolve them by searching online. These descriptions are easy to find on the internet
and are not complicated.
Page 22
V2.1
4.5 BLE Large Data Volume Testing

The host computer sends 1832 bytes of data in a single This is a screenshot of the completed reception.
transmission via UART. Total time taken: approximately 220ms.

The above test data is based on the connection interval settings of our chip.
In fact, reducing the connection interval can also speed up data communication, but it simultaneously increases
power consumption.

Note: The data received by the phone is still divided into packets of 20 bytes each. This is because the default
maximum packet length set internally in our chip is 20 bytes.

The normal process is that after the app connects to the Bluetooth chip, it can actively request an MTU
(Maximum Transmission Unit) — you can search online for more details.
Once the MTU is set, the single data packet size will no longer be limited to 20 bytes, thereby speeding up
data interaction.

Page 23
V2.1
4.6 BLE Broadcast Packet Data Description—advertisData

Here, we have added the Bluetooth MAC address of the chip to the
broadcast packet.
By comparing the screenshot on the right, you can identify the pattern.

We refer to this as advertisData. The purpose of this is as follows:


1. WeChat Mini-Program Development: It is not possible to directly obtain
the MAC address of the Bluetooth chip, as there is no corresponding API.
Therefore, this method can be used to retrieve it. You can search online
for more details.
2. App Development—iOS: Similarly, there is no direct way to obtain the
MAC address on iOS. This method is also used to retrieve the Bluetooth
chip's MAC address.
3. App Development—Android: There is no such issue on Android. The
MAC address of the Bluetooth chip can be directly obtained through the
API. Therefore, using this feature is optional and not necessary.

4.7 Modifying BLE UUID via AT Commands [U0][U1][U2][U3]

AT+U0F000\r\n Set the service UUID to "F000".


Set Characteristic 1 UUID to "F001", with the properties "Write Without Response" +
AT+U1F001\r\n
"Notify".
AT+U2F002\r\n Set Characteristic 2 UUID to "F002", with the properties "Read" + "Notify".
AT+U3F003\r\n Set Characteristic 3 UUID to "F003", with the property "Write Without Response".

1. We provide three characteristics here to accommodate the diverse needs of different customers.
== 》 Some customers prefer to separate "Write" and "Notify" into different characteristics to ensure more
reliable data interaction between the phone and the Bluetooth chip.
== 》 Some customers only need to transmit a small amount of data and prefer simplicity, so they combine
"Write" and "Notify" into a single characteristic.
2. When setting up, it is recommended to configure all four UUIDs, regardless of whether you use them or not.
3. For customers without an app, it is recommended to use Characteristic 1 and Characteristic 2, separating
them into two different characteristics.
4. For products already in mass production that want to switch to our chip, only the UUID needs to be
modified. Even if it does not match, we can assist in adaptation.

Write Without Response = ATT_WRITE_WITHOUT_RESPONSE


Notify = ATT_NOTIFY ; Read = ATT_READ

Page 24
V2.1

5. Detailed Description of Bluetooth passthrough-- SPP

SPP operates on the Classic Bluetooth 2.1 protocol and is not recommended for new products. It is advised to
use BLE directly. To use SPP, first connect to "KT6368A-SPP" in the system.

5.1 SPP passthrough Description

1. The maximum single data throughput is 1024 bytes. You need to connect to "KT6368A-SPP-04".
2. If using SPP for data transmission, do not actively connect to the Bluetooth name "KT6368A-BLE" or any
custom BLE Bluetooth name.
3. Note that SPP is just a sub-protocol within Classic Bluetooth.
4. SPP data transmission and BLE are mutually exclusive. If you only use SPP for data transmission, please
disable BLE.

5.2 SPP passthrough Demonstration

1. SPP passthrough demonstration: https://v.qq.com/x/page/b0766jqw0p5.html

5.3 SPP passthrough Testing Instructions

1. For Android phones, use the "Bluetooth Serial Port" app, which can be downloaded from the "App Store".
2. If the Bluetooth name has not been modified, connect to the Bluetooth name "KT6368A-SPP".
3. SPP testing demonstration video: https://v.qq.com/x/page/e0766bz15fw.html

SPP Large Data Volume passthrough Demonstration Video:


https://v.qq.com/x/page/c0843j975hl.html For testing methods, please refer to the video demonstration
in our resource package.

5.4 SPP Connection Password Description[BE][B1]

AT+BE1234\r\n Set the Bluetooth SPP connection password to "1234". The password can only be numeric,
not alphabetic.

The "01" here represents 0x01, enabling the pairing password. This means the next
AT+B101\r\n
connection will require a password to connect to SPP.

1. Note that the SPP password can only be 4 bytes. Please do not exceed this limit.
2. If your phone has previously connected to the SPP of this Bluetooth chip, even if a password is set, you will
not need to enter the password again because the devices already recognize each other. To test the password,
use a different phone or modify the Bluetooth chip's MAC address.

Page 25
V2.1
3. To enable the password, send AT+BE1234\r\n, then power off and on the chip.
4. To disable the password, send AT+B100\r\n to disable the pairing password feature, then power off and on
the chip.

Page 26
V2.1

6. Detailed Description of AT Commands and Transparent Data Transmission

1. Currently, our serial port commands support AT commands, as well as full-duplex transparent data
transmission between Bluetooth and mobile phones or other host devices.
2. AT commands are available throughout the entire lifecycle of the chip. Once the chip initializes Bluetooth,
Bluetooth data passthrough will run in the background. AT commands are supported regardless of whether
the chip is connected or not.
3. However, please note that we also have a low-power version, KT6328A. For detailed information, refer to
Section 3.7.
Question 1 What is Bluetooth passthrough, and what are its characteristics?

Answer 1. Bluetooth data passthrough refers to the process where the host MCU sends any data
through the serial port, and the Bluetooth chip, upon receiving it, directly forwards it to the
mobile phone.
2. Similarly, any data sent from the mobile phone is transmitted by the Bluetooth chip to the
MCU via the serial port in UART format.
3. In our solution, Bluetooth passthrough does not require any commands or settings.

Question2 How does the chip distinguish between AT commands and passthrough data?

Answer 1. For commands sent by the MCU, as long as they are not standard AT commands, they will be
passed through. For example
Data sent by the MCU Explanation
AT+CT00\r\n This is a standard AT command and will not be passed through.
The KT6368A will process it directly.
AT+CT00 This is an abnormal command and will be passed through because
it lacks a line break. The KT6368A will return ER+7.
KT+CT00\r\n This will also be passed through because it does not start with
"AT".
1234AT+CM00\r\n This will be passed through because it does not start with "AT". The
AT command is in the middle, so it will be passed through.
12121212121212kkk This is pure passthrough data and will be transmitted to the phone.
As for how to handle these passthrough data, it is left to your smart discretion to freely explore
and implement!
2. For data sent from the mobile phone, it is easier to understand.———SPP and BLE
Passthrough Explanation
Any data sent from the mobile phone will be passed through. Even if the phone sends a
standard command like AT+CT00\r\n, it will be passed through. The Bluetooth chip will not
process it and will only output it to the MCU via the serial port.
Page 27
V2.1

7. Frequently Asked Questions (FAQs)

Question 0 What is KT6368A? What are its functions, characteristics, and suitable scenarios? What
crystal oscillator should it be paired with? Are there bulk discounts for KT6368A? Should the
Bluetooth antenna's reserved components be soldered or not?
Answer 1. The KT6368A is a Bluetooth chip that supports Bluetooth 5.1 BLE and SPP functionality from
version 2.1.
2. The KT6368A chip supports connecting to mobile phones for bidirectional data interaction,
commonly known as "Bluetooth passthrough." It uses a UART interface
==》Supports common AT commands such as setting the name, address, baud rate, etc. Refer
to the manual for details.
3. The main feature of the KT6368A chip is its low cost and ease of use. Its SOP8 package also
facilitates production.
4. The KT6368A chip is suitable for pure data communication scenarios, such as custom app
development, WeChat mini-programs, etc.
5. Currently, the KT6368A firmware only supports the slave version and can only connect to
mobile phones.
6. It is paired with a 24M crystal oscillator with a 12pF load and 10ppm accuracy. The crystal
oscillator's package can be 3225 or others, but it directly affects the Bluetooth frequency offset
and range. Therefore, do not use random crystal oscillators, or you may encounter issues like
not being able to find the Bluetooth name. We provide crystal oscillator samples for testing.
7. The crystal oscillator's capacitor does not need to be soldered. It is recommended to
reserve it. The chip automatically calibrates the crystal oscillator's load capacitor upon
startup.
8. There are no bulk discounts for the chip. If you are highly price-sensitive, please consider
other options.
9. For the Bluetooth antenna pin, the reserved components can be left unsoldered during
prototyping. Just connect a C1 capacitor. For mass production, it is recommended to reserve
them for certification or high antenna performance requirements. With just the C1 capacitor,
the Bluetooth range can easily exceed 10 meters.

Question 1 Does KT6368A have a test board? How to start testing after receiving the chip? Any hardware
considerations?
Answer The chip is in an SOP8 package with very few pins, making it simple to use. Currently, there is
no test module.

Page 28
V2.1

1. Pin 1 is for power supply. A 105 capacitor to ground is sufficient, or it can be omitted. Add it
for mass production.
2. For the Bluetooth antenna, simply solder a wire to pin 4. For actual products, add a 2p7
capacitor.
3. The crystal oscillator is the most challenging to solder. You can use the provided M49 2-pin
crystal oscillator.
4. The remaining pins are for the serial port. Since it operates at 3.3V, it can be directly
connected to a 3.3V MCU.
5. For initial debugging, use a serial port debugging tool. A USB-to-TTL converter like CH340G is
recommended and widely available on platforms like AliExpress.
6. We do not provide test boards mainly due to cost reasons, so customers need to handle it
themselves.

Question 2 Does KT60368A support WeChat mini-programs? What is the default UART baud rate?
Answer 1. WeChat mini-programs use BLE. Therefore, if the chip supports BLE, it can support WeChat
mini-programs.
2. The chip uses the BLE5.0 protocol. WeChat mini-programs need to be developed by the
customer. We only provide passthrough functionality.
3. The UART buffer size is 1KB, and the default baud rate is 115200.

Question 3 What is the supply voltage and current for the KT6368A chip? What are the passthrough rates
for BLE and SPP?
Answer 1. The recommended supply voltage is 3.3V (2.2V--3.4V).
2. The current at startup is 26mA, which drops to around 4mA after about 1 second.
3. The UART buffer size is 1KB, and the default baud rate is 115200.
4. For BLE rates, we have not conducted comprehensive tests. Please test it yourself if
high-speed transmission is required.
5. For SPP transmission, it is recommended not to exceed 512 bytes per packet. Test the
transmission rate yourself.
6. BLE transmission rates vary depending on the phone version, so we cannot provide a
unified rate. Please test it yourself.

Page 29
V2.1
Question 4 How to distinguish between AT commands and serial passthrough data? How to know if
Bluetooth is connected?
Answer 1. AT commands are valid in any state.
2. Once Bluetooth is connected, passthrough is enabled, but AT commands can still be
recognized. Refer to section 6 for details.
3. Check pin 2 of the chip. It outputs a low level when not connected and a high level when
connected.
4. You can connect an indicator light or connect it to an MCU GPIO pin.

Question 5 How to determine if the chip is working properly and if the serial port connection is correct?
Answer 1. Upon power-up, pin 2 will output a high level for 1 second and then pull low. Use an indicator
light to check the status.
2. The chip will definitely return information via the serial port upon power-up. If no
information is received, there is an issue with the serial port.

Question 6 Does it support single-chip shipments? What are the chip parameters and packaging? Is the
chip shipment stable?
Answer 1. The chip is in an SOP8 package, shipped in tubes of 100 pieces. For large quantities, it can be
reeled.
2. The chip comes pre-programmed with firmware and is ready to use.
3. The chip shipment is stable as it is used in high-volume products like selfie sticks and anti-lost
devices, keeping costs low.
4. No price negotiations are supported. The price is already very low.

Question 7 Does it support modifying UUID, Bluetooth name, and MAC address?
Answer 1. It supports modifying the Bluetooth name and MAC address.
2. It also supports setting and reading UUIDs. Refer to section 4.7 for details. However,
characteristics cannot be modified.

Question 8 Does it support single-chip shipments? What are the chip parameters and packaging?
Answer 1. The chip is in an SOP8 package, shipped in tubes of 100 pieces. For large quantities, it can be
reeled.
2. The chip comes pre-programmed with firmware and is ready to use.
Question 9 Any hardware design considerations?
Answer 1. Strictly follow the provided supply voltage. The power supply is not particularly demanding.
2. Design the Bluetooth antenna according to the provided package. The technology is mature,
and the range typically exceeds 15 meters.
3. Pins 7 and 8 must have test points reserved for upgrades.

Page 30
V2.1
4. The test points for upgrades should be arranged in the order of pins 1/7/8/3. This is
important.
5. The UART connection between the KT6368A chip and the MCU must include resistors on both
TX and RX lines, typically 100 ohms.

Question 10 Can I buy a few samples and have the baud rate modified to 9600?
Answer 1. In principle, modifications are not supported. Customers can change the baud rate
themselves using AT commands. The default is 115200.
2. If modification is necessary, a fee of $200 will be charged.
Question11 Can samples be modified according to our specific UUID and service?
Answer 1. In principle, modifications are not supported. The sample stage is for testing functionality.
Customers can develop hardware first, and we will assist with modifications if needed for
production.
2. If modification is necessary, a fee of $200 will be charged.

Question12 Is there stock for bulk orders of KT6368A? Can supply be guaranteed in the future?
Answer 1. Bulk orders are in stock, so there is no need to worry. Unless the order exceeds 200K units, no
prior communication is needed. For other quantities, you can place the order directly without
prior notice.
2. We maintain a long-term inventory, typically around 300K units, regardless of order size.

Question13 After connecting the KT6368A with a USB-to-TTL converter, can I communicate with a mobile
phone via a serial port debugging tool on the PC?
Answer 1. The manual is clear on this. The answer is yes. Refer to the test method provided in the manual
for details.
2. First, ensure the serial port is properly connected. Then, open the test app on the mobile
phone. Refer to the test instructions for details.

Question14 After connecting the KT6368A to the mobile phone's test app, is it necessary to open notify?
How should I explain this to the app developer?
Answer 1. Yes, notify must be opened. Data sent to the KT6368A chip via the serial port can only be
transmitted to the phone via Bluetooth if notify is enabled. This is a Bluetooth standard
requirement.
2. App or mini-program developers are aware that they need to enable notify after connecting to
the Bluetooth chip. This is a fixed API. MCU developers do not need to worry about this.

Question15 Why must the KT6368A be connected within the app? Why can't it be connected via the
system's Bluetooth settings?
Page 31
V2.1
Answer 1. Note that BLE must be searched and connected within the app. This is mandatory for both
Android and iOS devices.
2. Similarly, SPP must be searched and connected within an Android app. Note that iOS devices
do not support SPP.

Question16 Why does the Bluetooth chip return ER+1 or ER+3 when I send AT commands via the serial port
debugging tool?
Answer 1. For this issue, you should first refer to section 3.9 of the chip manual, which explains error
messages.
2. ER+1: The first two characters of the data received by the chip are not "AT".
3. ER+3: The data received by the chip does not end with a carriage return and line feed (\r\n).
4. Testing this is simple. Try to troubleshoot it yourself. Many customers immediately report
issues without checking.

Question17 Why are AT commands not passed through after a successful Bluetooth connection?
Answer Refer to section 6 of the manual for detailed explanations.

Question18 Why does the KT6328A version stop receiving AT commands after a few seconds?
Answer

Refer to the documentation to check if you purchased the low-power version, as its mechanism is
different.

Question19 Why can the KT6368A dual-mode chip connect via SPP but not BLE?
Answer 1. BLE connections must be made via an app, not through the system settings. You can use apps

Page 32
V2.1
like LightBlue or nRF Connect.
2. Another possibility is that the crystal oscillator's frequency deviation is too large, preventing
BLE connections. Ensure you use the recommended crystal oscillator.

For the remaining details, please refer to the special notes in Chapter 10.

Page 33
V2.1

8. Additional Notes

Recently, the most common question is:


Why do some boards not show a Bluetooth signal on the phone, some can search but not connect, and some
can connect but easily disconnect?

== 》 The primary reason is the use of incorrect crystal oscillators. Refer to the hardware design section of the
manual for details.

==》Crystal oscillators must not be randomly selected. This is crucial.


==》The defect rate of the KT6368A chip is extremely low because the chips are programmed before leaving the
factory. During the programming process, all pins are utilized, so any defective chips are identified and filtered
out at this stage. As a result, the defect rate delivered to customers is less than one in a thousand.
== 》 If the issue persists, consider purchasing a test module from AliExpress using the keyword "KT6368A
Bluetooth chip."

Currently,the KT6368A Bluetooth chip has four versions, each with the same hardware IO definitions but
different functionalities for different application scenarios and customer requirements.

Version Functional Description of Corresponding Version


KT6368A Dual-Mode 1. No low-power function. The current is 15mA at startup and drops to an average
Version of 6mA after 1 second.
2. Supports both BLE and SPP simultaneously.
3. Suitable for scenarios where power consumption is not a concern. This is the
most classic version with the largest customer base.
KT6328A Single-Mode 1. Supports only BLE, not SPP.
Low-Power Version 2. Ultra-low power consumption, with an average broadcast current of 100uA. The

Page 34
V2.1
broadcast period can be adjusted to optimize overall power consumption.
3. The current is 5mA after connection.
KT6368A Host Version 1. Supports connecting to our companion slave chips (KT6368A or KT6328A).
2. After successful connection, bidirectional data transmission is possible
(full-duplex).
3. Supports AT commands to modify the target slave's name.
4. Refer to the documentation in the data package for detailed functionality.
KT1328A Host-Slave 1.Supports only BLE, not SPP. Supports AT commands to set the role (host or slave).
Integrated Version 2.Does not support low power. The current is consistently 5mA.
3.Refer to the "12 About Host-Slave Integrated Version Function Description -
KT1328A" folder in the data package.

Page 35
V2.1

9. Additional Notes on Mass Production

Key Points Detailed Descriptions


1. Bluetooth Crystal (1) The chip is paired with a 24M crystal oscillator with a 12pF load and 10ppm accuracy.
Oscillator (2) This is critical as it directly affects Bluetooth stability, range, and other parameters.
2. USB Test Points (1) Ensure the chip's USB pins are accessible.
(2) If a USB connector is included, it is even better to facilitate future upgrades.

3. Production (1) After SMT (Surface Mount Technology) assembly, the


Tools-Bluetooth Bluetooth performance of the PCBA must be tested, with
Automatic Test Box frequency deviation being the most important parameter.
(2) Using our standard Bluetooth test box, you can test
Bluetooth audio, calls, and BLE. It is fully automated.

Step 1: Prototyping Stage


Pay close attention to the selection of the crystal oscillator. Use the test box to measure the frequency
deviation of the crystal oscillator. Always purchase crystal oscillators from the original manufacturer or us. Do
not source them from unreliable or counterfeit electronics markets.When changing crystal oscillator suppliers,
test 5-10 crystal oscillators on the board at room temperature to ensure consistency before finalizing the
supplier. Also, ensure the Bluetooth chip's power supply has minimal voltage fluctuations and is free from
strong interference.

Step 2: Mass Production Stage


After SMT assembly, use the test box to check the frequency deviation. A successful connection indicates that
the Bluetooth pathway is functioning correctly, and the Bluetooth performance is validated.

Step 3: Detailed Test Box Settings and Effects


Detailed test box settings, test results, and DIP switch configurations are shown in the figure below:

Page 36
V2.1

Refer to the label on the back of the test box for specific meanings.

1. This setup only tests BLE. If BLE works normally, SPP does not need to be tested separately as they share

the same RF (radio frequency) circuit.The frequency deviation parameter should be controlled within an error

range of ±20KHz, which is acceptable.

2. If the deviation exceeds ±50KHz, the crystal oscillator must be replaced. However, the crystal oscillators we

provide are generally controlled within ±30KHz.

3. Additionally, if the RSSI parameter is displayed, it can be ignored, as it represents signal strength.

Page 37
V2.1

10. Additional Usage Notes – Very Important!!!

Here, we highlight some design flaws from problematic customer productions to help other customers achieve
smoother production.

10.1 Level Conversion and Resistor Placement Between KT6368A UART and MCU

Resistors must be placed in series for the UART connection between the KT6368A and the MCU.Resistors must
be placed on between TX and RX.
This is because the KT6368A's core operating voltage is relatively low, and the MCU's TX line (note: the MCU's TX)
typically outputs a high level. This can cause backflow into the KT6368A, leading to abnormal operation or failed
resets. This is a potential risk.
1. Current tests using a CH340G serial board with 1K resistors on both TX and RX lines show excellent results,
with no leakage or abnormalities.
2. Tests with 100-ohm resistors on both TX and RX lines also show excellent results, with no leakage.
==> Recommendation: Use 100-ohm resistors. If using a 5V MCU, use 1K resistors instead.

Refer to the R5 and R6 settings in the diagram above.

Page 38
V2.1
10.2 Important Notes on KT6368A Crystal Oscillator

This has been clearly described in previous sections, but many customers still overlook it.
You can refer to Section 1.7, "Hardware Design – Bluetooth Crystal Oscillator," for detailed information.

Conclusion: Do not solder the matching capacitors next to the crystal oscillator. They can be reserved but must
not be soldered. If unsure, use the Bluetooth test box to measure the frequency deviation of the crystal
oscillator and KT6368A chip. For more details, refer to "Section 9 – Mass Production Notes."

10.3 Important Notes on Modifying Bluetooth Name, Baud Rate, and Other
Memorized Parameters for KT6368A

When the KT6328A or KT6368A chip is powered on for the first time, the system performs numerous internal
calibration operations.
This process takes approximately 2.5 seconds. Therefore, AT commands should only be sent about 3 seconds
after power-up.
However, during the second, third, or subsequent power-ups, the calibration time is reduced to around 500ms.

1. Therefore, users must pay close attention to the timing when sending AT commands to modify parameters
like the Bluetooth name, especially in systems with fixed power-up times. Incorrect timing can lead to strange
issues.
2. It is recommended to modify Bluetooth parameters (e.g., name, address, baud rate) between 2.5 to 3
seconds after power-up.

@@What is the First Startup of the Chip?


1. After programming, the chips are shipped directly to customers. If the chip has never been powered on, it is
considered the first startup.
2. Once the chip has been powered on, all subsequent startups are considered the second, third, or later.
3. If power is interrupted during the calibration phase, the chip will continue calibrating the remaining
parameters upon the next power-up.

@@ In Summary: --- We hope you will pay close attention.


1. To ensure chip stability, wait at least 2.5 seconds after power-up before sending commands to set parameters.
2. Alternatively, wait for the Bluetooth chip to return initialization data before sending AT commands to set
parameters like the Bluetooth name, address, or baud rate.
3. During the first startup, the calibration process takes longer, and the current draw is significantly higher,
peaking at around 30mA.

Page 39
V2.1
10.4 Power Supply Considerations for KT6368A

Some customers attempt to power the KT6368A or other versions using an MCU's GPIO pin. This is not
recommended for the following reasons:

1. Some MCU GPIO pins cannot supply sufficient current.


2. The KT6368A chip has periodic average current consumption. During broadcasting, the instantaneous current
can reach 25mA, but this lasts for a very short time. Most of the time, the chip is not broadcasting, so the
average current is low.
==> This means that MCU GPIO pins generally cannot handle the instantaneous current during broadcasting,
causing voltage drops and abnormal operation of the KT6368A chip. This is very important.

Conclusion:
Do not power the KT6368A directly from an MCU GPIO pin. Always use an LDO (Low Dropout Regulator) to
provide a stable power supply. The optimal supply voltage is between 2.8V and 3.3V.
Exceeding 3.4V can damage the chip.

Page 40
『 Contact US 』for Technical Support and Sales Service
/*********************************************************************

EMail: [email protected]

WhatsApp: +86 159 0279 7635

WeChat: JAJB-Go

Tel: +86 159 0279 7635

*********************************************************************/

- Feel free to call for consultation at any time.

- Welcome to contact us anytime to obtain documentation or communicate.

Linkedin: https://www.linkedin.com/company/blevoice/
Blogger: https://blevoice.blogspot.com
Tumblr: https://www.tumblr.com/blog/blevoice
TikTok: https://www.tiktok.com/@blevoice
[BLE Voice Store]: https://www.aliexpress.com/store/1104656113

1. To request samples, please search for key words such as "KT6368A" directly on
AliExpress, enter our official store [BLE Voice Store] for solutions.
2. For each product, through rigorous development, debugging, and testing processes,
we provide comprehensive technical documentation including user manuals, FAQs,
schematics, Datasheet, Reference Code, debugging guides, critical notes and ect.
3. As our products expand into broader applications and industries, all related
technical resources are continuously updated to ensure relevance.
4. Full technical packages for every product are permanently hosted on Google Drive,
offering free lifetime access, and the corresponding download links are highlighted on
the detail pages of each product in our AliExpress store.
5. While our documentation may appear on third-party platforms, forums, or
websites (shared by enthusiasts, partners, or industry peers), the latest versions are
exclusively available on Google Drive.

You might also like