mflorezm

Holy Mother of God, i found the problem.
 
I found on web blog that for eMMC as they are DDR they need a drive-strength of 40 instead of 30 like it was.
 
            mmc2-pins {
                pins = "PC5\0PC6\0PC7\0PC8\0PC9\0PC10\0PC11\0PC12\0PC13\0PC14\0PC15\0PC24";
                function = "mmc2";
                drive-strength = < 0x28 >; => equual to 40 in decimal
                bias-pull-up;
                phandle = < 0x12 >;
            };
 
So, i guess that now somebody has to update the DTB with a patch.
 
Thanks.
 
Mauricio F.

Holy Mother of God, i found the problem.
 
I found on web blog that for eMMC as they are DDR they need a drive-strength of 40 instead of 30 like it was.
 
            mmc2-pins {
                pins = "PC5\0PC6\0PC7\0PC8\0PC9\0PC10\0PC11\0PC12\0PC13\0PC14\0PC15\0PC24";
                function = "mmc2";
                drive-strength = < 0x28 >; => equual to 40 in decimal
                bias-pull-up;
                phandle = < 0x12 >;
            };
 
So, i guess that now somebody has to update the DTB with a patch.
 
Thanks.
 
Mauricio F.

Hi Martinayotte and Guidol:
 
So many thanks for you help and effort.
 
I have been deepth analizing the DTB file for BPI M2U and the board schematic from BPI at https://drive.google.com/file/d/0B4PAo2nW2KfndUZobUNSQ0YtalE/view?usp=sharing, and i'm pretty sure that the DTB file was developed to have eMMC like mmc2 and WIFI like mmc1. Nevertheless, the board boots and the kernel load eMMC like mmc1 and the WIFI like mmc2, (i don't know why).
 
I rewrite the bus width to 4 for SD (mmc0) and Wifi (mmc) and width to 8 for eMMC (mmc1) and now the board boots faster and does not crashes when i type fdisk /dev/mmcblk1 like it was before. So now, the board is working perfectly with armbian loaded from SD card, but i'm having problems to create a partition to mmcblk1.
 
As you can see on the attachd image below, the fdisk -l, list the mmcblk1 with the right size (7.3 GB), them i'm creating a new partition and writing the partition table without any issues, but once done,  the new partition never gets to the disk, and fdisk -l shows the disk like if was before. Of course, whithout a partition i can not format the eMMC and can not use nand-sata-install.
 
This only happens with armbian, because with bananapi images there was no issue to create the partition and save it to the disk like mmcblk1p1. 
 
Even worse, if the eMMC disk has been partitioned and it is not formatted again, i really don't know why armbian (kernel) can not see that partition that was done with BPI images if it is Ext4.
 
Regards,
 
Mauricio F.
 
 
 
 

Dear TangerineToupée:
 
I wrote a device tree user custom overlay to enable gpio-poweroff function on pin PA13 (hwd Pin8), see atatched file. The custom overlay was tested on orange Pi plus 2e, but it must work on all allwinner H3 based boards running mainline kernel 4.1x
 
I’m using armbian distro nigthly (kernel 4.14) as it won’t work on legacy kernel 3.x, so, I applied the custom overlay following the instructions on this link: https://docs.armbian.com/Hardware_Allwinner_overlays/#using-custom-overlays
 
The only problem is that the user cannot use the uart3 at the same time (hwd pins 6 and 8), but that is not a problem because H3 has 2 more uarts on the 40 pins headers that can be activated at any time.
 
regards,
 
MFM
gpio-poweroff.dts