- Edited
- #4
larrybarry
Hi there
For BIOS :
Please send us a picture of SN on the bottom to confirm.
Thanks for your patience and your understanding.
Do you have specs on ASM2464PD ? is it DDR4 or 5 ? what`s the PCIE speed ?
larrybarry
Hi there
For BIOS :
Please send us a picture of SN on the bottom to confirm.
Thanks for your patience and your understanding.
Do you have specs on ASM2464PD ? is it DDR4 or 5 ? what`s the PCIE speed ?
SN as requested
The enclosure is https://www.hypershop.com/products/hyperdrive-next-usb4-nvme-ssd-enclosure
Its specs are listed:
USB4 40Gbps Host Connection
M.2 NVMe PCIe Gen 4/3 SSD
Supports up to 4TB
The chipset it uses, the ASM2464PD, has these features which SHOULD work on the USB4 port:
General Features
USB4/Thunderbolt to PCI Express NVMe SSD Bridge.
Integrated two USB 20Gbps PHYs.
Integrated UFP CC Logic for USB Type-C cable orientation and detection.
Integrated BMC PHY for PD fixed 5V UFP/Sink mode.
VCCH/VCCL/VDD Power Supply.
Support SPI interface with External ROM for Customized RAM Code.
Support I2C and GPIOs and UART Interface.
Local 25MHz Crystal.
Universal Serial Bus Features
Support up to USB4/Thunderbolt Gen3 x2 with USB 3.2 and USB 2.0 (backward compatibility).
Support BOT and UAS Protocol.
Support USB Link Power Management.
Support USB Hot Plug.
Support Spread Spectrum Clock Control.
Support UNMAP Command Set.
Support SCSI Vendor Specific Command Set.
Compliant with Universal Serial Bus 4 (USB4 ®) Specification Rev. 1.0 (including Interoperability with Thunderbolt™ 3 (TBT3) Systems)
Compliant with Universal Serial Bus Type-C Cable and Connector Specification Revision 2.1
Compliant with Universal Serial Bus Power Delivery Specification Revision 3.1 Version 1.3
PCI Express Features
Support up to PCI Express Gen4 x4.
Support PCI Express NVMe SSD.
Support Spread Spectrum Clock Control.
100MHz Differential Reference Clock Output.
Support Various Types of PCI Express Socket including M.2, U.2, U.3 and CFexpress.
Support PCI Express Link Power Management.
Compliant with PCI Express Base Specification Rev. 4.0
Compliant with PCIe M.2 Specification Rev. 1.1
NVM Express Features
Support NVMe Power Management.
Support NVMe: SCSI Translation Reference Rev. 1.5
Support NVMe Error Reporting & Recovery.
S.M.A.R.T Drive Monitoring.
Compliant with NVM Express Base Specification Rev. 1.4c
The website also states:
“To achieve the 40 Gbps transfer speed, you should use a USB 4.0 or Thunderbolt 4 interface and update the OS build and NVM FW version to the latest version.”
I realized that the steps from the first support comments dealt with OS recognizing the enclosure. However, it isn’t recognized in the
BIOS either. When connected and in the BIOS, it isn’t showing up as a possible drive. So, steps within the OS wouldn’t help to fix the issue.
I think the BIOS itself needs to recognize the drive before the OS even has a chance. Maybe a BIOS update that includes the latest
NVM FW version?
Thanks again for your help and assistance to get this fixed. 🙏
Hi ,there
Your model only supports Max 2TB .
Hi ,there
Your model only supports Max 2TB
Not sure what you are referring to…..
The enclosure clearly states it supports 4TB. And it works on other computers just fine with a WD SN850× 4TB drive. It also
is recognized on the USB3 port of the SER 6 Pro just fine. Only at USB3 speeds.
If you are referring to the SER 6 Pro, that is also not correct. The USB4 port recognizes the exact same hard drive in an Acasis
enclosure without issue. It is only on the enclosure with the ASM2464PD chipset that it has problems. It doesn’t work with
ANY drives. I have tried 500GB, 1TB, 2TB, and 4TB drives. I have tried Gen3 and Gen4 drives. None are recognized on the
USB4 port.
Are you confused and think I am trying to get it connected to the M2 slot on motherboard? Please elaborate your response.
I am trying to get the USB4 port on my SER 6 PRO to recognize my hard drives in the enclosure with the ASM2464PD chip.
Also, I gave both the BIOS screen and SN. No mention if update on BIOS? It’s been over 20 months since last firmware.
larrybarry
Hello,
Here are some possible solutions:
①Check the manufacturer’s website of the Hyperdrive NVME enclosure or the ASM2464PD chipset to see if there are any specific USB4 drivers available. Download and install them to see if that resolves the recognition problem
② Please go to AMD website and download the auto-detect program.
It will update some chipsets and video drivers automatically. It will identify and install appropriate drivers for their AMD hardware. The program works by scanning the user’s system to detect the installed AMD hardware components, such as graphics cards or processors. It then compares the detected hardware information with a database of AMD drivers and software versions.
③ Please uncheck the save energy in the device manager—universal serial bus controller–USB hub—properties–power management—uncheck “Allow the computer to turn off the device to save power”
Best regards!
Wendy
Customer Support
1.
I have the newest drivers for the Hyperdrive ASM2464PD enclosure. It was from September of 2024. 3 months ago. There
isn’t a newer firmware available.
2.
I have already done this, see post 3 above. Didn’t help unfortunately.
3.
Already done this as well. See post #3 above. Same results. And as I stated in post #5, these steps are for issues with the OS.
However, the enclosure isn’t seen during post in the BIOS either, before the OS has a chance to load. Hence my comment below.
Still waiting if there is a BIOS update for my SER 6 PRO. I did as advised and uploaded a pic of BIOS and SN. The version I have
is from 2/21/23. Over 20 months ago. There really should be an update to fix at least some of these issues.
Enclosure Firmware: The Hyperdrive NVME enclosure with the ASM2464PD chipset may have outdated or incompatible firmware. Check the manufacturer’s website for any available firmware updates for the enclosure and apply them if necessary. Updating the firmware can often resolve compatibility issues and improve device performance and recognition.
Device Initialization Sequence: Some devices require a specific initialization sequence or protocol to be recognized by the host system. It’s possible that the ASM2464PD chipset has a different initialization requirement compared to the JHL7440 chip, and the SER 6 Pro is not handling it correctly. This could be a more complex issue that may require further investigation or input from the device manufacturers.
support7 Enclosure Firmware: The Hyperdrive NVME enclosure with the ASM2464PD chipset may have outdated or incompatible firmware. Check the manufacturer’s website for any available firmware updates for the enclosure and apply them if necessary. Updating the firmware can often resolve compatibility issues and improve device performance and recognition
See point 1 in post #9 above you. Already done. It is dated 09/24. 3 months old. Much newer than the BIOS for my Beelink product.
Which I’m still waiting to see if there is an update since support asked me for the SN in post #4. Do you guys even read my responses?
support7 Device Initialization Sequence: Some devices require a specific initialization sequence or protocol to be recognized by the host system. It’s possible that the ASM2464PD chipset has a different initialization requirement compared to the JHL7440 chip, and the SER 6 Pro is not handling it correctly. This could be a more complex issue that may require further investigation or input from the device manufacturers.
As far as I can tell, it is only this host system that is not recognizing it properly. It is working on my Lenovo laptop, HP desktop, Mac mini, iphone, ipad, etc. It is ONLY an issue with the USB4 port on my Beelink Ser 6 Pro. I don’t have another Beelink product to test on, but
I would wager that it wouldn’t work there as well. Since it works on EVERYTHING else so far. This is why I am trying to "further investigate
from the device manufacturer." on this forum.
For some reason my previous post is “awaiting approval” and not showing on forum?
Hello,
Have you reinstalled the system? If you have reinstalled other systems, it is recommended to use our system again.
Best regards!
Wendy
Customer Support
If I connect my enclosure and boot into BIOS and it isn’t recognized there, how would a fresh install of the operating
system help? If it isn’t being recognized during POST, before any operating issues would affect the system, why would
a different operating system help???
I could load a new version of Win 11.
I could load a version of Win 10.
I could load a linux distro.
I could load a live boot system.
NONE of these will help if the system itself doesn’t recognize the enclosure. The recourse would be to update the BIOS to
accommodate different USB4 protocols. I still haven’t heard if or why there isn’t a BIOS update for this system. It is almost
2 years old!
larrybarry
Regarding Compatibility Issues
While USB4 was indeed designed to minimize compatibility problems, in reality, there can still be situations where certain devices don’t work properly with specific computers. To know which devices will work with your computer in advance, you can check the technical specifications and compatibility lists provided by the device manufacturer. These lists usually indicate whether a particular device is officially supported by your computer model and the USB4 standard it adheres to. Additionally, it’s a good idea to refer to other users’ reviews and experiences, such as those on forums, social media platforms, or product review websites. This way, you can get an idea of whether there have been any reported issues with that device when used with similar computers.
Regarding Driver Problems.
Since the AMD auto-detect tool didn’t find any missing drivers and reinstalling/repairing them didn’t solve the problem, you could try manually downloading and installing the latest versions of USB4 drivers, storage controller drivers, etc. Overwrite the existing drivers to ensure their integrity and compatibility. When it comes to the USB or storage drivers and host controllers that you’re unsure about, it’s not advisable to uninstall them randomly as it might cause other issues in the system. If you do decide to uninstall them, it’s better to back up the relevant drivers first and then uninstall them one by one for troubleshooting purposes.
Regarding to the BIOS, currently , we don’t hve newer BIOS for this item model.
Hi Larry,
I ran into (likely the same problem) trying to connect the USB4/TB3 EGPU ADT-Link UT3G to BeeLink SEi12Pro i5-1240P. FYI I show you the message I send Beelink, and hopefully you have found a solution that you could share!
For some reason I cannot get the BeeLink to recognize the eGPU when directly connected to the SEi12’s front USB4/Thunderbolt port. As a result I cannot install the drivers.
As a troubleshooting step I tried to connect the beelink to a CalDigit TS3Plus thunderbolt Station. This thunderbolt dock is recognized immediately. With the eGPU connected to this thunderbolt station the eGPU is recognized, driver are installed and everything seems to work well (although it looks like only at at half speed)
But, when connecting the ADT-Link UT3G directly to the Beelinks USB 4 port (instead of via the TB3 dock) I cannot get the Beelink to recognize the E-gpu, and as a result the drivers can not be installed.
The ADT-Link UT3G (the ASM2464PD USB4 controller that is) shows up in the system tray as an removable storage device (see pic tray), but the installed videocard does not get detected when connected directy. When I approach the card (using ASM2464PD tooling) it shows the USB4 connection is in legacy mode (see pic legacy). When connecting the ADT-Link UT3G via the CalDigit TS3Plus thunderbolt Station the ASM2464PD tooling shows the USB4 connection is working in Thunderbolt3 mode (see pic TBT3), the videocard gets connected and everything works.
So clearly something goes wrong setting up the USB4 connection between BeeLink SEi12Pro i5-1240P and the ADT-Link UT3G directly that causes it to step down to USB5 legacy mode. Perhaps an updated USB4 driver could be required? I flashed the ADT-Link UT3G to the latest ASM2464PD firmware, 240703850000.
Perhaps a Jeyi driver could be a solution?
https://www.usbdev.ru/files/asmedia/jeyiasm2464usb4enclosurefw/