# Samples and known issues
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
## Sample testing
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
See [Table : Device identification details](https://docs.qualcomm.com/doc/80-73480-1/topic/mechanical-information.html#topic_dcw_1jl_bhc__table_uyx_bjl_bhc) for device identification details for all available samples.
### Engineering sample (ES)
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
These devices undergo limited testing and sometimes have significant feature limitations.
They are suitable to assist with PCB development, to conduct board-level electrical
evaluation tests, and to explore manufacturing considerations. Engineering samples
should not be used for product-level qualification.
### Commercial sample (CS)
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
These devices undergo full production-level testing, and meet the specifications and
features described in the data sheet, except as otherwise noted in this document. They
have passed device level qualification. Commercial samples are suitable for performance
testing, and also for product level production and qualification.
## Compatible software release
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
Each sample type is for use with a particular software version (or later). Sample types
are not expected to be compatible with AMSS software releases that occurred earlier than
that particular version. The following table identifies the software compatibility of
each sample type.
| Variant | PRR | Compatible software | Comments |
| --- | --- | --- | --- |
| QCS615 | 000 | QCS615.LE.1.0-00005-STD.PROD-1 | ES software release |
| QCS615 | 000 | QCS615.LE.1.0-00016-STD.PROD-1 | CS software release |
| | | | |
## Known issues
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
### Summary of known issues
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
All known issues for each revision of the QCS615 device are summarized in the following
table. The text within the Issue column provides links to the sections of this document
that explain the issues, regardless of the sample type (or types) on which they occur.
An X in one or more of the sample type columns indicates that the issue occurs in the
corresponding sample type.
The following information is provided for each issue:
- Issue description
- Impact to system performance
- Possible workarounds to minimize impact
Table : Example functional area descriptions
| Functional area | Description |
| --- | --- |
| Modem | Modem subsystem |
| MMSS | Multimedia subsystem |
| CPUSS | CPU subsystem |
| DDRSS | DDR subsystem |
| LPASS | Low-power audio subsystem |
| PSS | Peripheral subsystem |
| RPM | Resource and power management |
| SPSS | Secure processor subsystem |
| TME | Trust management engine |
| WCSS | Wireless connectivity subsystem |
| General | General area |
| Issue # | Issue description | Functional area [^1^](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html#fntarg_1_summary-of-known-issues) | Workaround | ES | CS |
| --- | --- | --- | --- | --- | --- |
| Issue # | Issue description | Functional area [^1^](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html#fntarg_1_summary-of-known-issues) | Workaround | PRR = 000 | PRR = 000 |
| 1 | [RMII packets drop due to CRS_DV sensitivity](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html#topic_myt_tfl_bhc__section_z43_ngl_bhc) | Peripheral | None available, information only | X | X |
| | | | | | |
[^1^](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html#fnsrc_1_summary-of-known-issues) The functional areas are defined in [Table : Example functional area descriptions](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html#topic_jz3_yfk_bhc__table_sq5_4gk_bhc).
^2^ P and RR values are detailed in the
Variant column of [Table : Device identification details](https://docs.qualcomm.com/doc/80-73480-1/topic/mechanical-information.html#topic_dcw_1jl_bhc__table_uyx_bjl_bhc).
### Issues – description, impact, and workaround
Source: [https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html](https://docs.qualcomm.com/doc/80-73480-1/topic/samples-and-known-issues1.html)
### Issue 1: RMII packets drop due to CRS\_DV sensitivity
| Description | RMII controller in the SoC is sensitive to the PHY toggling
CRS\_DV signal towards end of packet transmission. |
| --- | --- |
| Impact | Packets may be dropped due to CRC mismatch. |
| Workaround | No known workaround – the RMII PHY should keep the data valid
(CRS\_DV) signal asserted from start to end of the packet to avoid
packet drops. This issue is observed only for RMII
implementation. |
Last Published: Mar 09, 2026
[Previous Topic
Part reliability](https://docs.qualcomm.com/bundle/publicresource/80-73480-1/topics/part-reliability.md) [Next Topic
Revision history](https://docs.qualcomm.com/bundle/publicresource/80-73480-1/topics/revision-history.md)