<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[PublMe - Space: Posted Reaction by PublMe bot in PublMe]]></title>
	<link>https://publme.space/reactions/v/68975</link>
	<atom:link href="https://publme.space/reactions/v/68975" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://publme.space/reactions/v/68975</guid>
	<pubDate>Thu, 30 Jul 2026 22:00:55 +0200</pubDate>
	<link>https://publme.space/reactions/v/68975</link>
	<title><![CDATA[Posted Reaction by PublMe bot in PublMe]]></title>
	<description><![CDATA[
<p>Fixing a JMicron-Based M.2 USB Enclosure That Stopped Working</p>
<div><img width="800" height="506" src="https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg?w=800" alt="" srcset="https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg 1097w, https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg?resize=250, 158 250w, https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg?resize=400, 253 400w, https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg?resize=800, 506 800w" data-attachment-id="1131183" data-permalink="https://hackaday.com/2026/07/30/fixing-a-jmicron-based-m-2-usb-enclosure-that-stopped-working/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube/" data-orig-file="https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg" data-orig-size="1097,694" data-comments-opened="1" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;,&quot;orientation&quot;:&quot;0&quot;,&quot;alt&quot;:&quot;&quot;}" data-image-title="jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube" data-image-description="" data-image-caption="" data-large-file="https://hackaday.com/wp-content/uploads/2026/07/jmicron_orico_ssd_enclosure_fix_mark_furneaux_youtube.jpg?w=800"></div><p>As useful as USB-to-M.2 SSD adapters are, sometimes you come across a bit of a dud. A case in point is the Orico-branded TCM2-C3 that features both an attractive clear case and in its earlier revisions a JMicron controller-based circuit that apparently degrades over time, causing erratic boot behavior. After implementing a fix a few years ago, [Mark Furneaux] <a rel="nofollow" href="https://www.youtube.com/watch?v=Y6X1v1zW5gw" target="_blank">can happily report</a> that the thus fixed enclosures are still working.</p><p>These faulty board revisions feature the JMicron <a rel="nofollow" href="https://datasheet4u.com/download/1563513/JMS583.html" target="_blank">JMS583</a> controller IC, which has a 1.0V core voltage input pin. Apparently to save power, Orico designed the board to target the minimum ~-0.95V core voltage per the datasheet. Apparently due to component drift or degradation, this lower core voltage is after a while often not enough any more to start the controller, which thus translates into an unresponsive USB device and presumably some panic about lost data.</p><p>Although [Mark] doesn’t describe the fix in detail, it entails bumping up this core voltage to something closer to the nominal 1.0V, which restores functionality at the cost of presumably a measurable amount of extra heat production by said controller.</p><p>Later versions of the Orico TCM2-C3 enclosure switched from this JMicron controller to a Realtek one, which so far appears to be noticeably more reliable. Although Orico kept the same model name, the transparent enclosure makes it at least a snap to see which revision you are dealing with.</p><p></p><p></p>]]></description>
	<dc:creator>PublMe bot</dc:creator>
</item>

</channel>
</rss>