<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Stock Wake on Medium]]></title>
        <description><![CDATA[Stories by Stock Wake on Medium]]></description>
        <link>https://medium.com/@voohukukook?source=rss-d66e50688036------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hitLBEhsYcFRueX8utwbcw.png</url>
            <title>Stories by Stock Wake on Medium</title>
            <link>https://medium.com/@voohukukook?source=rss-d66e50688036------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:47:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@voohukukook/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Similar Part Numbers Don’t Guarantee Interchangeability]]></title>
            <link>https://medium.com/@voohukukook/why-similar-part-numbers-dont-guarantee-interchangeability-c783806564cb?source=rss-d66e50688036------2</link>
            <guid isPermaLink="false">https://medium.com/p/c783806564cb</guid>
            <category><![CDATA[procurement]]></category>
            <category><![CDATA[quality-control]]></category>
            <category><![CDATA[embedded-systems]]></category>
            <category><![CDATA[supply-chain]]></category>
            <category><![CDATA[electronics]]></category>
            <dc:creator><![CDATA[Stock Wake]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 09:47:15 GMT</pubDate>
            <atom:updated>2026-11-19T09:47:15.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMuOMRzF9zMpsCKe0ljXpQ.png" /><figcaption>Chart comparing LP038 and LP039 CAN specs and 4 substitution review steps, noting similar parts are not interchangeable.</figcaption></figure><p><em>A practical way to connect a component proposal to the board, firmware, and evidence behind the decision.</em></p><p>Imagine an approved BOM specifies CY8C5868LTI-LP039. A supplier offers CY8C5868LTI-LP038 instead, pointing to the same package and memory capacities. Purchasing has a reasonable question: can this offer keep the order moving?</p><p>Disclosure: This article includes AI-generated text checked against the linked manufacturer documents. The example is hypothetical; no hardware or firmware testing was performed for this article.</p><p>The answer starts with the design. A quotation identifies the component being offered. Engineering needs to establish what changes when that component goes onto a particular board.</p><p>That becomes easier to discuss when the review follows three connected questions.</p><h4>What resource does this design actually use?</h4><p>Infineon’s <a href="https://www.infineon.com/assets/row/public/documents/30/49/infineon-psoc-5lp-cy8c58lp-datasheet-datasheet-en.pdf">CY8C58LP family datasheet</a>, document 001–84932 Rev. *O, Table 12–1, lists both devices with 68-QFN packaging, 256 KB Flash, and 64 KB SRAM.</p><p>The same table shows an important difference: built-in CAN 2.0B is listed for CY8C5868LTI-LP039, but not CY8C5868LTI-LP038.</p><p>If the existing design relies on LP039’s built-in CAN controller, that difference changes the proposal immediately. Offering LP038 removes a resource the application uses. Proceeding would require assessment of an architecture change, rather than approval based on the shared package and memory.</p><p>This is also where a quick look at the PCB can mislead us. A CAN transceiver and a CAN controller have different roles. Section 7.5 of the datasheet describes the controller’s connection to an external transceiver. Seeing that external chip on the board therefore leaves an important question open: where is the controller?</p><p>If a separate device supplies the controller, the review takes a different path. If the application never uses CAN, this particular difference may be irrelevant. Either finding is useful because it connects a feature-table difference to the actual application.</p><h4>Which board and firmware are being considered?</h4><p>Once the required functions are understood, the proposal becomes more specific: this device, on this board revision, with this firmware target.</p><p>Engineering can review the actual pin assignments, power and reset connections, and programming interface against the relevant documentation. The original firmware project should remain identifiable while the proposed device target, resource assignments, and resulting build are assessed.</p><p>Keep the programming image tied to that assessment. An unnamed file passed between purchasing, engineering, and production makes it difficult to know whether everyone is discussing the same change.</p><p>There is a concrete safeguard here. The <a href="https://www.infineon.com/assets/row/public/documents/30/436/infineon-cy8c58lp-cy8c56lp-cy8c54lp-cy8c52lp-psoc-5lp-device-programming-specifications-programming-specifications-en.pdf">PSoC 5LP Device Programming Specifications</a>, document 001–81290 Rev. *F, Section 3.3, calls for comparing the target device ID with the Device ID information in the HEX file. A mismatch should stop programming.</p><p>Keep that check in place and investigate the mismatch. Editing identification metadata to get past it would leave the application-suitability question unanswered.</p><h4>What evidence supports release?</h4><p>A completed build is useful evidence about the build stage. Successful programming adds evidence about another stage. The application still needs validation on the proposed hardware under the conditions engineering defines.</p><p>For the LP039-to-LP038 example, the sequence matters. Establish the required resources, assess the board and firmware configuration, then evaluate the required behavior. Compilation or programming success cannot resolve an earlier finding that the application needs a controller the proposed device lacks.</p><p>The final record can be compact. It should connect the full original and proposed ordering codes to the reviewed board revision, firmware target, identified image, relevant test conditions and results, and the person responsible for the decision.</p><p>That gives purchasing an actionable answer with a clear scope. Approval for one board and build stays attached to that configuration, instead of quietly spreading to every product using the same family.</p><p>A small difference in an ordering code can lead to a substantial engineering question. Following the design helps both teams reach an answer they can explain.</p><h4>When an alternative component is proposed, what helps your purchasing and engineering teams reach a clear decision together?</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c783806564cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>