
CY8C5868LTI-LP038 does not include the CAN 2.0B controller that is built into the CY8C5868LTI-LP039. If a supplier offers the LP038 as a drop-in replacement for an LP039 design, this missing internal resource is your first red flag. You need to confirm whether your application actually relies on that built-in controller. If it does, the substitution fails.
If it doesn't, you still have to review the board connections, select the exact firmware target, and rebuild the project. Matching packages and memory sizes do not make the parts—or an existing HEX file—interchangeable.
Confirm the Complete Codes and the CAN Difference
The Ordering Table Defines This Comparison
Start with the full approved code and the full offered code. Keep them next to the BOM revision and the original manufacturer document. A shortened family name (like "PSoC 5LP") can hide the exact feature difference that matters here. The guide to top markings and full manufacturer part numbers explains why those identification fields serve different purposes.
The Infineon CY8C58LP family datasheet, document 001-84932 Rev. *O, lists both codes in Table 12-1 on printed page 127. The table below uses those exact rows. LP038 and LP039 are shortened labels for the two complete codes in this article.
| Listed Field | LP038 | LP039 | Review Meaning |
|---|---|---|---|
| CAN 2.0B | Not included | Included | Check the application's controller requirement. |
| Package | 68-QFN | 68-QFN | Check the actual pin assignments and footprint. |
| CPU speed | 67 MHz | 67 MHz | A shared speed field does not resolve CAN support. |
| Flash | 256 KB | 256 KB | A shared capacity does not establish binary compatibility. |
| SRAM | 64 KB | 64 KB | Review the selected device and project configuration. |
Key takeaway: Proposing an LP039-to-LP038 change removes a listed built-in CAN resource. Keep that direction explicit in your review. The reverse proposal (LP038 to LP039) also needs its own assessment; adding a resource does not automatically approve the rest of the change.
Locate the CAN Requirement in the Actual Design
The CAN Controller and Transceiver Serve Different Functions
Pull up the schematic and the firmware project together. Identify where the CAN control logic is implemented, which software uses it, and how its signals reach the bus interface. A board-level label that just says "CAN" answers none of those questions.
The datasheet's Section 7.5 and Figure 7-14 (printed page 47) distinguish the CAN controller from an external transceiver. Just because you find a transceiver on the PCB does not mean the LP038 contains the missing controller. If a separate device implements the controller, have your engineering team review that architecture. The missing built-in resource alone does not settle that different design.
The Package Label Does Not Resolve Board Mapping
Compare the existing schematic, assigned signals, and footprint with the manufacturer drawings. Include the connections for power, reset, and programming/debug. Keep the board revision in your record. These are checks to perform on the actual design, not evidence that either proposed arrangement has already passed.
Retarget the Project and Check the Programming Image
The Selected Device Belongs in the Build Record
The PSoC Creator User Guide, document 001-93417 Rev. *N, describes the Device Selector on printed pages 119-120. It selects the device and silicon revision. The Build Menu section (printed page 100) describes cleaning and rebuilding the named project.
- Preserve the existing project and identify the board revision it supports.
- Select the complete proposed device in Project > Device Selector. Record the Creator version and selected silicon revision.
- Clean and rebuild that project. Review build messages, resource use, and pin assignments before accepting the output.
- Identify the generated image by filename and hash. Keep it separate from the image released for the original code.
A successful build just means the reviewed project produced an output under that tool configuration. It does not prove that CAN communication, startup, or the rest of the application will work on the proposed hardware.
The Device Identity Check Must Remain Intact
Infineon documents this check in the PSoC 5LP Device Programming Specifications, 001-81290 Rev. *F. Section 3.3 (printed page 34) requires comparing the target device ID with the HEX device ID. A mismatch should stop programming. Appendix Table A-1 (printed page 79) describes the HEX metadata.
Do not assume an old HEX file will work just because the package or memory sizes match. Retain the programmer's identity check and investigate any mismatch. In section 3.3, the target device ID read for the check is the JTAG ID; it is compared with the Device ID stored in the HEX metadata. Keep the actual read, the datasheet's reference ID, and the HEX metadata location distinct. Do not replace a real device reading with a table value, and never alter the HEX metadata just to force a match.
Bind the Decision to a Defined Board and Build
The Evidence Must Show What Was Reviewed
Bring all review outputs into one record. Engineering should define the board checks, operating conditions, and acceptance criteria needed for this specific application. If testing is required, keep the actual results against the exact board and image. This article does not report a board test or approve a substitution.
| Decision Gate | Evidence to Retain | If Evidence Is Missing |
|---|---|---|
| CAN requirement | Controller location and the project functions that use it | The required resource remains unconfirmed. |
| Board mapping | Board revision, schematic, and reviewed signal assignments | The physical implementation remains unreviewed. |
| Build target | Full device code, Creator version, project revision, and image hash | The image is not tied to the proposed device. |
| Programming | Target identification and programming result for that image | Any mismatch needs investigation. |
| Application behavior | Defined checks, conditions, results, and engineering decision | Required validation remains incomplete. |
Once an alternative is approved, the guide to recording approved alternatives in a BOM request explains how to preserve its scope. For affected purchases, reconcile the BOM revision with open component orders before carrying the change into those lines. Neither a supplier quotation nor this comparison supplies the engineering approval.
Frequently Asked Questions
Does LP038 have the same CAN support as LP039?
No. The reviewed ordering table includes CAN 2.0B for the CY8C5868LTI-LP039 and does not include it for the CY8C5868LTI-LP038. Check whether your actual project needs that built-in resource before considering the change.
Does an external CAN transceiver make the parts equivalent?
No. A transceiver does not supply the missing CAN controller. Identify where the controller is implemented in the actual design. A design with a separate controller needs its own review; a fitted transceiver alone does not establish that architecture.
Can the original LP039 HEX file be used with LP038?
Do not assume it can. Confirm the project target, rebuild for the proposed device, and retain the programmer's device-ID check. A mismatch should stop programming. Even successful programming still leaves the application's required validation to complete.
Does selecting the new device approve the replacement?
No. Device selection just identifies the intended build target. The review still needs the correct resources, board mapping, programming image, and application evidence. Keep the final engineering decision tied to those exact revisions and conditions.
Is an LP038-to-LP039 change automatically safe?
No. That direction adds the CAN resource listed in the table, but it does not establish board or firmware suitability. Review the actual target, connections, image, and required behavior before approving the change.
Keep the Proposed Change Within the Reviewed Scope
Start with the exact ordering rows, locate the application's CAN controller, and rebuild for the proposed target. Preserve the device-identity check and the evidence required by engineering. Purchasing can then follow a documented decision for that board and build. Do not approve the substitution while a required CAN function, target match, or validation result remains unresolved.