Jmicron JMS576 Firmware 01.02.00.01

I picked up Two Orico 25PW1-C3 that arrived today

They are Listed as 6Gbps capable in comparison to the 25PW1-U3 that is listed as 5Gbps capable
So presumed they where USB 3.x Gen2

They are JMS576 USB 3.1 Gen1

They only cost £3.50 each so whatever

There doesnt seem to be any firmware around for the JMS576
so here's one

I dumped both devices they have identical firmware and nvram
I have included the flasher that i dumped the firmware with

mega.nz/file/Fi5lQJBL#gFZgo8iQEZ6EUdeVaq...wGkJkkzwP2IzbfTQR_7g

I have a couple of those around, I don't think that bridge was used a lot for some reason, mine were in Blueendless enclosures for 3.5'' SATA drives.

One of the has a firmware that's a bit newer than yours, 01.02.01.04, the other one has some crazy numbering, 250.01.00.03, I wonder what that's about. You can find them both here:  mega.nz/folder/EVUyzDwD#GDJCjq149xicZcDER68zfw

I haven't changed anything yet, but the sleep timer is at 0xC4F6 and 0xC4F7 encoded as number of seconds (00 B4 = 3 minutes), but in JMS578 0xC4F2 needed to be changed as well to 30 (I think it was, hex) to disable the timer, setting the other bytes to 0; by the way, none of those firmwares use the details of the connected drive to populate the descriptions (make, model). I remember another adapter I had that used a JMS578 doing it by default if its configuration was cleared (everything set to 0xFF on NVRAM), so perhaps the 576 does as well, but it's probably better to figure out how what to tweak instead thought 😅

Thanks

250.01.00.03 is really old it doesnt recognise the Flash Type as PUYA instead it says unknown
i have seen this type of numbering before some oem's do it for some reason, it will be 01.01.00.03 with 250 added to it..

I tried 01.02.01.04 with your nvram it id's as Jmicron Generic SCSI Disk Device 01.02.01.04
I decided to keep my nvram so it id's as Jmicron Tech SCSI Disk Device and oddly the firmware now id's as 01.05.01.04

all 3 firmware's dont support trim btw

I have a puzzle in my hands I’m not sure I can finish Shonk 😅

So, I have another adapter that uses the JMS576, it's branded MAIWO K1683. It’s small, for M.2 SATA drives up to 2242 and the flash chip on it is a 128 KB XT25F01D; its firmware supports TRIM (UNMAP technically, since it works in UAS mode, works as expected). Here are some pictures of it:  imgur.com/a/VOfLRzn

But I am not entirely sure it is a JMS576. The FW update utility for the 576 does detect the device as being part of the series, correctly detects the manufacturer of the NOR (in this case) flash and its version. It also reads it, but it is truncated to 49.5 KB (the size of usual 576 firmware?).

 

Dumping it through JMS FW reader tells another story, it also labels it a 576, but the dump is a bit larger at 65.5 KB with the configuration data. Inspecting it with an hex editor shows odd stuff. There’s JMS580 in the clear for starters, and although the other firmwares we have contained 0s there, at 0x22, there’s “1576” in hex. A flag to indicate it’s a 576 or just some marker that happened to have the same numbers?

 

The FW update utility for JMS580 that’s hosted here at Station Drivers doesn’t detect the device as compatible, so I don’t know which one it is. Rebadged maybe? Or similar families with something in the firmware to discern one from another? Directly programming the contents of this flash onto the one in the large enclosure for 3.5’’ disks I have makes the attached drive not to show up, but the enclosure itself is recognized, I wonder if it has to do with it being powered externally, or some flags needed to be tweaked in the firmware for it to work.

Anyway, I have uploaded it here, in case you're more experienced or can make sense of it:  mega.nz/folder/NNEQXaIL#xMUKRjRWKfmyh2Uy1-_2Fg

If you think of things to try let me know, I was going to try to stitch the firmware dumped through the JMS FW reader onto the raw flash, flash it back and see what happens, but I still didn't get to it.