08-08-2018, 03:01 AM
Looks like you have tried most things. I presume you got the card & USB adapter from ameridroid?
Your note 2: yup, my official Pine64 ForeSee card also shows as HS200 in dmesg, dont panic.
I see the no 1 thing you tried was dd from the running SDcard - if you did that the same way I did here
then I worry as much as you about the card. (IIRC there have been mutterings, possibly on IRC, about timing issues with some USB adapters which has caused grief? So avoiding using the adapter would be my strategy.)
A long shot - make sure the 2 pins next to the eMMC card and SPI do NOT have a jumper on - this would stop the boot from eMMC. (But I think would also stop the eMMC being recognised at all even after boot so doubt it.)
Your note 2: yup, my official Pine64 ForeSee card also shows as HS200 in dmesg, dont panic.
I see the no 1 thing you tried was dd from the running SDcard - if you did that the same way I did here
then I worry as much as you about the card. (IIRC there have been mutterings, possibly on IRC, about timing issues with some USB adapters which has caused grief? So avoiding using the adapter would be my strategy.)
A long shot - make sure the 2 pins next to the eMMC card and SPI do NOT have a jumper on - this would stop the boot from eMMC. (But I think would also stop the eMMC being recognised at all even after boot so doubt it.)
- PinePhone BraveHeart now v1.2b 3/32Gb daily driver, Tow-boot with pmOS/SXMO on eMMC
- PinePhone pmOS Community Edition 2/16Gb driving my picture frame, Tow-boot with pmOS/SXMO on eMMC
- PinePhone Pro Explorer Edition, Tow-boot on SPI, Arch/SXMO on eMMC
- ROCKPro64 v2.1 2GB, 16Gb eMMC retired in favour of a fruity upgrade
