06-15-2018, 08:26 AM
(05-08-2018, 02:44 PM)ramprasad Wrote:(05-01-2018, 04:16 AM)pfeerick Wrote:(04-30-2018, 09:46 PM)t4_4t Wrote: To connect the serial console (TX / RX) and "ROCK64", insert the Device:"74HC4050".Nice one. Like the use of a buffer instead of a diode!
If I have issues which I suspect are related to the usb-serial and I see that dimly lit power light I just unplug the usb serial for a second or two to make sure the rock64 has fully powered down / reset. Can't say I remember any issues I can directly attribute to the usb-serial... but doesn't mean it hasn't happened (or won't!)!
ramprasad Wrote:Is there any way to enable POST (power on self test) before starting the reboot (may PSCI Power Domain Map related to POST).
When I logged in as the root user - full login, not via su - on 0.6.25 xenial-containers, it rebooted just fine (other than a kernel autotune related panic with auto-reboot)... did it two or three more times, and also as a sudo user, and couldn't get anything different to happen. I have seen that "INFO: PSCI Power Domain Map:" info before, I'm not sure what the difference was though. Are you on debian stretch? As far as any POST stuff, you'd probably have to implement that yourself, as that is something that the ARM architecture doesn't have.
Code:[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[1061865.715205] reboot: Restarting system
DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Yes, I am using Debian stretch. I also suspected that it could be serial cable connected. But when I connected the WiFi dongle, log-in with SSH as rock64 user and then to the root. Still I could reproduce this issue.
I wonder, why the above log doesn't show the "INFO: PSCI Power Domain Map:". Does it change between different OS (Debian/Xaniel etc..).?
Hi pfeerick,
We have contacted the Longsys (FORSEE eMMC support company) regarding this issue and provided the FORSEE eMMC model (NCEMAD6B-16G - from Pine64 website). The LONGSYS responded that this model was End of Life and it may be signal compatibility issue and was asked to change the MODE to SDR50. Can you please somebody provide some pointers how to change the mode. I observed the mmc command in uboot to set several parameters, but not the MODE. Also checked the documentation (/Documentation/devicetree/bindings/mmc/mmc.txt) provided a parameter (sd-uhs-sdr50) in .dtsi file. But I am not sure about correct procedure. Can somebody provide some info about how to change and achieve this.
And one more information is that LONGSYS recommended another model of eMMC recommended (NCEMAD9D-16G) and I am not sure about that we need to change the MODE for this model too. I requested the same info with LONGSYS, I will share more details once I received the response.
Thanks,
Ramprasad