08-05-2018, 01:27 AM
(08-04-2018, 09:52 PM)paradise Wrote: The big thing with these ARM's is the clock tree; to get stuff at a specific frequency you may have to switch more clocks and dividers then you like and end up messing up the timing for some other components (USB, etc).
Just take a quick look at the 'Clock Tree' of the Allwinner datasheet for instance and you will understand.
Yes, the A10 datasheet v1.21 for example shows a spectacular clock tree on pp. 53–55!
I just removed the microSD card and rebooted. Voila! The filesystem on the eMMC card turned out to be already resized:
Code:
rock64@rockpro64:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 388M 464K 388M 1% /run
/dev/mmcblk1p7 57G 2.1G 53G 4% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/mmcblk1p6 112M 18K 112M 1% /boot/efi
tmpfs 388M 0 388M 0% /run/user/1000Now that I'm sure the microSD card is really not needed, I can prepare the Z5B enclosure for the SBC before continuing with the system configuration and installation of the additional packages.
Quote:Also for eMMC to go 'fast' the driver needs to calibrate the delay chain so if the driver fails to do that or doesn't do it correctly the timing will be wrong and neither the device or card will be a happy camper and most likely start yelling at you trough dmesg. :-)
How do I verify that the eMMC driver has calibrated the delay chain correctly, and if it hasn't, how do I make it do it?