__Dirk__

Members
  • Content Count

    11
  • Joined

  • Last visited

  1. Dear all, Finally managed to get my Pine64 H64 model-B to boot from the Foresee 32GB eMMC module after applying the next patch that adds HS200 and HS400 support to the device tree. --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-03-30 11:24:41.176470382 +0200 +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-03-30 11:24:41.176470382 +0200 @@ -127,8 +127,10 @@ pinctrl-0 = <&mmc2_pins>; vmmc-supply = <&reg_vcc3v3>; vqmmc-supply = <&reg_vcc1v8>; - non-removable; cap-mmc-hw-reset; + mmc-hs200-1_8v; + mmc-hs400-1_8v; + mmc-hs400-enhanced-strobe; status = "okay"; }; Don know how this patch will impact other brand/type eMMC modules... but for me this now works!!!!! @martinayotte, I guess your remark pushed me in the correct way :-D Regards, __Dirk__
  2. Igor, Thank you for your reply. I did not mean to insult anybody by stating 'Armbian dev's do not seem to care for the few boards that do not work out of the box either.' but it's a fact and an understandable one as you already noted .. budget, time , etc.. Another fact is that there seems to be a bug in the Armbian build for certain eMMC modules... the hardware (Pine64 H64-B and eMMC I have) are verified to be working... it's running on AOSC without any problems. I am happy to put time in investigating why.. (although my knowledge about SBC's in not by far as extended as your's)... From the thread all I got from my questions is.. it works for me ... that is not helpful .. and I understand that if you don't have the board you can't test anything.. even if you DO have the board.. if you can't reproduce the problem, it's difficult to help. But you do have the knowledge to give me a hint on where to start, it's somewhere in the booting process.. so is it u-boot not setting up the environment correctly, or is it the kernel , or the board config files? ... or.. .? I think I posted all the logs (Console output, dmesg) to give me some hint on where to start looking... older kernel, older u-boot ... kernel patch .. any other hints.. That's what I was looking for.. a hint to continue.. not asking anybody to solve my problem.. To end this reply... A big thank you for developing Armbian and sharing it with the community! Kind regards, __Dirk__
  3. JK, Thanks for sharing your findings! :-) I was looking into compiling Armbian with an older version of u-boot (same as the AOSC) but the extended compile options for armbian do not support this... as far as I can see.. Armbian dev's do not seem to care for the few boards that do not work out of the box either. So for now I chucked the Pine aside and switched to a Raspberry 4.. just costs me to much time to get all things I want running on the H64 B Regards, __Dirk__
  4. Update: Out of curiosity I downloaded the "AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180216]" for my Pine64 H64 and wrote the image to the eMMC module using Balena etcher... It's running.. without any issues...... __Dirk__
  5. Gents, Giving it a 2nd, 3rd, 4th .... try... dmesg show trouble with reading the eMMC module (mmcblk2) on startup. When the system is booted there is no trace of the mmcblk2 block device and running "fdisk -l " just never returns.. whereas it does when the eMMC is not installed. Edit: The dmesg output is from the EMMC module installed and formatted as ext4 without any further content. SBC booting from SD. The eMMC does work from the USB2eMMC converter... so the question is.. is the board broken or incompatible with the eMMC module ? I can ask the seller for support.. but I am not expecting to much from them.. @NicoD , Would it be an option to send my board and eMMC module to you so you can filter out the culprit with your "know to be working" hardware ? [ 3.320856] libphy: stmmac: probed [ 3.476407] mmc2: new DDR MMC card at address 0001 [ 3.477631] mmcblk2: mmc2:0001 NCard 28.9 GiB [ 3.478413] mmcblk2boot0: mmc2:0001 NCard partition 1 4.00 MiB [ 3.479158] mmcblk2boot1: mmc2:0001 NCard partition 2 4.00 MiB [ 3.480389] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.480690] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.480957] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.481223] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.481488] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.509232] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 3.596826] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.596887] blk_update_request: I/O error, dev mmcblk2, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 3.596897] Buffer I/O error on dev mmcblk2, logical block 0, async page read [ 3.597218] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.597491] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.597758] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598024] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598291] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598559] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598598] blk_update_request: I/O error, dev mmcblk2, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 3.598604] Buffer I/O error on dev mmcblk2, logical block 0, async page read [ 3.598623] mmcblk2: unable to read partition table Regards and thank you in advance, __dirk__ Netherlands
  6. Btw.. the ext4 or FAT32 formatted eMMC should show up in /dev/disk/by-uuid ..when the board fully booted from SD card... right? Dirk
  7. Martin, I gave your image a try on the eMMC module.. unfortunately.. same behavior.. it hangs after: Begin: Running /script/local-block .. done.. I guess I have to go to the reseller and verify the working of either the eMMC module or the board.. :-( Thanks for your effort though! Regards and happy holidays! Dirk
  8. Martin, Sounds like an idea. I'll give it a try.. thnx! :-D Btw.. probably not related.. but on the site of Pine64.. there is no 32GB related eMMC product.. only the 16GB and 64GB...coincidence? Since I have the 32GB.. https://store.pine64.org/?product=pine-h64-model-b-3gb-single-board-computer Regards, Dirk
  9. Gents, Thank you for your reply. I have a pine_H64_MODEL_B revision board. Production date? 2018-12-12
  10. Hi all, I hope someone can help me with an annoying but not pressing eMMC boot problem. Recently I bought myself a Pin64 H64 3GB SBC and an 32GB eMMC module (actually ordered a 16GB but got a 32GB :-) ) I have a Waveshare 7" TFT touchscreen attached. SBC and Screen are powered either a 5V/3A PSU or a batterypack. Now the board boots fine and fast! from a Samsung EVO sd card .. no problems there, but I cannot get the board to boot from the eMMC module. What I have done so far: 1) Flash an Armbian Buster image to the eMMC (using a USB_eMMC converter) with Etcher on Linux Mint... Boot the board from eMMC WITHOUT sd card installed. The system hangs when the kernel is started.. see attached picture and u-boot output. 2) Wipe the whole eMMC clean, format as ext4. Install it on the board, insert sd card .. boot the board.. OK.. try 'nand-sata-install' from cli or armbian-config->system->install ... both methods just hang instantly. Apart from these boot attempts I tried to access the (ext4 formatted) eMMC module after bootup from sd. But I do not see the device in the 'mount' output or /dev/disk/by-uuid listing. Is there anything else I can verify/try ? The eMMC module 'seems' to be functioning fine in the USB_eMMC converter ? Best regards and a big thank you to the dev team for Armbian.. it's running very swiftly ! Well worth my (first) donation :-) Dirk, Netherlands Armbian_boot_eMMC.txt