<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<span dir="ltr" style="margin-top:0; margin-bottom:0;">Just about every central processor under the sun has "errata" (plural of erratum) or "hardware bugs" when it first comes out. The RP2350 is continuing this tradition. It appears that external pull downs may be a workaround.</span>
<br>
<br><span dir="ltr" style="margin-top:0; margin-bottom:0;"><a href="https://hackaday.com/2024/09/04/the-worsening-raspberry-pi-rp2350-e9-erratum-situation/">https://hackaday.com/2024/09/04/the-worsening-raspberry-pi-rp2350-e9-erratum-situation/</a></span>
<br>
<br><span dir="ltr" style="margin-top:0; margin-bottom:0;">(In a former life I worked on compiler back ends and part of my job was to recognize intermediate code patterns and generate safe equivalent machine code sequences to steer around errata in the National 32K and Motorola 88K chips. Some of you may recall the Intel integer divide bug that forced a recall as an extreme example. With problems like this it was sometimes possible to avoid the machine instruction patterns that triggered the boo boo. </span>
<br>
<br><span dir="ltr" style="margin-top:0; margin-bottom:0;">But this RP GPIO latch bug appears to be in peripheral hardware and unavoidable in some circumstances. The question is how unusual is the Bus Pirate use case? Conversely, how likely are most users to ever encounter this? We should watch for a high S/N statement by the RP org in the near future.) </span>
<br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Pete</span>
<br>
</body>
</html>