Any news about the new pcb board ?

[ghost]

Hi,

We dont have any news about new pcb board. Deskpi team doesnt answer to mail too.

i need also another USB3 rear adaptater

Can you make an answer for that

thx

[jamsoft]

I've just discovered that you can't plug a standard ribbon cable onto the GPIO breakout on the DeskPi daughterboard ... despite there even being a cut out on the rear acrylic panel ...

There doesn't seem to be enough clearance between the first row of pins and the PCB.

Has anyone managed too?

[jamsoft]

Took off the rear panel, managed to get it squeezed on, did that a few times, replaced the panel and it now seems a little happier.

Maybe revisit this bit of the design as the tolerances are really, really tight.

[leicray]

同样，前端USB端口由于某些原因可能会停止工作。

前面的USB端口的行为肯定很奇怪。对我来说，如果我从SSD引导，它们可以正常工作，但是，如果我从microSD卡引导，它们将无法工作。顺便说一句，我正在运行Raspberry Pi OS 5.10。

did you add : dtoverlay=dwc,dr_mode=host to config.txt file on you MicroSD card ?

I believe that this question relates to one of my posts. It's hard to say for certain as I have absolutely no knowledge of Chinese. Could we please keep the postings in English?

The answer to the question, is no. Normally I boot from the SSD.

[haan2787]

yoyojacky thanks for your reaction i bought 1 deskpi-pro from digi-key i askt them if they no about the not working pcb (hdmi-usb-ssd) they told to contact you deskpi i want to know if i olso getting the replacement pcb board (new board) now its trash because i can not use it and i was waiting from october2020 for this case now 11-5-2021 i have trash i realy hope you can help me

[yoyojacky]

，

OK, could you please tell me your order number and i will follow up your case.

DP1747

Your order on the PayPal interface shows that there is no replacement button after it is completed. The platform has changed on 4.21. The refund has been refunded a long time ago. Please check the following PayPal account information，

[yoyojacky]

I've just discovered that you can't plug a standard ribbon cable onto the GPIO breakout on the DeskPi daughterboard ... despite there even being a cut out on the rear acrylic panel ...

There doesn't seem to be enough clearance between the first row of pins and the PCB.

Has anyone managed too?

Can you provide photos of the installation? The GPIO cable should be passed through the gap of the USB interface

[yoyojacky]

Took off the rear panel, managed to get it squeezed on, did that a few times, replaced the panel and it now seems a little happier.

Maybe revisit this bit of the design as the tolerances are really, really tight.

Are you saying that the gap between the acrylic shell and the aluminum alloy shell is too small?

[yoyojacky]

please

That's just your post which i quote here, I answer you question that you said the front usb port work well when you use SSD booting up raspberry pi but out of working once you use MicroSD card booting up, it caused by you just did not add : dtoverlay=dwc,dr_mode=host to config.txt file on you MicroSD card ?

[yoyojacky]

yoyojacky thanks for your reaction i bought 1 deskpi-pro from digi-key i askt them if they no about the not working pcb (hdmi-usb-ssd) they told to contact you deskpi i want to know if i olso getting the replacement pcb board (new board) now its trash because i can not use it and i was waiting from october2020 for this case now 11-5-2021 i have trash i realy hope you can help me

OK, could you please send your order number and the issue of your board to sale@deskpi.com and cc to jacky.li@52pi.com

[Mister-42]

，

OK, could you please tell me your order number and i will follow up your case.

DP1747

Your order on the PayPal interface shows that there is no replacement button after it is completed. The platform has changed on 4.21. The refund has been refunded a long time ago. Please check the following PayPal account information，

As I have tried to explain multiple times: this is not the case! My best guess is that, because the cancellation has been done after 6 months of payment, a normal refund is not possible from Paypal. No money have been returned. You can check the Paypal account to verify my claim!

Edit: here is a current screenshot. Status is "COMPLETED", not "REFUNDED"

[jamsoft]

Took off the rear panel, managed to get it squeezed on, did that a few times, replaced the panel and it now seems a little happier. Maybe revisit this bit of the design as the tolerances are really, really tight.

Are you saying that the gap between the acrylic shell and the aluminum alloy shell is too small?

No, the row of pins nearest the PCB have an incredibly tight tolerance making it hard to plug in a standard ribbon cable.

It's nothing to do with the alu case or acrylic panels.

[bpicon]

some chip with :174c：1153 does not support UASP and TRIM but supports USB booting well. chip with 174c：55aa supports UASP and TRIM and supports USB booting but need update firmware, we are going to pack a software pack for all of you so that you can upgrade the firmware by yourself and enable TRIM function.

@yoyojacky , From your comment I must understand that new boards are being shipped with 174c: 55aa and for these a firmware update is going to be preparing? I have received 174c: 1153 (not 1153E), uasp and trim support is not available, the system directly enables the usb-storage driver. However, the manufacturer includes within the chip specifications the uasp support (https://www.asmedia.com.tw/product/995Yq54sX2YI1th2/d1Eyq85QN8GhBwRC) Can you tell me if the firmware update you propose will enable these features in my case, changing the product_id to 174c: 55aa? Or that new boards are provided with different types of chip and I have gotten one that only allows usb booting?

Thanks.

[haan2787]

yoyojacky I did sent you a email but sale@deskpi.com gives a error back i hope that the mail is in youre emailbox thanks

[leicray]

I answer you question that you said the front usb port work well when you use SSD booting up raspberry pi but out of working once you use MicroSD card booting up, it caused by you just did not add : dtoverlay=dwc,dr_mode=host to config.txt file on you MicroSD card ?

I did not add the dtoverlay=dwc,dr_mode=host to the config.txt file on the microSD card. I think that the need to modify the file corresponds to the fifth Fault on the FAQs card in the box: "Fault: Abnormal USB interface on the front panel." This issue is not explained clearly enough as the problem and cure only relates to the situation where the Pi has been booted from the microSD card rather than from the SSD.

Clearer instructions would help too. Above, you have said that it is necessary to adddtoverlay=dwc,dr_mode=host to the config.txt file, but the instruction card says to add dtoverlay=dwc, dr_mode=host with a space after the comma. I think that including the space is incorrect.

[haan2787]

yoyojacky i saw youre website and many intresting thing on it but can you transform it in englisch so we al understand it (mabe a idee) I hope everything is oke because we do not here from you for 4 days please give us a word back thanks

[leicray]

I posted my case back to Pi Hut (UK vendor) on Friday morning and it was delivered this morning. My refund, via PayPal, was sorted out within a couple of hours. Fantastic service!

[bpicon]

It seems that the firmware update is already official (the date April 20 must be an error, it will be May 20) If someone has tried updating, they could share their impressions.

[Mister-42]

Edit: here is a current screenshot. Status is "COMPLETED", not "REFUNDED"

@yoyojacky It is really ridiculous there is still no answer. Either refund me immediately, or send me the full package of a case with a working board (UASP / TRIM support included!), a32GB SD-card and bracket, as promised. I only cancelled since the first board was faulty and the second had no UASP / TRIM support. Since that has now changed, I am still interested in the product.

[leicray]

It seems that the firmware update is already official (the date April 20 must be an error, it will be May 20) If someone has tried updating, they could share their impressions.

Although its encouraging to see that a firmware update for UASP and TRIM is now available, I'm not convinced that it will necessarily cure the problem. My Pi is now back in its original simple case with the SSD connected via a StarTech adapter cable that supports both UASP and TRIM. It has been up for nearly eight days without problems.

If I was to substitute the SSD adapter with another that did not support UASP and TRIM, I doubt that it would cause the Pi to crash or kernel panic. Apart from anything else, the crashes/panics were happening when the device was idling. There must be something else going on in addition.

[csmale]

I received a replacement board on 20 April but it has the 174c:1153 chip. As I understand it I cannot use the firmware update because that is for the 174c:55aa hardware on the V3 board. Do I need a V3 board? How can I get one?

[bpicon]

I received a replacement board on 20 April but it has the 174c:1153 chip. As I understand it I cannot use the firmware update because that is for the 174c:55aa hardware on the V3 board. Do I need a V3 board? How can I get one?

I received the board with the same chip (174c: 1153) and I have been able to update the firmware without problems. The original version that it showed, before updating was 130531210000. The update changes the product-id of the chip to 55aa and it is now detected by the kernel as compatible with the uas driver. Later I activated TRIM without problems and the performance data reported by agnostics has improved substantially.

pi@raspberrypi:~ $ lsusb Bus 003 Device 003: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub ...

pi@raspberrypi:~ $ lsusb -t /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M | Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M | Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=ch341, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M ...

Raspberry Pi Diagnostics - version (unknown) Sun May 23 18:08:50 2021

Test : SD Card Speed Test Run 1 prepare-file;0;0;322837;630 seq-write;0;0;321254;627 rand-4k-write;0;0;48473;12118 rand-4k-read;50257;12564;0;0 Sequential write speed 321254 KB/sec (target 10000) - PASS Random write speed 12118 IOPS (target 500) - PASS Random read speed 12564 IOPS (target 1500) - PASS Test PASS

Before update firmware:

After update:

[csmale]

Thanks @bpicon - I went ahead and did the update. However I can no longer boot from the SSD - it does the pre-boot, then hangs for a couple of minutes and eventually dumps me into the recovery shell (initramfs). I can't "see" or access /dev/sda* and the white LED is on continuously (although it does flash during the earlier stages).

If I boot from an SD card I can mount the SSD without problems - it is detected as :55aa and is using uas.

So it looks like the hardware is OK but there is something in the boot sequence screwing it up. Does anyone have any ideas?

I am running Ubuntu 20.04 by the way.

[G6EJD]

In the boot config you will find that it is referencing the wrong device now, can’t find it… Edit that and normal service will be resumed, use lsusb to find the new device ID

[csmale]

In the boot config you will find that it is referencing the wrong device now, can’t find it… Edit that and normal service will be resumed, use lsusb to find the new device ID

Thanks for the suggestion... I have looked in the boot dir through all the config.txt, cmdline.txt etc files but I can't see any reference to either the old or the new device. Can you explain a bit more about what you mean?

[G6EJD]

What does this report as the boot device: lsblk /dev/sda do you see the SSD interface?

Run the command “gksu gedit” (or use nano or vi). Edit the file /etc/fstab. Change the UUID or device entry with the mount point / (the root partition) to your new drive. ... Edit the file /boot/grub/menu. lst.

[mjeshurun]

Hello friends, Has anyone received a completely new V3 Deskpi Pro order (not a pcb board replacement for an old order)? Are new V3 orders preconfigured to use USAP and TRIM out of the box, or users still need to manually run the process described on the Deskpi website? https://deskpi.com/blogs/news/about-uasp-trim Also, on V3 which pcb board is used for the SSD, ASM1153 SATA 3Gb, or ASM1153E SATA 6Gb? Does all other features work as they should (Front USB ports, Safe Shutdown with the button, WiFi/Bluetooth signal...)?

[haan2787]

no iam still waiting

[TeoTN]

I've received the new board but it's pretty much unusable, it keeps randomly crashing - I wasn't able to find any meaningful piece of log but it seems it ends up in rebooting spontaneously and freezes, probably same issue as mentioned earlier in this thread. It seems like if SSD was disconnecting from time to time. The previous board didn't have that particular problem. While DeskPi Pro looks nice, I regret buying it instead of Argon One, that was quite a waste of money...

[sjb5]

I received the new board. Everything appears to be working as intended except for booting from SSD. I performed the firmware update. When I run lsusb, I get the following: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge. My issue is similar to the issue described by csmale. I cannot access the SSD when it is connected to the DeskPi Pro board. The white LED turns on, but is on continuously. It shows no activity. If I connect the SSD by way of a Startech SATA to USB cable, the system boots without a problem. I have tried various old and new SSDs from Crucial, WD, Samsung and even Intel with the same result. I have tried the current versions of both Raspbian and Ubuntu MATE. The results are the same. Unless I am missing something, I believe my new board is defective.

[csmale]

I received the new board. Everything appears to be working as intended except for booting from SSD. I performed the firmware update. When I run lsusb, I get the following: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge. My issue is similar to the issue described by csmale. I cannot access the SSD when it is connected to the DeskPi Pro board. The white LED turns on, but is on continuously. It shows no activity. If I connect the SSD by way of a Startech SATA to USB cable, the system boots without a problem. I have tried various old and new SSDs from Crucial, WD, Samsung and even Intel with the same result. I have tried the current versions of both Raspbian and Ubuntu MATE. The results are the same. Unless I am missing something, I believe my new board is defective.

I got it going eventually, but it took a lot of hassle. I even managed to screw up my boot partition with all the desperate attempts to get it going. In the end I created a clean install of Ubuntu 20.04 LTS on an SD card, booted from that with the SSD connected, mounted the SSD partitions, and copied the boot partition and the firmware from the card to the SSD. After checking the config.txt was going to find the root partition on the SSD I could get it to start. I also remember starting from Raspbian and using raspi-config to set the boot order to start from the SD if present, otherwise SSD. Now it runs OK - SSD performance is up to 700MB/sec - but it has spontaneously restarted once and the WiFi is not working properly. I have read there can be some RF interference between the USB3.0/SSD circuitry and the WiFi.

[sjb5]

csmale, thanks for the quick response. My problem is that when I boot from the SD card with the SSD connected, I am unable to mount the SSD partitions. When I run gparted, the SD card is the only device listed. When I run fdisk -l, the SSD is not listed. When I run lsblk, the SD card is listed, but not the SSD.

[csmale]

Aah, sorry, I misread a bit. When I had that problem in the beginning, it turned out that the four power pins from the main board had missed their correct holes in the daughter board. But you are probably not as clumsy as me...

It's definitely possible that your board is dead. I thought that several times during the most stressful 48 hours of my recent life.... And it still ended up being a software/config problem in my case.

[yoyojacky]

取下后面板，设法将其挤压，做了几次，更换了面板，现在看起来更快乐了。 也许重新审视设计的这一点，因为公差真的非常非常紧。

你是说亚克力外壳和铝合金外壳的间隙太小了？

不，最靠近 PCB 的那排针脚公差非常小，因此很难插入标准的带状电缆。

与铝壳或亚克力板无关。

I received the new board. Everything appears to be working as intended except for booting from SSD. I performed the firmware update. When I run lsusb, I get the following: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge. My issue is similar to the issue described by csmale. I cannot access the SSD when it is connected to the DeskPi Pro board. The white LED turns on, but is on continuously. It shows no activity. If I connect the SSD by way of a Startech SATA to USB cable, the system boots without a problem. I have tried various old and new SSDs from Crucial, WD, Samsung and even Intel with the same result. I have tried the current versions of both Raspbian and Ubuntu MATE. The results are the same. Unless I am missing something, I believe my new board is defective.

Could you describe what steps did you make ? to boot from SSD ?

[yoyojacky]

I've received the new board but it's pretty much unusable, it keeps randomly crashing - I wasn't able to find any meaningful piece of log but it seems it ends up in rebooting spontaneously and freezes, probably same issue as mentioned earlier in this thread. It seems like if SSD was disconnecting from time to time. The previous board didn't have that particular problem. While DeskPi Pro looks nice, I regret buying it instead of Argon One, that was quite a waste of money...

what you mean random crashing is ? Does the SSD offline randomly?

[yoyojacky]

csmale, thanks for the quick response. My problem is that when I boot from the SD card with the SSD connected, I am unable to mount the SSD partitions. When I run gparted, the SD card is the only device listed. When I run fdisk -l, the SSD is not listed. When I run lsblk, the SD card is listed, but not the SSD.

please try to add sudo before command and try again...

[yoyojacky]

Aah, sorry, I misread a bit. When I had that problem in the beginning, it turned out that the four power pins from the main board had missed their correct holes in the daughter board. But you are probably not as clumsy as me...

It's definitely possible that your board is dead. I thought that several times during the most stressful 48 hours of my recent life.... And it still ended up being a software/config problem in my case.

Dose your deskpi work properly after correcting installation?

[yoyojacky]

Took off the rear panel, managed to get it squeezed on, did that a few times, replaced the panel and it now seems a little happier. Maybe revisit this bit of the design as the tolerances are really, really tight.

Are you saying that the gap between the acrylic shell and the aluminum alloy shell is too small?

No, the row of pins nearest the PCB have an incredibly tight tolerance making it hard to plug in a standard ribbon cable.

It's nothing to do with the alu case or acrylic panels.

Edit: here is a current screenshot. Status is "COMPLETED", not "REFUNDED"

@yoyojacky It is really ridiculous there is still no answer. Either refund me immediately, or send me the full package of a case with a working board (UASP / TRIM support included!), a32GB SD-card and bracket, as promised. I only cancelled since the first board was faulty and the second had no UASP / TRIM support. Since that has now changed, I am still interested in the product.

Please check your paypal account, we have already refund for a long time....

[Mister-42]

Yes you did. But that was 6 days AFTER the message you quote. So at the time of my writing, that was absolutely correct.