Part Review and Datasheet Update


Review all available part information (MPN, package, pin count, description, properties). If no datasheet URL is already set, search the web for the official datasheet and update the part's Datasheet property with the URL. Then cross-check the schematic symbol, footprint, and pin descriptions against the datasheet. Summarize key specs and flag any mismatches.
I’ll review the current part metadata, find and attach the official datasheet if missing, then cross-check symbol pins, footprint, and descriptions against the datasheet and report mismatches.
The part already has a Datasheet URL set, so I’m using that document as the review source and won’t overwrite it unless it proves unofficial or inaccessible.
Completed the BT860-SA part review and saved the full findings in BT860-SA Part Review. The part already had a Datasheet URL, so I did not overwrite it, but I found official Ezurio/Laird datasheet sources and flagged that the current URL is an uploaded PDF copy rather than an official source.
Open items:
  • Pin types and pin descriptions are all unspecified and should be populated from the datasheet.
  • Pin 17 is labeled RF, but for BT860-SA it is no-connect.
  • I2S_WS/PCM_SYNC_ has a trailing underscore.
  • Project description/version metadata may conflict with newer BT860 v5.0 references.
Suggested next steps:
  1. Update symbol pin types/descriptions from the datasheet.
  2. Rename/fix the pin 17 and pin 19 labels.
  3. Optionally replace the Datasheet URL with the official Ezurio/Laird datasheet URL.
  4. Verify exact footprint pad geometry against the datasheet land pattern.
Fix pins and verify
Fix symbol issues
Update official datasheet
Verify footprint geometry
Run ERC/DRC review

BT860-SA Part Review
Source material
  • Current project/part: BT860-SA
  • Published part UID: fb5b8ec5-bdcb-4ca2-aa84-25caf5234d1d
  • Existing Datasheet URL: https://storage.googleapis.com/graviton-electric-symbols/document_assets/user-uploaded/2ce9abca5cb38a7d013c148115ccd8105ed9fb4d88e015e0100978bab5080bb3.pdf
  • Official web sources found:
    • Ezurio / Laird support page: https://www.ezurio.com/support/part/bt860-sa
    • Ezurio datasheet landing page: https://www.ezurio.com/documentation/datasheet-bt860
    • Legacy Laird PDF: https://assets.lairdtech.com/home/brandworld/files/BT860%20Datasheet%20-%20v1_1.pdf
The part already had a Datasheet URL, so no Datasheet URL property update was required by the user’s condition. The existing URL appears to be an uploaded copy, while official Ezurio/Laird sources are available above.
Existing part metadata reviewed

Table


FieldCurrent value
Manufacturer Part NumberBT860-SA
Manufacturer NameLaird
Package or Case CodeModule
Designator PrefixIC
Project descriptionBluetooth Modules (802.15.1) BTv4.2 Dual Mode UART HCI Module (truncated)
Schematic terminals30
PCB pad nodes30 pad nodes
Key datasheet specs

Table


SpecDatasheet value
FunctionBluetooth dual-mode UART HCI module with integrated antenna for BT860-SA
Supply voltage3.0 V to 3.6 V on 3.3V input
InterfacesUART HCI up to 4 Mbps; I2S/PCM; SECI coexistence; BT_HOST_WAKE
RF band2.402 GHz to 2.480 GHz
TX powerClass 1, +8 dBm from antenna
RX sensitivity-94 dBm
Current8 mA idle; 23 mA inquiry; 43 mA file transfer; 26–27 mA typical BLE active modes listed
Operating temperature-30 °C to +85 °C
Module dimensions8.5 mm × 12.85 mm × 2.2 mm for BT860-SA
AntennaIntegrated multilayer ceramic / chip monopole antenna
Layout notesPlace near PCB edge/corner; keep antenna area copper-free on all layers; use solid GND plane and nearby GND vias
Datasheet pin table vs schematic symbol

Table


PinDatasheet name / functionSchematic terminalMatch?Notes
1NCNC_1YesName differs only by instance suffix.
2GNDGND_1YesName differs only by instance suffix.
3GPIO_5GPIO_5YesPin type should be Bi-directional.
4UART_RTSUART_RTSYesPin type should be Bi-directional; datasheet describes request-to-send output.
5UART_TXDUART_TXDYesPin type should be Bi-directional; datasheet describes UART transmit data.
6UART_CTSUART_CTSYesPin type should be Bi-directional; datasheet describes clear-to-send input.
7UART_RXDUART_RXDYesPin type should be Bi-directional; datasheet describes UART receive data.
8RESETRESETYesPin type should be Input; active-low reset.
93.3V3.3VYesPin type should be Power In/Input.
10NCNC_2YesName differs only by instance suffix.
11GNDGND_2YesName differs only by instance suffix.
12GNDGND_3YesName differs only by instance suffix.
13GNDGND_4YesName differs only by instance suffix.
14GNDGND_5YesName differs only by instance suffix.
15GNDGND_6YesName differs only by instance suffix.
16GNDGND_7YesName differs only by instance suffix.
17RF: BT860-SA no connection; BT860-ST 50 Ω RF outputRFPartialFor BT860-SA this should be clearly marked NC / RF no-connect to avoid routing it as an RF port.
18GNDGND_8YesName differs only by instance suffix.
19I2S_WS/PCM_SYNCI2S_WS/PCM_SYNC_PartialSchematic has trailing underscore; likely typo.
20I2S_CLK/PCM_CLKI2S_CLK/PCM_CLKYesPin type should be Bidirectional.
21I2S_DI/PCM_INI2S_DI/PCM_INYesPin type should be Bidirectional.
22I2S_OUT/PCM_OUTI2S_OUT/PCM_OUTYesPin type should be Bidirectional.
23GNDGND_9YesName differs only by instance suffix.
24NCNC_3YesName differs only by instance suffix.
25BT_SECI_INBT_SECI_INYesPin type should be Input.
26BT_SECI_OUTBT_SECI_OUTYesPin type should be Output.
27NCNC_4YesName differs only by instance suffix.
28NCNC_5YesName differs only by instance suffix.
29BT_HOST_WAKEBT_HOST_WAKEYesPin type should be Output.
30GNDGND_10YesDatasheet unused recommendation says NC, but function is Ground; schematic name is acceptable.
Footprint review
  • PCB footprint contains 30 pad nodes, matching the 30-pin datasheet pin table.
  • Silkscreen/fab outline visible in layout spans approximately 12.85 mm × 8.5 mm, matching the datasheet module body dimensions, with a larger outline/keepout-style shape visible around the module.
  • Pin 1 marker is present near one corner.
  • Detailed pad geometry was not exposed in the available structured layout response, so pad width, pad pitch, exact pad locations, and antenna keep-out copper exclusion were not fully machine-verified.
Mismatches / issues flagged
  1. Project description says BTv4.2 while queried datasheet content and distributor listings identify BT860-SA as Bluetooth v5.0 dual-mode. Official search results include both legacy “v4.2” title text and newer Ezurio v5.0 references, so this should be normalized to the current official datasheet revision being used.
  2. All schematic terminal Pin Type properties are Unspecified. Datasheet provides clear electrical directions: GND, Power Input, Input, Output, and Bidirectional. This should be corrected for better ERC/symbol quality.
  3. No Pin Description properties are populated on the terminals. The datasheet descriptions should be copied into terminal descriptions.
  4. Pin 17 is labeled RF in the symbol, but for BT860-SA it is no-connect. This is risky because it implies an RF signal port. Recommended label: RF_NC or pin description “BT860-SA no connection; BT860-ST 50 Ω RF output.”
  5. Pin 19 symbol label has a trailing underscore: I2S_WS/PCM_SYNC_. Datasheet label is I2S_WS/PCM_SYNC.
  6. Datasheet property points to an uploaded PDF copy rather than the official Ezurio/Laird URL. Not strictly wrong because a datasheet URL exists, but an official support or datasheet URL is preferable for traceability.
  7. Manufacturer name is Laird; current branding is Ezurio, formerly Laird Connectivity. Consider updating to Ezurio (formerly Laird Connectivity) or keeping Laird only if matching legacy procurement data.
  • Update terminal Pin Type and Pin Description properties from the datasheet pin table.
  • Rename I2S_WS/PCM_SYNC_ to I2S_WS/PCM_SYNC.
  • Clarify pin 17 as BT860-SA no-connect rather than a routable RF output.
  • Consider updating Datasheet URL to the official Ezurio datasheet landing page or official PDF.
  • Consider updating project description/version metadata to match the selected official datasheet revision.
  • If publishing for reuse, verify exact pad geometry against the datasheet land pattern manually or with a layout data export that exposes pad dimensions and coordinates.
  • Source material

  • Existing part metadata reviewed

  • Key datasheet specs

  • Datasheet pin table vs schematic symbol

  • Footprint review

  • Mismatches / issues flagged

  • Recommended fixes